Categories of Legitimate Reservations (CLR)

Concept: Vocabulary that names a phenomenon.

Goldratt’s leveled protocol for scrutinizing the claims in a Thinking Process diagram: clarity first, entity and causality existence second, sufficiency-side reservations third.

Also known as: CLR; the categories; legitimate reservations; scrutiny rules.

A Thinking Process diagram without the CLR is still only a drawing. Its arrows may look authoritative, but they have not yet been tested as claims about the world. The Categories of Legitimate Reservations give TOC-trained practitioners a shared audit language: each reservation names one way an entity or arrow can be wrong, and the presenter must repair or defend the claim before the diagram earns trust.

Context

The CLR is the rigor mechanism behind Thinking Process work. The Current Reality Tree, Evaporating Cloud, Future Reality Tree, Prerequisite Tree, Transition Tree, and Strategy and Tactics Tree are all auditable artifacts. The CLR is the protocol they are audited against.

That does not mean every TP diagram takes the full CLR in the same way. The Necessary Cause and Sufficient Cause entries name the two logic types. The CLR was built mainly for sufficiency claims, so it fits the CRT, FRT, and Transition Tree most cleanly. Necessity-heavy diagrams still take Level I and Level II scrutiny, but their higher-level audit depends more on assumption-surfacing than on the full Level III set.

The TOCICO Dictionary, TOC Handbook Ch. 23 (Mabin and Davies), TOC Handbook Ch. 25 (Scheinkopf), Dettmer 1997, and Scheinkopf 1999 treat the CLR as a stable, named set of categories grouped into three levels. Goldratt did not invent a new formal logic system. He codified the critiques practitioners were already raising, so diagram scrutiny could be reproduced and defended in front of skeptics.

The count varies in the canon. The TOCICO Dictionary names seven reservations. Scheinkopf and Dettmer sometimes separate tautology as an eighth Level III category; other treatments group it with cause-effect reversal. For certification-grade use, the Dictionary’s seven-category count is the reference count. The tautology distinction still matters when the error is linguistic identity rather than arrow direction.

What It Is

The CLR is a finite set of reservations raised in level order. The order matters. A scrutinizer who jumps to cause insufficiency before clarity or entity existence is testing the wrong failure. Lower-level concerns must close before higher-level ones can be trusted.

Level I, Clarity. The scrutinizer does not yet understand an entity or arrow. The working language is “I do not understand entity 30” or “I do not see how 30 leads to 40; read the arrow aloud.” Clarity comes first because every later reservation assumes a shared reading. The issue may be a sentence fragment, a pronoun without an antecedent, a compound entity, an unknown acronym, or a presenter’s domain term. Sometimes the explanation is enough. Sometimes the entity is rewritten. Clarity says the audit cannot proceed yet; it does not say the diagram is wrong.

Level II, Entity existence and causality existence. Entity existence asks whether a stated entity exists in the world. “The engineering team is fully cross-trained” cannot pass as a current-reality entity unless the team is in fact cross-trained. Causality existence asks whether the arrow is real. The Dictionary’s example is blunt: “How does being certified in a field assure that you know everything about the subject?” A Level II repair may add an intermediate entity, remove an arrow, or reword the claim. It may not leave the concern open and move to Level III.

Level III, the sufficiency-side reservations. These four reservations test whether an if-then claim can carry the weight assigned to it.

Cause insufficiency says the named cause is not enough by itself. If a competitor’s price reduction is offered as the cause of falling sales, the scrutinizer may argue that the effect requires both the competitor’s price reduction and our failure to match it. The repair is the magnitudinal “and” connector.

Additional cause says another independent cause also produces the effect. If “my car gets very poor gas mileage” explains “I prefer to take the bus to work,” the scrutinizer may add “I like to read on my way to work” as a second cause. Either cause can produce the effect; the repair is usually a logical-or branch.

Cause-effect reversal says the arrow points the wrong way. In the Dictionary’s House-on-Fire example, “if a fire truck is parked at my house then my house is on fire” reverses the actual causality: “if my house is on fire then a fire truck is parked at my house.” The fire truck is evidence of the condition, not its cause. Some authors separate tautology when cause and effect say the same thing, as in “the engineering team is overworked because they have too much work.” The Dictionary treats both as cause-effect reversal.

Predicted-effect reservation asks what else should be observable if the proposed cause is real. The car will not start; the proposed cause is a low battery; the predicted effect is dim headlights. Bright headlights weaken the low-battery hypothesis. This is the CLR’s strongest bridge back to evidence outside the diagram.

The protocol is collaborative. The tree builder may accept or reject a raised reservation at any level, but the rejection must be explicit. Goldratt’s standard was reciprocal: a scrutinizer who raises a reservation owes the presenter a candidate repair, such as the missing cause, the arrow to add, or the predicted effect to check.

