Document Your Social Strategy So Someone Else Can Run It

You are a marketing operations writer for an Australian small business owner handing social media to someone else — a junior, a VA or a contractor. Your output is the handover document itself: complete enough that a competent stranger could run the channels for a month without asking the owner anything routine.

<context>
- Business: [BUSINESS — e.g. 'Bayline Marine, boat servicing in Hervey Bay']
- Channels being handed over: [CHANNELS — e.g. 'Facebook and Instagram']
- Why social exists for this business: [PURPOSE — e.g. 'keep the workshop booked in winter; be the name locals think of']
- Audience in the owner's words: [AUDIENCE — e.g. 'boat owners 40+, practical, hate wanky marketing']
- Voice, with 2-3 example posts the owner rates: [VOICE + EXAMPLES — paste them]
- Content sources the new person can access: [SOURCES — e.g. 'workshop photos, job stories (names withheld), tide/season hooks']
- Non-negotiables and never-dos: [RULES — e.g. 'never show client rego numbers; no memes']
- Approval appetite: [APPROVAL — e.g. 'owner approves promos only; everything else posts freely']
</context>

<task>
Before writing, extract the owner's implicit strategy: from [PURPOSE], [VOICE + EXAMPLES] and [RULES], state in 3 sentences what this account is actually doing when it's done well — the new person needs the why, not just the what.

Then write the handover document with these sections:
1. Mission — the 3-sentence why, plus the 2 outcomes the channels are judged on (from [PURPOSE]).
2. Audience card — who they are, what they respond to, what switches them off (from [AUDIENCE], expanded only by inference you can defend).
3. Voice guide — 3 rules derived from the pasted examples, each with a sounds-like/never-sounds-like pair; then annotate ONE pasted example, pointing at what makes it right.
4. Content system — 4-5 recurring post types built from [SOURCES]: for each, its job, cadence, a template skeleton (hook / body / close), and one worked example written new.
5. Weekly operating rhythm — what happens which day (create, schedule, reply, report), sized for roughly [X HOURS — e.g. '5 hours/week'].
6. Guardrails — [RULES] expanded into a checkable list, plus the standard lines: get consent before featuring customers or their property; no claims about pricing/turnaround unless confirmed that week; competitions need owner sign-off (state permit rules may apply).
7. Escalation and approval — exactly what needs owner sign-off (from [APPROVAL]), what the new person decides alone, and the response protocol for complaints or a brewing pile-on (acknowledge, take offline, alert owner — with a drafted holding reply).
8. Monthly report template — 5 lines: what went out, what worked, what flopped, what customers said, next month's one change.
</task>

<output_format>
A single clean document with the 8 numbered sections and a title block (business, channels, version date, owner contact). Under 1,300 words. Australian spelling. Written TO the new person ('you post…', 'you never…') — it's their manual, not a strategy essay.
</output_format>

Rules: build only from the inputs; where the owner hasn't supplied something load-bearing (posting hours, approval scope), insert [OWNER TO CONFIRM: …] rather than deciding for them. Do not invent example customers, jobs or numbers in the worked examples — keep them generic-but-plausible and clearly marked as templates. If [VOICE + EXAMPLES] is empty, stop and ask for 2-3 real posts first; a voice guide can't be honestly written without them.

Copy the block above straight into Claude — anything in [BRACKETS] is yours to fill in.