Handover runbook prompt
A handover runbook prompt writes the document that lets you run your site without the person who built it: who owns what, how to edit and publish, how to undo a mistake and what to check each month.
- Stage
- Grow, step 40 of 40
- Use it
- At the end of any website project, and again whenever a login or supplier changes.
- You need
- A list of the site's accounts and suppliers
- Someone who knows how publishing works today
- You get
- A runbook with placeholders for every login, name and date.
The prompt
Write a handover runbook for my website. Sections:
1. What I own: domain, hosting, code and accounts, and who holds each login.
2. How to edit a page and publish it, step by step.
3. How to undo a bad change.
4. Monthly checks: forms, speed, broken links, backups, renewals.
5. What to ask AI to do, with the prompts to use.
6. Who to call for what.
Write [PLACEHOLDER] for every login, name and date I must fill in.
Never put a password in the document.JSON version, for teams and automations
Fill each value under "inputs", keep the rest. It follows the prompt schema. When to use JSON.
{
"$schema": "https://websitesdesigner.com/insights/prompts/prompt.schema.json",
"id": "handover-runbook",
"name": "Handover runbook prompt",
"stage": "grow",
"step": 40,
"of": 40,
"version": "2026-11-19",
"url": "https://websitesdesigner.com/insights/prompts/handover-runbook/",
"inputs": {},
"instructions": [
"Write a handover runbook for my website.",
"Sections:",
"1. What I own: domain, hosting, code and accounts, and who holds each login.",
"2. How to edit a page and publish it, step by step.",
"3. How to undo a bad change.",
"4. Monthly checks: forms, speed, broken links, backups, renewals.",
"5. What to ask AI to do, with the prompts to use.",
"6. Who to call for what.",
"Write [PLACEHOLDER] for every login, name and date I must fill in.",
"Never put a password in the document."
],
"output": "A runbook with placeholders for every login, name and date.",
"checks": [
"Every account has an owner named.",
"The undo steps have been tested once.",
"No password appears anywhere."
]
}What good output looks like
- Every account has an owner named.
- The undo steps have been tested once.
- No password appears anywhere.
What experts miss
- Check whose name is on the domain. The registrant on the domain record is its owner, whoever paid the invoice.
- Test the undo before you need it. A restore process nobody has tried is a hope, not a process.
- Send renewal reminders to a shared inbox. Domains lapse when the reminder goes to a former employee.
Why it works
A handover is the moment a site becomes fully yours. Many businesses find out too late that someone else holds the domain or that nobody knows how to publish. A runbook makes ownership and routine work explicit.
How to adapt it
- Add a section of prompts from this library for routine edits.
- Add your AGENTS.md if the site lives in code.
Mistakes to avoid
- Storing logins in the runbook.
- Writing it once and never updating it.
Go deeper
See website handover and how to choose a website designer, where ownership should be agreed before you hire. This prompt is part of the grow stage. It follows the AI website design prompts guide and the six steps in how to use AI to design a website.