Pull Replenishment Signal¶
Signalling protocol — instantiates Work-in-Progress Limiting
Authorizes the next start only when a downstream slot actually opens, so capacity — not demand — pulls new work into the system.
A Pull Replenishment Signal is the trigger that couples a new start to a completed exit. Where the other mechanisms declare how many items may be active, this one governs when the next may begin: it fires only when a downstream slot empties, and that firing — not a request, a deadline, or an idle worker — is the sole authorization to draw the next item out of the backlog. It inverts the default direction of work. Instead of demand pushing items in from the top, freed capacity pulls them in from below. On a board it is the returning card; in a warehouse it is the empty bin; in a queue it is the released slot. The signal carries no opinion about priority or size — only the bare fact that room now exists.
Example¶
A regional parts warehouse stocks each fast-moving part in two bins on the pick shelf. Pickers draw from the front bin; the moment it runs dry they slide the back bin forward and drop the empty bin's reorder card into a collection slot. Nothing is reordered on a schedule or a forecast — the empty bin is the only event that triggers a replenishment order to the supplier. When demand spikes, cards pile into the slot and reorders naturally accelerate; when demand sags, the shelf simply stops asking. No planner decides the pace; consumption does.
The same protocol runs on knowledge work with the bins replaced by active slots: a support team pulls the next ticket only when an agent closes one, the "closed" event acting as the returned card. In both cases the mechanism's genius is that a start is physically impossible until something finishes — the empty bin, and only the empty bin, unlocks the next fill.
How it works¶
- The unit of authorization is an exit, not an arrival. A start cannot happen until something finishes, moves on, or is cancelled — the completion literally emits the card the next start must hold.
- The signal travels upstream, hop by hop. A freed slot at one stage pulls from the stage before it, which (now short an item) pulls from the one before that, back to the backlog. Local and chained, with no central scheduler.
- It is silent by default. No free slot, no signal, no start. The protocol's "no" is the absence of a signal, which is why it fails safe: a stalled system simply stops starting rather than piling on.
Tuning parameters¶
- Trigger point — how empty a slot must be before the signal fires (reorder at one bin dry, or at a low-water mark). Earlier triggers cut the risk of starvation but raise average WIP.
- Signal batch size — whether one exit authorizes one start (one-piece flow) or a freed batch authorizes a batch. Smaller batches smooth flow; larger ones cut signalling overhead.
- Signal latency — how fast a freed slot's signal reaches the backlog. A once-a-day standup leaves capacity idle between beats; an instant automated event keeps flow tight but can whipsaw on noise.
- Backlog readiness — whether pulled items must be pre-qualified before they may answer a signal. Ungated pulls are fast but admit half-baked work into an open slot.
When it helps, and when it misleads¶
Its strength is that it makes stop starting, start finishing structural rather than exhortatory: you cannot start without freeing a slot, so the completion bias is enforced by the protocol instead of by willpower, and the system self-regulates to demand with no forecast. This is the pull principle at the heart of the Toyota Production System's supermarket method.[n1]
Its central failure mode is starvation: if a downstream stage chronically fails to signal, upstream capacity sits idle, and because the protocol transmits a jam as silence, a stalled pull can hide a bottleneck rather than expose it. It also says nothing about which item to pull — priority belongs to a separate queue-discipline mechanism. The classic misuse is a "pull" system that quietly keeps a push hatch open: an expedite lane that starts work with no freed slot, restoring the overload the signal existed to prevent. The discipline is to honour the signal as the only start authorization and route genuine exceptions through a visible override, never a side door.
How it implements the components¶
Pull Replenishment Signal fills only the admission side of the machinery — the trigger, not the cap:
admission_control_rule— it is the admission rule in its pull form: new work becomes active only when a slot opens, never on demand pressure.pull_replenishment_signal— the signal itself: the exit event that both authorizes and triggers the next start.
It does not set the cap (wip_limit → Work Slot Token or Kanban WIP Limit), justify the number (capacity_basis → Throughput-Based Limit Review), or decide what happens to stuck items (blocked_work_policy → Blocked Work Swarming).
Related¶
- Instantiates: Work-in-Progress Limiting — this protocol is what turns a static cap into live flow behaviour.
- Consumes: Work Slot Token supplies the finite slots whose release the signal reports.
- Sibling mechanisms: Work Slot Token · Kanban WIP Limit · Active Case Cap · Blocked Work Swarming · Concurrency Limit · Project Portfolio Limit · Sprint Capacity Rule · Team Workload Cap · Throughput-Based Limit Review
Editorial Notes¶
Form Classification¶
Form family: Control, Automation & Runtime
Rationale: Pull Replenishment Signal operates as a live operational control that automatically routes, enforces, adapts, or responds during execution because it authorizes the next start only when a downstream slot actually opens, so capacity — not demand — pulls new work into the system.
Independent corroboration: The frozen evidence defines Pull Replenishment Signal as 'Authorizes the next start only when a downstream slot actually opens, so capacity — not demand — pulls new work into the system', so its operative form is Control, Automation & Runtime.
Nearest alternative: Protocol, Workflow & Routine — Pull Replenishment Signal includes features of a repeatable ordered procedure or handoff sequence that coordinates action, but its defining operation is a live operational control that automatically routes, enforces, adapts, or responds during execution.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Logistics & Supply Chain Management
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Downstream consumption authorizing upstream replenishment is the canonical kanban pull-and-fill mechanism of production logistics; Toyota's history documents these pull and kanban replenishment systems.
Related originating lineages:
- Operations Research — Inventory and queueing models supplied formal capacity and replenishment analysis.
- Organizational & Management Science — Lean production and visual workflow management generalized pull to knowledge work.
Review resolution: The blind reviewers disagreed on primary lineage. Light authoritative research resolves the defining form in favor of logistics_supply_chain: Downstream consumption authorizing upstream replenishment is the canonical kanban pull-and-fill mechanism of production logistics; Toyota's history documents these pull and kanban replenishment systems. The other materially formative traditions are retained as alternates; current breadth of use remains separate as domain_reach=multi_domain.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
The signal enforces a limit it does not set: it presupposes a defined number of slots to replenish. Bolt it onto a system with no cap and it has nothing to trigger on. This is why it pairs naturally with Work Slot Token — the token release is precisely the exit event the signal transmits.
[n1] The pull system — producing or starting work only in response to a downstream consumption signal rather than a forecast — is the core of Taiichi Ohno's Toyota Production System and its "supermarket" replenishment method. It is the standard corrective to demand-push overproduction, which is why it names this mechanism. ↩