Codebase handoff checklist: what to receive from a developer or an AI tool
Check the code, documentation, accounts, data and deployment information needed to maintain an app after a developer handoff.
Whether a freelancer, an agency or an AI coding tool built your app, you should be able to run, change and move it without them. This checklist covers what to ask for. It is advice from Omnistu.
Access and ownership
- Source code in a repository that you own, with full history if possible.
- Accounts for hosting, domains, app stores, analytics, email and payment providers held in your name or company's name, not the developer's personal account.
- A list of every third-party service used, with who pays for it.
- Written confirmation of who owns the code and assets. We have not researched typical terms; ask a lawyer if unsure.
Running it
- Written steps to run the app locally and deploy it, tested by someone other than the author.
- A list of environment settings and secrets needed, delivered through a safe channel and not in the code. Do not paste passwords into chat.
- The database structure and how to back up and restore it. Ask to see a restore done once.
Understanding it
- A short architecture note: main parts, how they connect, where data lives.
- A list of known issues and unfinished work.
- Automated tests, if any, and how to run them. See our mobile testing guide.
Safety checks
- A security review against the basics in our articles on passwords, sessions, input validation, rate limits and logging. Confirm that no secrets are stored in the code.
- A list of libraries used, so that known issues can be checked later.
- If AI generated parts of the code, ask which parts, and have the important ones reviewed by someone who can read them. We make no claim about the quality of any AI tool.
Before you sign off
- Have a different developer clone the repository and run the app from your notes.
- Check you can deploy a small change yourself or through a new vendor.
- Review the old developer's access during the handover, keep only permissions still needed for agreed work, and revoke access promptly when it is no longer needed. Suspected compromise needs a separate, immediate security response rather than waiting for routine sign-off.
By Omnistu.