A short-horizon field Gantt: tasks as bars across a 7/14/21-day window, weekends shaded, today marked. Deliberately not a CPM tool — no dependencies, no float, no critical path. Runs entirely offline; everything persists in this browser via localStorage.
Use limits: A look-ahead is a commitment device, not a schedule. It works when it's built with the foreman and updated weekly — not printed once and taped to the trailer wall. There are no logic ties here on purpose: if you need dependencies, float, or a critical path, that's the master schedule's job, not a bigger look-ahead. The governing dates come from the master schedule.
Look-ahead
Tasks in window
—
Tasks extending beyond window
—
Busiest day (most concurrent)
—
How the Numbers Are Derived
Calendar vs. working-day durations
In calendar mode a task's end is start + (duration − 1) days — a 5-day task starting Friday ends the following Tuesday, weekend included. In working-day mode the tool walks the calendar counting only Monday–Friday until it has counted the duration; a 5-working-day task starting Friday spans Fri–Thu and ends the following Thursday. The bar is drawn as one continuous span from start to end so it reads as a block; the weekend columns underneath it are shaded so you can see the skip. Dates are parsed as local, so the axis never drifts a day.
What the panel counts
“Tasks in window” is every task whose span overlaps the visible window at all. “Extending beyond” counts tasks that start before the window or run past its end — those get a clipped bar (a colored notch at the cut edge) and a line in the flag list below. “Busiest day” walks each day in the window and counts how many task spans cover it, reporting the peak — a rough read on where the crews stack up.
Make-ready field notes
The point of a look-ahead is to surface constraints early enough to clear them: material on site, access granted, information (RFI/submittal) answered, manpower assigned. A task that can't answer all four isn't ready to promise.
Anything still sitting on the look-ahead three weeks running is a constraint problem, not a scheduling problem. Bumping it another week doesn't make it ready — find the missing prerequisite.
Build it with the foreman who'll do the work, not for them. A look-ahead the crew didn't help write is a wish list.
This tool has no dependencies by design. If moving one bar should move another, you're describing logic that belongs in the master schedule (P6/MS Project), where float and the critical path actually live.
References
Ballard, G. — The Last Planner System of Production Control (lean construction look-ahead / make-ready planning).
The project master schedule (P6, MS Project, or equivalent) — the governing document for dates, durations, logic, and float.