Skip to content
All insights
Insight

Software handover checklist: what your business should receive

A practical software handover checklist covering source code, accounts, deployment, backups, documentation, training and support before your project closes.

By Syed Aalishan Asghar · 11 November 2026 · 9 min read

A finished website or application should leave your business able to run it, support its users and commission changes with confidence. That depends on more than receiving a link and an administrator password. A software handover brings together the code, accounts, instructions and responsibilities needed to operate the product after delivery. Planning it early helps both the client and the developer understand what completion means. This guide explains what to request, how to review what you receive and which questions to settle before a project closes.

1. Agree what is being handed over

Begin with a list of the systems included in the delivery. A customer portal might depend on a public website, a staff dashboard, a database, file storage, an email provider and a payment service. Each part needs an owner, an access arrangement and enough information for the next person to understand its purpose. A handover that covers the visible interface alone leaves important dependencies unexplained.

Compare the delivery with the approved scope and any recorded changes. Identify the version being accepted, the environments included and the features deferred to a later release. Keep known limitations in a separate register with their effect on users and the agreed next action. This makes it possible to distinguish completed work from outstanding work without relying on memory.

Ask for a short inventory that connects each component to its account, repository or documentation. Include services supplied by other companies and any work the client must perform. The inventory should be understandable to the business owner even if a technical colleague manages the detail. Review it before the final meeting so missing items can be resolved while the delivery team is available.

2. Receive the source code and the instructions to build it

Where the agreement includes source code, confirm which repositories and assets are part of that delivery. The main application may have separate code for background jobs, a mobile companion, infrastructure configuration or an administrative tool. Request access through an account controlled by the business, with named users for the people who need to contribute.

The code should have instructions explaining the required tools, dependency installation, configuration and build process. Ask the developer to identify the release currently running in production. A repository containing unfinished changes without a reliable release reference makes future work harder to begin. A compressed folder can preserve files, but it does not provide the same change history or collaboration workflow as a maintained repository.

Have a suitable technical person follow the instructions in a clean environment. They should be able to produce the expected build without relying on unrecorded settings on the original developer’s laptop. Record any extra steps discovered during this exercise. Do not copy production credentials into the repository simply to make the build easier.

3. Put business accounts under the right control

List the domain registrar, DNS provider, hosting, storage, email, analytics, monitoring and relevant app store accounts. Confirm who owns each account, who pays the bills and who receives renewal or service notices. These responsibilities should remain clear if the original contact leaves the business or the development arrangement changes.

For each essential service, check that an authorised person in the business can sign in and use the recovery process. Use individual access where the provider supports it, with permissions appropriate to each person’s responsibilities. Agree how development and support access will continue or be removed after delivery. Avoid making a departing contractor’s personal inbox the only recovery route.

Access and ownership are separate questions. Having an administrator login does not by itself establish ownership of intellectual property or third-party assets. Check the signed agreement for the rights transferred and any licence conditions that remain. Ask for clarification where the wording is unclear, and obtain professional advice where the commercial consequences justify it.

4. Document deployment and recovery

A deployment guide should explain how an approved change reaches the live environment. Include the build command, configuration requirements, release steps and checks performed afterwards. Identify who can approve a deployment and who can carry it out. If there are separate staging and production environments, explain their differences and how work moves between them.

Record how to return to a previous working release if a deployment causes trouble. Code, configuration and database changes may need different recovery steps. For example, an older application build may no longer understand a changed database structure. The guide should describe the supported recovery approach and any point after which restoring an older version requires additional work.

Walk through a routine release with the person who will maintain the product. Observe the result rather than accepting an unexplained successful command. Check that important tasks still work and that the team knows where release history is recorded. When a deployment remains a supplier responsibility, the business still needs the procedure, contact route and agreed support arrangement.

5. Check backups by restoring something

A backup policy needs to identify the information covered, how often copies are taken, where they are held and how long they are retained. Databases, uploaded files and configuration may be stored separately. Confirm whether a hosting provider’s backup includes all of them and whether restoring a copy is included in the service you pay for.

Discuss acceptable data loss and recovery time in business terms. Losing a day of enquiries has different consequences from losing a day of paid orders. These expectations help the technical team recommend an appropriate arrangement. They are targets to design and test against, and should not become promises unsupported by the system and support plan.

