Plan compliance: plan-vs-actual over 30 days

4 min read · Updated 15 Jun 2026

Plan compliance is one honest number: the approved hours your crews actually worked against the crew-hours your foremen planned, over a rolling 30 days. It reads approved entries only, so a busy close-out can't inflate it — it tells you whether the plan is being kept.

What it measures

Every daily plan commits a number of crew-hours — crew size × hours per person across the activities on it. Plan compliance compares that planned figure against the approved hours that landed on those same activities, across the last 30 days. Above 100% means more got worked than planned; below means the plan is slipping.

Approved hourslast 30 days ÷ Planned crew-hourscrew size × hours/person = Compliance%

Approved-only, on purpose

The KPI counts approved hours and nothing else. Draft and submitted entries don't move it, and — importantly — the hours correction a PM can make when closing a plan never feeds it either. That correction fixes the plan's own record; the compliance number stays anchored to what was genuinely approved, so it can't be talked up at close-out.

Where to find it

1
Open the project dashboard

Plan compliance sits in the KPI grid alongside % complete, S/E, SPI, CPI and EAC. It shows the percentage, the number of plans in the window, and the hours behind it.

2
Click through to the plans

The tile links straight to the project's daily-plans list, so when the number looks off you're one tap from the plans that drove it.

Closing a plan feeds the record

At end of day a foreman or PM closes the plan and enters what actually got installed against each activity, with a one-line variance reason where the day didn't go to plan. They can also enter an actual-hours correction — but that needs its own reason and, again, it adjusts the plan's record, not the compliance KPI. Anyone who can manage plans can close them, and the foreman who authored a plan can always close their own.

Reserved draft entries don't count until they're approved. Sharing a plan can pre-create blank-hours placeholders so clock-ins land in the right place — but they only contribute to compliance once a foreman approves the real hours.
Plan compliance is read-only and respects project access — everyone on the project can see it, and it only ever reflects the projects you're allowed to view.

What next?

Compliance tells you the past 30 days; look-ahead tells you the next six weeks: Look-Ahead →

Frequently asked

What exactly does plan compliance divide?

Approved hours worked on planned activities over the last 30 days, divided by the planned crew-hours (crew size × hours per person) for those plans. Above 100% means more was worked than planned; below means the plan is slipping.

Can the hours correction at plan close-out change the KPI?

No. The actual-hours correction a PM can enter when closing a plan adjusts the plan's own record only. The compliance KPI always reads genuinely approved hours, so it can't be inflated at close-out.

Do reserved draft entries count toward compliance?

Not until they're approved. Sharing a plan can pre-create blank-hours placeholders so clock-ins land in the right place, but they only contribute once a foreman approves the real hours.

Who can see plan compliance, and who can close plans?

Everyone on the project can see the KPI (it respects project access). Anyone who can manage daily plans can close them, and the foreman who authored a plan can always close their own.

Is the window always 30 days?

30 days is the default rolling window shown on the dashboard. The underlying report accepts a custom window if you need a shorter or longer view.

Related