A useful project plan is not a document that sits untouched after a kickoff meeting. It is a working guide that helps a team understand what must be delivered, who is responsible, when decisions are needed and how changes will be handled.
For people managing projects alongside their usual workplace responsibilities, the planning process can feel complicated. The practical approach is to make the plan detailed enough to guide action, while keeping it simple enough for the team to use. The following steps can be adapted to small internal projects, client work, process improvements and other workplace initiatives.
Free project plan templates in Word and Excel
Use these two files together to plan a small workplace project. The Word template covers the project purpose, scope, deliverables, acceptance, resources, communication and approval. The Excel tracker organises tasks, owners, dates, dependencies and completion evidence. Both include a fictional office induction guide example. No email address is required.
- Download the Project Plan Template (Word .docx) — two pages to complete plus a completed example.
- Download the Project Plan Task Tracker (Excel .xlsx) — a blank task sheet and a separate example sheet.
How to use the project planning templates
- Agree the objective, scope and acceptance criteria in Word with the sponsor or approver.
- Break each deliverable into tasks in Excel and assign an owner, start date, due date and dependency.
- Review progress regularly, record completion evidence and obtain approval before changing scope, budget or key dates.
- Confirm acceptance and record who will receive the outputs and any outstanding actions.
The Excel duration column calculates calendar days including the start and due dates, weekends and public holidays. It flags reversed dates. Dependencies are recorded for manual review; the tracker does not automatically reschedule tasks.
Example project sequence
| Milestone | Fictional example |
|---|---|
| Agree the scope | Confirm the induction guide content and acceptance criteria by 2 October. |
| Review the draft | Collect reviewer comments by 9 October. |
| Pilot and hand over | Test with two supervisors and obtain sponsor acceptance by 16 October. |
Use the free Project Risk Register for ongoing risk reviews, or browse all free workplace templates and checklists.
1. Clarify the purpose and expected outcome
Begin by writing a short explanation of why the project exists. Describe the workplace problem, opportunity or requirement it addresses, and the outcome the organisation expects. A clear purpose helps people make consistent decisions when priorities compete.
Then define what successful completion will look like. Wherever possible, use observable outcomes rather than broad statements. For example, “introduce a new staff induction process by 30 November” is clearer than “improve onboarding”. You can then identify how completion will be confirmed, such as approval from a sponsor, delivery of agreed materials or completion of a system change.
2. Define the project scope
Scope describes what the project will and will not deliver. List the major outputs, boundaries and exclusions. This reduces the risk of people holding different assumptions about the work.
A practical scope statement can answer four questions:
- What products, services or changes will the project deliver?
- Which teams, locations, customers or systems are included?
- What is specifically outside the project?
- Who has authority to approve a change to the scope?
Scope may evolve when new information appears. The aim is not to prevent change, but to make proposed changes visible so their effects on time, cost, quality and resources can be considered before approval.
3. Break the work into manageable activities
Once the scope is clear, divide each deliverable into smaller activities. Each activity should be specific enough that a person can estimate the effort, understand the expected result and identify when it is complete.
Arrange the activities in a logical sequence. Some can happen at the same time, while others depend on earlier work. Identifying these dependencies helps prevent avoidable delays. It also shows which activities are likely to affect the overall completion date if they fall behind.
For a small project, a spreadsheet or shared task board may be sufficient. More complex projects may require scheduling software. The tool matters less than ensuring the information is current, accessible and understood by the people using it.
4. Assign responsibilities and decision points
Every activity should have a clear owner. This does not mean that one person performs all the work; it means one person is accountable for coordinating the activity and reporting its status.
Record who will complete the work, who will approve it, who needs to be consulted and who should be kept informed. Also document important decision points. Teams can lose time when a task is technically complete but no one knows who can approve the next step.
Before finalising assignments, check availability with the people involved. A plan based on assumed capacity is unlikely to remain realistic once normal workloads, leave and competing priorities are considered.
5. Build a realistic schedule
Estimate how long each activity will take and place it in the schedule according to its dependencies. Include milestones for major deliverables, reviews, approvals and handovers. Milestones make progress easier to communicate without requiring stakeholders to read every line of the plan.
Avoid treating every date as equally fixed. Identify genuine deadlines, preferred dates and tasks with some flexibility. Add reasonable time for review and rework where quality checks or stakeholder approval are required. A schedule should support informed coordination, not create an appearance of certainty that the team cannot maintain.
6. Identify resources, costs and quality requirements
List the people, equipment, information, suppliers and budget needed to complete the work. Confirm when resources will be available and note any approval or purchasing lead times. If a specialist is required for only one part of the project, schedule that involvement early rather than assuming the person will be free when needed.
Define quality requirements for each important deliverable. This might include technical standards, internal procedures, review criteria, testing or stakeholder acceptance. Clear quality criteria help the team understand what “finished” means and reduce disagreement near the end of the project.
7. Record risks, issues and responses
A risk is an uncertain event that could affect the project; an issue is a problem that is already occurring. Record them separately and review both regularly.
For each significant risk, describe the possible cause and effect, assess its likelihood and consequence, nominate an owner and plan a response. Responses may reduce the likelihood, reduce the impact, transfer responsibility or accept the risk with appropriate monitoring. Keep the process proportionate: a short, actively reviewed risk register is more useful than a long list that no one updates.
For a step-by-step method covering identification, assessment, ownership, responses and monitoring, read our practical guide to project risk management.
8. Plan communication and reporting
Different stakeholders need different information. A project team may need weekly task updates, while a sponsor may only need a concise summary of progress, decisions, budget and major risks.
For each audience, decide what information they require, who will provide it, how it will be shared and how often. Include a clear path for escalating urgent issues and obtaining decisions. Communication planning is particularly important when people work across locations or combine project duties with other roles.
9. Establish change control
Even well-planned projects change. Create a simple method for recording proposed changes and assessing their effect before work proceeds. The record should explain the request, reason, impact, decision and person who approved or declined it.
This protects the team from informal additions that consume time or budget without a corresponding adjustment to expectations. It also creates a useful history when stakeholders ask why the final outcome differs from the original plan.
10. Review the plan with the team
Before work begins, review the plan with the people responsible for delivery and approval. Ask whether the sequence is workable, estimates are reasonable, responsibilities are clear and major risks have been recognised. People are more likely to use a plan when they have had an opportunity to test its assumptions.
During delivery, update the plan when approved changes occur and compare actual progress with the agreed baseline. Keep version control simple and make sure the team knows where the current plan is stored.
A practical project plan checklist
Before approving the plan, confirm that it includes:
- a clear purpose and measurable outcome;
- deliverables, boundaries and exclusions;
- activities, dependencies, milestones and realistic dates;
- responsibilities and approval points;
- resources, costs and quality requirements;
- current risks, issues and planned responses;
- communication and reporting arrangements; and
- a process for assessing and approving changes.
Project planning is a workplace capability that improves through practice, review and feedback. If you would like to explore structured learning in this area, review the BSB50820 Diploma of Project Management. You can also read about how project management skills support workplace capability, see how online study works at WorkForward, or contact the WBS course advice team to discuss the course information and entry requirements.
This article provides general educational information. Workplace requirements, project methods and organisational procedures vary. Confirm the requirements that apply to your role and project.