Reliable Promises and the Commitment Cycle

Overview
In the PMI Construction Professional (PMI-CP) body of knowledge, Reliable Promises and the Commitment Cycle are central ideas in communication tools and strategy, especially in Lean construction and the Last Planner System (LPS). Construction projects are networks of commitments between owners, designers, general contractors, trade partners, suppliers and inspectors. When those commitments are vague, coerced or unreliable, work flow breaks down, rework increases and schedules slip. This topic explains how to turn casual statements like 'I'll try to get it done' into dependable commitments that others can plan around.

Why It Is Important
1. Construction is a chain of hand-offs. Each trade depends on the one before it. A broken promise ripples down the chain and causes idle crews, stacked trades and safety risks.
2. Reliability matters more than speed. Lean thinking holds that predictable work flow lets teams plan with confidence, reduce buffers and cut waste. A team that keeps 90 percent of its promises usually beats a team that promises a lot and delivers half.
3. It builds trust and accountability. Reliable promises create a culture where people speak up early about problems instead of hiding them.
4. It improves communication quality. The commitment cycle gives a shared structure for requests and agreements, reducing misunderstanding about scope, timing and quality.
5. It is measurable. Promise reliability is tracked with Percent Plan Complete (PPC), which supports continuous improvement through root-cause analysis of missed commitments.

What It Is
Reliable Promise: A commitment made by a performer to a customer (requester) that the performer has good reason to believe they can keep. It is made freely, not imposed. In Lean construction (drawing on the work of Fernando Flores, Hal Macomber and the Lean Construction Institute), a promise is reliable when the person promising can answer yes to these conditions:
  - Clear Conditions of Satisfaction: The performer and customer both understand exactly what will be delivered, to what standard, by when and where.
  - Competence / Capability: The performer has the skills, information, tools and authority to do the work.
  - Capacity: The performer has the crew, time, materials and resources available, with prerequisites (constraints) removed.
  - Sincerity: The performer genuinely intends to deliver and is not just saying yes to avoid conflict.
  - Willingness to be accountable: The performer accepts responsibility and will notify the customer early and renegotiate if circumstances change, and will deal with consequences if the promise is missed.

Commitment Cycle (also called the Conversation for Action or Workflow Loop): A structured, repeatable conversation between a customer (who needs something) and a performer (who will provide it). It has four main phases:
  1. Request (Preparation / Ask): The customer makes a clear request, stating conditions of satisfaction and the needed date.
  2. Negotiate and Promise (Agreement): The performer responds. Valid responses are accept (promise), decline, counter-offer, or commit to commit later (e.g., 'I will confirm by Tuesday after I check material delivery'). Negotiation continues until there is a mutual agreement.
  3. Perform (Execution): The performer does the work. If something threatens the promise, the performer informs the customer immediately and renegotiates.
  4. Declare Complete and Accept (Acceptance / Satisfaction): The performer declares the work complete; the customer checks it against the conditions of satisfaction and declares acceptance, closing the loop. If not satisfied, the loop reopens.

How It Works in Practice
Within the Last Planner System:
  - Master and Phase (Pull) Planning: Trades negotiate hand-offs backward from milestones, making promises to each other about what they need and what they will deliver.
  - Lookahead Planning and Make-Ready: Constraints (drawings, RFIs, materials, permits, prior work, equipment, labor) are identified and removed so that tasks become 'sound' and promises can be reliable.
  - Weekly Work Planning: Last Planners (foremen and crew leaders who directly control the work) make commitments only for work that is sound. This applies the principle of should, can, will, did: only commit to what can be done.
  - Daily Huddles: Short check-ins to confirm progress and flag risks to promises early.
  - Measure and Learn: PPC = number of promises completed as committed divided by total promises made. Missed commitments are analyzed for root causes (e.g., using 5 Whys) and countermeasures are applied.

