--- slug: full-kitting type: pattern summary: "The release-readiness discipline that keeps project tasks, manufacturing orders, and service work from starting until the inputs needed to finish are available." created: 2026-06-02 updated: 2026-06-02 related: critical-chain: relation: complements note: "Full Kitting protects the critical chain by keeping tasks from entering execution before the requirements, approvals, materials, and resources needed to finish are ready." project-buffer: relation: complements note: "The project buffer absorbs execution variation after work starts; Full Kitting prevents avoidable false starts from consuming that buffer before execution is real." feeding-buffer: relation: complements note: "Feeding buffers protect critical-chain merge points from late feeder work; Full Kitting keeps feeder tasks from beginning with missing inputs that make the buffer signal misleading." resource-buffer: relation: complements note: "Resource buffers warn people to prepare for critical-chain work; Full Kitting checks that the work itself is ready for the resource when the warning matures." agile-ccpm: relation: used-by note: "Agile CCPM keeps Full Kitting as a project-release rule while changing the estimation and buffer-reading mechanics for software work." bad-multitasking: relation: prevents note: "Full Kitting prevents a common cause of bad multitasking: resources starting work, discovering missing inputs, switching away, and returning later with lost focus." multitasking-cascade: relation: mitigates note: "Full Kitting mitigates portfolio-wide multitasking cascades by making release readiness part of the project-start rule instead of a local scramble after release." drum-buffer-rope: relation: complements note: "DBR uses Full Kitting before manufacturing-order release so the shop floor doesn't start work that will stall before reaching or protecting the constraint." s-dbr: relation: complements note: "S-DBR relies on Full Kitting before order release because missing materials, specs, or tooling turn a simple release rule into noise." buffer-management: relation: supports note: "Buffer Management reads variation during execution; Full Kitting removes missing-input noise that would otherwise look like execution variation." --- # Full Kitting [CCPM (CCPM Practitioner)](learning-tracks.md#ccpm): [prev: Resource Buffer](resource-buffer.md) -> Full Kitting -> [next: Fever Chart](fever-chart.md) > **Pattern:** A named solution to a recurring problem. *Hold a project, task, order, or service visit out of execution until the inputs needed to finish it are available, so scarce attention is not wasted on false starts.* *Also known as: Full Kit; Whole Kit; Kitting.* Full Kitting is the discipline behind the sentence "don't start what you can't finish." In TOC use, that sentence is a release rule for protecting flow. A task without the requirements, signoffs, materials, or decision rights needed to finish will start, stall, demand expediting, pull scarce resources away from other work, and consume buffer protection reserved for real execution variation. ## Context Full Kitting appears in two TOC domains that look different on the surface: [Critical Chain Project Management](critical-chain.md) and [Drum-Buffer-Rope](drum-buffer-rope.md) / [S-DBR](s-dbr.md). The *TOCICO Dictionary* defines the term in both settings. In DBR and S-DBR, Full Kitting means staging or checking the availability of the materials, tooling, specifications, and other inputs for a manufacturing order before release to the shop floor. In CCPM, it means clarifying requirements, getting approvals, staging materials, and doing the preparatory work needed before the project or task enters execution. The common logic is release control. TOC systems usually fail less from lack of local effort than from too much work released into a system before the constraint can benefit from it. Once work is released, managers want visible progress. People start tasks to show motion, discover missing inputs, switch to something else, then come back later with setup time lost and priority unclear. Full Kitting blocks that pattern at the release gate. The rule is especially important in multi-project environments. When an organization freezes lower-priority projects to reduce work in process, durable-results CCPM implementations use the freed capacity to full-kit the projects on hold: clarify requirements, secure approvals, stage materials, and make the next releases cleaner. ## Problem A task can look ready because a schedule says its start date has arrived. That is the wrong test. The real question is whether the task can flow to completion once a resource starts it. When readiness is weak, starting early creates a local appearance of progress and a system-level delay. The resource opens the work, finds that a drawing is missing, a customer decision has not been made, a material is late, a room is not prepared, or an approval path is unclear. The resource waits, works around the gap, or switches to another task. Waiting burns buffer. Workarounds create rework. Switching creates [Bad Multitasking](bad-multitasking.md). ## Forces - **Start dates create pressure to start.** A visible schedule can make starting on time look more important than finishing without interruption. - **Preparation work is easy to misclassify.** Clarifying requirements and staging inputs help execution; doing part of the task early is execution disguised as readiness. - **Constraints should not wait on missing inputs.** If the constrained resource reaches a task and the task is not ready, the system has wasted the resource's scarcest attention. - **Too much release creates bad multitasking.** Work released before readiness joins the queue, competes for attention, and then stops when the missing input appears. - **Some work is genuinely uncertain.** Research and discovery tasks may not be full-kit in the same way as engineering-to-order, manufacturing, or service work. ## Solution **Use Full Kitting as a release gate: the work does not enter execution until the inputs needed to complete it are present or explicitly reserved.** Define the full kit for each work type before the release decision. A project task's kit may include accepted requirements, design decisions, approvals, materials, test access, named resources, customer availability, and a clear handoff rule. A manufacturing order's kit may include raw material, tooling, routing, inspection criteria, specs, and a protected release time. A service visit's kit may include records, preauthorizations, lab results, and room setup. Separate readiness from execution. Readiness work removes obstacles to an uninterrupted task: clarifying requirements, getting signoffs, staging material, checking setup, confirming decision rights, or preparing the customer. It does not advance the task's deliverable. Realization Technologies' durable-results chapter states the distinction sharply: activities that let project tasks be done without interruptions belong in the full kit list; activities that directly progress the tasks are excluded. If the "preparation" changes the deliverable itself, it is not preparation anymore. Assign ownership for the gate. The *TOCICO Dictionary* names the Full Kit Manager as the person responsible for making sure projects have what they need before release. Kendall's strategy chapter goes further in large CCPM implementations: define generic full-kit templates by project type, customize them for each project, and give an executive-level Full Kit Manager authority to stop follow-on work until the kit is reached. The title matters less than the authority. Someone must be able to say "not yet." Use the gate with buffer discipline. Full Kitting is not a substitute for the [Project Buffer](project-buffer.md), [Feeding Buffer](feeding-buffer.md), [Resource Buffer](resource-buffer.md), or [Buffer Management](buffer-management.md). It protects those mechanisms from avoidable noise. Buffers should absorb normal execution variation, not missing drawings, material, approvals, or customer decisions. > **⚠️ Do not turn Full Kitting into early execution:** Full Kitting prepares the work so execution can run without interruption. It does not authorize hidden progress on a task before release. If preparation starts consuming constraint time or producing the task's deliverable, the organization has moved execution ahead of the gate and renamed it readiness. ## How It Plays Out **A multi-project CCPM transition.** A product-development organization has too many projects active. The first CCPM move freezes part of the portfolio so current projects can finish faster and scarce resources can stop switching. The freed resources are not sent to start another visible deliverable. They full-kit the frozen projects: close open requirement questions, secure approvals, stage test assets, confirm resource assignments, and prepare the release package. As active projects finish, frozen projects are released one by one with fewer missing inputs and less rework. **A manufacturing order under S-DBR.** A make-to-order shop releases orders by due-date priority against the shipping buffer. That rule works only if the order can actually move once released. Before the order enters the shop floor, the scheduler checks materials, specs, tooling, and routing. If a low-value component is missing, the order waits outside execution rather than entering the floor and stalling halfway to the constraint. The wait is visible at the release gate, not disguised as work in process. **A healthcare practice.** Wadhwa's healthcare S&T material uses Full Kit language for patient flow. The doctor should not be brought to the patient before lab work, room setup, preauthorization, patient history, X-rays, and referring-doctor information are ready. Otherwise the doctor, often the capacity-constrained resource, spends billable time waiting or sends the patient away for another visit. **A software release using Agile CCPM.** Ujigawa and Updegrove keep Full Kitting in their software-specific CCPM variant. The method can adapt to discovered scope, but release still depends on a clear kit: prioritized feature list, release objective, developer access, integration path, test environment, and decision policy for the scope buffer. A feature that enters execution without those inputs doesn't become agile. It becomes a queue of interruptions. ## Consequences **Benefits.** Full Kitting reduces false starts. Scarce resources spend less time opening work they can't finish, waiting on missing inputs, and rebuilding context later. It also makes buffer signals cleaner: when a buffer is consumed, the cause is more likely to be execution variation rather than preventable release failure. It reduces rework. Kendall's strategy chapter names early detailed work before design or definition is complete as a major source of project rework. A full-kit gate forces the organization to finish the definition work before follow-on work starts. It also makes release priority more honest. Work outside the gate may be high priority, but it is not ready. That distinction helps project managers resist the portfolio pressure that creates a [Multi-Tasking Cascade](multitasking-cascade.md). **Liabilities.** Full Kitting can become a bureaucratic checklist if the kit is defined without reference to flow. A good kit names only the inputs needed to finish without interruption. A bad kit asks each department to add preferred documentation whether or not the missing document would ever stop the work. It can also delay learning when the work is genuinely exploratory. Budd and Cerveny's Critical Chain primer allows that research projects may violate the full-kit rule because the point of the work is to discover what the kit would have been. The exception has to stay narrow. Many organizations call work "research" when they mean "we haven't clarified the requirements yet." Finally, the gate needs authority. If the Full Kit Manager can identify a missing input but cannot stop release, the pattern decays into reporting. The schedule still starts the work, the resource still discovers the gap, and the system still pays for the interruption. ## Sources - Cox, *TOCICO Dictionary* (2nd ed., 2012), entries "full kitting," "full kit manager," "freeze (defrost) mechanism," "critical chain project management (CCPM)," "drum-buffer-rope," and "simplified drum-buffer-rope." The Dictionary supplies the certification-grade boundary across manufacturing release and project release. - Cox and Schleier, [*Theory of Constraints Handbook*](https://openlibrary.org/works/OL18346923W) (2010), Ch. 3 (Budd and Cerveny, "A Critical Chain Project Management Primer"), Ch. 4 (Realization Technologies, "Achieving Durable Results with Critical Chain Project Management"), Ch. 9 (Schragenheim, "Simplified Drum-Buffer-Rope for Make-to-Order"), Ch. 18 (Kendall, "TOC Strategy"), and Ch. 31 (Wadhwa, "Using TOC to Create a Viable Vision for Health Care"). These chapters place Full Kitting in project starts, manufacturing-order release, strategy-and-tactics execution, and service-flow preparation. - Goldratt, [*Critical Chain*](https://openlibrary.org/works/OL8384933W) (1997), the originating business-novel treatment of CCPM's project-release discipline, bad multitasking problem, and buffer-protected execution. - Newbold, [*Project Management in the Fast Lane*](https://openlibrary.org/works/OL2747345W) (1998), the implementation-grade CCPM companion that treats release pacing, preparation, and multi-project flow as part of the same project-throughput problem. - Ujigawa and Updegrove, "*Agile* CCPM: Critical Chain for Software Development" (TOCICO White Paper Series, 2016). The paper preserves Full Kitting inside the software-specific CCPM variant, pairing it with project staggering, velocity-based buffer management, and scope-buffer policy. - Ferguson, "Standing on the Shoulders of Giants" (TOCICO BOK paper, 2018). The paper describes full-kit freezing as one mechanism for preventing unnecessary bad multitasking when projects, tasks, or project legs are released too early. --- - [Next: Fever Chart](fever-chart.md) - [Previous: Resource Buffer](resource-buffer.md)