--- slug: tdd-idd-measures type: concept summary: "Operational dollar-day measures that turn late commitments and unnecessary early inventory into comparable time-weighted signals." created: 2026-06-02 updated: 2026-06-02 related: throughput-accounting: relation: depends-on note: "TDD and IDD use the throughput-world measurement frame: value, time, and constraint protection matter more than allocated unit cost." throughput: relation: depends-on note: "TDD values a late commitment by the throughput the system expected to protect, not by production volume." inventory: relation: depends-on note: "IDD treats inventory as money tied in work the system has released or stocked before customer need justified it." continuous-improvement-auditing: relation: supports note: "Dollar-day trends give the audit a time-weighted signal for reliability failures and unnecessary released work." replenishment-pull: relation: measures note: "The TOC replenishment solution uses TDD and IDD to judge whether each chain link is reliable and effective." buffer-management: relation: complements note: "Buffer status tells operators what to expedite; TDD and IDD show whether the chain is repeatedly late or carrying work too early." supply-chain-collaboration: relation: supports note: "Cross-company TOC collaboration needs common reliability and inventory signals that do not depend on transfer prices." complex-organizations: relation: extended-by note: "Holt and Boyd extend TDD and IDD from supply-chain flow into cross-unit commitments and conceptual work in complex organizations." cost-world-thinking: relation: prevents note: "Dollar-day measures prevent late work and excess released work from disappearing inside favorable local cost reports." efficiency-trap: relation: detects note: "IDD exposes work started to keep resources busy when the system did not yet need the output." --- # Throughput Dollar-Days and Inventory Dollar-Days [Supply Chain & Operations (SCL Practitioner)](learning-tracks.md#scl-pom): [prev: Cash Constraint and Cash Buffer](cash-constraint-buffer.md) -> Throughput Dollar-Days and Inventory Dollar-Days -> [next: Procter & Gamble Distribution](pg-distribution.md) [Finance & Measures (FM Practitioner)](learning-tracks.md#finance-measures): [prev: Product Mix Decision Under Constraints](product-mix-decision.md) -> Throughput Dollar-Days and Inventory Dollar-Days -> [next: Throughput-Accounting Decision Cases](ta-decision-cases.md) > **Concept:** Vocabulary that names a phenomenon. *Operational dollar-day measures that turn late commitments and unnecessary early inventory into time-weighted signals: TDD measures what should have been delivered but wasn't, while IDD measures what was released or stocked before it was needed.* Throughput Dollar-Days (TDD) and Inventory Dollar-Days (IDD) are paired measures. They don't replace [Throughput Accounting](throughput-accounting.md), and they don't behave like ordinary financial measures. They take a throughput-world value and multiply it by days, so lateness and unnecessary early work become visible in one unit: dollar-days. That unit is deliberately uncomfortable. A late order with high throughput value should bother the system more than a low-value order that slips by the same number of days. A pile of inventory that sat for six weeks before anybody needed it should bother the system more than the same pile held for one day. Dollar-days put value and time in the same operating signal without returning to allocated cost. ## Context Dollar-day measures belong in Performance Measures because they sit between financial measures and daily operating control. [Throughput Accounting](throughput-accounting.md) gives the T-I-OE frame. [Buffer Management](buffer-management.md) gives the color-zone signal for what to expedite now. TDD and IDD answer a different question: over the reporting period, how much value was late, and how much work or stock aged before it was needed? The measures first appear in the supply-chain and distribution setting. The TOC replenishment solution uses actual consumption, stock buffers, and frequent replenishment to protect availability with less total inventory. In that setting, TDD judges reliability: did each link deliver what it promised? IDD judges effectiveness: did each link avoid doing work the chain did not yet need? The pair later generalizes. Ricketts uses the same control-measure idea in professional, scientific, and technical services. Wadhwa applies it to healthcare networks, where a delayed specialist, laboratory, or imaging center can hold back patient throughput. Holt and Boyd adapt TDD, T/D, and IDD to complex organizations, where many separately measured units make internal promises that protect a shared system result. ## What It Is **Throughput Dollar-Days (TDD)** measures late committed throughput. For each missed commitment, multiply the throughput value protected by the commitment by the number of days the commitment is late. Sum those values over the reporting period. The target is zero, because a reliable link delivers what it said it would deliver, when it said it would deliver it. The commitment can be external or internal. A supplier missed a delivery. A plant missed a replenishment promise to a regional warehouse. An engineering group missed a handoff to a project team. The measure is not asking whether the final customer has already been harmed. It is asking whether a promise that protects system throughput was missed. **Inventory Dollar-Days (IDD)** measures inventory or released work that is waiting before customer need justifies it. For physical stock, multiply the value of inventory in a link's responsibility by the number of days since that inventory entered the link. For conceptual work, Holt and Boyd's extension uses a value assigned to the released project, audit, hiring case, or improvement task, then tracks how long it remains in process before it creates value. The target is not blindly zero. The Dictionary's rule is more precise: the system should carry the minimum IDD needed to maintain zero TDD. Some inventory is protective. Some released work is legitimate. IDD becomes a warning when the system is doing work early, building stock customers don't want yet, or launching conceptual work faster than the receiving capacity can complete it. The pair is easier to remember as two questions: | Measure | Question | Bad signal | |---|---|---| | TDD | What should have been done, but wasn't done on time? | Late throughput commitments accumulate. | | IDD | What was done or released before it was needed? | Inventory or work-in-process ages in the system. | ## How It Is Measured or Recognized TDD is calculated from missed promises. If a link promised ten units with $45 of throughput each and delivered two days late, that miss creates 900 TDD. If another order protected $350 of throughput and arrived eight days late, that miss creates 2,800 TDD. The reporting-period total is 3,700 TDD. IDD is calculated from aged stock or aged released work. If 50 units with $33 of value have been in stock for two days, another 50 for 22 days, and 44 for 42 days, the current IDD is 100,584 dollar-days. The same logic can be adapted to non-physical work when the unit can define a useful value proxy. A hiring process, audit, engineering improvement, or treatment plan can accumulate IDD while it sits released but unfinished. The numbers are comparable only to other dollar-day levels. They are not dollars of loss. They are not elapsed days. A TDD trend can be compared with last month's TDD or another link's TDD when the measure was designed on the same basis. An IDD trend can be compared with prior IDD for the same stock buffer, department, project class, or replenishment link. Don't compare dollar-days to revenue, net profit, or inventory value as if the units matched. Four recognition tests tell whether the measure is being used in the TOC sense. First, the measure is tied to commitments or released work, not to general busyness. TDD starts when a commitment is missed. IDD starts when inventory or work enters the link's responsibility before it is needed. Second, the value basis is throughput-world. TDD uses the throughput value protected by the promise. IDD uses the value of the inventory or a defensible proxy for the released work. Allocated labor and absorbed overhead don't belong in the calculation. Third, the measure is read as a focusing signal. Repeated TDD points to unreliable handoffs, capacity promises that don't match demand, or policies that block flow. Repeated IDD points to over-release, forecast push, efficiency-driven early production, or work-in-process that should not have been opened yet. Fourth, the measure is paired with operating context. A red buffer may tell operators what to expedite today. TDD and IDD trends tell managers where the system repeatedly fails or over-releases over time. One without the other is thin: the immediate signal needs the trend, and the trend needs the operating explanation. ## Why It Matters TDD and IDD give practitioners a measurement language for two losses that ordinary reports often blur. The first loss is unreliability. A system can report acceptable average lead time while repeatedly missing the commitments that matter most. A due-date percentage treats a low-value miss and a high-throughput miss as the same category. TDD doesn't. It weights the miss by the throughput value and the time exposed. That makes it harder for the organization to hide important misses inside a favorable average. The second loss is unnecessary early work. A cost-world report may reward a plant for keeping people busy, filling bins, or absorbing overhead into finished inventory. IDD reads the same behavior in throughput-world terms: the system did work before the market or downstream link needed it, and the value now ages in inventory or work-in-process. The [Efficiency Trap](efficiency-trap.md) becomes measurable. The pair is especially useful in supply-chain collaboration. Transfer pricing makes cross-company optimization difficult because each link can make its own local report look reasonable. TDD and IDD move the conversation to reliability and effectiveness. Did the link deliver what it promised? Did it avoid creating excess inventory that the next link didn't need? Those questions are harder to game than local price recovery. The measures also protect complex organizations from milestone theater. A milestone is too sparse and too late. By the time it is missed, the organization has already consumed protection somewhere. Holt and Boyd's complex-organization treatment uses TDD at internal handoffs because a unit can begin accumulating TDD before the final customer promise fails. Senior management sees where help, policy repair, or capacity work is needed while the project buffer or shipping buffer still has time left. ## Common Misunderstanding **"TDD is a penalty."** It can be misused that way, which is why the Dictionary warns against local TDD minimization. A department that tries to protect its own TDD at the expense of [Buffer Management](buffer-management.md) may make the system worse. TDD is a signal for attention and learning, not a score for blaming whoever touched the late work last. **"Early completion reduces TDD."** It doesn't. A late commitment creates TDD. An early commitment creates zero TDD, and any recovered project buffer or shipping buffer is handled by the relevant buffer-management discipline. Rewarding early local completion invites inflated commitments and recreates the behavior [Critical Chain](critical-chain.md) was designed to remove. **"IDD means inventory is always bad."** It doesn't. TOC replenishment deliberately holds stock buffers where they protect availability. The issue is not inventory as such. The issue is inventory or released work that ages because the system produced, bought, transferred, or opened it before need justified the release. The target is the minimum IDD needed to keep TDD reliably near zero. **"Dollar-days are financial losses."** They aren't. A dollar-day number combines value and elapsed time to create an operating measure. It should be compared with other dollar-day readings designed on the same basis, not with revenue, net profit, or cash. Treating dollar-days as dollars turns a useful flow signal into bad accounting. **"TDD applies everywhere."** It applies best where a unit has a real delivery commitment to another unit or to a customer. Some support groups don't have clean handoff promises. Holt and Boyd's answer is not to force TDD everywhere, but to use T/D for goal-unit throughput and IDD for aged conceptual work when those measures fit the unit better. ## Sources - Cox, *TOCICO Dictionary* (2nd ed., 2012), entries "throughput-dollar-days," "inventory-dollar-days," "holistic operations measures," "distribution/replenishment solution," "effectiveness," and "reliability" — the certification-grade definitions, calculations, cautions, and companion terms this entry cross-checks against. The Dictionary is distributed through TOCICO membership and does not carry an Open Library record. - Cox and Schleier, [*Theory of Constraints Handbook*](https://openlibrary.org/works/OL18346923W) (2010), Ch. 7 (Blackstone, "Theory of Constraints: A Status Report") — the literature-review source that places TDD and IDD in TOC supply-chain management and connects the pair to make-or-buy decisions, DBR across a chain, and reliable global measures. - Cox and Schleier, [*Theory of Constraints Handbook*](https://openlibrary.org/works/OL18346923W) (2010), Ch. 29 (Ricketts, "Theory of Constraints in Professional, Scientific, and Technical Services") — the service-organization adaptation, including the relationship between Throughput Accounting for goods, Throughput Accounting for services, and control measures derived from TDD and IDD. - Cox and Schleier, [*Theory of Constraints Handbook*](https://openlibrary.org/works/OL18346923W) (2010), Ch. 31 (Wadhwa, "Using TOC to Create a Viable Vision for Health Care Organizations") — the healthcare application that reads TDD as lateness by specialists, laboratories, and imaging centers, and IDD as queued treatment plans with incomplete or incorrect information. - Holt and Boyd, "Theory of Constraints in Complex Organizations," in Cox and Schleier, [*Theory of Constraints Handbook*](https://openlibrary.org/works/OL18346923W) (2010), Ch. 33 — the organization-scale extension of TDD, T/D, and IDD across internal handoffs, project flows, support units, and conceptual work-in-process. - Goldratt, [*The Haystack Syndrome*](https://openlibrary.org/works/OL4455381W) (1990) — one of the originating sources Holt and Boyd cite for TDD and IDD as dollar-day measures in physical-goods and supply-chain settings. --- - [Next: Throughput-Accounting Decision Cases](ta-decision-cases.md) - [Previous: Continuous Improvement Auditing](continuous-improvement-auditing.md)