Build a Reusable Report or Memo Template Anyone on Your Team Can Fill In
Get a blank document template with headed sections, one-line guidance under each, a fully filled example, and a short pre-send checklist.
You getTemplate name and one-sentence purpose, blank template and filled example
Prompt
You are an operations lead who designs document templates that new team members can fill in without asking anyone for help.
Your job: build a reusable template for a recurring report or memo my team writes. Before you start, ask me these questions in one message, then wait for my answers:
1. What is the document (e.g. weekly status report, incident memo) and how often is it written?
2. Who reads it, and what decision or action should it support?
3. What usually goes wrong with the current version (too long, missing data, inconsistent)?
4. Any required sections, length limit, or tool it lives in (Google Docs, Notion, email)?
Rules:
- Use 5-8 headed sections, ordered by what the reader needs first.
- Under each heading, write one line of guidance in italics stating what to include and a length limit (e.g. "3 bullets max").
- Mark each section Required or Optional.
- Write a filled example of the whole template with realistic fictional content that stays within the stated limits.
- Keep the blank template under 250 words so it is quick to copy.
Output format:
1. Template name and one-sentence purpose
2. Blank template (headings plus guidance lines)
3. Filled example
4. Three-item checklist the writer runs before sending
End with one line noting any assumptions you made or information that would improve the template.Example output
Tips and common edits
Why this works
- One italic guidance line per heading tells any writer exactly what goes there, so the template needs no separate instructions.
- Length limits and Required/Optional labels stop reports from bloating and make missing sections obvious.
- The filled example shows the expected tone and detail, which new team members copy faster than written rules.
Use this in ChatGPT, Claude or Gemini when a recurring report keeps coming back inconsistent. Know who reads it, how often it goes out, and what currently goes wrong.
Common edits
- Ask for a version formatted as a Notion or Google Docs page with heading levels already set.
- Add a request for a short email version that summarizes the report in 4 lines for busy readers.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Build a Timed Meeting Agenda with Owners, Decision Labels and Pre-Reads
Get a timed agenda where every item has a Decide, Discuss or Inform label, an owner and minutes that fit the slot, plus pre-reads and a list of items to handle async.
Draft a Hard Team Announcement for a Reorg, Delay or Policy Change
Get a clear team announcement that states the news first, shows what changes and stays the same for each group, and answers likely questions honestly.
Plan a Sprint Retrospective with Timed Steps, Questions and a Dot-Vote
Get a retro format matched to your team's mood and problems, with a timed agenda, warm-up, open questions, and a dot-vote that ends in at most three owned actions.
Prepare a Constructive Feedback Conversation with a Teammate Using SBI
Get a ready-to-say feedback script with an opening line, a situation-behavior-impact statement, one clear request, and calm replies to defensive reactions.
Replace Your Weekly Status Meeting with an Async Written Check-In
Get a reusable async check-in with a posting schedule, response deadline, short questions, a sample answer and clear rules for when a live call is still needed.
Write a Project Kickoff Message for Your Team and Stakeholders
You get a short team kickoff message covering why, scope, roles, first deadline and questions, plus a shorter stakeholder version and a list of gaps.