Plan the delivery
Project Plan Maker
Set out phases, milestones, owners and dates in one approved project plan you can share and print.
Your company
PNG, JPG, SVG or WebP. Max 2MB.
Document details
Project manager
Client sponsor
Phases, owners and dates
Plan sections
Plan notes
No signup required for your first 100 documents. Create an account to save history.
| Phase | Owner | Start | Finish | Milestone |
|---|---|---|---|---|
| 1. Mobilisation | PMO | 02 Mar | 06 Mar | Kick-off signed off |
| 2. Site survey & design | Engineering | 09 Mar | 27 Mar | Design approved |
| 3. Build & configure | Delivery | 30 Mar | 08 May | System configured |
| 4. Test & train | Delivery | 11 May | 22 May | UAT passed |
| 5. Go-live & handover | PMO | 25 May | 29 May | Handover accepted |
Reduce inbound pallet processing time by 40% and reach 99% stock-count accuracy within one quarter of go-live, measured from the current baseline report.
Phase 2 depends on warehouse access and current layout drawings. Phase 3 depends on ERP API credentials and hardware delivery. Phase 4 depends on nominated key users being released for training.
Hardware lead time (mitigate: order at design approval). Key-user availability during peak season (mitigate: schedule training in two half-day groups). Network coverage gaps in Warehouse 3 (mitigate: survey in Phase 2 and quote separately).
Weekly delivery call every Tuesday, written progress report each Thursday, steering review at the close of each phase. Change requests raised in writing and priced before work continues.
Dates assume a Sunday to Thursday working week and exclude public holidays. This plan is the agreed baseline; any change is issued as a new revision.
Project delivery workflow — step 2 of 6
Documents that usually come next
Continue the same workflow without re-typing your company details.
- Scope of Work Maker
Attach the detailed scope behind each phase.
- Timesheet Maker
Start recording hours against the planned tasks.
- Progress Report Maker
Report progress against this baseline each period.
Related on DocMak
Keep exploring DocMak
- Company Profile Makerbuild a UAE company profile for tenders, banks and clients
- Invoice Makerissue FTA-compliant tax invoices in AED
- Quotation Makersend professional UAE quotations in AED
- Proforma Invoice Makerissue proforma invoices for advance payments and LC openings
- Purchase Order Makerraise purchase orders to UAE suppliers
- UAE VAT Calculatoradd or remove 5% UAE VAT in seconds
GCC business document hub
Browse FTA-ready quotation, invoice, proforma and PO templates for every emirate.
Visit the UAE hubA project plan your client and your team both use
A project plan turns an agreed scope into a dated sequence of work with named owners. It is the document you baseline at kick-off and report against for the rest of the job. This maker keeps it to one readable sheet: phases with start and finish dates, milestones, owners, dependencies, risks and the governance rhythm — meetings, reporting and approvals.
It suits contracting, fit-out, IT rollout, marketing and consultancy work across the UAE and GCC, where the plan often travels with the proposal as an annexe. Edit each phase in the form and watch the printable plan build beside it.
- Phase table with owner, start date, finish date and milestone
- Dependency and risk sections you can rewrite for your project
- Governance section for meeting cadence, reporting and approvals
- Revision number and baseline date printed on the document
- Branded PDF export ready to attach to a proposal or contract
How to write a project plan
- 1
Break the work into phases
Group the scope into four to eight phases that each end in something the client can see or accept.
- 2
Add milestones, owners and dates
Give every phase a named owner, a start and finish date and the milestone that proves it is done.
- 3
Record dependencies and risks
Note what each phase waits on and the two or three risks most likely to move the dates.
- 4
Baseline and circulate
Export the PDF as your baseline, then report against it with a progress report each period.
Frequently asked questions
What is the difference between a project plan and a scope of work?+
A scope of work defines what is included, excluded and how work is accepted. A project plan defines when it happens, in what order and who owns each part. Most delivery teams issue both: the scope for agreement, the plan for execution.
How detailed should a project plan be?+
Detailed enough that a phase can slip without the whole plan being rewritten. In practice that means phase-level dates with named owners and milestones, not a task list of hundreds of rows. Keep daily task detail in your tracker and use the plan as the agreed baseline.
Do I need a project plan for a small job?+
For anything longer than a few weeks or involving more than one party, yes. A one-page plan with five phases, dates and owners prevents most of the disputes that arise when an interim delivery date was only ever agreed verbally.
How do I handle changes to the plan?+
Keep the original as your baseline, issue a revised plan with a new revision number, and note in your next progress report what moved and why. Changes that affect price or deliverables should go through a written variation to the scope of work.
Project Plan guide, templates and country rules
Everything that pairs with the project plan generator — the step-by-step guide, the templates businesses use alongside it, and the GCC rules covering local project plan requirements.
Matching guide
Learn how to write a project plan
Related templates
Templates used with a project plan
Country rules