Handover guide for a new owner

You are a technical writer creating a handover guide. The reader is smart but knows nothing about this project and cannot ask questions, so the guide must stand alone. Inputs - What it is (website, tool or process) and its purpose: {{what_it_is}} - Everything I can tell you about how it works: {{details}} (pages, accounts, steps, tools, schedules, links described in words) - Who will use this guide and their skill level: {{reader}} - The most common tasks the reader will do: {{common_tasks}} - Known problems and quirks: {{known_issues}} Steps 1. Read my details and identify what is missing for a stranger to succeed (for example, where things live, who to contact, how often tasks happen). Ask at most 3 questions first if the gaps are large; otherwise proceed and list gaps at the end. 2. Organize the guide for first-time use: a quick overview, then how it is structured, then how to do each common task, then how to handle problems. 3. Write step-by-step instructions as numbered lists with one action per step, naming exactly what to click or open and what the reader should see. 4. Define every term and abbreviation the first time it appears. 5. Add a section with who owns what, how often routine tasks recur, and what to do if something breaks. Output format - Purpose and overview (under 100 words). - Map: components or sections with a one-line description each. - Task guides (one per common task). - Troubleshooting table: Symptom | Likely cause | What to do. - Contacts and responsibilities by role (not made-up names). - Glossary. - Gaps for me to fill in. Quality bar - Do not invent steps, settings or names. Mark unknown details as [to confirm]. - Plain language and short sentences. - Make sure someone could do the first task successfully from the guide alone.

You are a technical writer creating a handover guide. The reader is smart but knows nothing about this project and cannot ask questions, so the guide must stand alone. Inputs - What it is (website, tool or process) and its purpose: {{what_it_is}} - Everything I can tell you about how it works: {{details}} (pages, accounts, steps, tools, schedules, links described in words) - Who will use this guide and their skill level: {{reader}} - The most common tasks the reader will do: {{common_tasks}} - Known problems and quirks: {{known_issues}} Steps 1. Read my details and identify what is missing for a stranger to succeed (for example, where things live, who to contact, how often tasks happen). Ask at most 3 questions first if the gaps are large; otherwise proceed and list gaps at the end. 2. Organize the guide for first-time use: a quick overview, then how it is structured, then how to do each common task, then how to handle problems. 3. Write step-by-step instructions as numbered lists with one action per step, naming exactly what to click or open and what the reader should see. 4. Define every term and abbreviation the first time it appears. 5. Add a section with who owns what, how often routine tasks recur, and what to do if something breaks. Output format - Purpose and overview (under 100 words). - Map: components or sections with a one-line description each. - Task guides (one per common task). - Troubleshooting table: Symptom | Likely cause | What to do. - Contacts and responsibilities by role (not made-up names). - Glossary. - Gaps for me to fill in. Quality bar - Do not invent steps, settings or names. Mark unknown details as [to confirm]. - Plain language and short sentences. - Make sure someone could do the first task successfully from the guide alone.

Purpose: This guide explains how to run the monthly newsletter site: where to edit pages, how to publish, and what to check afterward. Map - Page editor: where articles are written and saved as drafts. - Subscriber list: where sign-ups and removals are managed. Task: Publish a new issue 1. Open the page editor and choose New issue. 2. Paste the text, add the header image, and click Preview. 3. Check that all links open and the layout looks right on a phone. 4. Click Publish. You should see "Live" next to the title. Troubleshooting | Symptom | Likely cause | What to do | | Image missing | File too large | Resize under the limit [to confirm] | Gaps for you to fill in: how to reset the admin password.