Project Management guide · Scheduling and time
Project Scheduling: Steps, Techniques and Example
Project scheduling is the process of working out which activities a project needs, the order they must happen in, how long each will take and who will do them, then turning that logic into a dated plan. This guide walks you through the steps, the main techniques, a worked example with real dates and the mistakes that make schedules fall apart.
Key takeaways
- A project schedule turns scope into ordered, estimated, resourced and dated activities.
- Build the logic first (activities and dependencies) and let the dates calculate; never type dates in by hand.
- The critical path shows the shortest possible duration and the activities where any delay moves the finish date.
- Check resource availability and calendars before you commit: a logically correct schedule can still be impossible to staff.
- Baseline the approved schedule, update it at a regular cadence and change the baseline only through change control.
What is project scheduling?
Project scheduling is the part of project planning that decides when each piece of work will happen. You list the activities needed to deliver the scope, link them in a logical sequence, estimate their durations, assign resources and calculate start and finish dates. The output, the project schedule, is the timetable the team works to and the baseline you measure progress against.
It helps to separate two ideas. The schedule model is the network of activities, dependencies, durations and calendars held in your tool. The schedule presentations are the views you produce from that model: a Gantt chart, a milestone list, a project timeline for executives or a network diagram. When people say "update the schedule", they should be updating the model, so every view stays consistent.
A good schedule does three jobs:
- Commitment: it gives the sponsor and customers dates they can plan around, such as a launch, a handover or a go-live.
- Coordination: it tells each person and supplier when their work is needed and what it depends on.
- Early warning: because the dates are calculated from logic, a slip in one activity shows its knock-on effect immediately, while there is still time to act.
Scheduling sits inside the wider discipline of project time management, alongside estimating and controlling progress, and it shares its inputs with cost and resource planning.
Project scheduling in the PMBOK Guide
PMI's *PMBOK Guide* has described scheduling in different ways over the years, and you will meet both views in exams and job descriptions.
Earlier process-based editions grouped scheduling into six processes: plan schedule management, define activities, sequence activities, estimate activity durations, develop schedule and control schedule. Many organisations and courses still teach these as the backbone of schedule management.
The *PMBOK Guide* Eighth Edition, which PMI published in November 2025, is organised around seven performance domains: governance, scope, schedule, finance, stakeholders, resources and risk. Schedule is one of these domains, and the guide again describes non-prescriptive processes that you tailor to your project rather than follow rigidly. It also stresses ideas such as rolling wave planning, the difference between effort and duration, and tailoring the approach to predictive, adaptive or hybrid life cycles.
Our advice: treat the classic steps as a checklist that makes sure nothing is missed, and scale the effort to the project. A two-week marketing campaign needs a page of tasks; a two-year construction programme needs a full schedule management plan. For an overview of the standard itself, read our guide to the PMBOK Guide.
What a project schedule contains
Whatever tool you use, a complete schedule has the same building blocks.
| Element | What it is | Where it comes from |
|---|---|---|
| Activities | The individual pieces of work, each with a clear verb-noun name | Work packages in the work breakdown structure |
| Dependencies | The logical links between activities (usually finish-to-start) | Team knowledge, technical constraints, contracts |
| Durations | Working time from start to finish of each activity | Estimates, historical data, three-point estimates |
| Resources | People, equipment and materials assigned to each activity | Resource plan and team availability |
| Calendars | Working days, hours, holidays and shutdowns | Organisation and resource calendars |
| Milestones | Zero-duration checkpoints such as approvals and handovers | Charter, contract and governance gates |
| Dates and float | Calculated early and late dates and the slack on each activity | The schedule calculation (critical path method) |
| Baseline | The approved version of the dates, used to measure variance | Sign-off by the sponsor or governance board |
Activities and tasks are often used interchangeably; what matters is that each one has a single owner and a clear finish. Project milestones deserve special care because they are what most stakeholders actually read.
Types of project schedules
One project usually needs several views of the same schedule, each pitched at a different audience.
| Type | Audience | Level of detail |
|---|---|---|
| Milestone schedule | Sponsor, executives, customers | Key dates only: approvals, phase ends, go-live |
| Summary (master) schedule | Steering group, programme managers | Phases or major deliverables as summary bars |
| Detailed schedule | Project team, suppliers | Every activity with dependencies, owners and dates |
| Workback schedule | Teams working to a fixed deadline | Built backwards from a required finish date |
| Release and sprint plans | Agile teams and product owners | Timeboxed sprints and target releases rather than detailed tasks |
A workback schedule is useful for events and marketing launches where the date cannot move: you start with the deadline, then count back through each activity to find the latest date each must start. Where the work is too uncertain to plan in full, many teams combine a milestone schedule for the whole project with a detailed schedule for only the next few weeks.
How to create a project schedule step by step
The steps below follow the classic schedule management sequence. On small projects you can do several of them in one workshop; on large ones each step may take days.
1. Agree how the schedule will be managed
Decide the scheduling tool, the units (days or hours), the level of detail, how often progress will be updated, who may change the schedule and what counts as a significant variance. On larger projects this becomes a short schedule management plan inside the project management plan.
2. Break down the scope
Start from the approved scope and decompose it into deliverables and work packages using a work breakdown structure. If something is not in the WBS, it will not be in the schedule, so this step protects you against missing work.
3. Define the activities
Break each work package into activities that one person or team can own. A common rule of thumb is that an activity should take between a day and two weeks; anything longer is hard to track, anything shorter is usually too much admin. Give each activity a clear verb-noun name, such as "Approve design" rather than "Design".
4. Sequence the activities
Link each activity to its predecessors and successors. Most links are finish-to-start, but you can also use start-to-start, finish-to-finish and, rarely, start-to-finish. Add leads and lags where work can overlap or must wait, for example a three-day lag for concrete to cure. Our guide to task dependencies explains each type with examples.
5. Estimate durations
Estimate how long each activity will take, not just how much work it involves. Effort is the person-hours needed; duration is the elapsed working time, which depends on how many people work on it and how much of their week they can give. Use historical data where you have it, ask the people who will do the work and use three-point estimates for uncertain activities. Analogous estimating (comparing with similar past work) and parametric estimating (for example, metres of cable per day) are also common.
6. Assign resources and calendars
Assign named people or roles, equipment and suppliers to each activity, then apply calendars for holidays, part-time staff and site shutdowns. Check that nobody is booked for more hours than they have. Compare the hours each person is booked for in a week with the hours they actually have, after meetings, support work and other projects.
7. Calculate the schedule and resolve conflicts
Run the critical path method to calculate early and late dates, float and the critical path. Then resolve problems: use resource levelling to remove overloads, and if the end date is too late, consider schedule compression through crashing or fast tracking.
8. Review, approve and baseline
Walk through the schedule with the people doing the work and the sponsor. Check that the logic makes sense, the critical path is believable and the key risks have contingency. Once approved, save it as the project baseline so you can measure variance later.
From that point on, the job becomes controlling the schedule: updating progress, re-forecasting and managing changes, which we cover below.
Worked example: scheduling an office move
A team of 20 is moving to a new office. The project manager lists six activities, their durations in working days, their predecessors and an owner for each.
| ID | Activity | Duration | Predecessors | Owner |
|---|---|---|---|---|
| A | Plan the move | 3 days | None | Office manager |
| B | Order furniture | 4 days | A | Procurement |
| C | Book removals firm | 2 days | A | Office manager |
| D | Install furniture | 5 days | B | Supplier |
| E | Pack and label | 3 days | C | All staff |
| F | Move and unpack | 2 days | D, E | Removals firm |
There are two paths from start to finish:
| Path | Activities | Length |
|---|---|---|
| Path 1 | A, B, D, F | 3 + 4 + 5 + 2 = 14 days |
| Path 2 | A, C, E, F | 3 + 2 + 3 + 2 = 10 days |
The longest path, A-B-D-F, is the critical path, so the move needs at least 14 working days. Activities C and E sit on the shorter path and share 4 days of float: they can slip by up to 4 days in total without delaying the move. The full early and late date calculation is shown step by step in our guide to the forward and backward pass.
Turning the logic into calendar dates
If work starts on Monday 2 November 2026 and the team works Monday to Friday, the calculated early dates are:
| Activity | Start | Finish |
|---|---|---|
| A Plan the move | Mon 2 Nov | Wed 4 Nov |
| B Order furniture | Thu 5 Nov | Tue 10 Nov |
| C Book removals firm | Thu 5 Nov | Fri 6 Nov |
| D Install furniture | Wed 11 Nov | Tue 17 Nov |
| E Pack and label | Mon 9 Nov | Wed 11 Nov |
| F Move and unpack | Wed 18 Nov | Thu 19 Nov |
Two things are worth noticing. First, the weekend adds calendar days without adding working days, which is why the 14-day project ends on 19 November rather than 15 November. Second, the furniture supplier's lead time is on the critical path, so the project manager should confirm it in writing and chase it early, while the packing (which has float) can absorb small delays.
You can rebuild this example in our free project schedule template, or see the critical path calculation laid out in the critical path template.
Project scheduling techniques
Most schedules use a combination of techniques. The table summarises when each one helps.
| Technique | What it does | Best for |
|---|---|---|
| Gantt chart | Shows activities as bars on a timeline, with dependency links | Building and communicating the plan |
| Critical path method | Calculates early and late dates, float and the longest path | Any project with clear dependencies |
| PERT | Uses optimistic, most likely and pessimistic estimates | Activities with uncertain durations |
| Critical chain | Schedules around resource limits and protects the finish with buffers | Resource-constrained and multi-project work |
| Resource levelling | Moves activities to remove resource overloads | Shared or scarce specialists |
| Schedule compression | Shortens the schedule by crashing or fast tracking | Fixed or imposed deadlines |
| Rolling wave planning | Plans near-term work in detail and later work at a higher level | Long or uncertain projects |
| Monte Carlo simulation | Runs the schedule many times with random durations to estimate the likely finish date | High-risk projects needing a confidence level |
Critical path method
CPM is the calculation behind almost every scheduling tool. A forward pass finds each activity's earliest start and finish; a backward pass finds the latest dates that still meet the project finish. The difference is float, and the chain of activities with zero float is the critical path. It tells you where to focus attention and which activities must be shortened if the project needs to finish earlier.
PERT and three-point estimating
When durations are uncertain, ask for three estimates: optimistic (O), most likely (M) and pessimistic (P). The PERT weighted average is (O + 4M + P) ÷ 6. For an activity estimated at 4, 6 and 14 days, the expected duration is (4 + 24 + 14) ÷ 6 = 7 days, a day longer than the most likely estimate, which reflects the risk of things going wrong.
Resource levelling and smoothing
Resource levelling delays activities until the people they need are free, which can extend the finish date. Resource smoothing moves activities only within their float, so the end date stays fixed but some overloads may remain. Use levelling when people are genuinely over-allocated; use smoothing to even out peaks without moving the deadline.
Crashing and fast tracking
Crashing adds resources to critical activities to shorten them, which usually costs more. Fast tracking runs activities in parallel that were planned in sequence, which increases risk and rework. Both only help when applied to the critical path. Our comparison of fast tracking vs crashing shows how to choose.
Scheduling Agile and hybrid projects
Agile teams still schedule, but at a different level. Instead of a detailed network of activities for the whole project, they usually work with:
- Timeboxes: fixed-length sprints or iterations, so the dates are known and the scope inside each one flexes.
- Release plans: a forecast of which features are likely to be ready by which release date, based on the team's measured velocity. See Agile release planning.
- Sprint plans: the detailed plan for the next sprint only, created in sprint planning.
- Milestones for governance: funding gates, regulatory dates or a marketing launch that the wider organisation needs to plan around.
Hybrid projects are common: a construction or infrastructure project may use a predictive critical path schedule for physical works and an Agile approach for the software that runs the building. In that case, link the two through shared milestones rather than forcing sprint tasks into the master schedule. A single high-level timeline can then show both the construction phases and the planned software releases.
Controlling the schedule
A schedule is only useful if it reflects reality. Once the project is under way:
- Update progress at a fixed cadence, usually weekly. Record actual start and finish dates and the remaining duration of activities in progress, not just a percentage complete.
- Recalculate and re-forecast. Let the tool recalculate the dates and check whether the critical path has moved. A near-critical path can become critical after a small slip.
- Measure variance. Compare forecast dates with the baseline. Teams using earned value also track schedule variance and the schedule performance index, and an S-curve shows planned versus actual progress over time.
- Act early. Use float, re-sequence work, add resources to critical activities or agree scope changes before small delays add up.
- Manage changes formally. Changes to the baseline go through change control, so variance reports stay meaningful and stakeholders know which dates are approved.
Project scheduling tools
You can schedule a small project in a spreadsheet, but as soon as dependencies change often or several people share the plan, dedicated software saves time and errors.
| Option | Good for | Watch out for |
|---|---|---|
| Spreadsheet or template | Small projects, one planner, quick start | No automatic recalculation of dependencies or critical path |
| Gantt-based project management software | Teams that need shared, dependency-aware timelines and collaboration | Check which plans include Gantt, baselines and workload views |
| Dedicated scheduling software | Large engineering and construction schedules with thousands of activities | Training needed; less suited to day-to-day team collaboration |
When you compare tools, look for: finish-to-start and other dependency types, automatic rescheduling when a task slips, critical path highlighting, baselines, resource or workload views, and easy sharing with stakeholders.
Among the tools we review, Wrike is a strong choice for teams that run several projects at once and need interactive Gantt charts, dependencies and workload views in one place. Smartsheet suits teams that like a spreadsheet layout with Gantt and dependency features on top. For lighter needs, compare options in our project management tools ranking or see our guide to Gantt chart software.
Common project scheduling mistakes
| Mistake | Why it hurts | How to fix it |
|---|---|---|
| Typing dates instead of building logic | The schedule cannot recalculate when something slips | Enter durations and dependencies and let the tool set dates |
| Missing or dangling dependencies | The critical path looks shorter than it really is | Give every activity a predecessor and a successor, except the start and finish |
| Activities that are too big or too small | Large ones hide delays; tiny ones bury you in admin | Aim for activities of roughly one day to two weeks |
| Assuming people are full time | Durations are too optimistic | Use real availability and resource calendars |
| Ignoring holidays and lead times | Dates are wrong before work starts | Set calendars and include supplier lead times as activities |
| No contingency for known risks | Every risk that happens becomes a delay | Add schedule reserve linked to the risk register |
| Planning far-off work in false detail | Effort is wasted and the plan is rewritten anyway | Use rolling wave planning |
| Never rebaselining after approved changes | Variance reports become meaningless | Rebaseline through change control and keep the history |
Project scheduling checklist
Use this quick check before you ask for sign-off:
- Every deliverable in the WBS is covered by at least one activity.
- Every activity has an owner, a duration and logical links.
- Calendars include holidays, part-time staff and supplier lead times.
- No resource is overloaded, or overloads are understood and accepted.
- The critical path is believable and has been reviewed with the people doing the work.
- Key milestones match the commitments in the charter or contract.
- Risk contingency is included and visible.
- The baseline is saved and the update cadence is agreed.
Free templates for this topic
Frequently asked questions
What is project scheduling?
Project scheduling is the process of listing the activities a project needs, putting them in a logical order, estimating their durations and resources, and calculating start and finish dates for each. The result is the project schedule, which the team works to and progress is measured against.
What is the difference between a project plan and a project schedule?
The project management plan describes how the whole project will be run: scope, cost, quality, risk, communication and more. The schedule is one part of it and covers timing: activities, dependencies, durations and dates.
What are the steps of project scheduling?
Agree how the schedule will be managed, break down the scope, define activities, sequence them, estimate durations, assign resources and calendars, calculate the schedule (usually with the critical path method), then review, baseline and control it.
What are the main types of project schedules?
Common types are the milestone schedule for executives, the summary or master schedule for steering groups, the detailed schedule for the team, the workback schedule built from a fixed deadline, and release or sprint plans for Agile teams.
What are the main project scheduling techniques?
The most widely used are Gantt charts, the critical path method, PERT three-point estimating, critical chain, resource levelling and smoothing, schedule compression (crashing and fast tracking), rolling wave planning and Monte Carlo simulation.
What is the critical path in project scheduling?
The critical path is the longest sequence of dependent activities from start to finish. It sets the shortest possible project duration, and a delay to any activity on it delays the project unless you recover the time. See our critical path method guide.
What is a schedule baseline?
The schedule baseline is the approved version of the schedule's dates. You compare actual and forecast dates with it to measure variance, and you change it only through formal change control. See project baseline.
How detailed should a project schedule be?
Detailed enough that each activity has one owner and can be tracked, typically one day to two weeks long. Many teams plan the next few weeks in detail and keep later work at a summary level, refining it as they learn more (rolling wave planning).
How often should a project schedule be updated?
Most projects update weekly, in line with status reporting. Short or fast-moving projects may update more often; long programmes with stable work may update fortnightly. The key is a fixed cadence that everyone knows.
Can Agile projects have a project schedule?
Yes. Agile teams schedule with fixed-length sprints, release plans based on velocity and milestones for governance, rather than a detailed activity network for the whole project.
Who is responsible for the project schedule?
The project manager owns the schedule and is accountable for keeping it current. The people doing the work should help define, sequence and estimate their activities, because they know the work best and are more committed to dates they helped set.
What is the best tool for project scheduling?
Any tool that handles dependencies, recalculates dates automatically and shows the critical path will do the core job. For team-based work, Gantt-capable tools such as Wrike or Smartsheet are popular; small projects can start with a project schedule template.
How do you make a project schedule realistic?
Involve the people doing the work in estimating, use real availability rather than assuming full-time staff, include holidays and supplier lead times, add contingency for known risks and review the critical path before you baseline.
What is the difference between resource levelling and resource smoothing?
Resource levelling delays activities until resources are free and can push out the finish date. Resource smoothing moves activities only within their float, so the finish date does not change. See resource levelling.