Project plan template for firms
By Tom Hunt · Updated October 2026
A project plan turns the scope in your SOW into a timeline everyone can see - phases, milestones, who owns what, and the dates that keep it honest. It's what you build right after the kickoff. Copy it below, or run it live in a branded client portal.
0/3 filled - the rest of the [prompts] you finish in your copy.
PROJECT PLAN Project: [project name] Client: [Client name] Owner: [name] Prepared by [Agency name] Start: [date] Target finish: [date] GOAL [One sentence: the outcome this project delivers.] PHASES & MILESTONES | Phase | Key milestone / deliverable | Owner | Due date | Status | |--------------|-----------------------------|---------|----------|----------| | Discovery | [brief approved] | [who] | [date] | [ ] | | Design | [concepts signed off] | [who] | [date] | [ ] | | Build | [deliverable shipped] | [who] | [date] | [ ] | | Launch | [go live] | [who] | [date] | [ ] | DEPENDENCIES - [What each phase needs before it can start - e.g. "assets from client by [date]"] WHO DOES WHAT - Agency: [owners by role] - Client: one approver - [name]; feedback within [3] business days RISKS & MITIGATIONS - [Risk] -> [how we'll handle it] HOW WE TRACK IT - [Weekly status / live status page]; changes go through a change order.
pick a version, copy it, or download as .docx or .pdf - then make it yours.
How to fill it in
Plan in phases
Group the work into a handful of phases with a clear milestone each - it's easier to track than a flat task list.
Every milestone has an owner and a date
A milestone with no owner or date isn't a plan, it's a wish. Name both.
Surface dependencies
Note what each phase needs before it can start - the client asset due-dates are usually the hidden critical path.
Make it visible
A plan only you can see isn't shared. Put it where the client can check status without asking.
Route changes through a change order
When the plan moves, capture it - a change order keeps the timeline and budget honest.
A filled-in project plan
A realistic, filled-in version - so you can see what good looks like before you start.
PROJECT PLAN Project: Brand refresh Client: Acme Roasters Owner: Maya Prepared by Northwind Studio Start: 14 Mar 2026 Target finish: 30 Apr 2026 GOAL A refreshed identity + one-page guide, ready for the Q3 packaging rollout. PHASES & MILESTONES | Phase | Key milestone | Owner | Due date | Status | |-----------|--------------------------|-------|----------|--------| | Discovery | Brief approved | Maya | 17 Mar | [x] | | Design | 2 logo concepts presented| Theo | 28 Mar | [x] | | Refine | Final logo signed off | Theo | 18 Apr | [ ] | | Handover | Brand guide delivered | Maya | 25 Apr | [ ] | DEPENDENCIES - Existing brand assets from Acme by 17 Mar (received) WHO DOES WHAT - Agency: Maya (account), Theo (design) - Client: approver Dana; feedback within 3 business days RISKS & MITIGATIONS - Q3 deadline is fixed -> built a week of buffer before handover. HOW WE TRACK IT - Live status page; scope changes via a signed change order.
Common mistakes
- A flat task list with no phases - impossible to see where the project actually is.
- Milestones with no owner or date, so nothing is anyone's responsibility.
- Ignoring client dependencies, then blaming the slip on yourself when their assets are late.
- A plan locked in a spreadsheet the client never sees - so they ask 'any update?' anyway.
- Letting the plan drift without a change order, so scope and timeline quietly diverge.
A plan the client can actually see
A plan in a spreadsheet only you open isn't a shared plan. Forge puts the timeline, milestones and status in a branded client portal the client checks anytime - so 'where are we?' answers itself and the project stays on track.
Frequently asked questions
What should a project plan include?
The goal, phases and milestones with owners and dates, dependencies, who approves work, key risks, and how progress is tracked.
What's the difference between a project plan and a SOW?
The SOW is the contract - scope, deliverables and fees. The project plan is the schedule that delivers it - phases, milestones, owners and dates.
How detailed should a project plan be?
Detailed enough that everyone knows the next milestone, its owner and date - not a 200-line Gantt chart nobody updates.