Project plan template

Business templates

Plan a project’s scope, milestones, tasks, roles, risks and reporting in an editable Word document. It suits job seekers, students, small business owners, committee members, landlords and tenants. You get a free template with clear sections, working tables and prompts to replace. Fill it in and share it with everyone involved.

Download Word template Free · .docx · 39 KB · edit in Word, Google Docs or WPS

What's in the template

Project Plan Template

Use this plan to agree what the project will deliver, who will do the work, and how progress will be reported.

Project details

Project name	[project name]
Plan owner	[name or role]
Sponsor or client	[name or organisation]
Location	[town, municipality or work site]
Plan date and version	[date and version]
Plan status	[draft, approved or other status]

Purpose and intended outcome

Need or problem	[briefly explain what the project addresses]
Intended outcome	[describe what will be different when the work is complete]
How success will be recognised	[observable result or evidence]

Scope

List the work included in the project and work that sits outside it. Record assumptions that could affect what the team can deliver.

Area or activity	Included work	Excluded work or assumption
[area or activity]	[work included]	[work excluded or assumption]
[area or activity]	[work included]	[work excluded or assumption]

Deliverables and milestones

Describe each result, how it will be accepted, who owns it, and its target date.

Deliverable or milestone	Acceptance evidence	Owner	Target date	Status
[example: venue confirmed]	[example: written confirmation received]	[example: event coordinator]	[example: agreed date]	[example: not started]
[deliverable or milestone]	[evidence of acceptance]	[owner]	[target date]	[status]
[deliverable or milestone]	[evidence of acceptance]	[owner]	[target date]	[status]

Task schedule

Break the work into tasks. Note dependencies so the team can see what must happen first.

Task	Related deliverable	Depends on	Owner	Start date	Finish date	Status
[example: contact venue about access]	[example: venue confirmed]	[example: venue shortlist]	[example: event coordinator]	[example: agreed date]	[example: agreed date]	[example: not started]
[task]	[deliverable]	[dependency or none]	[owner]	[start date]	[finish date]	[status]
[task]	[deliverable]	[dependency or none]	[owner]	[start date]	[finish date]	[status]

Roles and decisions

Role	Person or organisation	Responsibilities	Decisions they can make
[role]	[name or organisation]	[responsibilities]	[decision authority]
[role]	[name or organisation]	[responsibilities]	[decision authority]
[role]	[name or organisation]	[responsibilities]	[decision authority]

Risks and responses

Record issues that could affect delivery. Use simple likelihood and impact descriptions that everyone understands.

Risk	Likelihood	Impact	Response or fallback	Owner	Review date
[example: venue becomes unavailable]	[example: medium]	[example: high]	[example: confirm a backup venue]	[example: event coordinator]	[example: review date]
[risk]	[likelihood]	[impact]	[response or fallback]	[owner]	[review date]
[risk]	[likelihood]	[impact]	[response or fallback]	[owner]	[review date]

Resources and estimated costs

Resource or item	Estimated amount in rand	Funding source	Person confirming	Status
[resource or item]	[amount in rand]	[funding source]	[name or role]	[status]
[resource or item]	[amount in rand]	[funding source]	[name or role]	[status]

Reporting and updates

Update or report	Audience	Frequency	Channel	Owner
[progress update]	[people who need the update]	[frequency]	[meeting, email or other channel]	[owner]
[decision or issue report]	[people who need the update]	[frequency or when needed]	[channel]	[owner]

Changes and decisions

Record changes that affect scope, dates, costs or responsibilities. Note who agreed to each decision and who needs to know.

Date	Change or decision	Reason	Agreed by	People to inform
[date]	[change or decision]	[reason]	[name or role]	[people or group]
[date]	[change or decision]	[reason]	[name or role]	[people or group]

Approval

Sign to confirm that the plan reflects the agreed work, responsibilities and reporting arrangements.

Project owner: [name and signature]

Sponsor or client: [name and signature]

Committee representative, if applicable: [name and signature]

Date: [date]

How to fill it in

Project details Enter the project name, owner, sponsor, location and plan details. Replace each bracketed prompt with agreed information.
Purpose and outcome Describe the need, intended result and evidence of success. Keep the outcome clear enough for the team to recognise.
Scope List the work included and excluded. Add assumptions that could change what the team can deliver.
Deliverables and schedule Define each deliverable and its acceptance evidence, owner and target date. Break the work into tasks and record dependencies, owners and status.
Roles and decisions Name each person or organisation responsible for a role. State which decisions they can make.
Risks and resources Describe likely risks and practical responses, then estimate needed resources and costs in rand. Record who will confirm each estimate.
Reporting and approval Choose the updates, audience, frequency and channel. Record changes and decisions, then collect the relevant approvals.

Tips before you send it

Keep scope exclusions explicit, especially work another person or supplier will handle.
Give every task and risk one named owner; shared ownership can hide follow-up.
Describe milestone evidence as something observable, such as an approved draft or completed handover.
Update task status and reporting together so readers see the same position.

Questions & answers

Can I use this plan for a community project?

Yes. It can organise a school, stokvel, neighbourhood or small business project. Adjust the roles and reporting to suit the group.

Can I change the headings and tables?

Yes. Add or remove rows and headings to suit the work. Keep decisions, owners and updates clear.

Who should approve the plan?

Agree the approvers with the people responsible for the work. A small project may need its owner and sponsor; a committee can include its chairperson.

Should I include a budget?

Include expected costs in rand when they affect a decision or delivery. Mark estimates clearly and record who will confirm them.

What should I do when plans change?

Update the affected task, milestone, risk or cost, then record the decision and tell people who rely on it. Keep an earlier copy if your group needs an audit trail.