Seeing the Gap Between Plan and Actual on a Gantt Chart
Delays usually surface after it's already too late. Three days before the deadline, you count what's left and go pale. Or someone asks "hey, how far along are you?" and you realize you don't actually know either.
The strange part is that you were keeping records. The tasks were listed; the time was tracked. The reason the delay still snuck up on you is, I think, that "where the plan says you should be" and "where you actually are" were never drawn on the same picture. You had the numbers, but not the gap. A Gantt chart is a tool for laying those two on top of each other. In this article we'll walk through how LayerClock's Gantt overlays plan and actual, and how to read it.
A Task List Doesn't Show the Gap
A vertical list of tasks tells you "what's left" very well. But "am I behind schedule?" is nearly unreadable from a list. Seven boxes checked, three remaining — that tells you nothing about whether that's on track or late. There's no time axis.
Say a task is marked "not started." On the list, it looks exactly like every other not-started task. But if that task's planned start date was three days ago, it isn't a "not started I'll get to" — it's a "not started that's already behind." A list can't tell those two apart. Whether you're past the day you should have begun becomes visible only once it's placed on a time axis.
What a Gantt chart adds is exactly that time axis. Each item is placed on time as a horizontal bar, "from when to when." Now you can see where the "today" line falls, and whether each bar sits ahead of it or behind it, at a glance. "Behind" becomes something visible as a relationship between positions.
Layering the Plan Bar and the Actual Bar
LayerClock's Gantt draws each bar in two layers. The pale outer frame is the "plan" — the start date and due date you set on that item. Inside it, a darker bar extends, and that's the "actual."
The length of the inner bar is decided by how much tracked time has stacked up against the estimate. Put five hours of timer on a deliverable estimated at ten, and the inner bar reaches about halfway across the plan frame. You can see, visually, how far the contents have progressed against the plan. A completed item turns grayish rather than dark, so you can tell "this one's done" at a glance.
Picture a screen with a few deliverables lined up. The "basic design document" frame has its inner dark bar filling about 80% of the frame, not yet in the done color — a lot of the estimate spent, but close to finished. The "screen mockups" frame has its inner bar barely extended from the left — just started. The "checkout feature" frame is only a frame, empty inside — untouched. Just those three stacked vertically tell you "where the energy is right now, and what's still untouched," without reading a number.
The Red Line for Today, and Three Ways to Read It
And a red vertical line marks today's position. The relationship between that line and the leading edge of the inner actual bar is the gap between plan and actual. I always read it, roughly, in three patterns against that red line.
Ahead — the actual bar extends past today's line. Running early, or at least not behind. This is a healthy state.
Not caught up — the frame (plan) crosses today's line, but the inner actual bar stops short of it. It's a day when you should have progressed this far, yet the actual hasn't reached there. This is the classic look of "behind," and how far the dark bar sits short of the red line is a gauge of how big the delay is.
About to eat through the frame — the inner dark bar has reached the right edge of the plan frame. Not yet complete, but the estimated time is nearly used up. This is less "behind" than "over estimate," and left alone, it overflows the frame. A different warning sign from being late to start.
Without reading a single precise number, the position of the dark bar relative to the red line sorts things into these three. That's the plainest and most effective use of the Gantt, I think.
Survey the Whole, Then Descend Where It Worries You
Sometimes you want to eyeball the plan by the month; sometimes you want to press in on this week's fine-grained progress. LayerClock's Gantt switches between a month view and a day view, and the day view shows per-day ticks with weekend columns faintly tinted. When you're checking a day-level squeeze — "I meant to finish this deliverable across the weekend" — the day view is the one for it.
In practice, I'd first collapse the hierarchy and survey the whole with just the project- and phase-level summary bars. Even collapsed, an upper bar reflects the average progress of its children in its length, so "which phase hasn't caught up to the red line" shows first. Then open only the phase that worries you and descend to its deliverables and tasks. Expand everything from the start and there's too much information — the delay that matters gets buried. Get a bearing from the overview, then look deep only where it worries you — that order reaches the delay fastest.
Hover a bar and a small card shows the start and due dates, the assignee, the progress rate, and the estimate, so once you've descended you can confirm "this deliverable — who holds it, when was it due" on the spot.
After You've Noticed the Gap
What the Gantt shows you stops at the fact "you're behind"; it doesn't, at a glance, tell you "where this ends up if it continues." Beyond that — forecasting remaining effort, analyzing burn pace per phase — is the report screen's job (I wrote about that side in heading off the "suddenly over budget" surprise and how EAC works).
But even that forecasting starts from one thing: did you notice you're behind before it was too late? However precise a landing forecast is, if you notice the delay the day before the deadline, you can't act. The Gantt does no flashy analysis, but it supports that first "noticing" with nothing more than a red line and a two-layer bar. I use it as something like a health check every time I open the plan — glance at the bars crossing the red line, check that the count of "not caught up" ones hasn't grown. That alone noticeably increases the number of times I can act before it's too late.
Related articles
- Time Tracking That Lets You Say, in Numbers, Where the Time Went
- Heading Off the "Suddenly Over Budget" Surprise — Reading "Where This Ends Up," Phase by Phase
- Forecasting Remaining Effort: How EAC (Estimate at Completion) Works
- Why Drawing the Gantt Chart First Warps Your Plan
- Making "Who's Doing What" Visible in a Small Team
The Gantt chart in this article is available right in LayerClock's plan screen. The dates you set on the four-level WBS (project, phase, deliverable, task) and the actuals your timer stacks up appear layered as a plan bar and an actual bar. Everything up to here is free to use.