Buyer guides / Arttechz

A software handover checklist for international projects

Use this ungated checklist when planning an outsourced build or accepting a release. Agree responsibilities early and verify them at handover; these are questions for your project, not promises about Arttechz contract terms.

Discuss your handover needs

Code and account access

Identify the source repository, administrators, and how access will be transferred or maintained.
Record the release version and the steps needed to build it.
List hosting, domain, database, email, analytics, and third-party service accounts.
Assign account owners, billing responsibility, and recovery contacts.
Confirm ownership, licensing, and reuse terms in the project agreement; do not infer them from repository access.

Release and recovery

Request a deployment guide that names prerequisites, configuration, and verification steps.
Confirm where secrets are stored and who can manage them; keep secrets out of general handover documents.
Identify backups, restore instructions, and the owner responsible for testing recovery.
Record a rollback route and conditions for using it.
Confirm how operational failures become visible and who responds.

Acceptance and known limitations

Keep a list of agreed acceptance checks and their outcomes for the release being handed over. Include permissions, important failure paths, and the integrations the project relies on.

Record unresolved issues, their impact, and the decision to fix, defer, or accept each one.
Identify any demonstration data or unfinished integration that must not be mistaken for production behavior.
Agree the format and location of user instructions and operator training.
Record who can approve launch and what remains dependent on the client.

After the handover meeting

Agree the boundary between defects, support requests, and new work. Confirm availability, escalation contacts, response expectations, and charges in writing rather than assuming ongoing cover.

Run a practical walkthrough: can the receiving person locate the code, identify the running release, find the operating instructions, and reach the right account owner? Record any gaps with an owner and next action.

Bring this checklist into scoping

Use these items in the cost planning brief so handover does not become an unpriced afterthought. Discuss them with Arttechz when scoping custom software or workflow automation.