Glossary · Projects

Task dependencies: the four types and the critical path

Also known as: Finish-to-start · predecessors

Task dependencies are the rules that tie the start or finish of one task to another, such as painting not starting until the plaster has dried.

The four types

  • Finish-to-start: B starts when A finishes. The most common: you do not paint until the plaster is dry.
  • Start-to-start: B starts when A starts. Site layout and safety signage begin together.
  • Finish-to-finish: B finishes when A finishes. The installation documents are closed out with the final tests.
  • Start-to-finish: B cannot finish until A starts. The rarest: the old equipment keeps running until the new one starts up.

Each one can have a lag, such as waiting two days after pouring concrete, or a lead, such as starting to paint when the plaster is half done.

The critical path

Chaining dependencies together reveals the critical path: the sequence of tasks where every day of delay is a day of delay on the handover. Tasks outside it have slack. Knowing which is which tells you where to put people when something goes wrong.

The usual mistake

Keeping dependencies in the project manager’s head. If they are not written into the plan, moving one date does not move the ones that depend on it. And the Gantt chart shows a schedule that is no longer possible.

Keep reading

Related terms

Projects

Gantt chart

Project timeline · schedule chart

A Gantt chart is a project schedule drawn as bars: each task takes one row, and its bar starts and ends on its planned dates.

Projects

Baseline

Project baseline · schedule baseline

A baseline is the saved copy of a project’s approved plan, with its dates and durations. It lets you compare what was planned with what is actually happening at any time.

Projects

Resource utilization

Team workload · utilization rate

Resource utilization is the share of each person’s available hours that is already committed to planned work, measured by day, week or month.

On the blog

See all 53 glossary terms

Request a demo

Shall we look at it with your data?

We will show you how what you just read works in attendo, with your own assets, tickets and customers. If it is not a fit, we will tell you.

  • With your operation, not a generic demo
  • A real person from our team replies
  • No cold calls afterwards

Would you rather talk first?

Which area do you want to see in the demo?

With your work email we prepare the demo around your case.

In one or two sentences.

If you chose Maintenance (CMMS)

If you chose Field work (Field Service)

If you chose Facility Management

If you chose any other area

Only if you would rather we call you.

Data protection. Controller: AxisOne Group SL. Purpose: preparing the demo you request and replying to you. Legal basis: your consent and the request you make. Recipients: we do not disclose your data; Cloudflare (website) and Brevo (email notices and confirmation) process it on our behalf. Rights: access, rectification, erasure, objection, restriction and portability, at privacy@attendo.me. More information in the privacy policy.

What happens when you send it. Someone from our team reads what you tell us and writes to you to agree on a time for the demo. Our hours: Monday to Thursday 9:30 AM to 6:30 PM and Friday 9:30 AM to 2:30 PM, Spain time.