Bottom-line-up-front rewrite for decision memos and updates
Restructures a long update, email or memo so the decision or ask comes first, followed by only the context a busy reader needs. For anyone writing to executives, clients or cross-functional leads.
Prompt in Writing by AISkillHub Library
What it does
Long updates often bury the one sentence the reader needs ("we need a yes on vendor B by Friday") under three paragraphs of background. This prompt restructures your text into a bottom-line-up-front (BLUF) format: the ask or conclusion first, then the minimum context, options and risks, then details for anyone who wants them.
**Use it when** you are sending something to a reader with little time: a leadership update, a request for approval, a client status email, an escalation, a project change notice.
**How it differs from a line edit:** it changes structure, not sentences. It decides what the reader must know first, moves it to the top, groups the rest under clear headings and cuts what the reader does not need for this decision. For sentence-level polish, run a line edit afterwards.
**What you get** - A subject line or title that states the ask. - A BLUF block of one to three sentences: what you want, by when, and why it matters. - Supporting sections: context, options (with your recommendation), risks, next steps. - A "removed" list showing what was cut, so nothing important disappears silently.
**What it will not do** - It will not invent a recommendation, deadline or owner. If the original does not contain one, it marks the gap with `[needs: ...]` so you fill it in before sending. - It will not change numbers, dates or commitments. - It will not soften bad news into something misleading. If the original reports a slip or a problem, the rewrite still says so plainly.
**Example** A 420-word project update that ends with "so let us know if B works" becomes: Subject "Approval needed by Fri 14 Nov: switch payment vendor to B". BLUF: "Please approve moving to vendor B. A is two weeks late on the API we depend on; B adds 4% cost but keeps the December launch." Then options, risks and next steps.
How to use it
## How to use
1. Open `prompts/bottom-line-up-front-memo.md` and copy everything below the title line. 2. Replace each `{{variable}}` with your own content. Paste long material (notes, transcripts, tables) directly in place of the variable; keep the surrounding tags so the model can tell inputs apart. 3. Start a new chat in ChatGPT, Claude or Gemini and paste the filled prompt as your first message. 4. Read the output against the quality checks at the end of the prompt before you use or send it.
## Variables
- `{{original_text}}`: your existing draft, email thread or notes. - `{{reader}}`: who will read it and what they care about, e.g. `CFO, cares about cost and risk`. - `{{channel}}`: `email`, `memo`, `Slack message` or `slide notes`. Controls length and formatting. - `{{decision_needed}}`: the decision or action you want from the reader, if you know it. Write `none` for a pure update.
If you do not have a value for an optional variable, write `none` rather than deleting it, so the prompt still reads correctly.
## Reusing it
To reuse it often, save the prompt (with the variables left in) as the instructions of a Claude Project, a custom GPT or a Gemini Gem, then paste only the inputs in each new chat.
## Tips
- If the BLUF still feels long, the piece may contain two separate asks. Split them into two messages.
Files
Save each file at the path shown, relative to your project root.