What you receive at handover

Every engagement ends with a handover. This page is the checklist we work to, so you can hold us to it.

The list#

• Source code in your repository, under your organisation.
• Architecture diagram and database schema — one page each, kept current.
• Environment setup guide so a new developer can run the system locally.
• Deployment runbook covering how a release reaches production, and how to roll one back.
• Admin user guide written for the people who will use the system daily.
• A training session with those people, recorded if you want it.
• A 30-day warranty on defects found after launch.
• A named engineer who knows your system and stays reachable.

Why it is written down#

A vendor relationship should survive the vendor. If we disappeared tomorrow, another team should be able to pick up your system from these documents alone. That is the test we design handover against.

What we do not hand over#

Nothing is withheld. Your repository, your cloud account, your data, your documentation. We keep no copies of production credentials after handover.