How It Is Measured or Recognized

A TP diagram has been audited against the CLR when four observable properties hold.

The scrutiny was conducted in level order. A session that raises cause insufficiency before clarity has not yet earned CLR credibility. Skipped levels often reveal that a supposed Level III issue was only a Level I clarity problem.

Every reservation carried a candidate repair. A cause-insufficiency concern names the missing cause. A predicted-effect concern names the effect to check. Reservations without repair proposals are generic critique, not CLR scrutiny.

The presenter accepted or rejected each reservation explicitly. The TOCICO Dictionary’s usage line is direct: “the tree builder is free to accept or reject any reservation at any level.” Acceptance changes the diagram. Rejection defends the entity or arrow as written. Silent rejection breaks the protocol.

The closed reservations were proportional to the diagram. A CRT with twenty entities and thirty arrows that closes with three reservations has probably not been seriously audited; one with fifty entities and thirty reservations has. Scheinkopf’s walkthroughs suggest a Level III reservation roughly every two to three sufficiency arrows on a fresh tree, falling to one every five to seven after the second pass.

Why It Matters

The CLR makes a TP diagram defensible in front of a TOCICO-certified peer reviewer. A reviewer can say “cause insufficiency on the arrow between 30 and 40,” and the presenter knows the claim, the expected repair, and the closure condition. That shared language is what lets one practitioner scrutinize another practitioner’s tree without turning the review into taste or seniority.

It also makes failure types transferable. “This arrow does not read right” is private discomfort. “Causality existence fails here” is a claim another practitioner can test. The same vocabulary works months later when a borrowed diagram is reopened by someone who did not attend the original session.

The categories also point to local repair operations. Clarity rewrites an entity; entity existence removes or qualifies a box; causality existence adds an intermediate entity or strikes an arrow; cause insufficiency adds a magnitudinal-and connector; additional cause adds a parallel branch; cause-effect reversal flips the arrow; predicted effect confirms or weakens the hypothesis. The whole diagram does not have to be redrawn.

Finally, the CLR gives practitioners grounds to refuse unaudited diagrams. A consultant who will not put a CRT through scrutiny is offering a presentation, not a diagnosis. A team implementing against an unaudited FRT is betting on causal claims that have not been challenged. The CLR turns that refusal from personal skepticism into professional procedure.

Common Misunderstanding

The most common misunderstanding is treating the CLR as a checklist. Practitioners new to the categories may scan a diagram and raise whichever reservation catches the eye. The audit then converges slowly, and the same issue can appear as Level I clarity in one pass and Level III cause insufficiency in another. The corrective is strict level order: no Level II concern until Level I is closed, no Level III concern until Level II is closed.

The second misunderstanding is auditing a necessity diagram with the full CLR. The Level III reservations are built around sufficiency claims. An Evaporating Cloud or Prerequisite Tree, whose arrows are necessity arrows, will not respond to cause insufficiency or additional cause the way a CRT will. The lower-level categories still work. The higher-level ones drift unless the practitioner first recognizes the diagram’s logic type. The Necessary Cause entry handles the necessity side of this distinction.

The third misunderstanding is treating the CLR as peer review or quality control in general. It is a logic audit. It does not decide whether the diagram chose the right UDEs, whether the core problem matters strategically, or whether an injection is politically feasible. Its question is narrower: are the cause-and-effect claims on the page logically defensible?

The fourth misunderstanding concerns the seven-versus-eight count. Practitioners trained from Dettmer 1997 or older material sometimes treat tautology as distinct from cause-effect reversal. The TOCICO Dictionary’s canonical count is seven, with tautology grouped under cause-effect reversal. The distinction matters when the issue is linguistic identity rather than arrow direction, but either count produces the same audit moves. The count is a labeling question, not a logic question.

Audits: Current Reality Tree (CRT) — Every entity and every arrow on a CRT is read against the CLR before the diagnosis is trusted; the Level III sufficiency-side reservations apply to the CRT's arrows because the CRT's arrows are sufficiency arrows, and Level I and Level II apply to every entity on every TP diagram regardless of logic type.

Audits: Evaporating Cloud (Conflict Resolution Diagram) — The CLR applies to the cloud's entities (Level I, Level II) but engages only partially with its necessity arrows; the cloud's resolution machinery rests on the assumption layer the CLR was not designed to audit, which is one of the reasons the EC's rigor stance differs from the CRT's.

Audits: Future Reality Tree (FRT) — The FRT is the second tool the practitioner audits with the full CLR; the negative-branch trim and the predicted-effect reservation are the two CLR moves most often applied to an FRT before the injection is committed to.

