The first week of a block
The first week is for the trace and the edge, not for a surprise rebuild.
Slides are already over by the time the week starts.
Confirm, then touch the real item.
On a website, the first week is the page map and the message. Visual design follows that list. If the offer is still being argued, the week is spent on the argument, not on a homepage composition that will be thrown away.
On automation or an integration, the first week follows one real item. We write what is automatic, what stops for a person, and what we will not touch. If the item cannot be followed, we stop and say the block was early. That is cheaper than a connection built on a guess.
On an AI pilot, the first week is the source, the example set, and the place the draft will wait. We do not start by picking a model brand. We start with the job and the person who sends.
On a monthly block, the first week is the queue written down and the first few items actually done, with notes. It is not a workshop. You should be able to point at something that changed before the week ends, even if the something is small.
During that week
Can the scope change?
Yes, in writing. A change that enlarges the job becomes a revision of the scope, not an informal addition.
Who do we talk to?
The note on the scope names the contact. Support months exist so that person is not a group chat.
What if we were wrong about the job?
Say so. Stopping or narrowing in the first week is cheaper than a polite overrun.