I used to write content briefs the hard way. I would open a blank document, stare at it for ten minutes, then produce a page of notes that mixed the goal, the audience, the tone, the length, and half-formed ideas about structure. By the time I finished, I had a brief that was thorough enough to feel responsible and messy enough that I still had to reinterpret it when I sat down to write.
The prompt below grew out of that frustration. It is short on purpose. It forces the three variables that actually change from one piece of content to the next—audience, goal, and format—into clear slots, and it leaves everything else out until those three are settled. The result is a brief I can hand to myself (or to a collaborator) and start using without a second translation step.
The Baseline Prompt
Create a content brief from the notes below.
Fill in these three sections clearly:
Audience
Who this is for and what they already know or struggle with.
Goal
What the finished piece should help the reader do, decide, or understand.
Format
The type of content, approximate length or structure, and any non-negotiable elements.
Use only information present in the notes. If a section cannot be filled from the notes, leave it blank and mark it “Needs input.” Do not invent audience details, goals, or format requirements.
That is the entire core. I paste rough notes, a voice memo transcript, or even a few bullet points underneath and run it. The output is a structured starting point, not a finished strategy document.
Why These Three Variables
Most briefs fail because they treat every possible consideration as equally important. Tone, SEO keywords, brand voice, calls to action, examples, and references all get mixed together before the basics are clear. When the audience, the goal, and the format are still fuzzy, the extra details just create more places for the brief to drift.
Audience tells you what knowledge you can assume and what language will land.
Goal tells you what success looks like for the reader and, by extension, for the writer.
Format tells you the container so you do not write an essay when you needed a checklist, or a checklist when you needed a narrative.
Once those three are explicit, adding tone guidance or example requirements becomes a controlled next step instead of another layer of confusion.
How I Use It in Practice
I keep the process deliberately light.
I dump everything I know so far into a rough note—bullet points, half-sentences, links, constraints, anything.
I paste the baseline prompt above the note and run it.
I read the three sections and immediately correct anything that drifted or got over-specified.
Only after the three sections feel accurate do I decide whether the brief needs one more variable (tone, length limit, must-include examples, etc.).
The whole cycle usually takes less than ten minutes for a straightforward piece. The time saved shows up later, when I sit down to write and do not have to re-decide what the piece is supposed to do.
A Realistic Before-and-After
Rough notes I started with:
Need something for the site about why short prompts are better. People who already use ChatGPT for work but get inconsistent results. Should feel practical, not academic. Maybe 1,500–2,000 words. Include the “one variable at a time” idea. Don’t make it sound like I’m attacking long prompts, just show the testing method. Want readers to try it on one of their own prompts the same day.
Output from the baseline prompt (after light human edit):
Audience
Professionals and freelancers who already use AI tools for work tasks and are frustrated by inconsistent results. They are not looking for beginner definitions of prompting; they want a method they can apply to prompts they already have.
Goal
Help the reader understand why starting with a short, testable prompt produces more reliable improvement than starting with a long, fully loaded one, and give them a simple way to try the method on one of their own prompts immediately.
Format
Blog post, approximately 1,500–2,000 words. Practical tone. Must include the one-variable-at-a-time testing approach. Should not frame long prompts as wrong, only as harder to diagnose and improve.
The structured version did not add new ideas. It simply forced the existing ideas into the three slots that matter most for writing. That clarity is what I was missing when I worked from the original pile of notes.
Useful One-Variable Extensions
I treat every addition as optional and testable. Here are the three I reach for most often, each added alone and only when the baseline brief is already solid.
Tone guidance
When the piece needs a more specific voice than my default:
Add a short Tone section that describes how the piece should sound, using concrete contrasts (for example, “direct but not blunt” or “calm and practical, not enthusiastic”).
Must-include elements
When certain examples, data points, or structural moves are non-negotiable:
Add a Must Include section that lists only the elements that have to appear, with no extra commentary.
Length or scope limit
When the format section needs tighter boundaries:
Replace the general format description with a hard limit (word count, number of sections, or “one main example only”).
I never add all three at once. I add one, regenerate or edit, and keep the addition only if it reduces later confusion rather than creating new decisions.
Common Failure Modes and Simple Fixes
The prompt invents a more specific audience than the notes support.
The “use only information present” and “Needs input” instructions usually catch this. When they do not, I strengthen the rule: “If audience details are thin, keep the description general and mark specifics as Needs input.”
The goal becomes a list of writer intentions instead of reader outcomes.
I add one clarifying line for the next run: “State the goal in terms of what the reader should be able to do or understand after reading.”
The format section drifts into structure or outline.
I tighten the instruction: “Describe only the content type, length, and non-negotiable elements. Leave section-by-section structure out of the brief.”
These fixes stay temporary. Once the problem stops appearing, I remove the extra sentence so the baseline remains short.
When to Use a Different Approach
This prompt is built for the common case: you have rough material and need a clear, shareable starting brief. It is less useful when:
The audience, goal, and format are already decided and documented elsewhere
You are doing exploratory writing where the goal itself is still being discovered
The piece is so short (a social post, a quick email) that a formal brief adds more overhead than value
In those situations I skip the prompt and work directly from the existing decisions or from a single sentence of intent.
Building Your Own Version
Copy the baseline exactly and use it on two or three real sets of notes this week. After each use, look at the places where you had to edit the output. Those repeated edits are candidates for a single new instruction. Add the instruction, test it against the original baseline, and keep it only if the improvement is obvious across different kinds of content.
The goal is not a perfect brief generator. The goal is a short, reliable method that turns messy notes into three clear decisions you can write from. Everything beyond that is optional.
Start with the smallest useful version—the three-variable core. Let the audience, goal, and format settle first. Add complexity only when the work itself proves you need it. That sequence has produced cleaner briefs and faster drafting than any longer template I have tried.
No notes on this sheet yet.