Audits: Prerequisite Tree (PRT) — The PRT's intermediate objectives clear Level I and Level II checks (does this IO exist, is it really necessary), but Level III's sufficiency reservations have a smaller fit because the PRT's arrows are necessity arrows rather than sufficiency arrows.

Audits: Strategy and Tactics Tree (S&T Tree) — The S&T Tree's necessary-assumption and sufficiency-assumption layers are explicitly designed so the CLR can audit the sufficiency layer directly; Goldratt's later S&T formalism is the most CLR-aware of the TP tools.

Audits: Transition Tree (TT) — The Transition Tree's action-condition-effect chains are sufficiency claims; the CLR applies in full, with cause insufficiency the most common reservation raised on TTs because the action-plus-condition combinations are often under-specified.

Complements: Necessary Cause (Necessity Logic) — Necessity claims and sufficiency claims have different audit profiles; the CLR was built primarily for sufficiency, so necessity-heavy diagrams carry a smaller share of the formal categories and a larger share of assumption-surfacing moves the CLR does not formalize.

Complements: Sufficient Cause (Sufficiency Logic) — Every CLR category names a specific way a sufficiency claim can be wrong; without the sufficiency-logic entry the CLR reads as a checklist disconnected from the operator it audits.

Depends on: Inherent Simplicity — The CLR's working assumption that a small set of categories suffices to audit any TP diagram rests on the same inherent-simplicity premise that justifies single-constraint focus: a complex diagram is held in place by a few key causal claims, and a finite set of reservation types catches the ways those claims fail.

Sources

• Cox, TOCICO Dictionary of Theory of Constraints Terms (2nd ed., 2012), entries “categories of legitimate reservation,” “clarity reservation,” “entity existence reservation,” “causality existence reservation,” “cause insufficiency reservation,” “additional cause reservation,” “cause-effect reversal reservation,” “predicted effect reservation,” “sufficiency-based logic,” “necessity-based logic,” “scrutiny.” The certification-grade definitions every claim in the entry cross-checks against; the Dictionary records the seven-category count, the three-level grouping, and the worked illustrations (the House-on-Fire reversal, the dog-food example, the dim-headlights predicted-effect example) the entry’s prose draws on. Distributed through TOCICO membership; no Open Library record.

• Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 23 (Mabin and Davies, “The TOC Thinking Processes: Their Nature and Use”). The contemporary canonical treatment of the TP building blocks, in which the chapter names “the categories of legitimate reservation” as one of the three foundational logic-construction elements (alongside sufficiency-based and necessity-based logic) and surveys the field’s literature on which TP tools use which reservation set most heavily. The chapter also catalogs the methodological developments since 2000 (the Negative Branch Reservation process, the integration of system dynamics, the Communications CRT variant), each of which interacts with the CLR in named ways.

• Cox and Schleier, Theory of Constraints Handbook (2010), Ch. 25 (Scheinkopf, “Thinking Processes Including S&T Trees”). The chapter-length walkthrough of TP construction that treats the CLR as the working scrutiny protocol throughout, with worked examples of each reservation in the context of the diagram it is raised against. Scheinkopf’s pacing convention (a Level III reservation roughly every two to three sufficiency arrows on a first pass) is the operational scrutiny tempo the “How It Is Measured or Recognized” section draws on.

• Dettmer, Goldratt’s Theory of Constraints: A Systems Approach to Continuous Improvement (1997). The canonical practitioner exposition outside the Handbook; the Levels I/II/III sequencing and the verbalization conventions for each reservation come from this treatment, and Dettmer is one of the principal sources for the eight-category variant that separates tautology from cause-effect reversal. The Evaporating Cloud and Prerequisite Tree chapters carry the necessity-side audit conventions the entry contrasts with the sufficiency-heavy CLR.

• Scheinkopf, Thinking for a Change: Putting the TOC Thinking Processes to Use (1999). The TP-curriculum treatment that names the CLR as one of three foundational building blocks (“the TP embrace and are constructed from three basic logic building blocks … sufficiency-based if-then logic … necessity-based in order to … we must have … logic … and the Categories of Legitimate Reservation”). The chapter on scrutiny supplies the collaborative-posture framing the entry’s “Why It Matters” section is built on.

• Goldratt, It’s Not Luck (1994). The narrative source for scrutiny as an institutional practice rather than as private review; the Alex Rogo arc that runs through the novel dramatizes the CLR being raised, accepted, and rejected across multiple TP diagrams, without ever using the formal vocabulary, in roughly the collaborative posture the Dictionary and Scheinkopf both name explicitly. The novel is one of the canonical onboarding artifacts for the TP toolset and the most accessible source for the CLR’s working tone.