Blog › Claude for Work › Part 3
How to Use Claude to Draft
a Project Plan in 10 Minutes
The first draft of a project plan is the hardest part. You're staring at a blank document trying to remember every section. Here's how to go from a brief description to a working first draft in one focused session.
The blank document problem
Every project manager has sat in front of a blank project plan template trying to remember all the sections, all the standard risks for this type of project, all the stakeholders they'll need to map, all the governance touchpoints that need to be scheduled. It's not that the knowledge isn't there - it's that pulling it all out, structured and sequenced, takes time that could be spent on the actual project.
Claude doesn't replace the project manager's judgment. It replaces the blank page. Give it enough context about the project and it'll produce a structured first draft covering scope, objectives, stakeholders, risks, milestones, and assumptions. You refine, fill in the specifics, and move on. The ten minutes isn't the whole job - it's the scaffolding that lets you do the rest of the job faster.
Before you start - what Claude needs to know
The quality of the plan is directly proportional to the quality of the brief.
Before prompting for a project plan, spend two minutes writing down the basics. You don't need a perfect brief - rough notes are fine. Claude will work with what you give it and flag where it's had to make assumptions.
What Claude needs
Project name and type
The problem it's solving
The desired outcome
Approximate timeline
Known stakeholders
Known constraints (budget, resources, dependencies)
Any known risks or issues already on your radar
What it'll generate
Project objectives
Scope (in and out)
Stakeholder map
High-level milestones
Risk register (top 5-8)
Assumptions log
Governance structure
Next actions
The prompts - section by section
Copy and adapt. Fill in the [brackets] with your project details.
Step 1 - Set the context first (do this once)
"I'm a project manager building a project plan. Here's the context: Project name: [name]. Type of project: [e.g. system implementation, process redesign, office relocation]. Problem being solved: [one paragraph]. Key stakeholders: [list names and roles]. Timeline: [start date to end date]. Budget: [if known]. Known constraints: [list anything that limits scope, resources, or approach]. Known risks already on my radar: [list any]. I'll ask you to build each section of the plan one at a time. For now, just confirm you've understood the context and ask me any clarifying questions."
Step 2 - Project objectives
"Draft the project objectives section. Write 3-5 SMART objectives (Specific, Measurable, Achievable, Relevant, Time-bound). Each should be one sentence. Flag any where I'll need to fill in the measurable target."
Step 3 - Scope
"Draft the scope section as two lists: In Scope and Out of Scope. 5-8 items in each list. Out of Scope should include things a stakeholder might reasonably assume are included but aren't. Flag any items you're uncertain about."
Step 4 - Stakeholder map
"Create a stakeholder table with columns: Name/Role, Interest in Project, Influence Level (High/Medium/Low), Engagement Approach. Use the stakeholders I mentioned. Add any I might have missed for a project of this type. Keep the Engagement Approach column to one sentence."
Step 5 - Milestones
"Draft a high-level milestone schedule. Use the timeline I gave you. List 6-10 milestones as a table with: Milestone name, Description (one sentence), Target date. Space them logically across the project lifecycle. Mark any dates you've had to estimate."
Step 6 - Risk register
"Create a risk register table with: Risk ID, Risk Description, Category (Technical/People/Schedule/Budget/External), Probability (H/M/L), Impact (H/M/L), Risk Rating (H/M/L), Mitigation Action, Owner (role only). Include the risks I mentioned plus any standard risks for this type of project. Aim for 8-10 risks."
Step 7 - Assumptions
"List the assumptions this project plan is based on. Include assumptions you've made in building the plan above, plus common assumptions for this type of project. Format as a numbered list. Flag any high-risk assumptions that should be validated early."
What Claude gets right and what it gets wrong
Know the limitations before you send anything to a sponsor.
What it gets right
Structure and completeness
Standard risks for common project types
PMBOK-aligned section coverage
Stakeholders you might have forgotten
Assumptions you've taken for granted
Consistent formatting throughout
What needs your input
Specific dates and durations
Organisation-specific processes
Political context and stakeholder dynamics
Budget figures and resource allocations
Regulatory and compliance specifics
Anything that requires institutional knowledge
The mental model: Claude produces the skeleton. You add the muscle. Review every section before sharing - not because the output is likely to be wrong in obvious ways, but because you know context that isn't in the prompt. The ten minutes produces a document you can work from. It doesn't replace the judgment that makes the plan actually fit the situation.
After the first draft
Three prompts for refinement.
Challenge it
"Review this plan as a sceptical executive sponsor. What questions would you ask? What's missing? What assumptions look risky?"
Pressure-test the risks
"Are there any risks I've rated too low given the context? What am I most likely underestimating?"
Executive summary
"Write a one-page executive summary of this plan for a steering committee. Objectives, scope, timeline, top 3 risks, what they're being asked to approve."
Done for NSW Government & Corporate
Templates ready to implement
Take the first cut of AI-generated information and drop it into your project documentation, where you can contextualise and customise it with confidential information inside your tenant. Every stage gate, every document.
fully calculated & dashboarded
Start with the context prompt
Copy Step 1 above, fill in your project details, and paste it into Claude. The rest follows from there.
Open Claude at claude.ai →Claude for Work - series
Part 1 - What Claude Actually Is
Part 2 - How to Write a Prompt That Doesn't Waste Your Time
Part 3 - How to Use Claude to Draft a Project Plan in 10 Minutes (you're here)
Part 4 - How to Use Claude for Stakeholder Updates (coming soon)
Part 5 - Is Claude Safe for Work Documents? (coming soon)