You can turn a messy pile of meeting notes, voice memos, or bullet points into a clear project brief by feeding those raw notes to an AI model along with a specific brief structure to fill in, rather than asking it to “clean this up” and hoping it guesses the right format. The notes almost always contain the actual information a brief needs — the goal, the constraints, who’s involved, roughly when it’s due — just scattered out of order and mixed with irrelevant tangents. The model’s job is extraction and structuring, not invention, which is exactly why you should never let it fill gaps with guesses.
What Should a Project Brief Actually Contain?
Asana’s own guidance on project briefs recommends four core elements: background information explaining why the project exists, objectives and success metrics stated in specific, measurable terms, a timeline with key milestone dates, and a description of the target audience the project serves. Asana also recommends keeping the whole document to one page or less, so it stays a quick-reference document rather than something stakeholders have to dig through. That structure is exactly what you should hand an AI model as the template to fill from your notes.
How Do You Prompt AI to Extract a Brief From Raw Notes?
Paste your raw notes in full and give the model the exact structure to extract into: “Here are my raw notes from a project kickoff conversation. Extract them into a one-page project brief with these sections: Background, Objectives & Success Metrics, Timeline, and Target Audience. Only include information that’s actually present in the notes — if a section is missing information, write ‘Not yet defined’ instead of guessing or inventing details.” That last instruction is the one people skip, and it’s the one that prevents the model from confidently fabricating a deadline or a metric that was never actually discussed.
How Do You Handle Notes From Multiple Sources?
When your notes come from more than one meeting or person and contain contradictions — two different deadlines mentioned, say — ask the model to flag conflicts instead of silently picking one: “If you find conflicting information across these notes (for example, two different dates for the same milestone), list both versions under that section and mark it as needing clarification, rather than choosing one automatically.” This turns a potential silent error into a visible action item you can resolve with a quick follow-up question.
How Do You Turn the Brief Into Next Actions?
Once the brief itself is drafted, a second, separate prompt works better than asking for everything at once: “Based on this project brief, list the first 5 concrete action items needed to move this project from brief to kickoff, each with a suggested owner role (not a specific person) and rough timing relative to the project start.” Splitting brief-writing and action-item generation into two prompts keeps each output focused and easier to review than one long response trying to do both jobs.
Frequently Asked Questions
What if my notes don’t mention a clear objective or success metric?
Let the AI flag that gap rather than inventing a metric. A brief that honestly says “objective not yet defined — needs stakeholder input” is more useful than one with a plausible-sounding but made-up success metric, since the fabricated version can quietly become the team’s actual target if nobody double-checks it against what was really discussed.
Should the brief be written by AI or just organized by AI?
Organized is the safer framing for how to prompt it, even if the output reads as clean prose. Ask explicitly for extraction and structuring of what’s already in your notes rather than “writing” a brief, since that framing makes it more likely the model sticks to your actual input instead of generating generic project-brief boilerplate that sounds right but doesn’t reflect your specific situation.
How long should the final brief be?
Aim for one page, in line with Asana’s own recommendation. If your extracted brief runs much longer than that, ask the model to condense each section to 2-3 sentences and move any additional detail to a linked or attached appendix — a brief that’s too long to skim defeats its own purpose as a quick-reference document.
For the structure this prompt template is based on, see Asana’s own guide to writing a project brief. Once your brief is drafted, our guides to turning meeting notes into action items and weekly planning and task prioritization prompts cover the next steps once the project is underway.
Featured image by Shixart1985, licensed under CC BY 2.0, via Wikimedia Commons.
