ChatGPT
How to Write Better ChatGPT Prompts With a 5-Line Brief
Turn a vague ChatGPT request into a clear five-line brief covering the outcome, audience, context, constraints, and output format.
A long prompt is not automatically a good prompt. Many people put the task, background, examples, preferences, and formatting instructions into one large paragraph. ChatGPT then has to guess which details matter most.
A better approach is to separate the request into five lines:
- Outcome
- Audience
- Context
- Constraints
- Format
Then ask the AI to repeat the brief before it starts. This catches missing or conflicting information while it is still easy to fix.
Line 1: define the outcome
Describe the result you need, not only the activity.
Weak:
Write about our product launch.
Better:
Outcome: Write an announcement that explains the new feature and encourages existing customers to try it this week.
The second version gives the model a destination. It can judge whether each sentence supports the intended result.
Use one primary outcome. If you need a launch email, landing page, social posts, and support article, create separate requests or ask for an ordered plan first.
Line 2: name the audience
The same information should sound different for a beginner, a technical buyer, a manager, or an existing customer.
Audience: Small-business owners who use spreadsheets but have never used workflow automation.
Useful audience details include:
- What the reader already knows
- The problem they care about
- Their likely objection
- The action they should be able to take
Avoid broad labels such as “everyone” or “business users.” A narrow audience usually produces clearer examples and more useful language.
Line 3: provide relevant context
Context is the information the model should use to complete the task. Include facts, approved source material, or the situation surrounding the request.
Context: The feature turns meeting notes into decisions, owners, deadlines, and risks. It is available to current customers at no additional cost.
Only include context that changes the answer. A large information dump can hide the important details.
When the task depends on a document, paste or attach the approved source and say that the answer must stay within it. Remove passwords, private customer information, confidential workplace data, and other details that should not be shared.
Line 4: state the constraints
Constraints define the boundaries of an acceptable result.
Constraints: Use plain English, keep it under 180 words, avoid exaggerated claims, and do not invent customer results.
Common constraints include:
- Length
- Tone
- Facts that must or must not appear
- Words to avoid
- Privacy and safety requirements
- Source or evidence rules
- A deadline or reading level
Use hard rules only for real requirements. Too many unnecessary restrictions can make the result stiff or contradictory.
Line 5: specify the output format
Tell the model what the finished answer should look like.
Format: Return a subject line, a preview sentence, a three-paragraph email, and one button label.
The format can be a checklist, table, email, JSON object, step-by-step tutorial, or another structure. Name the fields you need so you do not have to reorganize the answer later.
Ask ChatGPT to repeat the brief
Before asking for the final result, add this instruction:
Repeat the five-line brief in your own words. Identify any missing information or conflict. Ask only the questions that could materially change the result. Do not create the final answer until I confirm the brief.
This creates a short review step. You can correct a wrong assumption before it spreads through the full output.
For a low-risk, simple task, you can let the model continue automatically when no important information is missing:
Repeat the brief first. If no material information is missing, continue with the requested output. If a missing detail could change the result, stop and ask one concise question.
Complete copy-and-paste template
Outcome: [Describe the result I need and what it should help accomplish.]
Audience: [Describe who will use or read it, what they know, and what they care about.]
Context: [Provide the facts, source material, situation, and examples that should guide the answer.]
Constraints: [State length, tone, evidence, privacy, accuracy, and content boundaries.]
Format: [Describe the exact structure and fields of the final output.]
First, repeat this brief in your own words. Identify missing information or conflicts. Ask only questions that could materially change the result. After I confirm, create the final output and check it against every line of the brief.
Example: turn notes into an executive update
Outcome: Turn these project notes into an update that helps leadership decide whether to move the launch date.
Audience: Non-technical executives who need the decision, evidence, risk, and next action quickly.
Context: Use only the notes below. Separate confirmed facts from assumptions. [Paste approved notes.]
Constraints: Maximum 250 words. Do not invent dates, owners, costs, or progress. Mark missing evidence clearly.
Format: Return Summary, Evidence, Risks, Decision Needed, and Next Actions with owners only when the notes provide them.
Repeat the brief and identify any material gap before writing the update.
Review the result
Do not assume a well-formatted answer is accurate. Check:
- Does it achieve the stated outcome?
- Is the language right for the audience?
- Did it use the supplied context instead of inventing facts?
- Did it obey every meaningful constraint?
- Is the output in the requested format?
For important work, verify claims against the original source and have the appropriate person review the result.
The five-line brief is useful because it is short enough to reuse. Save the template, change the five fields for each task, and improve the brief when the result exposes a missing requirement.