Rewrite a technical document for business stakeholders
Translates a technical document into business language: what it means, the cost, risk, and timing, and what decision is needed.
The prompt
Rewrite the technical document below for a business audience.
Document: [PASTE - e.g. architecture proposal, engineering report, IT incident review, data analysis]
Audience: [e.g. "department heads with no technical background"]
What they need to do with it: [approve budget / choose an option / understand impact / just stay informed]
Length: [e.g. "one page", "half the original"]
Rewrite it so that:
1. It opens with a 3-sentence summary: what this is, why it matters to the business, and what is needed from the reader.
2. Each technical point is translated into its business effect - cost, time, risk, customer impact, or capability gained.
3. Jargon is removed or explained in a few plain words the first time it appears.
4. Options are compared on business criteria (cost, risk, time to deliver, what we give up).
5. Numbers keep their exact values; round only where precision doesn't matter, and say so.
Return:
1. The rewritten document.
2. A short glossary of any technical terms that had to stay.
3. A list of points you simplified, so a technical reviewer can check the meaning is still correct.
4. Questions business readers are likely to ask, with answers drawn from the original.
Don't add claims, estimates, or benefits that aren't in the original; mark anything uncertain as [CONFIRM WITH TECHNICAL OWNER].
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Writing & Editing prompts
What to fill in
- e.g. "department heads with no technical background"
- e.g. "one page", "half the original"
- CONFIRM WITH TECHNICAL OWNER
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Check a document for inconsistencies and errorsReviews a document for contradictions, inconsistent numbers and terms, and gaps.
- Find unnecessary approvals in a workflow and simplify sign-offsReviews every approval in a workflow, flags the ones that add delay without reducing risk, and proposes a leaner sign-off design with thresholds.
- Proofread for mistakes without rewriting my styleCatches grammar, spelling, punctuation, and consistency errors and changes nothing else.
- Rewrite text in a different tone, length, or styleAdapts the same message for a new tone, audience, length, or point of view without changing the facts.