One-Page Project Brief Generator

Turn long planning documents into a clear one-page executive brief.

Prompt · 3 variables

You are a seasoned project planner who has crafted dozens of high-impact one-pagers. You know exactly what to discard from lengthy source materials.

This one-pager is about {{official project name}} and is written for {{target reader audience}}. These readers are learning about the project for the first time or have only heard the name; they need to make an informed decision based solely on what fits on a single screen.

Review the planning materials below and produce a one-page summary. Do not simply compress the text—curate only the critical details a first-time reader needs to make a call.

Follow this exact structure: one title line, followed by these six sections: "One-Line Summary (within 60 characters)", "Why Now? (2 lines)", "What We Will Do (3 lines)", "Cost of Inaction (2 lines)", "Required Resources (table of People, Timeline, Budget)", and "Decisions Needed (1–2 bullet points)". Keep these exact section headers and keep the entire output under 300 words.

Do not invent numbers, dates, or milestones not found in the source. If an item lacks supporting data, do not omit the section; write "Not specified in materials". Spell out any internal acronyms and system names on first mention, and replace buzzwords like "streamline" or "optimize" with concrete explanations of what actually changes.

Planning Materials: """ {{planning materials}} """

Copy, then paste here · ChatGPT and Claude open with the prompt filled in Open in ChatGPT ↗Open in Claude ↗Open in Gemini ↗ Edit in builder Download classroom card

Some variables here may contain personal data. Replace real names, numbers and company names with placeholders.

Why it is written this way

Role
You are a seasoned project planner who has crafted dozens of high-impact one-pagers. You know exactly what to discard from lengthy source materials.
Context
This one-pager is about {{official project name}} and is written for {{target reader audience}}. These readers are learning about the project for the first time or have only heard the name; they need to make an informed decision based solely on what fits on a single screen.
Task
Review the planning materials below and produce a one-page summary. Do not simply compress the text—curate only the critical details a first-time reader needs to make a call.
Format
Follow this exact structure: one title line, followed by these six sections: "One-Line Summary (within 60 characters)", "Why Now? (2 lines)", "What We Will Do (3 lines)", "Cost of Inaction (2 lines)", "Required Resources (table of People, Timeline, Budget)", and "Decisions Needed (1–2 bullet points)". Keep these exact section headers and keep the entire output under 300 words.
Constraints
Do not invent numbers, dates, or milestones not found in the source. If an item lacks supporting data, do not omit the section; write "Not specified in materials". Spell out any internal acronyms and system names on first mention, and replace buzzwords like "streamline" or "optimize" with concrete explanations of what actually changes.
Input
Planning Materials: """ {{planning materials}} """

When you paste a lengthy project plan and simply say "summarize this into one page," you usually get the same document with shorter sentences. That is why a dedicated one-pager prompt is essential. A true one-page brief is not just a condensed proposal; it is a fundamentally different document. It must retain only what a newcomer needs to make a decision, ruthlessly cutting even the most polished paragraphs.

Setting the Role in the first paragraph as someone "who knows exactly what to discard" addresses this directly. Without this framing, the AI tries to preserve a snippet of every section, resulting in a vague overview lacking actionable depth. Specifying that the reader is "learning about the project for the first time" in the second paragraph serves the same purpose, filtering out insider jargon and uncontextualized backstory.

The fourth paragraph defining the Format is the core of this prompt. It locks in the exact headers, line limits, and total word count. Without strict constraints, models tend to write lengthy background intros and cram budget and key decisions into a single closing line. Creating a dedicated "Cost of Inaction" section highlights the urgency that decision-makers care about most—a detail often missing from standard project drafts.

The "Not specified in materials" rule in the fifth Constraints paragraph prevents the most dangerous issue with AI-generated summaries: hallucinated data. When faced with rigid templates, models often invent plausible numbers that might be mistaken for real commitments in high-stakes meetings. Finally, wrapping the planning materials in """ prevents incidental phrases like "see next slide" from being misinterpreted as instructions.

Unfamiliar terms? See Aha AI: output-format, context-window

Compared with a bad example

Common bad example

Summarize this into one page:

(Pasted full proposal text)

This produces a generic outline that blindly mirrors the original document's structure. Background and current status take up more than half the page, while resource needs, timelines, and costs remain buried in paragraphs. Without an assigned audience, internal jargon persists, confusing stakeholders from other departments. Furthermore, "one page" without explicit constraints often spills across multiple screens.

Variations

For Slack or Email Sharing

For Slack or Email Sharing

Please summarize the planning materials below into a concise message to share with {{target reader audience}} via team chat. Write exactly three short paragraphs under 150 words total, without tables or subheadings. The first sentence must clearly state what {{official project name}} is. End the final paragraph with the specific action required from the recipient, and add a closing line noting where they can find the full documentation.

""" {{planning materials}} """

Optimized for chat tools where tables break, using a concise paragraph flow tailored for quick mobile reading.

For In-Flight Project Status Updates

For In-Flight Project Status Updates

{{official project name}} is already in progress. Using the materials below, write a one-page status update for {{target reader audience}}. Use these exact sections: "Current Status (2 lines)", "Completed This Month (3 lines)", "Blockers & Help Needed (2 items)", "Next Month Plan (3 lines)", and "Schedule Changes". If progress percentages cannot be verified directly from the text, write "Needs confirmation" rather than estimating.

""" {{planning materials}} """

Swaps pre-kickoff approval sections for progress, blockers, and milestone tracking tailored to active projects.

Model notes

If your source material is very long and risks hitting context limits, paste it in sections and conclude with: "Using all the material provided so far, write the one-page brief." This ensures the model considers the entire document rather than just the opening pages.

Related prompts

Last updated 2026-09-02 · Found a mistake? Let us know