Commitment-based Management (CbM)

Overview
Commitment-based Management (CbM) is a core communication and coordination approach in the PMI Construction Professional (PMI-CP) body of knowledge. It treats a construction project as a network of commitments (promises) between people rather than just a schedule of activities. Under CbM, work moves forward because specific people make, track, keep and learn from reliable promises to each other. CbM is closely linked with Lean Construction and the Last Planner System (LPS).

Why Commitment-based Management Is Important
Construction projects involve many interdependent parties: owners, designers, general contractors, trade partners, suppliers, inspectors and authorities. Most delays and rework are caused by coordination failures, not by technical gaps. Examples include a trade arriving before the area is ready, a submittal approved late, or materials delivered to the wrong place. Traditional push-based management assumes that if a task is on the schedule, it will happen. CbM recognizes that work only happens when someone sincerely commits to do it and has what they need to do it.

CbM matters because it:
- Increases plan reliability: work promised is work delivered, which stabilizes workflow for downstream trades.
- Builds trust and accountability: commitments are public, specific and owned by named people.
- Surfaces problems early: performers are expected to speak up as soon as a promise is at risk, which supports candor and psychological safety.
- Reduces waste: there is less waiting, rework, over-production and expediting.
- Improves communication quality: vague requests ('get it done ASAP') are replaced with clear requests that have defined conditions of satisfaction and due dates.
- Enables continuous learning: broken promises are analyzed for root causes rather than blamed on individuals.

What Commitment-based Management Is
CbM is a management philosophy and practice, rooted in the language/action work of Fernando Flores and Terry Winograd, and applied to construction by Lean practitioners such as Glenn Ballard, Greg Howell and Hal Macomber. Its central idea is that management is the making and keeping of promises through conversation.

Key concepts:
- Customer (Requester): the person who needs something done and makes a request.
- Performer (Provider): the person who promises to deliver it.
- Request: a clear ask with specific Conditions of Satisfaction (CoS), a due date, and a shared understanding of what 'done' means.
- Promise / Commitment: the performer's sincere agreement to deliver to the CoS by the due date.
- Conditions of Satisfaction: the explicit criteria the customer will use to accept the work, such as quality, quantity, location, format and time.
- Declaration of Completion: the performer states that the work is done.
- Acceptance: the customer confirms the CoS were met, which closes the loop.
- Network of Commitments: the project is the sum of many linked customer-performer promise loops.

How It Works: The Conversation for Action (Promise Cycle)
Every commitment follows a four-phase loop:
1. Preparation / Request: the customer prepares and makes a clear request. It states who, what, when, the CoS and why it matters.
2. Negotiation: the performer can respond in one of five ways:
- Accept (promise)
- Decline
- Counter-offer (for example, a different date or scope)
- Commit to commit later (for example, 'I will confirm by Tuesday after checking with my crew')
- Clarify (ask questions about the CoS)
Saying 'no' or counter-offering is legitimate and encouraged. An honest 'no' is far more valuable than an unreliable 'yes'.
3. Performance: the performer does the work. If something threatens the promise, the performer notifies the customer immediately and re-negotiates or re-promises. They do not stay silent until the due date.
4. Acceptance / Declaration: the performer declares completion and the customer assesses the work against the CoS. The customer then accepts it or explains what is missing. The loop closes only when the customer accepts.

Characteristics of a Reliable Promise
A performer should make a promise only when they:
- Understand the request and the conditions of satisfaction clearly.
- Are competent to do the work, or know how to get it done.
- Have assessed their capacity, meaning resources, time and crew.
- Know that the constraints are removed or will be (information, materials, prior work, equipment, permits, space).
- Are sincere and willing to be held accountable.
- Are prepared to re-promise or notify early if they discover they cannot keep the commitment.

CbM in Practice: The Last Planner System
In construction, CbM is put into practice mainly through the Last Planner System. The 'last planners' are the foremen and superintendents who directly control the work.
- Master Schedule / Milestones: sets the overall targets.
- Phase (Pull) Planning: trades work backward from a milestone and make handoff commitments to each other ('What do you need from me, and when?').
- Lookahead Planning (Make-Ready): typically covers 3 to 6 weeks. The team identifies and removes constraints so that tasks become 'ready' to be promised.
- Weekly Work Plan: last planners make reliable promises for the coming week, choosing only ready work (can, should and will).
- Daily Huddles / Coordination: short check-ins on commitment status.
- Measurement: Percent Plan Complete (PPC) = completed promises divided by total promises for the period. It measures plan reliability, not productivity.
- Learning: the team records Reasons for Variance on missed commitments, performs root cause analysis (for example, 5 Whys) and takes corrective action.

