Inherited software handover worksheet
Use this one-page check when a developer or agency has moved on. Mark what your team knows today, then take the open questions to the person responsible for the system. You can print or save it as a PDF without entering your details.
1. What do you control?
| Check | Yes | No | Unsure |
|---|---|---|---|
| We can access the source code and know who owns it. | □ | □ | □ |
| We control hosting, domains, key accounts, and credentials. | □ | □ | □ |
| We know where backups are and when they were last tested. | □ | □ | □ |
| We know how a change is tested and released. | □ | □ | □ |
| We know which integrations and workflows would hurt most if they failed. | □ | □ | □ |
2. What must keep working?
System and main business purpose:
Most important workflow, report, or integration:
3. What should happen first?
Biggest current risk or unknown:
One useful improvement needed in the next 1–3 months:
Next step: if several answers are “No” or “Unsure”, recover access and confirm the release and backup paths before making riskier changes.
Industrial Hypertext · Perth Discuss an inherited system 0432 000 583