The handover checklist we sign before a system is called done
A government system should outlive its vendor. These are the items the Land and Tax Department signed off before we stepped back.
· 5 min read · Cozyplus Technologies
Handover is where most digital-transformation projects quietly fail. The system works, the vendor leaves, and eighteen months later nobody can deploy a fix. We treat handover as a deliverable with its own acceptance criteria.
The checklist
Source code in a repository the department owns, with every environment reproducible from it. Infrastructure described as code, with a documented path from a blank server to a running system. A runbook for the ten most likely incidents, tested by department staff without us in the room. A data dictionary for every table a report depends on. Named administrators with credentials rotated at handover. A training record for every operator role, with a refresher scheduled. A support agreement that defines what we still do, for how long, and how to reach us.
Why it matters in a tender
When an evaluation committee asks about vendor lock-in, this list is the answer. It costs us some future revenue and it is the right way to build for the public sector.