Leadership Brief Template Pack
Everything you need to draft one real brief end-to-end — pre-flight worksheet, raw inputs and voice samples, three prompt variants for decision / status / escalation, a fillable seven-part brief template, a voice cheat sheet, and a final-pass checklist. Fill one out. Save it. Send the brief. Repeat.
1. Pre-flight. Pick the mode and audience in Section 1. Write your one-sentence BLUF before you open Claude. If you can't compress it to one sentence, go do the thinking.
2. Inputs & voice. Dump the raw information into Section 2. Paste 2–3 samples of your own writing. This is what turns "an AI brief" into "your brief."
3. Draft, fill, ship. Pick a prompt variant in Section 3, run it in Claude, drop the output into the Section 4 template, and walk the Section 6 checklist before you send.
Pre-Flight Worksheet
Before you open ClaudeThree decisions before Claude writes a word: the mode, the audience, and your one-sentence bottom line. If any one of these is soft, the brief will be soft. Do the thinking here.
Raw Inputs & Voice Samples
What Claude seesTwo dumps. The first is the information the brief needs to stand on. The second is two or three samples of your own writing so the brief sounds like you, not like a generic template.
Prompt Variants
Decision / Status / EscalationOne core scaffold, three variants — each with the right emphasis for its mode. Pick the one matching Section 1, paste your inputs and voice samples beneath, run it in Claude.
ROLE: You are a senior operations communications specialist. You write clear, direct leadership briefs to a professional standard. BLUF discipline is non-negotiable. No throat-clearing. No adjectives where a number works. CONTEXT: [Who I am, what operation, my relationship to this decision.] AUDIENCE: [The specific reader from Section 1 — name, title, seniority, what they already know.] MODE: Decision brief. MY BLUF: [Paste your one-sentence bottom line from Section 1. Refine — do not reinvent.] DECISION DATE: [From Section 1 — when the reader must act, and the cost of missing it.] RAW INPUTS: [Paste everything from Section 2 — data, notes, quotes, prior decisions, numbers with sources. Unorganized is fine.] VOICE SAMPLES: [Paste 2–3 samples of my writing from Section 2. Match the tone, vocabulary, and rhythm. The final brief should be indistinguishable from my own writing.] TASK: Draft a one-page executive decision brief using this structure: • Subject line (one line, states the decision and the direction) • BLUF (1–3 sentences: situation → recommendation → decision date) • Context (the minimum background that makes the BLUF make sense — no history) • Key Facts (3–5 bullets, numbers with sources, no adjectives) • Options (A / B / C — each with cost, outcome, and trade-off; one marked "Recommended") • Recommendation / Ask (specific, actionable, named owner, named date — what I need from the reader) • Appendix (optional — link only if needed, do not inline) STANDARD: Lead with the point. Active voice. Every claim traceable to the raw inputs. Flag anywhere the inputs have gaps or contradictions — do not invent facts. The brief should sound like an experienced operator wrote it, not a generative tool. Match the voice samples exactly.
ROLE: You are a senior operations communications specialist. You write clear, direct status updates to a professional standard. BLUF discipline is non-negotiable. No throat-clearing. No hedge language. CONTEXT: [Who I am, what operation, what I'm reporting on.] AUDIENCE: [The specific reader from Section 1 — what they're tracking, what they already know.] MODE: Status update. MY BLUF: [Paste your one-sentence bottom line from Section 1 — the headline of the period being reported.] REPORTING PERIOD: [The window this status covers — e.g., week of April 14–20.] RAW INPUTS: [Paste everything from Section 2 — metrics, milestones, issues, changes from plan, upcoming events. Unorganized is fine.] VOICE SAMPLES: [Paste 2–3 samples of my writing from Section 2. Match the tone exactly.] TASK: Draft a one-page status update using this structure: • Subject line (period + headline) • BLUF (1–3 sentences: on track / at risk / off track, and the single most important fact) • What Moved (3–5 bullets — quantified progress, milestones hit, numbers with context) • What Didn't (2–4 bullets — variances, misses, blockers — with the reason and owner) • What's Next (specific actions, named owners, dates) • Risks & Asks (what could change the trajectory; anything you need from the reader) STANDARD: Concrete numbers over descriptions. Dates on every action. No "continue to monitor." No "we remain focused on." Every variance has a reason and an owner. Flag anywhere the inputs are incomplete — do not paper over gaps. Match the voice samples.
ROLE: You are a senior operations communications specialist. You write clear, calm, direct escalations to a professional standard. BLUF discipline is non-negotiable. No alarm language, no hedge language, no throat-clearing. CONTEXT: [Who I am, what operation, what is wrong or about to be.] AUDIENCE: [The specific reader from Section 1 — why this is being escalated to them specifically.] MODE: Escalation. MY BLUF: [Paste your one-sentence bottom line from Section 1 — the issue, quantified, with the action I'm recommending.] URGENCY: [When this becomes worse if nothing happens — concrete, with a date or event.] RAW INPUTS: [Paste everything from Section 2 — what happened, when, who saw it, the numbers, the affected parties, attempts already made. Unorganized is fine.] VOICE SAMPLES: [Paste 2–3 samples of my writing from Section 2. Match the tone exactly — measured, not alarmed.] TASK: Draft a one-page escalation using this structure: • Subject line (issue + action needed) • BLUF (1–3 sentences: what is wrong, the impact quantified, what I'm recommending) • Situation (the facts of what happened and when — neutral, sourced) • Impact (quantified effect if nothing changes — dollars, throughput, timeline, customer exposure) • Actions Already Taken (what I and the team have done so far) • Recommendation / Ask (specific action, owner, date — and exactly what I need from the reader to unblock) • Risk if No Action (the bounded worst case, not hypothetical panic) STANDARD: Calm register. Impact in numbers, not adjectives. No "critical," no "urgent" unless paired with a specific timeline and dollar figure. Every claim traceable to the inputs. Flag gaps — do not invent. Match the voice samples.
The Brief Template
Seven parts · one pageDrop Claude's output into this template, or write it by hand. Every section is editable. Seven parts are always present — their depth scales with audience (one page for an exec, two to three for a board). Structure does not change; only depth does.
Voice Cheat Sheet
AI-speak → operator voiceKeep this in front of you during the final pass. If a line from the draft reads like the left column, rewrite it to read like the right. Over time you won't need the sheet — you'll just feel it.
"In today's rapidly evolving operational landscape, it is increasingly important to leverage data-driven approaches to drive meaningful outcomes."
"Assembly B missed target by 4.6% last week. The cause is a tooling wear issue we can fix this quarter."
"It may potentially be worth considering whether additional investment could possibly help improve throughput in certain areas."
"Throughput is the bottleneck. Investing $42K in the Line 3 upgrade recovers the capacity within one quarter. Recommend approval."
"Moving forward, it is essential that we continue to align on key priorities and ensure stakeholder engagement remains high."
"Next: I'll have the revised scope to you Thursday. Need your sign-off by Friday to hit the May 1 start."
"I hope this message finds you well. I wanted to take a moment to share a brief update on where we currently stand."
"Line 3 is 4.6% under target this month. Root cause identified, fix quoted at $42K. Detail below; approval needed by Thursday."
"We are looking into this matter and will provide further updates as appropriate in due course."
"Maintenance has scope by Wednesday. I'll send the revised plan Thursday AM. If Wednesday slips, I'll flag same day."
Final-Pass Checklist
Before you sendWalk every item before the brief goes out under your name. The tool drafts; you sign. Check each box; uncheck if you catch something to fix.
Track who reads it, who acts on it, and what happens. Save the brief into your personal archive with a one-line note on the outcome. That's how you build the feedback loop that makes the next brief sharper — the same way the prompt library compounds in Module 02.