Heatmap

Construction Progress Heatmap

Repeated work on every floor or area in one grid, built bottom to top from your schedule and colored by total float or by slippage since the last update.

A construction progress heatmap is a grid of floors or areas against the work that repeats on each of them, with every cell colored by the total float of that work. Update Slippage colors each cell by how far that work's finish moved since the last update instead, as a percent of its duration. Pathizer builds it from the schedule the Schedule Updater works from: rows are floors or areas from the bottom of the building up, columns are the repeated work, and each cell shows actual percent complete.

Why repeated work needs its own view

Multi-story buildings repeat the same work floor after floor: framing, rough-in, drywall, paint, flooring. A schedule lists that work as hundreds of separate activities under each floor's WBS, so a Gantt chart shows every one of them on its own row. What a superintendent wants to know is simpler. Which floors are behind, and in which trade?

A heatmap answers that in one grid. Floors run up the side, the repeated work runs across the bottom, and each cell takes a color for how that trade is doing on that floor. A trade slipping on every floor reads as a colored column. A floor where every trade is behind reads as a colored row. Both patterns are hard to see in a long activity list.

How Pathizer builds the grid

Nothing has to be set up. Pathizer reads the schedule the Schedule Updater works from and looks for activity names that appear under two or more WBS areas. Names are compared without case or extra spacing, with a leading zero ignored and bracketed notes and the area's own name left out, so a ceilings activity named for Area 01 and the same one named for Area 02 land in one column. Each repeated name is a column.

Work under a WBS that reads as a floor or level goes on that level's row, even when units or rooms sit between the floor and the activity. Other work takes the WBS level whose names differ the most between that column's activities. Either way, drywall on Floor 4 and Floor 5 lands on the rows Floor 4 and Floor 5, whether the schedule is built floor first or trade first. Rows are ordered as a building goes up: foundations and basements at the bottom, then ground, mezzanine, numbered floors and podium levels, penthouse and roof at the top. Areas that do not read as a level sit above them in natural number order. Columns run left to right in the order the work is planned to start. Work whose name does not repeat is left off the grid, and the page says how many activities that is.

What the colors mean

Each cell shows the duration-weighted actual percent complete of its activities. By default its color shows the lowest total float of its open work, in calendar days, so the most critical work sets the color. Completed work has no total float and does not count. Colors update when a new update is published.

  • Green: 31 calendar days of total float or more
  • Lime: 11 to 30 calendar days
  • Yellow: -10 to 10 calendar days
  • Orange: -11 to -30 calendar days
  • Red: -31 calendar days or less
  • Gray: no open work with a total float

Update Slippage

Tick Update Slippage to color each cell by how far its finishes moved since the last update instead: the actual finish when the work is done, else the forecast finish, as a percent of each activity's own duration. A five-day slip on a ten-day activity counts for more than the same slip on a ten-week one. Work that is under way, or not due yet, stays yellow unless its finish moved, so being unfinished never reads as a delay. Milestones and work with no duration are left out of the color.

  • Red: finish moved later by more than 30% of its duration
  • Orange: finish moved 10% to 30% of its duration later
  • Yellow: finish within 10% of its duration, or work not yet due that has not moved
  • Lime: finish moved 10% to 30% of its duration earlier
  • Green: finish moved earlier by more than 30% of its duration
  • Gray: nothing to compare (new work, work with no duration, or finished before the last update)

Views for the field and the update meeting

Floors and levels shows the rows that read as building levels; All areas adds every other repeated area. By default the grid keeps only work in this cycle or the last update that has a finish to compare, so no gray cell is left. Work that closed in the last update still shows: work that finished more than 10% of its duration ahead of where the last update had it shows lime or green. Show Out of range adds the rest back.

Click any cell to list its activities, each with its actual percent and its total float, or under Update Slippage how far its finish moved, in days and as a percent of its duration. Color the labels gives every row and work name the color of its cells: the lowest total float, or under Update Slippage their average. The work names and the legend stay in view while the grid scrolls, and the band that holds the names can be dragged taller for long names.

The percent in each cell reads the Schedule Updater's live copy, so progress the field team saves there shows the next time the page loads. The colors compare published updates, so they change when the next update is published. It changes no schedule data. It is a view of progress, not a delay analysis: why a floor is behind is a question for the float paths and the update review.

Who It Is For

Seeing which floors and trades are ahead or behind

Superintendents and field teamsProject managersSchedulers running the monthly update

What Pathizer Does

Rows and columns found from the schedule itself: repeated activity names become columns, and the floors or areas they sit under become rows

Floors ordered bottom to top, from foundations and basements up through numbered floors, podium and penthouse to the roof

Each cell's duration-weighted actual percent complete, colored by the lowest total float of its open work

Five total float bands from 31 calendar days or more down to -31 or less, and gray where there is no open work

Update Slippage colors the cells by how far their finishes moved since the last update instead

Floors and levels or All areas, Show Out of range, and Update Slippage

Click a cell to list its activities with the total float of each, or how far each finish moved

Definitions

Terms used on this page.

Repeated work

An activity name that appears under two or more WBS areas, such as the same drywall activity on Floor 4 and Floor 5. Each one becomes a column.

Update cycle

The period from the Schedule Updater's data date to the data date it would export now. Hide this period keeps only the rows and columns with work in it or in the last update's period.

Total float

How many calendar days an activity's finish can move before it delays the project: its late finish less its early finish in the schedule the Schedule Updater works from. A cell shows the lowest total float of its open work, so the most critical work sets its color.

Finish movement

How far an activity's finish moved from the last update to this one, as a percent of its own duration in the last update: the actual finish when the work is done, else the forecast finish. A cell averages it across its activities, weighted by duration, so a long activity and a short one are judged on the same scale.

More in the glossary: Work Breakdown Structure (WBS), Data date.

Practical Outputs

What you get.

One view of where repeated work stands on every floor or area

The floors and trades with the least total float, or whose finishes slipped since the last update, by color

The activities behind any cell, with the figures that set its color

Related Workflows

Related pages.

FAQ

Included with the Enterprise Plan

Heatmap comes with the Enterprise subscription, which carries Operations, Controls and Delay Analyzer for the whole organization. The Enterprise Plan is $250 a month for every 2,500 activities. See pricing

Run it on your own schedules with the 60-Day Pilot. It covers your whole organization for 60 days and needs no card.

Start a 60-Day Pilot

Each finding traces back to the schedule export it came from.

When the update history cannot tie a day of movement to a party, Pathizer leaves that day unattributed. It does not split the day pro rata or round it into the largest share.