FDE Foundations · Module 12: Business Impact & Handover
Handover and Acceptance
Handover is a deliverable with a checklist: repository, environments, runbooks, credentials, metrics baseline, and the acceptance record that formally ends the engagement.
10 min reading
Objectives
- Assemble the complete handover package
- Run the acceptance checklist against the brief
- Define what happens after: warranty, support, and phase two
The package
| Item | Contents |
|---|---|
| Code | Repositories, main branches, tags for the release |
| Environments | Access, configuration docs, deployment pipeline |
| Operations | Runbook, dashboards, alert routes, on-call notes |
| Data | Model docs, retention decisions, quarantine handling |
| Business | Brief, change log, metrics baseline, ROI model |
| Contacts | Escalation path, your support window, phase-two backlog |
Missing items in this table are the debts that surface in month two; fill every row before the acceptance meeting.
Acceptance against the brief
Walk the brief's acceptance criteria one by one with the evidence: metric, demo, or test. The change log explains every delta between original brief and delivered state. Sign-off is explicit: names, date, and the list of accepted deviations.
What happens after
State the support window (warranty period for defects), the channel for questions, and the phase-two backlog ownership. Ending cleanly is what earns the next engagement; ambiguity about "who fixes this now" is how endings turn sour.
The handover package is also your portfolio: it is the evidence of delivery you will point to in the next interview or the next customer.
Quick check
An optional 2-3 question self-check. Answers never leave your device, are not stored, and never count toward any assessment.
Exercise
Assemble the handover package for a fictional completed engagement: every table row with its real contents, three acceptance criteria with evidence, and the after-plan with dates.
Pass criteria
All six rows populated concretely, each criterion has evidence tied to the brief, and the after-plan states warranty window, channel, and backlog owner with dates.