Skip to content
MyPro Sync
Two astronauts on a planet, one looking at an hourglass, the other standing and waiting in front of a locked gate
Task & project dependencies

Late vs. Blocked Task: What Is the Difference and Why It Matters

A late task could move forward but is not moving fast enough. A blocked task cannot move because it is waiting on something else. They need different handling, and mixing them up sends you looking for the fix in the wrong place.

A late task is one whose deadline has passed or is about to pass, even though the work could be done. A blocked task is one nobody can work on because another task or decision is not finished yet. The difference matters because the two situations need different action. For a late task you look at the owner and their workload. For a blocked task you look at the blocker. Chasing the owner of a blocked task means asking the wrong person.

What it means for a task to be late

A task is late when it misses its planned date while nothing prevents work on it. The causes usually sit inside the task or around its owner.

  • The amount of work was underestimated.
  • The owner has too many tasks at once.
  • Other work was put ahead of it because it was judged more important.
  • The task is not described well enough, so it is hard to start.

All of these can be handled by the task owner and through team planning. You can reschedule, re-estimate, take other work off the owner’s plate, or clarify the description.

What it means for a task to be blocked

A task is blocked when it cannot meaningfully start or continue until another task is done. That relationship is called a task dependency. The owner of a blocked task can be completely free and motivated and still be unable to move.

A typical example is website copy that cannot be finalized until product pricing is approved. The copywriter is not slow. There is simply nothing to work from yet. Our article on what a blocked task is covers the basics in detail.

Why mixing up the two is risky

When a blocked task is treated as late, three things happen.

First, you chase the wrong person. The owner of the blocked task gets the questions, even though they cannot change the situation. That is frustrating, and over time it teaches the team that it is better not to speak up.

Second, the real blocker stays invisible. While everyone looks at the late task, the prerequisite that actually stopped the work gets no attention. It often sits with a completely different person who may not even know others are waiting.

Third, the delay spreads. Tasks that come after the blocked one start to slip too, and the problem appears in more and more places across the project. You can read about this chain reaction in our article on why tasks slip when everyone is working.

The opposite mistake happens too. If a task that is simply late gets labeled blocked, the real cause, such as overload or a poor estimate, stays hidden.

How to tell which situation you are in

One simple question helps a lot. If the owner could work only on this task tomorrow morning, could they make progress?

If yes, the task is late. The question then is why there is no time for it and what would make time available.

If no, the task is blocked. Then you need to find out exactly what it is waiting for, who owns that, and when it is expected.

A few signs give it away even before you ask.

  • A blocked task’s status has not changed for a long time, and the owner reports no progress.
  • When asked, the owner mentions another task or another person.
  • Several tasks are stuck at the same time, all waiting on the same prerequisite.

How to handle late and blocked tasks

Handling a late task

Sit down with the owner and look at their workload and the estimate. Ask whether the deadline can still hold if something is taken off their plate. If not, set a new deadline deliberately and tell the people who are waiting on it.

Handling a blocked task

Do not start with the owner of the blocked task. Start with the blocker. Find out which task is holding it back, who owns that task, and what it would take to clear it. Often a short decision or handing over a partial result is enough. In the meantime, give the blocked task’s owner other work that does not depend on anything, so they are not stuck.

How a task management tool makes this visible

In MyPro Sync a task can be marked as blocking another one. The blocked task automatically gets a blocked flag until the blocker is resolved, so nobody has to track by hand what is waiting on what. The dependency graph view shows which prerequisite is holding back several tasks at once. The status log shows how long a task has been sitting in the same state.

The practical takeaway

The next time a task falls behind, before you chase anyone, ask whether the owner could actually work on it. The answer tells you who to talk to. That single question saves a lot of unnecessary meetings and bad feeling.

More in this topic

Task & project dependencies