Most project managers know the feeling. A client email arrives asking, politely, where a deliverable is. You open the project and find the task is nine days past its end date, marked 40% complete, and nobody has said a word about it. The work is not lost. It just slipped quietly, and the client noticed before you did.

This is rarely a people problem. It is a visibility problem. The information was there all along, in dates, progress and status, but nobody was looking at it in a way that made the slip obvious. This article explains why overdue work tends to stay hidden and sets out a simple weekly routine for reading a project health report, so you are the first to know when something is drifting.

Why overdue work stays invisible until someone outside the team notices

Overdue tasks rarely announce themselves. A few patterns make them easy to miss:

  • Everyone looks at their own work, not the project. Each person sees their own task list. Nobody is scanning the whole project unless that is explicitly their job, and on a busy week the project manager is often too deep in meetings to do it.
  • Dates are set once and then forgotten. An end date is added when the task is created, and nobody revisits it when scope grows or a dependency slips. The date stays on the task; the plan moves on without it.
  • Status lags behind reality. A task sits in "In progress" for three weeks. Technically that is true, but it tells you nothing about whether it will finish on time.
  • Small slips hide inside big projects. One sub-task two days late does not feel urgent. Five of them on the same deliverable is a missed milestone, but you only see that if you look at them together.
  • Bad news travels slowly. People hope to catch up before anyone notices. That is human, and it means problems surface late unless the system surfaces them for you.

The client, meanwhile, is only watching one thing: the date you promised. So they spot the slip the moment it matters to them, which is usually after it is too late to fix quietly.

What a health check actually needs to tell you

A project health report is only useful if you know what questions you are asking it. Before opening any report, it helps to be clear about the four things you want to learn:

  1. What is already late? Tasks whose end date has passed but are not finished.
  2. What is about to be late? Tasks due in the next week or two where progress looks low for the time left.
  3. Who is carrying too much? Overdue work often clusters around one overloaded person rather than being spread evenly.
  4. Which of these does the client care about? Not every overdue task affects a deliverable. Some are internal and can wait.

The report shows you the facts. Your job is to turn those facts into a short list of things that need a conversation this week.

This only works if the underlying task data is reasonably honest. If end dates are missing or progress is never updated, any report will look healthier than the project really is. In Tilvin, tasks carry start and end dates, estimates, progress, priority, assignees and a status from the project's workflow, so the habit to build is simply keeping those fields current. A short nudge in the team stand-up ("update your progress before Friday") does more for report accuracy than any amount of after-the-fact chasing.

A 20-minute weekly routine for reading the report

You do not need a long review. You need a regular one. Pick a fixed slot, early in the week works well because it leaves time to act, and work through the same steps each time.

1. Start with project health, filtered to the next two weeks

In Tilvin, the project health report sits under Reports alongside billable hours, timesheet, team workload and a project Gantt chart, and each can be filtered by date, project and person. Filter to the project you are reviewing and a window that runs from today to two weeks out. Note anything already overdue and anything due soon that looks behind.

2. Check the Gantt chart for knock-on effects

One late task is a nuisance. One late task that other work depends on is a schedule problem. A quick look at the Gantt chart for the same period shows whether the slipping item sits in front of other work, and whether a client-facing milestone is now at risk.

3. Look at team workload for the same period

If three of the overdue items belong to the same person, the issue is probably capacity, not effort. The team workload report, filtered to the same dates, shows whether someone is stretched while others have room.

4. Open the tasks that worry you

Numbers tell you where to look; they do not tell you why. Open each flagged task and read its recent discussion. If a thread is long, Tilvin's AI summaries can condense a task's discussion into a summary, an item list and open questions, which is often enough to see whether the delay is a blocker, a waiting-on-client issue or simply forgotten work.

5. Write down three actions, not thirty

End the review with a short list: who you will talk to, what date needs to change, and what the client needs to hear. If you find yourself with a long list every week, that is a sign the plan itself needs reworking, not just the tasks.

If you run several projects, do this per project rather than trying to read everything at once. Our earlier article on managing multiple projects without missing deadlines covers how to keep that manageable.

Turning what you find into action before the client asks

A report you read but do not act on is just a more detailed way of being surprised later. Once you have your short list, a few habits help:

  • Talk to the assignee first, privately. Ask what is in the way, not why it is late. Use the task's discussion and @notify the person so the conversation stays attached to the work and is visible to anyone who picks it up later.
  • Reset dates honestly. If the work genuinely needs another week, change the end date and note why in the discussion. A realistic date is more useful than an optimistic one that keeps the task looking red.
  • Split stuck tasks. A large task that has sat at 40% for weeks often hides one blocked piece. Breaking it into sub-tasks with their own assignees and dates shows what is actually done and what is not.
  • Rebalance load. If workload shows one person carrying the slip, move a task or two to someone with room rather than asking for longer hours.
  • Tell the client early, with a plan. "This will land on the 18th rather than the 14th, because we are waiting on the final copy; here is what we need from you" is a very different conversation from answering their chaser.

That last point is the real goal. Clients rarely object to a slip they hear about early with a reason and a new date. What damages trust is discovering it themselves. If your clients have access to the project through a client role, remember they may be seeing the same task dates you are, which is one more reason to keep them accurate.

None of this needs to feel like surveillance. Reading the report is about spotting where the plan and reality have parted ways, not about checking up on people. Our piece on tracking progress without micromanaging goes further into keeping that balance.

Next steps for this week

You can start this routine on your next working day. Keep it small:

  1. Pick one project, ideally the one with the most client contact, and book a recurring 20-minute slot early in the week.
  2. Check the data first. Make sure open tasks have end dates and that progress has been updated recently. Ask the team to tidy their own tasks before your first review.
  3. Run the five steps: project health for the next two weeks, Gantt for knock-on effects, team workload, a read of the flagged tasks, and three actions.
  4. Send one proactive update to the client if anything has moved, before they ask.
  5. Repeat for a month, then add your next project to the routine.

After a few weeks, the difference is usually noticeable. Fewer surprises, shorter status meetings and, most importantly, client conversations that start with your update rather than their question. If you want to see where reports fit alongside tasks, discussions and time logging, the Tilvin features overview gives a quick tour.