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

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

Example for: a web portal redesign statement of work

1.0 Discovery and Architecture
  • 1.1 Stakeholder and User Research

    • 1.1.1 Conduct 6 internal stakeholder interviews
    • 1.1.2 Compile user persona document and user journey maps
  • 1.2 Technical Architecture Definition

    • 1.2.1 Draft system architecture specification
    • 1.2.2 Complete database schema design
2.0 Design and Prototyping
  • 2.1 Wireframing and UX Design

    • 2.1.1 Create mid-fidelity wireframes for core flows
    • 2.1.2 Run usability tests with 5 target users
  • 2.2 Visual Design System

    • 2.2.1 Build component library in Figma
    • 2.2.2 Deliver high-fidelity click-through prototype
3.0 Implementation and Integration
  • 3.1 Frontend Development

    • 3.1.1 Set up Next.js boilerplate and design system components
    • 3.1.2 Build authenticated user dashboard views
  • 3.2 API and Backend Development

    • 3.2.1 Implement REST API endpoints for user profiles
    • 3.2.2 Configure PostgreSQL database and ORM migrations
Key Phase Deliverables
  • Discovery: Approved technical architecture document and persona pack.
  • Design: Sign-off ready Figma UI kit and interactive prototype.
  • Implementation: Fully integrated staging environment passing core integration tests.
Phase Gate Sign-Off Criteria
  • Gate 1: Client sign-off on architecture document and schema before starting UI design.
  • Gate 2: Stakeholder sign-off on interactive prototype before committing engineering sprints.
  • Gate 3: 95% pass rate on integration test suite before code freeze.
Next Steps

Assign work package leads and schedule the Phase 1 kickoff meeting.

Written by AI from this prompt. Your results will vary.

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.

Keep exploring

More in Project Management
Project Management

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.

Project Management

Draft a formal project charter

Create a clear, authoritative project charter defining scope boundaries, measurable success metrics, and sponsor decision rights.

Project Management

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.