Esc

↑↓ move↵ openIndex · Pagefind
Scheduling / Last Planner: weekly work plans, commitments and PPC

Last Planner: weekly work plans, commitments and PPC

Turn the constraints lookahead into a weekly work plan. Record what each trade promises to finish, commit only make-ready work, mark each commitment met or missed with a reason, and follow percent plan complete (PPC) by week and by trade.

On this page

The master schedule says what should happen. The Last Planner method asks the people who do the work what they will do next week, and then measures how often they did it. In os.construction it lives on the Lookahead page (Schedule › Update › Lookahead), under the constraints lookahead, so a promise is made against the same list of open constraints the team is clearing.

How it fits the lookahead

The Constraints lookahead lists the activities coming up and the records linked to them as constraints: submittals, purchase orders and deliveries that gate an activity, and RFIs, inspections and punch items that block it. An activity with an open constraint isn’t make-ready. See activity links.

Below it, the page shows the weekly work plan for one week, Monday to Sunday, with Previous week, This week and Next week, and Plan reliability (PPC) for the 12 weeks up to the current week.

Plan a week

  1. Start the weekly work plan. One plan per project per week. It starts as a draft.
  2. Add commitments. Choose a lookahead activity for that week, then write the commitment (what will be finished), the trade or crew making the promise, and optionally a quantity and unit. The trade fills in from the activity when it has one: its Trade field, or else an activity code named Trade, Crew, Subcontractor, Responsibility or Discipline. Change it if a different crew is making the promise. The Make-ready column shows Ready, the number of open constraints, or Not in window.
  3. Commit the week. Committing is refused while any commitment has open constraints. Clear them, remove the commitment, or tick Commit work that is not make-ready (recorded). That choice is stored on the plan and shown as Committed with open constraints. It exists for loading past weeks, not for planning.
  4. Assess at the end of the week. Mark each commitment Met, or Missed with a reason. Clear sets it back to Not assessed.

Committing freezes the week. Commitments can’t be added, removed or reworded afterwards, only assessed and annotated. The database enforces this as well as the app. A draft week can be deleted; a committed one can’t.

Which activities a commitment can name

A commitment names an activity in the project’s current saved schedule that you can see. Anything else is refused, whether it’s a typo, an activity you can’t see or one that was deleted. The REST API answers 422 and says which IDs it didn’t find.

  • Activities removed later. When the schedule is re-planned and an activity is deleted, a committed week keeps its commitments on that activity, and you can still assess them. A draft week can’t be committed while one of its commitments names a removed activity. Point it at another activity or remove it first.
  • Past weeks. A week that has ended may also name an activity of the schedule as it stood that week: the version current when the week began, plus up to 25 versions saved during it. That lets you load history after the schedule has moved on. The current week and future weeks accept the current schedule only.
  • The trade. Through the API, leave trade out and it’s filled in from the activity, as on the page. If the activity has no trade field or trade code, the API asks for one (422). A trade you give is kept as written.

The rules that keep PPC honest

PPC (percent plan complete) is commitments met divided by commitments made, for one committed week. It measures how reliable the plan is, not how much work was done. The rules follow the method:

  • A commitment is met or missed. Partly done is missed.
  • A missed commitment needs a reason for variance: prerequisite work, materials, labour, equipment, information, design change, directive, weather, access, over-commitment, or Not recorded when nobody gave one. Unexplained misses are counted as such.
  • A week with any unassessed commitment has no PPC until it is assessed. It is never shown as 100%.
  • A week with no commitments, or with no plan, is unmeasured, never 0%.
  • Only committed weeks count. A draft’s denominator isn’t fixed yet.

Reading plan reliability

  • Latest PPC and Mean PPC (measured weeks), with how many of the weeks were measured.
  • A PPC trend by week, with gaps for unmeasured weeks.
  • Reasons for variance: missed commitments by reason.
  • PPC by trade: committed, met, missed, not assessed and PPC per trade over the window. A trade’s PPC is blank while any of its commitments is unassessed.
  • Warnings about the measurement itself: a week committed empty, a week not fully assessed, and misses with no recorded reason.

The trend is the signal. One week’s PPC says little; a run of weeks shows whether the planning is getting more reliable and which constraint keeps breaking promises.

Who can do what

Anyone with Schedule view can read weekly plans and PPC. Starting, editing, committing and assessing a week needs Schedule edit. Every change is audited. Nothing here moves a schedule date or records progress: update the schedule through the update cycle as usual.

Limits

  • A week holds up to 500 commitments. The REST API accepts up to 200 in one request.
  • The page offers only that week’s lookahead activities. The API accepts any activity of the current saved schedule, and for a past week, of the schedule as it stood then.
  • Changing a draft commitment’s activity doesn’t change its trade. Edit the trade yourself if the crew changes too.
  • Make-ready is read from the constraints lookahead when you commit. It isn’t re-checked when you assess.
  • The PPC report covers at most 104 weeks.
  • Weekly plans aren’t exchanged through XER or P6 XML.
  • Mistake: Committing everything in the lookahead

    In the app: Commit only work that is make-ready and that the trade has agreed to. Over-commitment is itself a reason for variance.

  • Mistake: Marking a commitment met because it is mostly done

    In the app: Met means finished as promised. Mark it missed and record why; partial credit hides the problem PPC is meant to show.

  • Mistake: Leaving commitments unassessed

    In the app: An unassessed week has no PPC. Assess every commitment, using Not recorded when nobody gave a reason.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file