Why You Write Change, Delay, and Termination First

Looking at a draft, someone said “just this one more slot.” The shop nodded. Nobody left a line. Two months later that slot was original scope, and the slipped days became a feeling about whose delay it was. A change that had looked fine became a fight about fairness.

The last article split the right from the source file. The empty box that remains is what happens when the work veers. Keeping a record of a schedule change, and putting a change–delay–stop procedure in the contract, are different layers. A record guards the past. A procedure makes the next record.

The moment a fine-looking change becomes a fight

A small add looks like that day’s courtesy. Three courtesies become scope. Refuse a courtesy that became scope, and it is an attitude. Accept it, and the date slips. People who hire well do not weigh the size of the courtesy. If the courtesy changes scope, calendar, or fee, they write those three boxes again.

A change you do not write again is later read as having always been there. Read as always there, the slipped day is the shop’s fault. If the shop kept a refusal, the refusal is uncooperative. With no procedure, character is what remains. Judging by character looks like fairness. Character that looks like fairness is the other side’s story next week.

This article does not treat every client as a prime contractor under a special statute. Which law applies depends on the size of the business and the kind of deal. What belongs here is not the name of a law. It is the order you write before anyone is angry.

What you write under change

Who may ask comes first. If anyone in the chat may ask, change opens in every meeting. The decision-maker named earlier needs a name here too. What changes comes next. One screen, a date, a fee. Do not fold those three into the one word change.

Leave off when it applies, and nobody knows which scope a draft in progress follows. People who hire well write the moment it applies. Only work after that writing is the new scope. They do not pull an earlier draft under the new scope. A back-date turns memory into scope.

Whether a change may be refused is also one line. A change that cannot be refused means a request is already scope. If a refusal exists, write the calendar and the deliverable that remain after it. Do not leave the refusal as a mood.

What you write under delay

Delay is not the feeling that a date moved. It is who notifies whom after how many days. Do not put a delay from late client material and a delay from late shop work in one pocket. In one pocket, every slip becomes the other side’s excuse.

People who hire well write the notice deadline. An apology after the slip is not a procedure. The line before the slip is the procedure. Attach to that line what moves. Only the draft, the acceptance day, the last-payment day. A last payment that does not follow splits the event you bound earlier.

If an outside dependency — an app review, a domain, a photo shoot — showed on the calendar, leave one contract line for whose delay it is when that dependency is late. If it lives only on the calendar, the dependency becomes your emergency again. An emergency is not a procedure.

What you write under a stop

If the stop day is a mood, the word stop sounds like a threat. Write the condition now, and the word becomes a procedure. The condition does not have to be long. Not how many messages — only what, after how many days.

Leave the settlement of work done by the stop day empty, and the stop is a fight about loss. Write that day’s deliverable and that day’s fee the same way. This article writes no amounts. What it writes is whether settlement looks at the same list as acceptance. With no list, settlement is a gut feel.

Leave off where files, accounts, and mid-drafts go, and the stop is a folder war. People who hire well write the stop-day handoff on the same tick mark as the acceptance sentence. If only part of the source exists, split what exists from what does not. Asking for the missing piece later is a dependency that survives the stop.

When the three boxes are empty, fairness stands in

The table is not a device for growing clauses. It is a device for choosing now the sentence you will later want to call fair. Fairness after anger feels different on each side. A procedure from before anger points at the same sheet.

Cover the three boxes with one line — mutual agreement — and agreement becomes a voice. People who hire well leave a place for agreement, and they write the door where agreement starts. Agreement with no door is the vague line from the first article. Not flexibility. A future argument.

Between courtesy and procedure

A sentence that refuses a courtesy sounds cold. So many teams leave the first add unwritten. A team that did not write the first add has no sentence for refusing the third. People who hire well do not make the first add cold. They leave it short. “This slot is a new line. The calendar moves one day.” That shortness makes the next refusal a procedure, not a character.

Some months the shop asks for the change first — late material, a block outside. The same three boxes apply. Who, what, from when. A contract where only the client writes change is a half. People who hire well open the same door for a shop request. A door on one side only lets the other side’s change stack as courtesy again.

Some teams replace a delay notice with an apology. An apology repairs a relationship. It does not repair a date. People who hire well put apology and notice in the same window, and they fill the notice box first. An apology with no “what slides, by how many days” is the vague line from the first article. The mood is warm and the event is empty.

If the afternoon you write a stop feels awkward, do not dodge the awkwardness. A condition written on an awkward afternoon stands in for fairness on an angry afternoon. A contract that dodged the awkwardness tries character on the stop day. Trying character makes the next hire start from that memory. A stop that followed procedure becomes material for the next page.

The procedure you write now

“Just this one more slot,” left for a month, becomes three slots. Nobody can point at where the three began. A start nobody can point at becomes original scope. People who hire well leave a line at the first slot. Without that line, fairness is a contest of memory. The side that wins a memory contest is usually the louder voice.

Write where a notice lives. If any chat is a notice, the notice cannot be found later. Putting the date and the sliding box in a named window is the procedure. The earlier article asked you to record a schedule change for this reason. A habit of recording, with no contract line for where it lives, is a private diary.

Operations can survive a stop. Whose account holds the domain, whose mail holds the ads. If you have a stop condition and no direction for the accounts, a stop does not close a door. It hides the key. People who hire well attach the direction of the key to the stop line. A stop with no direction cannot start the next hire.

Fill this table once before you sign. If you cannot fill it, you have not yet imagined the veer. An unimagined veer is handed to that day’s character. The procedure you write now stands in for fairness later.