The layout arrives. The main screen looks polished. Development starts, and the first question is about a state that is not in the file. No rows. Save failed. Name too long. No permission. None of that is an edge case for later. Each one is a day-one decision, and each one is paid for out of your budget.

When a state is missing, the developer still has to build it, and you pay for that build twice: once in the estimate, once in the change request that follows it. You will first see that choice at review. Then you say, correctly, that it is not the layout. Now the team redraws work that a few extra frames and one realistic sample would have settled earlier.

This note is for you, the owner of the product, and for the designer you hired. It is not the marketer’s brief. It is not the access pack. It is the visual part of the handoff: the frames and notes that stop a developer from guessing, and the list you use to check the file before you let the build start.

1. What the build asks on the first day

A happy path is necessary. It is not enough. Real use leaves that path quickly. A new account has no rows yet. A request fails because one field was rejected. A page waits because another step is slow. A real company name, address, or title is longer than the short sample in the layout. A person without access still needs a clear destination.

When those states are absent, the team does not save time. The choice just moves into code, where you cannot see it. Review then turns into correction, and you feel it as a delay to your own release.

You do not need to solve backend logic. You need to know what the person sees. Empty. Failed. Waiting. Too long. Not allowed. Ask the designer for those next to the happy path on every screen that is really part of this build, and ask for a note when a screen is only a direction.

2. Placeholder text hides the break

Placeholder text hides where the interface fails. A CRM card, a cart, and a staff list break in different places. One breaks on a company name. Another breaks on a product title and currency. Another breaks on a missing phone or a full legal name.

If the frame was sized around “John Smith” and a round price, the easiest case was the only case tested. Your users will not stay in it.

Ask for one anonymised sample from the real product: a long name, a missing phone, a price in the actual currency. You do not need a database export. You need one row that puts pressure on the layout. If there is no real sample yet, say that in writing and use the longest values the fields allow.

Also ask what is final content and what is still interface chrome. A short note is enough. “This title is final. This table is an example. This illustration is not supplied.” Without that note, a developer can build a sample as final content, or leave a missing asset as a plain rectangle until review.

3. Say whether this screen already exists

Many layouts are not new pages. They change a page people already use: a report, a checkout step, a customer card, a switch between accounts. If nobody marks that, the developer has two bad options. Rebuild from the frame and drop behavior the frame never showed, or keep the running behavior and ignore parts of the frame that do not fit.

You know which of your screens already exist, so that note costs the designer one line on the frame: “This is a change to an existing report.” or “This is new.” Then list what must stay untouched: the payment step, the account separation rule, the button that creates the lead. If the layout quietly replaces those, the team is no longer discussing one screen. It is discussing a larger project without naming it.

If you have not seen the current page, ask for a screenshot before you approve the file. One screenshot of the real page is more useful than another invented first screen. You can still redesign it, but you should know what already exists and what your users would lose.

4. What this file is not

The marketer still owes one sentence about the outcome: what a person can do after this change, and how the team will know it works. That pack is what to attach before development starts. Do not hide that sentence inside the design file. A frame is not an acceptance check, and a build signed off on frames alone is a build you pay to fix.

Access is a separate pack too. If the work sits on an existing Laravel system, the agency still owes a place to test the change and a named list of risky flows. That is how an agency hands the project over. A layout does not replace that, and it does not replace your job of putting the right people in the room.

You also do not need to choose the framework, query, or queue. But if the layout suggests behavior the product cannot support this month, the designer should show what the person sees instead. A disabled control with a short note is a valid design choice. A control that looks ready and then fails in code becomes a bug at review, and a bug at review costs another round of work.

5. Review the states you asked for, not one polished screen

Agree the review path before development starts, and write it into the plan. Then review is not a debate about taste. The developer opens the empty state, the failed save, the waiting state, the long value, and the access refusal. You review those because you asked for them.

The happy path is one item on the list. It is not the whole meeting.

If a state is intentionally out of scope, write “not in this build.” Do not leave a blank. Blank space gets filled, and then you pay for a decision nobody took with you. A written exclusion can be estimated later, which is usually the point of cutting scope.

Bring the anonymised sample back during review. If the long name fits, the layout held. If it does not, you found a real miss. Keep your own team on the same list. They should see the empty account and the failed save before your users see them in production.

When to bring a developer in before the build

You can add the five states and one sample yourself, with this note and the designer. Bring in a developer when the layout sits on a product that already has active users and you are not sure which changes will conflict with the running page. That is the gap a technical director would normally cover, and it is the one you are left to cover.

That check is cheaper before build than in the last review week.

I read the layout against the current product: what the picture is allowed to change, and which states are still missing. Services cover that kind of work on an existing system, and the technical audit shows the same thing from the code side. Selected work shows the same kind of situation with the result next to the task. This note is for you and for the designer you hired: here is what to ask for before the build starts, and what to check yourself in ten minutes. If you want that check, write to me. Send the state list and say whether the screen already exists. Leave client passwords out.