Note
Gantt Bars Too Long for Weekly Review
A Gantt chart with forty bars looks thorough. It is often useless at a Tuesday review. Not because the work has gone wrong, but because every bar that spans four to eight weeks will show the same status at week three that it showed at week one: in progress. A bar that cannot change between reviews is a decoration, not a planning tool.
The fix is not different software or a different chart type. It is deciding, before the project starts, how long each bar is allowed to be.
Why does a long bar stall your weekly review?
A bar that runs from week one to week eight covers eight update cycles. At any given Tuesday during that period, the bar is either not started, in progress, or finished. For six of those eight weeks it will be in progress, and nothing about those two words tells you whether the bar is on track, running late, or about to miss the billing pin it is carrying.
The person running the review cannot act on “in progress.” They can act on “zone 5 finished, zone 6 is four days in, material for zone 7 is confirmed for delivery Thursday.” Those are different statements, and they come from a different bar structure.
The problem compounds when a billing stage is attached to a long bar. If stage three closes at the end of week eight and the bar covering that work has shown in progress since week two, the first moment you can tell whether the billing pin is reachable is when the bar is nearly over. That is a very short window for a very late intervention.
What length makes a Gantt bar checkable?
A bar is checkable when it can change state between one review and the next. That means its maximum useful length is roughly one week, or the span between reviews.
In practice, construction bars rarely split into single-week units across a whole project. A more useful rule is: break any bar that spans more than two update cycles into units that map onto something real and countable. For site installation work, that unit is usually a zone, a floor, a room, or a run of metres.
An eight-zone partition install does not need one bar that says “partitions: weeks 2 to 9.” It needs eight bars, one per zone, each running roughly one to two weeks. At any given Tuesday, some are finished, one is in progress with a clear unit attached to it, and the next ones have start dates that are visible. Every bar in that group can change state between now and next week, which means every bar can be checked.
A worked example: zone-by-zone fit-out
A fit-out subcontractor is installing gypsum partitions across eight zones of a commercial office. Stage three billing covers zones five through eight and closes on the last Friday of the month.
Version A: one long bar. The contractor draws one bar: “partition installation, weeks 2 to 10.” At the week six review, the bar is green and in progress. Nobody can tell from the bar whether zones five through eight are on track for the stage three billing date. A call to the site manager takes twenty minutes to confirm that zones five and six are done, zone seven starts Monday, and zone eight has a two-day delay on board supply. That delay pushes zone eight’s finish past the billing close date. The contractor finds out on Friday, not on Monday.
Version B: eight bars. Eight bars, one per zone, each one to two weeks long. At the week six review, the chart shows zones five and six marked finished, zone seven marked started on Monday with material confirmed, and zone eight showing a gap: board delivery is not yet confirmed. One bar has a problem. The team fixes the delivery booking that afternoon. Zone eight finishes two days before the billing close date, and the invoice goes out on time.
The difference between the two scenarios is not a matter of how hard the contractor worked. It is a matter of whether the bar structure let the problem show up early enough to fix it.
How do you break a long bar without losing the schedule?
A long bar is usually the result of describing work by trade rather than by unit. “Partition installation” describes a trade. “Partitions zone 5” describes a unit. That switch costs five minutes at the planning stage and returns time every week for the rest of the project.
For work without countable physical units, count in time-boxed milestones rather than open-ended activities. Not “structural steel” as one bar, but “steel frame complete to level 3 by end of week four” and “steel frame complete to level 6 by end of week seven.” Two bars, each with a checkable state on a specific date.
What happens to the billing pin when you break the bar?
A billing stage in Thai subcontracting is typically tied to a scope milestone: zones accepted, floors complete, a system commissioned. When the bar behind that milestone is one long bar, the billing pin appears to be at risk only when the bar approaches its end date.
When the bar is broken into zones, the billing pin becomes visible much earlier. If zone seven is three days behind in week five, and zone eight depends on zone seven before it can start, the billing pin moves in the review where zone seven’s slip first appears. That is a four-day problem handled in week five, not a two-week problem discovered in week nine.
Billing stages that slip in Thai subcontracting rarely slip for reasons nobody saw. They slip because the bar structure did not show the slip while there was still time to act.
FAQ
Does breaking bars into zones mean creating a separate project file for each zone?
No. One project file, one timeline, bars named by zone. The naming convention does the work: partitions-Z5, partitions-Z6, and so on. Filtering by trade or by floor then gives you a clean view without touching the plan structure itself.
What if the main contractor’s programme uses long bars and asks us to match it?
Keep two views: one that matches the main contractor’s reporting format, and one internal breakdown by zone. The internal view is what you bring to Tuesday’s review. It takes roughly twenty minutes to produce from the zone-level data and satisfies the reporting requirement without surrendering the visibility you need to hit the billing dates.
How do you know whether your current bars are too long?
Run last month’s weekly reviews in your head. For each bar that was in progress at two or more consecutive reviews, ask: could you have checked its status without a phone call? If the answer is no, the bar was too long.
If you want to see where your current project bars can be split, a 45-minute call is the right format. We walk one pilot project together, identify which bars cross multiple update cycles, and map out the zone-level breakdown that makes each Tuesday check a two-minute scan rather than a twenty-minute chase.