Fast-tracking is a schedule compression technique in which activities that were planned one after another are done at the same time, or overlap, to finish a project sooner. It does not add budget or people, but it adds risk: starting work before its predecessor is complete can mean rework. Use it only on tasks that can safely run in parallel.

Fast-tracking in project management, in one example
A website project has three tasks planned in sequence: design (4 weeks), development (6 weeks) and content (3 weeks), 13 weeks in total. With fast-tracking, content writing starts in week 3 of design, and development starts when the first approved pages are ready, in week 3 as well. The three tasks now overlap and the project finishes in about 9 weeks. The price is risk: if the design changes after week 3, some development and content has to be redone.
Fast-tracking vs crashing
Fast-tracking and crashing are the two schedule compression techniques in the PMBOK Guide. They solve the same problem in opposite ways.
| | Fast-tracking | Crashing | | --- | --- | --- | | What you do | Run tasks in parallel or overlap them | Add people, hours or money to critical-path tasks | | Main cost | Rework and risk | Extra budget | | Main risk | Dependencies change after work started | Diminishing returns: more people do not always mean faster | | Best when | Budget is fixed, and tasks can overlap safely | Budget exists, and tasks can be split or sped up | | Works on | Critical path tasks with soft dependencies | Critical path tasks that scale with more resources |
Both only help if you work on the critical path, the longest chain of dependent tasks. Speeding up a task outside it does not shorten the project.
When to fast-track a project
- The deadline moved earlier, for example because of a launch date or a competitor.
- The project is behind schedule and the scope cannot be reduced.
- Budget is fixed, so crashing is not possible.
- The tasks you want to overlap have soft (discretionary) dependencies.
Do not fast-track when a task truly needs the output of the previous one (a hard dependency), when quality or safety checks must come first, or when your team has no capacity for parallel work.
Which tasks can be fast-tracked
Dependencies decide it:
| Dependency | Example | Fast-track? | | --- | --- | --- | | Finish-to-start, hard | Pour concrete, then build on top | No | | Finish-to-start, soft | Finish the design, then write the copy | Yes, with overlap (start-to-start with lag) | | Start-to-start | Testing starts shortly after development starts | Already parallel | | External | Wait for a supplier delivery | Only by changing the supplier's date |
How to fast-track a project in 5 steps
- Find the critical path. List tasks, durations and dependencies. Only tasks on the critical path shorten the project when you compress them.
- Pick the candidates. Look for sequential tasks with soft dependencies, where the second can start when the first is partly done.
- Check capacity. Overlapping tasks need people at the same time. Confirm owners and workload before changing dates.

- Reschedule and set checkpoints. Update the schedule and add a review point where the overlapped tasks reconnect, for example "approved design pages" in the example above.
- Track daily and communicate. Watch the critical path each day. When a predecessor changes, tell the owners of the overlapping tasks the same day.

A task board with owners, dates and comments makes the overlaps visible. In Edworking you can assign tasks with due dates and keep the discussion inside each task. A timeline or Gantt chart helps you see which tasks overlap.

Advantages and risks
Advantages
- The project can finish earlier without extra budget.
- Resources are freed sooner for other work.
- You can react to a moved deadline without reducing scope.
Risks
- Rework: if the first task changes, the overlapped task may need to be redone.
- Quality: less review time between stages.
- Communication load: more people working at the same time needs more coordination.
- Team strain: parallel work can overload people and increase errors.
To limit the risks, overlap only what you can reverse cheaply, agree on checkpoints and keep a short list of assumptions each overlapped task depends on.

Fast-tracking checklist
- The critical path is identified and up to date.
- Each overlapped pair has a soft dependency, not a hard one.
- Owners and workload are confirmed for the overlap.
- A checkpoint exists where the overlapped tasks reconnect.
- Stakeholders know the extra risk.

FAQ
What is fast-tracking in project management?
It is a schedule compression technique where tasks planned in sequence are done in parallel or overlapped to shorten the project duration.
What is the difference between fast-tracking and crashing?
Fast-tracking overlaps tasks and adds risk of rework. Crashing adds resources to critical-path tasks and adds cost.
Does fast-tracking increase cost?
Not directly, but rework caused by overlapping tasks can. Crashing increases cost directly.
Can you fast-track any task?
No. Tasks with hard dependencies, where the second needs the finished output of the first, cannot be safely overlapped.
Is fast-tracking in the PMP exam?
Yes. Schedule compression with fast-tracking and crashing is part of the PMBOK Guide's schedule management knowledge.



