Plan the handover from project team to operations
A transition plan that gets the receiving team ready to run what you built, with acceptance criteria and a clear exit date.
The prompt
Help me plan the handover of what my project delivered to the team that will run it day to day.
What is being handed over: [system, process, service, facility]
Receiving team: [WHO, their current workload, and how involved they have been so far]
Handover date and hypercare period: [DATES]
Known open issues or workarounds: [LIST]
Support model after handover: [who handles incidents, changes, vendor management]
Cover:
1. Readiness criteria the receiving team must agree are met before accepting: documentation, training, access, monitoring, support processes, open defect thresholds, vendor contracts transferred.
2. Knowledge transfer plan: sessions, shadowing, reverse shadowing (they run it while we watch), and recorded walkthroughs - with dates and owners.
3. Handover documentation checklist: runbooks, configuration, known issues and workarounds, contacts, SLAs, licenses and renewals, backlog of deferred features.
4. Hypercare: how long the project team stays on, how issues are logged and prioritized, and exit criteria for ending hypercare.
5. Formal acceptance: who signs off, and what happens if they refuse.
6. Open items register: issues and deferred scope moving to the operations backlog, each with an owner.
Rules: flag anything that has no owner after handover. Use [CONFIRM] for details I have not given.
Return the plan with a dated timeline table, plus a short message to the receiving team's manager proposing the handover approach.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- system, process, service, facility
- DATES
- LIST
- who handles incidents, changes, vendor management
- CONFIRM
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a project closure reportFormally closes a project: results vs. objectives, handover, open items, and lessons.
- Plan an event from start to finishTimelines, budgets, logistics, run-of-show, and checklists for work or personal events.
- Turn my project plan into an Excel task tracker with owners and dependenciesBreaks a project or plan into a task tracker with owners, dates, dependencies, and status columns you can paste into Excel.
- Turn my team's updates into a weekly RAG status reportPulls scattered team updates into a weekly status report with honest red-amber-green ratings, risks, and asks.