Turn a statement of work into a WBS
Convert complex, unstructured contract terms into a phased work breakdown structure with clear milestones and acceptance criteria.
Prompt
Act as a technical project manager. Review the provided statement of work excerpt and convert it into a structured, phased Work Breakdown Structure (WBS).
Rules:
- Group tasks into clear sequential phases (such as Discovery, Build, Testing, Deployment).
- Use standard WBS numbering (e.g., 1.0, 1.1, 1.1.1).
- Ensure every terminal task is actionable and has a clear physical or digital deliverable.
- Define clear acceptance criteria and formal sign-off gates at the close of each phase.
Output format:
Phase breakdown with numbered hierarchical tasks
Key Phase Deliverables list
Phase Gate Sign-Off Criteria for each phase
Next steps for team assignment
My statement of work excerpt is below:Example output
Paste this prompt into ChatGPT, Claude, or Gemini, then paste your contract scope or SOW text at the end. After running it, ask the model to estimate durations in working days for each terminal task.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Analyze timeline and budget trade-offs for scope requests
Turn vague stakeholder feature requests into clear trade-off scenarios. Use this when clients or leaders request additions without considering cost or delay.
Audit project estimates for hidden optimism bias
Spot hidden assumptions, under-budgeted handoffs, and optimistic delivery timelines within detailed project task breakdowns.
Draft a one-page project kickoff brief
Turn fragmented launch details into an aligned single-page kickoff document. Ideal for aligning cross-functional teams before delivery starts.
Draft a formal project charter
Create a clear, authoritative project charter defining scope boundaries, measurable success metrics, and sponsor decision rights.
Write a post-kickoff scope alignment email
Draft a clear, polite recap email to a client immediately after a kickoff call. Establishes agreed deliverables, out-of-scope boundaries, and upcoming approvals.
Flag unstated project assumptions before kickoff
Surface hidden assumptions about resources, data access, and vendor dependencies before projects stall mid-flight.
- Review a project schedule for bottlenecks
- Create a shared milestone alignment brief across teams
- Draft a formal deliverable sign-off request email
- Structure vague project lessons into searchable entries
- Turn engineering updates into marketing launch timelines
- Build an executive steering committee deck outline