Done means operable
We do not call a project done when the homepage looks right. Done means the client can keep the system useful without guessing. That requires a checklist, not optimism.
Pre-launch blockers
These items block "live" status:
- Production access inventory — DNS, hosting, CMS, email, analytics, payments, CDN
- MFA and password ownership — client-controlled where possible
- Staging or preview path — or an explicit reason it is absent
- Backup verification — not just "backups enabled," but a restore note
- Critical path test — forms, checkout, login, or contact flow checked on production
If any of those are missing, the launch is incomplete.
Day-of handoff agenda
Keep the live handoff meeting short and concrete:
- Walk the owner through one content update
- Confirm who gets alerted when something breaks
- Review the first 30 days of maintenance tasks
- Capture open questions in the private client channel
- Point to the written guide, not tribal knowledge
The written artifacts
Minimum set:
- Owner guide for weekly tasks
- Architecture / deployment notes for the next engineer
- Support boundary (what is included vs billable)
- Known risks and deferred improvements
30-day follow-through
A good handoff includes a short stabilization window: answer operating questions, fix clear launch defects, and tighten docs where the client stumbled. After that, ongoing work should be intentional — retainer, new scope, or clean exit.
Why this matters commercially
Clients remember whether they felt stranded. Clear handoff is trust infrastructure. It also makes future work easier because the next engagement starts from a documented baseline instead of archaeology.