Research notes rarely arrive in a form ready for other people to read. They are usually a mix of copied sentences, half-formed observations, links, and scattered bullet points. Turning that material into a coherent first draft is one of the most common slow points in ordinary knowledge work.
After testing multiple approaches, I settled on one prompt structure that consistently gets me from messy notes to a usable draft without inventing claims or drifting off the source. I use it for internal summaries, short research briefs, and the first version of longer documents.
Why Generic Prompts Fall Short
“Summarize these notes” is too open
The tool decides what matters, how long the result should be, and what tone to use. The output often looks tidy and still misses the points I actually need.
“Write a report based on these notes” invites invention
When the instructions are broad, models fill gaps with plausible-sounding statements that were never in the source. That creates extra verification work.
No stated audience or job for the text
Without knowing who will read the draft and what they need to do with it, the tool defaults to generic professional language that I then have to rewrite.
The Prompt Structure I Use
I keep the same five parts every time. The whole thing takes about two minutes to fill in.
1. Role and real context
One sentence that sets the situation.
Example:
“You are helping a marketing specialist turn rough research notes into a clear internal first draft.”
2. Exact job and output shape
State what the finished piece should look like and how it will be used.
Example:
“Create a first draft of 400–500 words with these sections: Key Findings, What Matters for Our Work, Open Questions. Use short paragraphs and bullets where they improve clarity.”
3. Hard constraints
List the non-negotiables.
Example:
“Use only information present in the notes. Do not add external facts, examples, or interpretations. Keep the tone plain and internal. If the notes are unclear on a point, mark it as unclear instead of resolving it.”
4. The source material
Paste the rough notes exactly as they are. Do not clean them first—that is part of what the prompt should handle.
5. Success criteria
Tell the tool how you will judge the draft.
Example:
“A good draft will let a colleague understand the main points and the remaining uncertainties without needing to read the original notes.”
Complete Example Prompt
Here is a real version I used recently (details generalized):
“You are helping a marketing specialist turn rough research notes into a clear internal first draft.
Create a first draft of 400–500 words with these sections: Key Findings, What Matters for Our Work, Open Questions. Use short paragraphs and bullets where they improve clarity.
Use only information present in the notes. Do not add external facts, examples, or interpretations. Keep the tone plain and internal. If the notes are unclear on a point, mark it as unclear instead of resolving it.
A good draft will let a colleague understand the main points and the remaining uncertainties without needing to read the original notes. Notes:
[pasted rough bullets, copied sentences, and fragmented observations]”
What the Output Usually Gives Me
A logical structure that follows the sections I requested
Language that stays close to the source material
Clear flags when the notes themselves are thin or contradictory
A draft that is ready for human editing instead of full rewriting
The Human Work That Still Remains
Accuracy check against the notes
I still read the draft side-by-side with the original material. The constraint reduces invention, but it does not eliminate the need to confirm.
Emphasis and relevance
The tool organizes what I give it. It cannot know which finding is most important for the current project or the current audience. That judgment stays with me.
Final tone and length
Even with good instructions, I usually tighten a few sentences and cut residual softness before the draft is ready to share.
When This Prompt Works Best
The notes are incomplete or messy but contain the core facts
I need a first draft quickly rather than a polished final document
The risk of invented details matters more than perfect prose
It works less well when the notes are extremely thin or when the real task is analysis that goes beyond what the source material supports. In those cases the prompt correctly surfaces the gaps instead of hiding them—which is still useful.
Quick Checklist Before Hitting Enter
Role and context stated
Exact output shape and length defined
Hard constraints against invention included
Raw notes pasted
Success criteria clear
If all five are present, the first draft is usually close enough to edit instead of restart.
I tried it so you don’t have to waste your afternoon.
No notes yet — be the first to inscribe one.