At the weekly review, a task marked complete may still have an unfinished handoff, and a Wednesday promise completed Friday may now carry a Friday due date. Those edits can inflate percent plan complete. Under a promised-day policy, PPC = (commitments completed in full by their promised day / commitments in the frozen weekly plan) × 100.
Keep the original scope and date beside the completion evidence (including the receiving trade’s acceptance when it was part of the promise). In a hypothetical week with eight commitments and six fully completed on time, PPC is 75%. That measures reliability against those promises; it says nothing about the percentage of the whole project built or the value earned.
Freeze the commitments before work starts
Start with the version agreed at the weekly planning meeting. Give each commitment a stable ID, location, responsible trade, completion condition, and promised finish day. “Work on rough-in” leaves the scorer to invent the finish condition later. “Complete overhead rough-in in Room A for the agreed inspection” gives the review something specific to accept or reject.
The Lean Construction Institute’s Weekly Work Planning standard work describes promises made by the performers and records the days activities will be completed. Preserve those promises in a dated snapshot. An Excel tab saved after Friday’s updates cannot establish what the team committed to before the week began.
Save the plan version, freeze timestamp, reporting period, and scoring policy with the rows. Keep later edits in a change log containing the original value, new value, author, time, and reason. Correcting a typing error may warrant a restatement, but overwriting the original prevents anyone from distinguishing a correction from a new promise.
Prepare next week’s commitments through construction lookahead planning, where access, materials, and other prerequisites can be checked before a trade promises the work. Once a week is frozen, the PPC review asks whether its commitments were kept. Reopening readiness decisions after the outcome is known changes the question.
Apply the agreed completion and timing rule
Use a binary result for each commitment: the full promised handoff was achieved, or it was not. LCI’s Last Planner System Workbook, pages 40-41 divides actual completions by weekly assignments and gives no credit for unfinished assignments. Starting work, using the planned labor hours, or finishing most of the quantity does not establish the promised completion.
Declare the timing convention before comparing scores. The workbook permits timing variation within the week when an assignment finishes by week end. The promised-day policy used here is stricter: a Wednesday handoff completed Friday fails its original timing commitment. Label that basis in reports so a week-end score and a promised-day score are never presented as the same measure.
Check the actual completion time against the promised day in the project’s agreed time zone. Keep the time evidence was entered separate from the time work was completed. A late report can document an on-time handoff, but it needs supporting evidence and a visible correction; moving the promised date to match the report would erase the miss.
Calculate a week with eight frozen commitments
Assume the following hypothetical commitments concern separate work areas and were frozen before the week started. Each has a full-handoff condition agreed with its receiving party. Six meet both that condition and the promised day. One finishes late within the week, and one remains incomplete at the weekly cutoff.
| Frozen commitment | Promised day | Verified outcome | Promised-day credit |
|---|---|---|---|
| Excavation, Area A | Monday | Full handoff Monday | Yes |
| Rebar, Area B | Tuesday | Full handoff Tuesday | Yes |
| Sleeves, Area C | Wednesday | Full handoff Wednesday | Yes |
| Framing, Area D | Thursday | Full handoff Thursday | Yes |
| Temporary lighting, Area E | Thursday | Full handoff Thursday | Yes |
| Door frames, Area F | Friday | Full handoff Friday | Yes |
| Overhead rough-in, Room A | Wednesday | Full handoff Friday | No: late |
| Blockwork, Area G | Friday | Part complete at cutoff | No: incomplete |
Promised-day PPC = 6 / 8 × 100 = 75%. Keep both missed commitments in the denominator. Giving partial credit to the blockwork or replacing Wednesday with Friday would increase the reported score without delivering the original handoffs. If you also publish a week-end measure, identify it as a different timing basis and retain the same frozen commitment list.
Retain the counts beside the percentage. For a rollup across reporting groups, sum credited commitments and frozen commitments before dividing; an unweighted average gives a small group the same influence as a large one. If the frozen list is empty, report no committed work and leave PPC undefined rather than displaying a perfect score.
Bring a weekly plan and its closeout into one review
Start for free with a saved plan and completion register to explore a report that keeps original promises beside the supporting records.
Record cancellations and late additions without repairing the denominator
Adopt a written rule that the frozen plan remains the basis for its original PPC. If a scope change cancels a commitment after the freeze, preserve the row and record who canceled it, when, and why. It remains an unfulfilled original promise under this policy, with the cancellation distinguished from a crew execution failure. Operationally, stop canceled work when directed; preserving a score never authorizes continuing it.
Keep late additions and workable-backlog tasks in a separate population. They may be useful work, but completing them cannot demonstrate that the original promises were reliable. Retain their quantities and completion evidence in the production record, and show them as additions alongside the frozen-plan result. Do not add completed extras to the numerator while leaving them out of the denominator.
If management needs a revised-plan view, publish it with a new version and an explicit explanation of the changed population. Preserve the original score and the reconciliation between versions. The same discipline applies when a source row was duplicated or a completion record was wrong: corrections should be inspectable rather than silently changing last week’s history.
Turn missed handoffs into changes for the next plan
Review every unfulfilled commitment with the person who made it. Record the immediate reason and the evidence behind it, then identify a prevention action with an owner and due date. “Materials” alone cannot explain whether a delivery was late, the order was released late, or an approved substitution never reached the field.
LCI’s Last Planner System overview places reasons-for-variance review after completion measurement. In your register, keep the cause separate from the score: a legitimate owner-directed change can explain a miss without turning it into an on-time handoff. Compare recurring causes across weeks to choose an action, then check whether that action was carried out.
Link the miss to the dated observation, inspection, delivery, or instruction that supports it. The capture and correction controls discussed in construction daily report software help establish those records. A Friday status word copied into a report cannot replace evidence that the receiving crew could begin its work as promised.
Read reliability beside workload and milestone movement
PPC counts commitments, so the way you size tasks affects the result. Splitting an easy task into many small promises increases its influence; leaving a difficult handoff as one large promise reduces its influence. Agree on task sizing and location detail before the freeze, preserve the method across weeks, and investigate a change in the number or size of promises before interpreting a rising percentage.
Pair the score with the committed workload, completed quantities where available, and movement against the relevant phase milestones. A team can keep every small promise while omitting the work needed for the next milestone. Christian and Pereira’s Lean Construction Journal paper on additional LPS metrics addresses that gap between weekly plans and longer-term milestones; PPC alone cannot resolve it.
Keep earned value management separate when you need budget-valued progress and cost performance. Applying budget or labor-hour weights changes the commitment-count measure. Report such analysis under its own name and assumptions, while retaining PPC for the declared promise population and timing rule.
Where Permute keeps the scoring definitions consistent
Permute sells the context layer between business data and the AI tools people already use. We can combine permitted Excel or Google Sheets planning records with completion evidence available through supported sources, keeping project, commitment, and plan-version identities aligned. Confirm that the source retains the freeze history before relying on a recurring calculation.
We can encode your agreed denominator, promised-day convention, and exception classifications as reusable definitions. The original population and later changes can then remain separate in a structured report, instead of each reviewer reconstructing the week from the latest spreadsheet. Missing original versions still need to be identified as missing.
A superintendent could ask in Claude, ChatGPT, or Copilot which commitments missed their promised handoff and inspect the source rows and declared calculation within their permissions. We supply the governed business data underneath those tools; the project team supplies and accepts the completion evidence.
Keep field acceptance and schedule decisions with the project team
We do not certify installed work, decide whether an inspection passed, or reconstruct an unsaved plan from a current status field. In this reporting workflow, we read supporting records and do not write changes back into the scheduling system. A human still needs to resolve disputed completion evidence and authorize any restatement.
We are not a forecasting engine. A reliability trend needs the project team’s schedule logic, remaining workload, and current constraints before anyone can judge a recovery date. Access to source rows also depends on connector scope, retained history, and permissions; missing records should qualify the report rather than become assumed completions.
Close the week against the promises it began with
Calculate percent plan complete from the frozen commitments and the timing rule agreed before work started. Give credit only when the full promised handoff meets that rule, while preserving cancellations, additions, and corrections as visible changes. Use missed commitments to choose preventive actions and read the result beside workload and milestone movement. The weekly review can then explain which promises were kept without rewriting those promises to fit the outcome.
Review the records behind your weekly score
Bring a frozen plan, its completion evidence, and a revised copy to a discussion of which histories and definitions a recurring report needs.
Questions about weekly commitment scoring
What if evidence arrives after the weekly review?
Keep the work-completion time separate from the time evidence was entered. If the later record substantiates an on-time full handoff, issue a versioned correction under the agreed review policy and preserve the earlier report. Do not change the original promised date to make the row pass.
What should a week with no commitments show?
Show no committed work and leave PPC undefined because there is no denominator. Do not display a perfect score. Check whether the empty population represents a planned pause or missing plan records before comparing it with other weeks.
Should large activities count more than small ones?
PPC gives each commitment equal weight, which makes consistent task sizing part of the measurement policy. You can review quantities or budget-valued progress alongside it, but label weighted calculations separately. Preserve milestone context so completing easy promises cannot conceal missing required work.