Delivery room link
A single room that shows status, file index, revision window, blockers, and buyer next action.
KK Automation Studio
Acceptance rules after handover
Acceptance rubric / revision boundary / first paid order
Acceptance should be boring, clear, and documented.
This rubric defines how a first paid order is accepted after handover: what counts as complete, what becomes a revision, what is blocked by missing inputs, and what becomes a separate add-on.
Decision table
Five possible outcomes after final handover.
| Outcome | Use when | Client note | Next action |
|---|---|---|---|
| Accepted | All agreed files are present, usable, and inside the original scope. | Your starter system is ready to use. The delivery room shows the files and next steps. | Ask for acceptance, honest review, and optional next-scope discussion. |
| Revision | An agreed item is unclear, missing, mislabeled, or needs a focused wording/structure change. | This is inside the included revision window. I will adjust the specific item listed. | Log one focused revision request and update the delivery room. |
| Blocked | Buyer input, assets, links, or access are missing and prevent a clean final delivery. | I can continue after the missing input is provided. The blocker list is below. | Pause the affected item and keep finished files available. |
| Add-on | The buyer asks for a new page, new platform, new tool, new offer, or ongoing operation. | This is useful, but it is outside the original order. I can quote it separately. | Close the original order first, then prepare a fixed add-on quote. |
| Stop | The request involves risky promises, platform bypass, payments, identity, spam, or sensitive credentials. | I cannot include that in this delivery. We can keep the safe parts only. | Escalate to user approval or decline the unsafe scope. |
Acceptance evidence
What must be present before requesting acceptance.
File index
Every file is named clearly and mapped to what the buyer should open first, second, and last.
What changed
A short summary explains the finished page structure, lead path, tracker, calendar, and handover notes.
Buyer next action
The buyer knows whether to review, accept, send one revision list, or provide missing inputs.
Revision window
The included revision limit and deadline are visible so the order does not drift into unlimited support.
Risk boundary
No guaranteed sales, traffic, rankings, approvals, investment returns, or platform bypass language appears.
Message snippets
Acceptance notes to keep the order calm.
Final handover note
Your delivery room is ready. The agreed files are listed with next steps. If everything looks good, please mark the order as accepted and leave honest feedback.
Focused revision note
Please send one clear revision list for the agreed deliverables. I will adjust the listed items inside the included revision window.
Missing input note
I can complete the remaining item after receiving the missing input below. Finished files stay available in the delivery room.
Separate scope note
This request is outside the original order. I can keep the current delivery clean and prepare a separate fixed-scope quote for the new work.