The out list
So the next request has somewhere honest to go.
What you leave with
A block is finished when you can operate the result and explain the edge.
If it is not listed, ask before you confirm the scope.
Handover is part of the block, not a favour.
A website leaves you a page map, the pages, titles and headings, an analytics hookup, and a note of what a non-developer can change. It does not leave you a ranking report. Care, if you bought it, is a separate month.
Software leaves you the agreed release, access, and a note of what the next block would be if you want one. Discovery leaves you the boundary and the plan, which is allowed to be the end of the relationship. An AI pilot leaves you the loop, the failure cases, and a continue, narrow, or stop recommendation. Prompts and access are part of that handover.
Automation and integrations leave you the path, the exception route, and a runbook for the day a password or a column changes. Document processing leaves you the field list and the review queue. Support and care leave you a short note of what changed. They do not leave you a new product.
You keep the materials you sent. Deliverables we make under a paid scope are yours once the agreed fees for that scope are paid, except for tools and methods we already used across clients. That exception is also in the terms. The scope should not contradict it by accident.
Ask for these if they are missing from the scope
01 02 The runbook
So a changed login is not a crisis.
03 The review owner
So a draft has a name attached.
04 The rate and the cadence
Hourly, or the hour times 30, written in the email.