Ask for evidence of a controlled restore into a separate environment. Check that the restored application starts, expected records are present and important files open. Record the date of the exercise, what was restored and any limitations discovered. A notification saying a backup completed does not establish that the business can recover its service.

6. Make operating instructions useful to staff

Write documentation around tasks people actually perform. Explain how staff create and correct records, manage users, review submissions, export information and handle common exceptions. A short guide with accurate examples is more useful than a long document that repeats every screen label without explaining the work.

Include the consequences of important actions. If cancelling an order sends a customer message, or changing a setting affects future invoices, say so where staff will look for instructions. Explain which mistakes staff can correct themselves and which ones need support. Use fictional examples in documentation that does not need real customer information.

Arrange a training session with the roles that will use the product. Let staff complete representative tasks and ask questions while someone observes. Update the guide when the session reveals missing instructions. Store training recordings only where appropriate, with access restricted if a session contains private business information.

7. Record integrations, licences and recurring costs

List the external services the product depends on and what each connection does. Include the account owner, plan, renewal date where relevant, usage limits and the place to check its status. A feature may work during development on a trial that expires soon after launch. Record what must happen before that trial ends.

Explain where credentials are stored and how an authorised maintainer changes them. Document the process without placing the secret values in a general handover document. For connections such as email or payments, show the business how failures are noticed and who is responsible for investigating them. Keep access to customer information limited to what the work requires.

Prepare a recurring cost summary covering hosting, domains, software subscriptions and any agreed support fee. Separate fixed charges from costs that depend on traffic, storage or message volume. Include licensed fonts, images, themes and components where their terms affect future use. An initial development invoice rarely explains every ongoing operating cost.

8. Settle support and outstanding work

Define how the business reports an issue after handover and what information the support team needs. Agree the hours of coverage, the meaning of different priorities and any response commitments. Distinguish acknowledging a report from resolving the underlying problem. A response time should not be presented as a guaranteed repair time.

Record which defects remain within the agreed delivery responsibilities and which requests need a new estimate. A fault against an accepted requirement, an external provider change and a new feature can require different handling. Keep those distinctions in writing so staff know what to expect when they ask for help.

Give each outstanding item an owner, impact and next decision or target date where one is agreed. Avoid closing the project with a vague promise to finish small things later. If the business accepts a release with known limitations, record those limitations and any temporary operating procedure. Keep the acceptance record alongside the release details.

9. Use a final walkthrough to confirm readiness

Bring the business owner, operational contact and technical maintainer together for a final review. Work through the inventory, demonstrate essential access, locate the documentation and confirm the support route. Ask the people taking responsibility to explain how they would handle a routine release, a failed integration and a recovery request.

Keep a checklist with evidence against each item. A repository link, a demonstrated sign-in, a restored sample and an agreed support contact are more useful than a single box saying everything was handed over. Mark items as complete, outstanding or outside the agreed scope. Make the acceptance decision against that record.

For a small website, this can be a concise document and a focused meeting. A business application with several roles and integrations needs a more detailed review. Match the effort to the consequences of losing access or interrupting work. The aim is to leave the people operating the product with the information and authority they need.

A practical software handover checklist

Before accepting the handover, confirm the items below with your delivery team. Keep the evidence in a place the business controls and review it again when the product or support arrangement changes.

If you are planning a website, application or SaaS product, include handover requirements in the proposal from the beginning. aaliSoft can help define the delivery scope, documentation and ongoing support arrangements around the way your business will operate the software.

  • Release and agreed scope recorded, with known limitations identified.
  • Source code, assets and build instructions delivered where included in the agreement.
  • Business account ownership, billing, recovery and access confirmed.
  • Deployment and recovery instructions reviewed with the maintainer.
  • Backup coverage documented and a controlled restore checked.
  • Staff task guides and training completed.
  • Integrations, licences and recurring costs recorded.
  • Support responsibilities and outstanding work agreed in writing.

Syed Aalishan Asghar

Founder and Delivery Lead at aaliSoft

Start a conversation

Bring us the problem. We will help shape the right product.

Tell us what you are building and where it currently stands. We reply within one business day, anywhere in the world.

Websites · SaaS · Mobile apps · Games

Discuss your project
(opens in a new tab)