---
slug: justice-time
type: pattern
summary: "Apply TOC to court congestion by treating judicial attention as the constraint, protecting trial-phase flow, and subordinating scheduling policy to case-level completion."
created: 2026-05-21
updated: 2026-06-02
related:
  services-management:
    relation: specializes
    note: "Justice in Time is a court-system specialization of Services Management: the work-in-process is cases, the scarce service resource is judicial attention, and the goal measure is timely case resolution at the required quality level."
  unique-features-government:
    relation: specializes
    note: "Courts are public agencies whose demand cannot be refused and whose goal unit cannot be reduced to sales; Justice in Time applies the government translation to judicial throughput."
  five-focusing-steps:
    relation: applies
    note: "The intervention explicitly walks the court process through identify, exploit, subordinate, elevate, and repeat."
  subordination:
    relation: uses
    note: "The case-level FIFO scheduling rule subordinates courtroom calendars, attorneys, parties, and clerical work to the judge's constrained trial-phase capacity."
  policy-constraint:
    relation: surfaces
    note: "The old hearing-level scheduling rule and written-closing-argument practice are policy constraints that consume constrained judicial time and extend case lead time."
  bad-multitasking:
    relation: detects
    note: "The court problem is a service-domain instance of bad multitasking: judges carry too many active trial-phase cases and repeatedly reacquaint themselves with old files."
  toc-prisons:
    relation: adjacent
    note: "Both entries apply TOC to justice-system institutions where public value, legal process, and flow constraints have to be kept distinct."
---

# Justice in Time

> **Pattern:** A named solution to a recurring problem.

*Apply TOC to court congestion by treating judicial attention as the constraint, protecting trial-phase flow, and subordinating scheduling policy to case-level completion instead of hearing-level busyness.*

*Also known as: TOC for courts; focused management in a court system.*

"Justice in time" names a narrow but important public-sector TOC move. A court system can have competent judges, legitimate procedure, and sincere urgency while still keeping cases alive for years. The visible complaint is delay. The TOC diagnosis asks a sharper question: which scarce resource or rule is causing cases to wait, and what has to change so completed cases flow through the system faster without damaging due process?

## Context

The pattern sits inside [Services Management](services-management.md) and [Unique Features of Government](unique-features-government.md). Courts are service systems, but they aren't ordinary services. They can't usually refuse demand, their work is constrained by legal procedure, and their output is not revenue. The goal unit has to be stated as timely case resolution at an acceptable quality of justice, not as money generated through sales.

Azaria, Ronen, and Shamir's 2023 TOCICO-recognized paper describes an intervention at the Jerusalem District Court in Israel. The intervention focused on first-instance civil cases in the district court, where the trial phase carried high work-in-process and long waits between hearings. The court used a one-case-one-judge assignment rule, so the judge assigned to a case remained responsible for it through the case's life cycle.

The intervention won the 2012 Goldratt Foundation New Knowledge Award and later appeared in the *Journal of Operations Management*. For certification-track readers, its value is not that every court should copy the Jerusalem design. Its value is that it shows the [Five Focusing Steps](five-focusing-steps.md) working in a legal-service environment where adding judges is politically difficult, procedurally constrained, and not necessarily effective.

## Problem

Court congestion often gets framed as a resource shortage: too many cases, too few judges, not enough budget. That diagnosis may be true, but it is too broad to guide action. Beenstock and Haitovsky's Israeli-court study found that appointing more judges did not automatically raise case output, and later work on court structure suggested that delay can come from process design rather than raw resource count.

The Jerusalem District Court's civil-case flow showed the classic service-WIP problem. Each judge had roughly sixty open cases in the trial phase. The common practice scheduled the next hearing only after the previous hearing ended, using the first available slot in the calendar. Because each judge was handling many active cases, the next available slot was often three to six months away.

The result wasn't one long trial. It was many partly active trials waiting on the same judge. Each delay forced the judge, attorneys, witnesses, and clerks to restart context. The court looked fully loaded, but the load itself was causing case lead time to grow.

## Forces

- **The constraint is scarce professional judgment.** A judge's in-court trial time is expensive, legally bounded, and hard to substitute.
- **Demand keeps arriving.** The court can't stop accepting filings merely because the trial calendar is full.
- **Procedural fairness matters.** A flow improvement that weakens due process is not an improvement.
- **Hearing-level scheduling feels efficient locally.** Filling the next available slot keeps the calendar busy, but it spreads attention across too many active cases.
- **Policy changes have to stay inside court authority.** The intervention has to work through scheduling and procedure that judges or court administration can actually change.

## Solution

Treat the judge's trial-phase capacity as the constrained resource, then change the court process so cases move through that constraint with less interruption.

The intervention followed the Five Focusing Steps. Step 1 identified judges as the constrained resource, based on prior Israeli-court research, the cost and scarcity of judicial time, and a demand-versus-capacity check. Step 2 exploited the constraint by adding a final pre-trial planning session before trial began. That planning session made sure documents, witnesses, time estimates, and trial requirements were ready before the court committed scarce in-court time.

Step 3 subordinated scheduling policy to the judge's constrained capacity. The old rule was hearing-level FIFO: schedule one hearing, hold it, then schedule the next hearing in the first open calendar slot. The new rule was case-level FIFO. Once a case entered the trial phase, the court scheduled all approved evidence sessions at one-week intervals, held only a small number of active trial-phase cases per judge, and kept other cases waiting outside the trial phase until an active case completed.

