Handover, acceptance and support afterward
What is handed over at the end of the work, how acceptance is carried out and how operations continue afterward are put in writing before the work begins. On this page we describe the deliverables, the acceptance steps, and support and incident management.
What you have at the end of the work.
The scope of the deliverables is set out in the proposal for each engagement; most projects include the items below.
Architecture documentation
Diagrams, components and decision records for what we built: what was chosen and why.
Infrastructure and configuration definitions
Environments and settings defined as code or documents; reproducible and traceable.
Operating procedures
Runbooks: the steps for backup, rollback, updates and incident response.
Monitoring and alerts
Dashboards, alert rules and what to do when each alert fires.
Training and knowledge transfer
Hands-on sessions for your team, with recordings where needed.
Acceptance test report
The tests performed, their results and the jointly approved handover list.
Acceptance is based on criteria set at the start.
When the work begins, we agree together which tests will verify the handover. At handover we work through these criteria and approve the results together.
Acceptance criteria
At the start, we define for each phase what will be tested and how success will be measured.
Joint testing
Depending on the project scope, functional, performance, redundancy and restore-from-backup tests are carried out together with your team.
Approval of the handover list
Once testing, documentation and training are complete, the handover list is approved together.
Handover checklist · platform setup
- Architecture document and decision records
- Infrastructure and configuration definitions
- Monitoring dashboards and alert rules
- Operating procedures: backup, rollback, version upgrades
- Restore-from-backup test · passed
- Load test · scheduled
- Training session · next week
- Mutual approval of the handover list
How do we continue after handover?
Support continues according to your engagement model. The scope, communication channels and response times are set out in the contract.
For what we delivered
Updates, bug fixes and minor improvements, under a support agreement with a defined scope.
Alongside your team
Architecture guidance, reviews and implementation support, during business hours through agreed channels.
We take on operations
Monitoring, maintenance and incident response; 24/7 for the systems defined in the contract, with response times set out in it.
How do we proceed when a problem occurs?
When a problem is detected on systems covered by support, the steps are clearly defined, and you are kept informed throughout.
Detection and logging
The problem is logged from a monitoring alert or from your report.
Prioritization
A severity class is assigned based on impact; the response target for each class is defined in the contract.
Response and updates
While we work on it, we share the status, the impact and the time of the next update.
Closure and post-incident review
For significant incidents, we share the root cause and the steps to prevent recurrence in a written review.
Incident update · update 2
- Severity
- High
- Affected
- Order service; new orders are being processed with a delay. Other services normal.
- Status
- Cause identified: the database disk is full. Disk space is being expanded.
- Workaround
- Pending orders are held in the queue; no data loss.
- Next update
- 10:45 or when resolved
About handover and support
Let's clarify your needs together.
In a free initial consultation we discuss your current situation and goals, and share our first impressions and possible next steps in the same meeting.
- A technical conversation with specialists in your area
- First impressions of your situation and possible approaches
- Where it fits, a next step: an assessment, a project proposal or consulting
- A non-disclosure agreement before the meeting when needed
- A reply within 4 business hours