Construction schedule report

Monthly CPM schedule update with phase subtotals and Gantt bars

Download template

Sample data

Template
DOCX
Export as
PDF, DOCX, ODT, HTML, PNG +25 more
Carbone
5.18+

Generate construction schedule reports from your scheduling software

On a commercial building project, the general contractor updates the CPM schedule every month: it records actual dates and percent complete at the data date, recalculates the network, and sends a schedule update to the owner's project management team with the pay application. Primavera P6, Microsoft Project or your own project controls platform holds the activities grouped by WBS: send them to the Carbone API as JSON and get back the PDF report. In this example, Calder Ridge Constructors issues update 14 of a four-story medical office building, with an 8 working day slip of substantial completion driven by the switchgear delivery.

The report follows the structure of a schedule summary layout: project header with the data date and the baseline, four status indicators, activities grouped by phase with original duration, start, finish, baseline finish, variance, total float, percent complete and the critical flag, a monthly Gantt column, a critical path narrative and the issued by and reviewed by block. Durations, variance and float are in working days.

In this example, you will:

  • Compute values per activity and per phase with :set
  • Add up durations and count critical activities with aggregators and array filters
  • Shorten a nested loop and draw Gantt bars with aliases
  • Repeat the column headers when the table continues on the next page

How to build the schedule report

Follow these steps to build the template:

1. Compute progress with :set

The JSON holds raw values from the scheduling software: for each activity, od (original duration), pct (percent complete) and schedulePct (baseline progress expected at the data date). At the top of the document, tags with :set add the computed values to the data:

{d.phases[].activities[].od:mul(.pct):div(100):set(.earned)}
{d.phases[].activities[].od:aggSum(..code):set(..odTotal)}
{d.phases[].activities[].earned:aggSum(..code):set(..earnedTotal)}
{d.phases[].earnedTotal:div(.odTotal):mul(100):formatN(0):append(%):set(.pctDone)}
{d.phases[].activities[].critical:ifEQ(true):show(B3261E):elseShow(57759C):set(.bar)}

earned is the completed part of each duration. :aggSum(..code) adds up the durations of each phase and stores them in the phase with ..odTotal, so pctDone is the percent complete of the phase, weighted by original duration. bar keeps the color of the Gantt bar: red for critical activities.

2. Show the status indicators

The project totals are stored in the complement object, then printed in the four indicators:

{d.phases[].activities[].od:aggSum:set(c.totalOd)}
{d.phases[].activities[].earned:aggSum:div(c.totalOd):mul(100):set(c.actualPct)}
{c.actualPct:formatN(1)}%
{d.phases[].activities[critical=true].id:aggCount}

The last tag counts the critical activities with an array filter. The alias {#sc = d.phases[code=MS].activities[id=M1040]} finds the substantial completion milestone with an array search, so {$sc.finish:formatD(DD-MMM-YY)} prints the forecast and {$sc.variance} the schedule variance. {$sc.variance:ifLT(0):show(B3261E):elseShow(1D2033):color(p)} turns it red when the project is late (colors).

3. Group the activities by phase

The table has one phase row, one activity row and two rows that end the loops, {d.phases[i].activities[i+1]} and {d.phases[i+1]} (nested loops). The phase row prints the subtotals: {d.phases[i].activities[].id:aggCount} activities, {d.phases[i].pctDone}, the lowest total float with {d.phases[i].minTf} (stored with :aggMin(..code)), and the number of critical activities with {d.phases[i].activities[critical=true].id:aggCount}.

In the activity row, the alias {#act = d.phases[i].activities[i]} shortens every tag: {$act.id}, {$act.name}, {$act.od}, {$act.finish:formatD(DD-MMM-YY)}, {$act.tf}, {$act.pct}%. Actual dates get an "A" suffix with {$act.finishActual:ifEQ(true):show(' A'):elseShow('')}.

4. Draw the Gantt bars

Each month is a narrow cell. A parametrized alias tests whether the activity overlaps the month, with dates converted to numbers by :formatD(YYYYMMDD):

{#bar($from, $to, $on, $off) = d.phases[i].activities[i].type:ifNE(MS):and(.start):formatD(YYYYMMDD):ifLTE($to):and(.finish):formatD(YYYYMMDD):ifGTE($from):show($on):elseShow($off)}

The October 2026 cell holds {$bar(20261001, 20261031, B3B9C4, E3E8EF):color(cell, background)}: gray for actual work up to the data date, a light tint to mark the data date month. Later months pass .bar as $on, so remaining work is blue, or red on the critical path. A second alias, $ms, prints a diamond in the month of each milestone, and $sum draws the phase summary bar.

5. Continue the table on the next pages

Select the two header rows, open Table Properties, and in the Row tab, check Repeat as header row at the top of each page (pagination). In the same tab, uncheck Allow row to break across pages on every row. The footer prints the project, the data date and "Page X of Y".

Save the DOCX template, send the JSON exported from your scheduling software, and let Carbone generate the PDF of each monthly update.

Check out these similar templates to learn more:

Trusted by 800+ paid customers in 40+ countries

Finance
Healthcare
Insurance
Legal
Public
Retail
Energy
Software
Telecom
Dior
Thales
Younited
Danfoss
CMA CGM
Illumina
KparK
Scalingo
French Ministry of the Armed Forces
BMW
Telus
Bestseller
Flagship Biosciences
Insly
Ninox
Sodexo