Construction Schedule Template

What a construction schedule does for a subcontractor

The general contractor has a master schedule. Yours is different: it is the sequence of your own crews through your own scope, at a level of detail the GC’s schedule never shows — which crew is on Level 2 rough-in the week the crane sets the rooftop units, whether controls rough-in can start before the submittal comes back, when the insulator needs to be on site. It is also the document that proves a delay was not yours. A schedule updated every week, with a status date and a % done on every task, is the record you reach for when the GC asks why the ceilings closed late.

This template is built for that use. It is a spreadsheet, not scheduling software, and it stays honest by keeping the math visible: durations are workdays, end dates are computed, and the Gantt bars are drawn by formulas you can read.

How the Excel Gantt works

Every timeline column has a date in its header: the chart start date plus a multiple of the days per column. Every task row has a start date and an end date computed as WORKDAY(start, duration − 1). A conditional-formatting rule on the grid then asks one question per cell: does this task overlap the dates this column covers? Written out, the rule is start ≤ column date + days per column − 1 and end ≥ column date. If both are true the cell shades light blue.

A second rule shades the done portion dark. It computes the point in the task that % done corresponds to — start plus the task length times % done — and shades any column that begins before that point. A third rule tints the column containing the status date, so the printed sheet shows where “today” falls against every bar. None of this needs a macro, and all of it works in Google Sheets and Numbers as well as Excel.

The sequence check uses the predecessor column the same way. For each task with a predecessor number, it looks up that task’s end date and turns the start date red if the task begins on or before it. It is not a full critical-path calculation — the spreadsheet will not tell you which chain of tasks controls the finish date — but it catches the sequence errors that make a schedule physically impossible before you print it.

A worked example: six months of mechanical work

The completed example that ships with the download is a mechanical subcontractor’s schedule on a medical office building: 23 tasks across eleven phases, from mobilization on June 1, 2026 to closeout on November 18, with the status date set to August 31, the end of the period billed on the third pay application. The chart is set to 14 days per column so the whole job fits in the 16 columns; switch it to 7 and the same rows become a 16-week weekly view.

Read across the bars and the state of the job is visible without a meeting. Underground, both rough-ins and the crane day for RTU-1 to RTU-4 are complete and shaded dark. Duct mains on Level 2 (25 workdays from August 10) are 65% done, hydronic piping to AHU-3 is 55%, and both bars change from dark to light in the column holding the status date. Controls rough-in, insulation, fixtures and testing are still light bars in September and October, and the summary row reports the whole scope at 55% complete, weighted by duration. The predecessor column carries the logic: controls rough-in (task 16) waits on the Level 2 ductwork (task 12), commissioning waits on testing and balancing, and the RTU curb task references change order CO-001, the relocation of the RTU-2 curb that added two days to the contract.

That is the level of detail that pays off. A schedule with a task called “HVAC” from June to November tells the GC nothing; one that shows the crane day on August 3 depending on curbs finished July 10 lets the superintendent plan the roofer, the electrician and the crane pad around you.

Schedule, look-ahead and Gantt software

• The baseline schedule is what this template holds: the whole scope, phase by phase, with the dates you committed to. Issue it once after the notice to proceed, then revise it when change orders move dates.
• A look-ahead is the next two or three weeks pulled out of the baseline and broken into crew-level detail for the weekly coordination meeting. Set the chart start to next Monday and 7 days per column and this sheet becomes one.
• Gantt software earns its keep when tasks depend on each other across phases and one slip should move everything downstream. The spreadsheet flags the conflict; software reschedules it. Read about dependencies and the critical path in BuildWorkPro when you get there.

Common scheduling mistakes this template is built to catch

• Durations in calendar days on a five-day crew — a 15-day task “finishes” on a Sunday and the real end date is a week later.
• No predecessors — every task is scheduled to the earliest date someone hoped for, and the sequence falls apart the first week.
• Long bars — a 40-day task at 50% tells you nothing about whether it is on track. Split it.
• Updating irregularly — a schedule updated when someone asks is ignored; one updated every Monday is used.
• Compressing after a delay — pulling every downstream task in to hold the finish date, without adding crew or hours, is a schedule that will slip again next month.
• Losing the change order trail — added days that are not tied to a CO number cannot be defended later. Note the number on the task.

Delays belong in the daily report the day they happen — the schedule shows the effect, the daily report proves the cause; our guide to writing a daily report that holds up covers what to record. As the job closes, the last tasks on this sheet hand off to the punch list, and the same dates feed the cost-to-complete on your construction budget.