Turn an approved outline into a brief a freelance writer can execute without back-and-forth

You are turning an approved outline into a content brief for a freelance or contract writer who has not worked with this brand before. The brief's job is to answer every question the writer would otherwise have to ask, so the first draft comes back usable instead of needing a full rewrite.

APPROVED OUTLINE
H1: The Onboarding Email Sequence That Doubled Our Open Rate. H2s: Why feature-first emails fail, The 4-email sequence we now use, The specific open-rate numbers, What we'd change next.

BRAND VOICE NOTES
"Direct, no fluff, a little irreverent — think a smart coworker explaining something, not a corporate blog."

REQUIRED FACTS OR LINKS
Must link to the /email-sequence-builder tool page in the "4-email sequence" section, anchor text should describe the tool, not say "click here".

SEO REQUIREMENTS
Primary: "onboarding email sequence". Secondary: "welcome email open rate", "email onboarding flow" — primary should appear in H1, first 100 words, and one H2.

EXAMPLES OF PAST POSTS THAT WORKED
The "Why Your Trial Users Ghost You" post from March — same directness, same short-paragraph rhythm.

DEADLINE AND LENGTH
1,500-1,800 words, first draft due in 6 days

BRIEF-WRITING RULES
State why this post exists and for whom in the first two lines — a writer who understands the actual goal makes better judgment calls on every sentence that follows than one just executing a heading list blind. Translate every voice adjective into something checkable: instead of "friendly, professional tone," specify what that actually means in sentence-level terms — contractions allowed or not, second person or third, how much humor, one real example sentence from a past post that hits the target register. Never leave a brand-voice instruction as an unqualified adjective a different writer could reasonably interpret three different ways; if the brand voice notes given are themselves vague, tighten them using the past-post examples as the actual reference. List every required fact, statistic, or link explicitly with where it should go and why it matters, not just "include relevant internal links" — a writer with no context on the site's link structure cannot make that call correctly, and guessing produces links that don't serve the actual SEO or user-journey goal. State the SEO requirements as specifics — target keyword, one or two secondary keywords, and roughly where each should naturally appear — not as an instruction to "optimize for SEO," which is unactionable without knowing what that means for this specific post. Give a real length range, not an approximate one — "1,500-1,800 words" is checkable, "around 1500ish" invites a draft that comes in at 900 or 2,400 and is technically not wrong. State explicitly what would get a draft sent back for revision — the specific, concrete criteria, not a vague "if it doesn't feel right" — so the writer knows the actual bar before submitting, not after missing it once.

OUTPUT FORMAT
A complete brief document with these sections in order: Why This Post Exists, Audience, Outline (as given), Voice (with the checkable specifics and one reference example), Required Facts/Links (each with placement), SEO Requirements, Length & Deadline, What Gets a Draft Sent Back.