Handover Checklist

Run this in order. Do not mark the engagement complete until every item is done.

1. Code#

• Repository transferred to the client's account, or client added as owner
• All branches merged or documented
• README written: what this is, how to run it locally, how to deploy
• No secrets, keys, or credentials anywhere in git history — check history, not just the current state
• Dependencies documented with versions locked

2. Infrastructure#

• Hosting account transferred to the client, or client added with owner access
• Domain DNS configured and documented
• SSL verified working
• Database access credentials handed over securely — password manager share or encrypted channel, never plain email
• Third-party service accounts (Stripe, email, storage) transferred or client-owned from the start

3. Documentation#

• Architecture overview — what the pieces are and how they connect
• Data model documentation — entities and relationships
• Environment variable guide — every key, what it does, where to get it
• Deployment instructions including rollback
• Known limitations, explicitly stated
• Recorded walkthrough of codebase and admin functions

4. Commercial#

• Final invoice issued and paid
• IP transfer confirmed in writing (triggered by final payment)
• 30-day warranty period start date recorded
• Testimonial requested
• Permission requested for portfolio use — name, industry, or anonymous
• Referral asked for

The last three are the most commonly skipped and the most valuable. Ask while the client is happy. The window closes fast — every month that passes makes the ask harder and less likely to succeed.

5. Internal#

• Case study drafted while details are fresh
• Anything reusable extracted into internal libraries
• Lessons learned noted — what was underestimated, what to scope differently next time
• Actual hours vs. quoted hours recorded, to calibrate future estimates