How Far Should You Check Before You Accept the Work?
Relief when the screen comes on is not completion. Acceptance is closing the boxes the contract named. A pretty demo dissolves the list.
Friday, four o’clock. A staging URL lands in the chat. The first screen hits the projector. The colors are close. The type is readable. Someone says it looks done. Final payment is next week. The contract treated inspection, acceptance, and that payment as one event. The moment the screen lights up, the sentence becomes a feeling.
A person who hires well already splits praise from acceptance here. Praise is allowed. Acceptance is closing a list.
The last chapter filled the contract’s boxes. Countable deliverables. A revision range. Acceptance and final payment in the same event. Source files kept apart from a rental of rights. A procedure for change and delay. That paper is not for a drawer. The day the files arrive, those boxes become the inspection list. This is not where the series of choosing and signing ends. It is where receiving begins.
The afternoon the screen comes on
When the screen comes on, the room exhales. The long week sounds finished. Coffee appears. Someone wants the next agenda. The air in that afternoon holds completion. It is relief, not completion.
A person who hires well unfolds the paper without breaking the air. Deliverable lines from the contract. Revisions still open. Accounts and originals still to move. The room watches the screen. That person watches the boxes that are still open.
Feeling is fast. A list is slow. The fast side pushes the payment date forward. The slow side is why you later hunt for files. This is not an argument for delay. Relief must not sign the line. Relief was needed. A room that survived a long week needs it to open the next one. Write a date in relief’s chair, and next month you buy the same screen again.
Some rooms write “no big problems” that afternoon. A demo hides the big ones. Small boxes stop operations. Booking mail that only hits a test inbox. An admin door on a personal address. Those boxes are not large. They grow on Monday.
Contract boxes become inspection boxes
A contract is easy to read as a dispute document. In the acceptance week it is the opposite. Those boxes are today’s close list. How many main pages. The path that actually books. What sits outside the finished rounds. The files that move before money moves.
An empty contract is fragile in this week. “Until you are satisfied” is not a list. Who is satisfied changes every day. A person who hires well does not invent a new standard in that week. They walk the boxes already written.
This chapter does not make a new standard. It rereads the written one in front of the screen. Choosing, asking, scheduling, and contracting all get used here at once. The closer energy of the series is not hurrying the last payment. It is finishing, in front of the screen, the boxes that already had names. The weight of closing is not a new sentence. It is walking a sentence you already have to the end.
The walking order is not taste. The path a customer takes, copy you will touch, a door that holds a key, files that were to move. With that order the room does not linger on the first screen. The first screen is where persuasion is strongest. Finish acceptance there, and the list remembers only that light.
A pretty demo dissolves the list
The smoother the demo, the paler the list. When the animation ends, the room claps. Behind the clap the admin login is still a personal inbox. The font sits on the studio subscription. Booking mail goes only to a test address.
Pretty is not the enemy. Pretty is a solvent. It dissolves unclosed lines until the eye skips them. After the clap, a person who hires well asks one line. Will this screen light tomorrow on our account. Will we walk the path a customer actually uses.
If the demo URL and the live URL differ, what worked in the demo is not promised in operation. Say “it looks done” without asking that difference, and you have bought a demo. A demo persuades. Acceptance transfers. One clap for both leaves only persuasion.
A room that bought a demo repeats the same praise next week. The screen is the same. The door is the same. The afternoon when praise stood in for acceptance is the cause. A person who hires well does not read that repeat as the vendor’s character first. They read the order that put clap and list in one chair.
The lines that actually close
Close lines are not taste. They are the lines the contract named. One path a customer actually walks. Copy you will edit yourselves. A screen you must log into. Originals and accounts that were to move. Spoken fixes still sitting inside the window.
When those lines close, that is acceptance. If they stay open and the screen is pretty, you have pretty unfinished work. Pay the last invoice against that, and next month you spend feeling looking for files. That is why the last chapter put acceptance and final payment in one event. Split the event, and the screen stays while the boxes empty.
You do not have to see every pixel. You do not have to close taste that was never written. How far is the question of this piece. The answer is not the size of appetite. It is the length of the list you already wrote. Looking farther into unlisted shine is not receiving. It is a draft of the next hire.
A room that does not know how far goes to two extremes. It spends five days on color, or it closes on feeling and looks at nothing. Both extremes come from having no list. A list makes a middle. The middle is not “good enough.” It is the seat where only named lines close.
Signals not to accept yet
When someone says the rest will be tidied after launch, that rest is not on the list. After launch sits outside acceptance. A person who hires well does not take that sentence as kindness. They move the leftover line into today’s box, or they peel it into the next scope.
A demo login with no name change is a visit, not a handover. Originals “to be packed later” are a picture. A license still in the studio’s name is a screen on a timer. These signals do not mean the feeling is bad. They mean a box is still open.
There is also the tired room. At the end of a long week the close wants to be quick. That fatigue folds the list. A person who hires well already put fatigue on the calendar. That is why the acceptance window is a dated box. Teams that finish acceptance in a tired afternoon buy the same screen again next month.
A payment date that rushes the list is the same signal. When a date pushes people, boxes fold. The last chapter put acceptance and final payment in one event not to make the date earlier. It was to keep money from leaving before files moved. If rush beats the list, that one event splits again.
The one page that closes
The page only needs lines closed today and lines still open. Closed lines carry a date. Open lines carry who closes them, and when. That page is acceptance. A bundle of screenshots is not. Screenshots help memory. Memory without a date becomes a fight next week.
The series starts receiving here. Why you chose, what was answered, what was scoped, what was scheduled — they gather on this page. For seven chapters to be used in one afternoon, that afternoon cannot end as a feeling. The next piece is what to open in that window, and what to leave unopened.
Acceptance is not a feeling. It is closing a list.
FAQ
Frequently asked questions
If it looks good, can we accept?
Pretty is for praise. If a named contract line is still open, you have pretty unfinished work.
Do we have to see every pixel?
No. Look as far as the list you already wrote. Unlisted taste is a draft of the next job.
If it worked in the demo, is live done?
Not if the URLs differ. Walk the path a customer actually uses.
They will tidy the rest after launch?
After launch sits outside acceptance. Move the line into today, or peel it into the next scope.
Are screenshots acceptance?
No. Acceptance is one page of closed and open lines, with dates.
Final payment is soon — shouldn’t we just take it?
A tired afternoon folds the list. That is why the window sits on the calendar.
The contract is empty. How do we accept?
Do not invent a new standard that week. Write today’s close lines on one page first.
Related updates
What to Open — and What to Ignore — in the Acceptance Window
The window is time to run the thing with your own hands. Seat demo polish in the next box. A polish complaint is often new work in costume.
Read moreBlogThe One Line That Separates an Error from a New Request
The line is chapter one’s completion sentence. Agreed and broken is an error. Never written is a request. Do not edit the sentence after the screen.
Read moreBlogA Handover Checklist for Accounts, Source Files, and Licenses
If the screen is on and the keys are not in your name, you accepted a rental. Close names, editable originals, and license scope on one table.
Read more