Output Format Fixer

Get the right format for emails, docs, presentations

analysisbeginnerCommunication FormatsOutput Structuring300-400 words
Customize Your Prompt
Fill in the variables to generate your personalized prompt
Preview
See how your prompt will look with the current variables
Your prompt produces good content but wrong format for [Intended Format]: "[Current Prompt]"

Role: Communication Format Specialist for PM deliverables.

Instructions:
1. Analyze format gaps
2. Add explicit format instructions
3. Include length and tone requirements
4. Add structure templates
5. Provide format examples

Specifics:
## Format Gap Analysis
**Current Output:** [What you're getting]
**Required for [Intended Format]:** [What you need]
**Key Differences:** [Specific gaps]

## Enhanced Format Instructions
### Structure for [Intended Format]
[Exact structure with sections]

### Style Requirements
- **Tone:** [Professional/Casual/Technical]
- **Length:** [Word/character limits]
- **Key Elements:** [Must-have components]

## Revised Prompt with Format
[Original prompt enhanced with:]

"Format as [Intended Format]:
- Structure: [Specific sections]
- Length: [Exact limits]
- Tone: [Specific style]
- Include: [Required elements]
- Exclude: [What to avoid]"

## Format Template
```
[Exact template for [Intended Format]]
```

## Success Criteria
- Correct format for [Intended Format]
- Right length and tone
- All required elements included
- Ready for review against the requested format

Purpose: Make the requested output structure clear and easy to check.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.
Specify the output format
  • • Name the sections and the order they should appear in.
  • • Set a length limit and describe the tone you need.
  • • Provide a template or an example to follow.
  • • Ask the model to check the draft against your requirements.
  • • Specify a format for each output when requesting more than one.
Common format mistakes
  • • Requesting an email without specifying its subject, audience, or intended action.
  • • Omitting a length limit when the output must fit a particular space.
  • • Naming a tone without explaining it for this audience.
  • • Expecting the model to follow a house style without supplying it.
Output format questions

How do I get a paste‑ready Slack message?

Give the section names, character limits, and examples. Ask the model to check those requirements before responding, then review the message before posting it.

How do I get a shorter response?

Set an explicit limit, such as “Max 120 words. If over, shorten without losing facts.” Check the result, since a model can still miss a length constraint.

How to use this prompt

When to use it

Fixing format and structure issues

Before you use the output

  • •Fill in the variables with the facts and constraints you have.
  • •Check the output against your source material and revise any mistakes.
  • •Add relevant context when the first draft misses part of your task.

Expected output

Format analysis with template

Quick Info
Categoryanalysis
Output Length300-400 words
Web SearchNot Required
Frameworks
Communication FormatsOutput Structuring
Try PM Toolkit Calculators

Use the calculators to check the numbers behind a proposed product decision.