Who maintains the system when the consultant leaves?
Go-live does not end responsibility for a solution. Before accepting delivery, agree who handles incidents, maintains access and implements future changes.
Where the problem starts
When only one person understands the system, their departure becomes an operational risk. Documentation matters, but it is insufficient without access to code and configuration, appropriate permissions and someone able to recover or change the solution.
What to check first
- Confirm ownership of accounts, environments, source code and configuration.
- Request operating, administration, deployment and recovery instructions.
- Agree incident reporting, response times and the scope of support.
- Complete a practical handover with the person or team taking over maintenance.
First step
A decision before a solution
Make handover and the receiving team’s ability to maintain the solution part of acceptance. Define response time, resolution commitments and additional development separately.
How MIDA can help
We help define maintenance and handover requirements. For the part we develop, we provide the agreed documentation and knowledge transfer; in an oversight role, we review the supplier’s handover and identify what is still missing.
Free introductory call