📋Project management9 min readUpdated: Oct 14, 2026

Developer Handover Checklist

A developer handover checklist lists everything to check and hand over when you deliver a finished app to a client or to an incoming development team.

👨‍💻
Roman
AboutTheApp

Overview & context

The app is done and you're handing it over to the client? Congratulations! All that's left is to gather everything you collected during development and deliver it in a clear form. Use this software handover checklist as a guide for a typical project handover.

A developer hands the finished app to a client. They both hold the app window during the handover.

1. Source code repository and ownership transfer

Before a project is marked as "delivered", all source code must live in a repository owned or managed by the client.

If the project is hosted on a developer's personal account, transfer ownership to the client or make sure the client has full rights to the repository.

Clean Git history

Committing .env files or private API keys is one of the most common causes of security incidents during a handover.

Task listClick to toggle

2. Hosting, domain and infrastructure

Transfer ownership of the production hosting account to the client's billing account.

Check the domain's DNS records, the hosting account, backups and SSL certificate renewal. Make sure everything is set up correctly and working.

Task listClick to toggle

3. Third-party accounts and services

If the app sends emails, uses a payment gateway, web analytics, third-party sign-in or other external APIs and services, each of them has its own account and owner.

List every service the app depends on. For each one, note who owns the account, who pays for it and whether the account is transferred to the client or the client creates their own.

Task listClick to toggle

4. CI/CD pipelines and environment variables

Automated deployments remove human error from the handover. Document every secret the deployment pipeline needs. If the client has specific hosting environments or security protocols, document those too.

.github/workflows/deploy.yml
name: Production deploy
on:
  push:
    tags:
      - 'v*'

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Deploy to production
        run: npm run build && npm run deploy
        env:
          DATABASE_URL: ${{ secrets.PRODUCTION_DATABASE_URL }}

5. Handover documentation

Documentation is more than a user manual. During development you collect a lot of information that ends up spread across various documents and documentation tools.

You don't have to rewrite everything into a single handover document. It's enough for the client to know where each part of the documentation lives. For what to record about an app, see What to Document in a Software Project. A software documentation template gives the client one page that points to all of it.

Task listClick to toggle

6. Testing and quality

If the client has a test environment, they should know how to use it and how to verify that the app works.

Task listClick to toggle

7. Security, licenses and personal data

The client also takes over responsibility for what the app contains and what data it processes. They need to know which third-party libraries the app uses, under which licenses and where it stores personal data.

Task listClick to toggle

8. App status at handover

The handover document has to state exactly what is being handed over. The most reliable way is a version number and a tag in the repository, along with a list of changes and known issues. For technical debt, note what each item costs so the next team can plan the repayment.

Task listClick to toggle

9. Knowledge transfer and post-handover support

Schedule a knowledge transfer session, walk through the app and the handover document together and clear up anything that's unclear.

Also agree on what happens after the handover: how long the warranty lasts, who fixes bugs and where to report them. If you keep maintaining the app, agree on a software maintenance plan with the client. Put response times for bugs into an SLA.

Task listClick to toggle

10. Add links to your application in AboutTheApp

Instead of writing a handover document, add links directly to the application for the repositories, CI/CD pipeline, domain administration and other services.

This gives the client or future maintainer instant access to every service directly from the application they use or maintain.

Tip for other projects

Adding the AboutTheApp widget to every project gives each handover the same predictable shape, which cuts down on "where do I find X" questions later. It'll always be in the same place, in the same form.

InformationPublic viewPrivate (unlocked) view
App version & release dateVisible to everyoneSame, plus full history
Author & licenseVisibleSame, plus agency contact
Repository & design linksHiddenVisible with the unlock code or depending on role
Deployment & environment statusHiddenVisible with the unlock code or depending on role

11. Handover sign-off and acceptance

The handover ends with a handover document signed by both parties. It summarizes what was handed over, in which version and with which known limitations. It also sets the date from which the client takes over operations. You'll find a template to copy in the project handover template guide.

Task listClick to toggle

Frequently asked questions

What should a software handover document include?

A list of the items being handed over (access, links to repositories, documentation, hosting accounts, backups, etc.), the state of the app at handover including its version, known bugs and limitations, contacts and the handover date. Both parties sign it.

Who owns the source code after the app is handed over?

That's determined by the development contract or license agreement, not by the handover itself. Before the project starts, clarify in the contract whether the client gets exclusive rights to the code or only a license to use it. During development, check the licenses of the third-party libraries and components you use.

How do I hand over passwords and credentials securely?

Never by email or chat. Use sharing in a password manager or transfer the accounts directly to the client. After the handover, have the client change passwords and generate new API keys so that nobody who no longer works on the project has access to production.

What should I hand over when another developer takes over the app, not the client?

Besides access and infrastructure, it's a good idea to hand over instructions for running the project locally, an internal description of the architecture and key decisions, a list of known bugs and technical debt and the deployment process. Ideally with a short joint code walkthrough.

Where should I keep information about the app so it doesn't get lost?

In one place, connected directly to the app, that the client and future developers can find quickly. In AboutTheApp, you attach links to repositories, documentation and other external services to the app. Private links are visible only to those with access; public links are available to everyone.

In short

Collecting all the information in one place while you build the app and embedding it directly into the app is the simplest way to make the whole project handover easier for your client.

AboutTheApp

Want to make handovers easier?

Add your application to AboutTheApp for free.