The underlying logic is: SHOULD (what the schedule says) is filtered by CAN (constraints removed) to produce WILL (what is reliably promised), followed by DID (what was actually completed and measured).

CbM as a Communication Tool and Strategy
- It replaces one-way directives with two-way conversations.
- It makes commitments visible, for example on pull-planning boards, commitment logs or digital LPS tools.
- It uses specific, observable language: who will do what, by when, to what standard.
- It treats a broken promise as a learning opportunity, not a reason for blame.
- It supports collaborative delivery models such as IPD, design-build and partnering, where trust and shared risk are central.

CbM vs. Traditional Command-and-Control
- Traditional: the plan is pushed from the top down. CbM: commitments are pulled and made by the people doing the work.
- Traditional: success means following the schedule. CbM: success means keeping promises and achieving reliable workflow.
- Traditional: problems are often hidden until late. CbM: early notice of at-risk promises is expected.
- Traditional: variance is met with blame. CbM: variance triggers root cause analysis and learning.
- Traditional: measures percent complete or earned value. CbM: also measures PPC and constraint removal.

Common Pitfalls
- Vague requests with no conditions of satisfaction or due date.
- Pressured 'yes' answers, which produce unreliable promises.
- Promising work that still has unresolved constraints.
- Failing to warn others when a commitment is at risk.
- Closing tasks without customer acceptance.
- Using PPC to punish people, which drives sandbagging and hidden problems.
- Managers making promises on behalf of the crews who will actually do the work.

Exam Tips: Answering Questions on Commitment-based Management (CbM)
1. Choose collaboration over command. When an answer choice involves the project manager directly assigning dates without consulting the performer, it is usually wrong. Prefer answers in which the people doing the work make the commitments.
2. An honest 'no' beats an unreliable 'yes'. If a scenario asks how a trade partner should respond to a request they cannot meet, the best answer is to decline, counter-offer or commit to commit. Agreeing and hoping is never the best answer.
3. Notify early and re-promise. When a commitment is at risk, the correct action is to inform the customer immediately and renegotiate. Waiting, hiding the problem or quietly working overtime without telling anyone is incorrect.
4. Clarify conditions of satisfaction first. If the scenario describes a dispute about whether work is 'done', the root cause is usually unclear conditions of satisfaction. Look for answers about defining or clarifying the CoS up front.
5. Know the loop. The phases are Request, Negotiate, Perform and Accept. The loop closes when the customer accepts, not when the performer says the work is finished.
6. Link CbM to the Last Planner System. Weekly work plans, pull planning, make-ready and constraint removal, daily huddles and PPC are all CbM in action. Expect PPC to appear as the metric of reliability.
7. Only promise ready work. If constraints such as materials, information, permits or predecessor work are not cleared, the work should not go on the weekly plan. The make-ready process comes before the promise.
8. Treat variance as learning, not blame. For missed commitments, the best answer typically involves recording reasons for variance and performing root cause analysis. Disciplining the foreman is not the preferred response.
9. Calculate PPC correctly. For example, if 18 of 24 promised tasks were fully completed, PPC = 18 / 24 = 75%. Partially completed tasks count as not complete.
10. Watch for keywords. Terms such as 'reliable promise', 'conversation for action', 'conditions of satisfaction', 'last planner', 'pull', 'network of commitments', 'trust' and 'accountability' signal a CbM question.
11. Eliminate distractors. Remove answers that rely on escalation first, contractual threats, or issuing more detailed top-down schedules as the primary fix for coordination failures. CbM favors direct conversation between customer and performer.
12. Think psychological safety. The best answers create an environment where people can speak candidly about capacity and risks without fear.

Sample Scenario
A drywall foreman says 'yes' to finishing Level 3 by Friday. On Wednesday, he realizes the inspection for the overhead MEP work has not happened. What should he do?
Best answer: immediately inform the requester (the superintendent or the next trade) that the promise is at risk, explain the constraint, and negotiate a new commitment or a way to help remove the constraint. In the next lookahead, the team should make sure inspections are identified and cleared as constraints before the work is promised.

Key Takeaway
Commitment-based Management turns project coordination into a disciplined system of clear requests, sincere and reliable promises, early warnings, explicit acceptance and continuous learning. On the PMI-CP exam, favor answers that build trust, respect the performer's right to negotiate, remove constraints before committing, communicate proactively and treat failures as opportunities to improve the system.