Weekly Work Plans: Commit to Work That Is Ready

LCI describes Last Planner System planning through connected conversations about what should, can and will happen, followed by execution and learning. Weekly promises are not the same as the work still needing preparation. [1]

OlbrichCo recommends two visible lists at the weekly meeting: work required to protect the next milestone, and work genuinely ready for a crew to undertake. Their difference is management’s constraint-removal agenda. Do not fill the week with convenient tasks and let a blocked, consequential handoff disappear. Choose one bounded work area with interacting trades for the first trial.

GAO’s schedule guide describes an integrated schedule as a model connecting activity completion to major events and supporting analysis of change. A weekly task list does not replace that wider model. [4]

On an Iranian project, name a site coordinator, participating trade supervisors and a scheduler who connects their assignments to the current programme. Include the people who can secure drawings, deliveries, inspections and access. Agree the actual workweek, shifts and one unambiguous date convention; show Persian dates if useful, but reconcile them with the schedule’s controlled calendar.

CII’s Advanced Work Packaging overview connects engineering, procurement and installation packages across delivery. It also identifies management commitment, contracts and education as implementation needs. AWP is a separate approach, not another name for LPS. [2]

Borrow the interface discipline for a small constraint register. For each upcoming assignment, record location, linked programme activity, prerequisite, responsible person, needed-by date, promised resolution date and evidence required for closure. Distinguish a requested drawing from an approved revision, ordered material from accepted stock, and an inspection booking from actual attendance confirmed for the needed window.

Walk the workface with the releasing and receiving trades. Check design information, predecessor completion, material identity and quantity, competent crew, tools, safe access, temporary works, permits and required quality holds. The responsible specialists retain their approvals. A readiness tick cannot authorize hazardous work, release a structural hold or waive a test. Mark uncertain conditions as unresolved rather than optimistically available.

Set the lookahead horizon from the time needed to resolve the actual constraints. A long-lead procurement decision may belong well beyond the weekly board. Obtain dated supplier commitments and review alternatives through the contract and engineering change process. Where a delivery or approval remains uncertain, escalate its milestone consequence early; do not force a crew to promise completion based on an unconfirmed arrival.

LCI’s weekly-planning guidance calls for clearly defined assignments, correct sequencing, feasibility and a match to team capacity. It places the promises with specific individuals rather than treating the plan as an anonymous instruction. [3]

Replace “continue ceiling work” with an agreed location, quantity or bounded scope, finish day and observable handoff condition. For example, define which corridor bay will be available for the following trade, with its required inspections complete. The supervisor making the promise and the receiving trade should agree what done means before the week starts. This is an illustrative assignment, not a project result.

Check the proposed load against available people, skills, work space, shared equipment and supervisory capacity. Resolve competing requests for the same lifting slot or inspection witness before issuing the plan. Reserve realistic capacity for known variability and keep a small list of genuinely ready alternative work. Do not give a universal buffer percentage or treat overtime as an automatic remedy for an overloaded plan.

Freeze the original weekly commitments with a revision and named owners. Keep required-but-unready work visible beside them, with escalation actions. Agree the meeting and cutoff around the site’s actual working pattern, not a foreign example’s weekday. Record scope changes and cancellations separately; planning agreement does not itself change the baseline, payment rights or the contract’s notice requirements.

At a short daily coordination meeting, ask each supervisor what was handed over, what threatens the next promise and which decision is needed today. Bring the receiver into a disputed handoff. Record an action owner and response time, then take detailed technical problem-solving to the appropriate people. The board should expose a blocked interface while there is still time to act.

When a prerequisite fails, first protect the work and people under the approved site arrangements. Decide whether to stop the affected assignment, use an already reviewed alternative, or seek a changed sequence. Check effects on other trades before moving a crew. Never bypass inspection, safe access or material approval merely to preserve the completion score.

Keep the original promise and its outcome even when a sensible recovery plan is agreed. Log unplanned work separately with its authorization and reason; it should not retrospectively replace a missed task. Give unfinished work a reviewed remaining scope and a new commitment, linked to the original. Distinguish an external change from a planning omission without making unsupported claims about delay liability.

For mixed paper and digital working, use stable assignment and location identifiers on a Persian board, an offline register and supporting photographs. Assign one coordinator to reconcile updates and withdraw obsolete versions. A messaging thread may alert people, but retain the decision and evidence in the controlled record. Introduce software only after the team can maintain these definitions consistently.

LCI defines Percent Plan Complete, or PPC, using assignments fully finished on the promised day divided by the assignments promised for the week, expressed as a percentage. [5]

Illustrative arithmetic: eight fulfilled promises out of ten give 80% PPC. That does not mean 80% physical progress, earned value or schedule completion. A nearly finished assignment is not a fulfilled promise. Predefine how to report authorized changes; retain the original denominator and explain them separately. Do not split easy tasks into many entries after the fact to improve the score.

LCI’s September 2026 Beyond PPC webinar description explicitly distinguishes commitment reliability from selecting the right work and protecting milestones. The published event brief is evidence of that distinction, not independent proof of a tool’s performance. [6]

Alongside PPC, review which milestone-required handoffs were due, which were achieved and which remain blocked or uncommitted. Ask the scheduler to update the consequence using the integrated programme. Track overdue constraints by age and decision owner. Discuss repeated reasons for noncompletion with the people involved, select one countermeasure and check its effect next week; use the measure for learning, not a crew league table.

Run a proposed four-week pilot in one coordinated zone before expanding. In the preparation meeting, agree assignment size, completion evidence, cutoff, constraint closure, escalation and change treatment. Obtain participation from the owner’s decision-makers and relevant subcontractors, not only the planning office. If nobody can resolve a critical approval or supply dependency, expose that limitation instead of declaring the planning process operational.

Retain each original plan, daily changes, handoff confirmations, constraint closures and weekly review. Measure fulfilled promises with counts, required handoffs achieved, overdue constraints, recurring failure causes and effort spent maintaining the record. Compare like-for-like scope and assignment definitions. Set project-specific improvement targets after establishing a credible baseline; this note claims no productivity percentage, cost saving or delivery guarantee.

At the review, ask whether a supervisor can explain tomorrow’s assignment, demonstrate its prerequisites and identify the receiver without reconstructing a chat history. Expand where the process supports timely decisions; simplify duplicate entry where it does not. Revisit the planning horizon and capacity assumptions when crews, suppliers, design, access or the milestone sequence changes. Preserve earlier records rather than rewriting an unsuccessful pilot.

Applicable Iranian requirements, contracts, actual site conditions and competent local planning, engineering and safety review govern implementation. Weekly planning does not authorize design changes, certify work or determine entitlement. Its useful outcome is narrower: an explicit, supportable promise and an early decision when that promise cannot be made. The cover’s timber key is a readiness metaphor, not an approved connection detail.