---
name: make-ready-constraints
description: Run the make-ready process of the Last Planner(R) System - screen lookahead tasks for constraints, keep the constraint log with owners and needed-by dates, and measure the planning system with PPC, reasons for variance (Pareto), tasks anticipated (TA), tasks made ready (TMR) and constraint release reliability. Use when the user manages a lookahead, "programación intermedia", "análisis de restricciones", "liberación de restricciones", asks why PPC is low, or prepares the weekly coordination meeting.
---

# Make-ready and constraint metrics

The Last Planner(R) System is a registered mark of the Lean Construction Institute (LCI). This skill helps a team run it; it does not replace the conversations between the people who do the work.

## Inputs
- The lookahead (usually 6 weeks) by task and location, and the constraint log.
- The weekly work plans with done / not done and the reason for each miss.
- Optional: snapshots of the lookahead from previous weeks (for TA and TMR).

## Procedure
1. Screen each lookahead task that enters the window against the constraint types the team uses (commonly: design/information, materials, labor, equipment, space/access, prerequisite work, permits/safety, approvals). One row per constraint: id, task, type, owner (a person who said yes, not a department), identified date, needed-by date (task start minus the lead time the user gives), promised date, released date.
2. Only tasks with all constraints released go to the "workable backlog"; only workable tasks should be committed in the weekly plan.
3. Compute the metrics: `python scripts/constraint_metrics.py --wwp wwp.csv --lookahead lookahead.csv --constraints constraints.csv --horizon 2`.
4. Read them as a system:
   - PPC low and reasons concentrated in materials or information -> make-ready is weak upstream.
   - TA low -> work enters the weekly plan without passing through the lookahead.
   - TMR low -> the lookahead is a wish list; constraints are not being released.
   - Old open constraints without dates or owners -> nobody is managing them.
5. Prepare the meeting: the overdue and due-this-week constraints by owner, the incomplete tasks without a reason (to ask, never to fill), and two learning questions from the Pareto (use `a3-problem-solving` for a recurring reason).

## Output
- `lps_metrics.md`: PPC by week and trade, reasons Pareto, TA/TMR, open constraints by urgency and owner.
- A short agenda for the weekly meeting.

## Never
- Never write a reason for non-completion that the crew did not give.
- Never use PPC to rank or blame crews; it measures the reliability of promises in the system.
- Never move a task into the weekly plan with an open constraint without flagging it.