Give every service an owner
List the domain registrar, hosting, source repository, database, email service, analytics and payment provider. Record the person or business that owns each account, plus who pays its bills.
Done when: The client can name the owner of every service the app depends on.
Make access a working handover
Record the dashboard URL and how the next person gets invited. Ask them to open it with their own account and confirm the right permissions. Transfer passwords and recovery codes through a password manager; keep them out of shared guides.
Done when: The recipient has tested their own access, including account recovery.
Put recurring costs on one page
Record each fixed amount, currency, billing interval and next renewal date. Keep usage-based charges separate and identify where to view them. Note which plan limits or card details the owner needs to review.
Done when: The owner knows what renews next, who pays and where to change it.
Describe the last working release
Link the source repository and identify the deployed version. Write down the release steps, a short smoke-test checklist and how to roll back. Locate the backup, name its owner and record when restoration was last tested.
Done when: The next developer can find the release and recovery instructions.
Set clear maintenance boundaries
Record what is included after handover, when the included support ends and how to request additional work. Name a contact for incidents. List known issues plainly, with an owner and the next action for each.
Done when: Both sides understand who responds when something breaks.
Close the loop with the recipient
Walk through the guide together. Ask the recipient to find a dashboard, the next renewal and the recovery instructions. Resolve missing items, record the handover date and give them a downloaded copy they can keep.
Done when: The recipient has a usable copy and knows what still needs attention.