That rule is counterintuitive if local busyness is the measure. It deliberately leaves some cases waiting before trial so the cases already in trial can finish faster. Little's Law explains the bet: for a given arrival rate, reducing work-in-process reduces average time in the system. In court language, fewer active trial-phase cases means less reorientation, shorter waits between sessions, and more coherent use of judicial attention.

Step 4 elevated the constraint by changing closing-argument practice. Written closing arguments had been used to save in-court time, but the practice often produced lengthy submissions that judges had to read, process, and rule on outside the visible courtroom schedule. The intervention encouraged oral closing arguments in a planned session, turning an open-ended document-review burden into a bounded piece of constrained-resource work.

Step 5 recognized that judges would remain the main constrained resource for the foreseeable future. The point was not to "break" the constraint once and declare victory. It was to keep the court from allowing its old scheduling inertia to become the constraint again.

## How It Plays Out

The Jerusalem District Court implementation began with a one-day workshop during the annual court recess. All judges were briefed on the TOC method and the operational changes: final pre-trial planning, case-level FIFO scheduling, and oral closing arguments. The change applied to new civil cases entering trial and to cases already in the trial phase, where judges were instructed to hold a planning session after the next evidence hearing and then schedule future evidence sessions under the new rule.

The active-trial WIP target was small: about five trial-phase cases per judge, instead of roughly sixty. That is the whole pattern in one number. The court did not try to make every file move a little. It tried to make a small set of active cases move decisively through the constrained resource.

The reported before-and-after data are indicative, not a randomized causal proof. In the sample, 64 civil cases ended with judgment on the merits before the intervention and 107 did so after it. Mean trial time fell from 22.19 months to 10.57 months, a 52.37 percent reduction. Mean total case time fell from 55.21 months to 41.01 months, a 25.72 percent reduction.

| Change | TOC interpretation | Court mechanism |
|---|---|---|
| Final pre-trial planning | Exploit the constraint | Prevent cancelled hearings, missing documents, and wasted judge time |
| Case-level FIFO | Subordinate to the constraint | Limit active trial-phase WIP and schedule sessions at one-week intervals |
| Oral closing arguments | Elevate the constraint | Convert open-ended written-review work into a bounded session |

The result matters because it wasn't a generic call for more judicial resources. It was a change in how cases were released into the constrained part of the system and how the system protected that constraint once a case entered it.

> **⚠️ Do not generalize the mechanism without re-identifying the constraint:** The Jerusalem design fits a court where judges are the constraint and trial-phase WIP is high. Another court may be constrained by clerical screening, interpreter availability, prosecutor readiness, defense counsel capacity, courtroom space, filing policy, or statutory deadlines. The pattern is the focusing logic, not the literal one-week interval.

## Consequences

**Benefits.**

- The court can reduce lead time before asking for more judges, more budget, or statutory reform.
- The intervention makes judicial time more productive by reducing cancelled hearings, missing-material delays, and repeated context restart.
- Case-level FIFO gives the court a simple release rule for trial-phase work instead of letting every active case compete for the same future calendar.
- The pattern shows how [Subordination](subordination.md) works in a public legal system: attorneys, parties, witnesses, clerks, and calendars align to the constrained judge's trial capacity.
- The case gives TOC practitioners a recent, peer-reviewed public-sector example beyond healthcare and classic manufacturing.

**Liabilities.**

- Cases waiting outside the trial phase can appear neglected unless the court explains why limiting active WIP improves total flow.
- The final pre-trial session adds visible work before trial, so the court has to protect it as an exploitation move rather than treat it as extra bureaucracy.
- Oral closing arguments may not fit every case type, especially where the evidentiary record or appellate posture requires written treatment.
- A local court may not control the policy constraint that binds it. When statute, funding authority, or higher-court rules define the system constraint, the intervention has to produce evidence for the body that can act.
- The reported data are promising but limited. Practitioners shouldn't treat the percentages as portable performance guarantees.

## Sources

- Azaria, Ronen, and Shamir, ["Justice in Time: A Theory of Constraints Approach"](https://www.tocico.org/_files/ugd/1ed33e_92630cbfe95e4f2e9e4a47ea4cd641db.pdf), TOCICO-recognized Body of Knowledge paper, later published in *Journal of Operations Management*. The primary source for the Jerusalem District Court intervention, including the final pre-trial session, case-level FIFO rule, oral-closing-argument move, and reported lead-time reductions.
- Bar-Niv, Lieber, and Ronen, "Focused Management in a court system: Doing more with the existing resources," *Human Systems Management* 29:4 (2010), 265-277. The earlier Israeli-court-focused-management source the Justice in Time paper cites for judges as the constrained resource.
- Beenstock and Haitovsky, "Does the appointment of judges increase the output of the judiciary?" *International Review of Law and Economics* 24:3 (2004), 351-369. Source for the caution that adding judges does not automatically increase processed cases.
- Bray, Coviello, Ichino, and Persico, "Multitasking, multiarmed bandits, and the Italian judiciary," *Manufacturing & Service Operations Management* 18:4 (2016), 545-558. Supports the paper's contrast between hearing-level and case-level FIFO policy.
- Alfredo Mycue and Eli Schragenheim, ["Unique Features of Government and How Governance Could be Assisted by the Theory of Constraints"](https://www.tocico.org/_files/ugd/1ed33e_61b3339345f948ae8ed1654d39d52fb8.pdf), TOCICO-recognized Body of Knowledge paper. The public-sector frame this court-specific pattern specializes.

---

- [Next: Oxfordshire Radcliffe Hospital A&E](oxfordshire-radcliffe-ae.md)
- [Previous: Unique Features of Government](unique-features-government.md)