Example: The drywall foreman asks the electrical foreman: 'Can you finish rough-in and inspection on Level 3 east wing by Thursday noon so we can start hanging board Friday?' The electrical foreman checks crew availability, material and inspection booking, then replies: 'I can complete rough-in by Wednesday, but the inspector is only available Thursday at 3 p.m. Can you start Friday at 7 a.m. instead of Thursday afternoon?' The drywall foreman agrees. That is a negotiated, reliable promise. On Tuesday, the electrician learns a panel is delayed and immediately tells the drywall foreman, who resequences to another area. The cycle protects work flow even when problems occur.

Key Behaviors and Cultural Elements
  - It is acceptable, even encouraged, to say no or to counter-offer. A forced yes is not a reliable promise.
  - Promises are made by the people who do or directly supervise the work, not imposed from above.
  - Early warning is a sign of reliability, not failure.
  - The focus of missed promises is learning, not blame.
  - Commitments are made publicly (e.g., on the weekly work plan board), which increases accountability and visibility.

Common Misconceptions
  - Misconception: A reliable promise means never failing. Reality: It means making promises carefully and communicating early when they are at risk.
  - Misconception: The project manager should assign tasks and dates. Reality: In Lean, the performer makes the commitment after negotiation.
  - Misconception: The cycle ends when work is done. Reality: It ends when the customer declares satisfaction.
  - Misconception: High PPC alone is the goal. Reality: Learning from variance and improving flow is the goal; PPC is the indicator.

Exam Tips: Answering Questions on Reliable Promises and the Commitment Cycle
1. Know the order of the cycle. Request, negotiate/promise, perform, declare complete, accept. If a question asks what comes next after performance, the answer is the performer declaring completion, followed by customer acceptance.
2. Memorize the elements of a reliable promise. Clear conditions of satisfaction, capability, capacity, sincerity, and willingness to be accountable and renegotiate. Questions often describe a scenario missing one element and ask what is wrong.
3. Choose answers that empower the performer. The best answer usually lets the trade foreman or Last Planner negotiate and commit, rather than having a manager dictate dates.
4. Early communication beats silent failure. If a scenario shows a performer realizing a commitment is at risk, the correct action is to notify the customer immediately and renegotiate, not to wait, work overtime silently, or hide the issue.
5. 'No' and counter-offers are valid. Answers that suggest accepting an unrealistic request to keep the client happy are usually wrong.
6. Link promises to constraints. If a question involves unreliable commitments, look for answers about make-ready planning, constraint removal, and committing only to sound tasks.
7. Connect to PPC and learning. When asked how to measure or improve reliability, choose PPC tracking plus root-cause analysis of variances, not punishment or blame.
8. Watch for the customer's role. The customer must state clear conditions of satisfaction and must formally accept. Ambiguous requests are a root cause of broken promises.
9. Eliminate blame-oriented options. PMI-CP favors collaborative, learning-focused, psychologically safe cultures. Answers that emphasize penalties, finger-pointing or escalation as a first step are generally distractors.
10. Read scenario keywords carefully. Words like 'assigned,' 'forced,' 'assumed,' or 'hoped' signal an unreliable promise. Words like 'negotiated,' 'confirmed,' 'clear criteria,' and 'resources verified' signal a reliable one.

Quick Practice Scenario
A superintendent tells the mechanical foreman to finish duct installation by Friday. The foreman says yes but knows the duct shipment has not arrived. What is the primary issue?
Answer: The promise is not reliable because the foreman lacks capacity (materials) and the commitment was not sincere or negotiated. The best action is for the foreman to state the constraint, counter-offer a realistic date or commit to confirm once delivery is verified, and for the team to address the constraint in make-ready planning.

Summary
Reliable promises and the commitment cycle turn project communication into a disciplined system of requests, negotiated agreements, execution and acceptance. They are the backbone of the Last Planner System, enable predictable work flow, and build trust across the project team. For the exam, remember the cycle's steps, the conditions of a reliable promise, the importance of early renegotiation, and the Lean preference for performer-made commitments, constraint removal, and learning over blame.