Local Signal Triage Board¶
Meeting format — instantiates Bottom-Up Signal Integration
Sorts incoming local signals into urgent versus exploratory and routes validated ones to decision owners.
A Local Signal Triage Board is a recurring live meeting in which a small standing group reviews the local signals arriving from the field, separates the urgent from the exploratory, applies a quick reality check, and routes the keepers to named decision owners. Its defining act is prioritization plus assignment: it decides what moves now, what waits as a pattern to watch, and who owns each. It is not a capture channel and not a cross-site pattern hunt — it works on signals that others have already captured, and its output is a triaged, owned queue rather than a stored record or an analytic trend.
Example¶
A city bus agency holds a weekly triage board where operations supervisors review the week's operator and rider signals. Three land on the table: an operator's report of a near-collision with cyclists at a specific intersection, a rider's note that one route runs chronically late, and a broken wheelchair ramp on a garage-bound bus. The board applies its threshold on the spot — the near-collision is high-severity and time-sensitive, so it is validated with a quick check against the incident log and routed the same day to the safety-engineering owner; the late route is parked as an exploratory pattern to accumulate more reports; the ramp is assigned to maintenance with a due date. The board's product is exactly this: a sorted, owner-assigned queue with urgency labels. It captured none of these signals and did not itself redesign the intersection — it decided what happens to each and who is on the hook.
How it works¶
- Standing cadence. A fixed recurring slot so signals do not pile up unattended between reviews.
- Urgent-versus-exploratory split. An explicit threshold sorts what escalates now from what accumulates as a watch-item.
- Fast validation gate. A quick corroboration check keeps a vivid one-off from being escalated as if it were established.
- Owner assignment. Every routed signal leaves the room attached to a named owner and, where relevant, a due date.
Tuning parameters¶
- Cadence — daily to monthly. Frequent boards move urgent signals fast but consume attention; sparse ones risk backlog and stale escalation.
- Urgency threshold — how severe or frequent a signal must be to jump the queue. A low bar catches weak high-severity signals early but floods owners.
- Validation-gate strength — a glance versus a real corroboration step. Stronger gates cut false alarms but slow urgent routing.
- Routing map — tight owner assignment keeps signals relevant; loose routing risks everything landing on everyone and nothing being owned.
When it helps, and when it misleads¶
Its strength is preventing signal backlog: it keeps a capture stream from silting up unread and gets urgent weak signals to an owner before they harden into failure. It is the joint where listening becomes action.
Its failure mode is misplaced urgency — vivid or recent reports leap the queue over the quiet, high-severity signal that lacks drama, and a slow or overloaded board becomes the bottleneck it was meant to clear. The word triage comes from battlefield medicine, where Napoleon's surgeon Dominique-Jean Larrey sorted the wounded by need rather than rank;[n1] the discipline is the same here — sort by an explicit severity threshold, not by who shouted, and protect the minority or quiet signal from being deprioritized simply because it is calm.
How it implements the components¶
signal_priority_threshold— the urgent-versus-exploratory split is the priority threshold applied in the room.validation_rule— a quick corroboration gate confirms a signal is real before it is escalated.decision_integration_path— validated signals leave routed to named owners, the step that turns collected signal into action.
It does not implement pattern_aggregation or context_preserving_signal_record — the board sorts and routes signals that others have already captured and patterned; the cross-site pattern extraction from the underlying records is Field Report Review, its nearest twin, which reads the corpus where the board triages the stream.
Related¶
- Instantiates: Bottom-Up Signal Integration — the joint where validated local signals are prioritized and handed to owners.
- Consumes: Frontline Feedback Form — the captured, severity-tagged signals it triages arrive from such forms.
- Sibling mechanisms: Community Listening Session · Field Report Review · Frontline Feedback Form · Frontline Feedback System · Near-Miss Reporting System · Participatory Sensing · Stakeholder Survey · User Research Synthesis · Worker Voice System
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Local Signal Triage Board operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it sorts incoming local signals into urgent versus exploratory and routes validated ones to decision owners.
Independent corroboration: The frozen evidence defines Local Signal Triage Board as 'Sorts incoming local signals into urgent versus exploratory and routes validated ones to decision owners', so its operative form is Decision, Gate & Allocation.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Medicine & Healthcare
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Triage by urgency under constrained capacity originated in battlefield and emergency medicine.
Related originating lineages:
- Disaster Management & Risk Reduction — Incident triage materially generalized priority sorting to incoming field signals.
- Organizational & Management Science — Visual work boards and ownership queues supply the standing operational artifact.
- Public Administration & Policy — Bottom-up policy implementation contributes escalation of local evidence into authorized decisions.
Review resolution: Light authoritative research supports medicine_healthcare as the primary provenance: Triage by urgency under constrained capacity originated in battlefield and emergency medicine. WHO defines triage as urgency-based sorting and prioritization under emergency-care constraints. The competing reviewed lineage (organizational_management) and other formative traditions remain explicit alternates rather than being erased or confused with downstream applicability. origin_mode=cross_disciplinary_synthesis records the relationship among those origin traditions, while domain_reach=universal separately records how broadly the generalized mechanism can be applied.
Attribution caveat: The exact meeting-board form is an encyclopedia synthesis over management review and triage practice. The signal-board form is an encyclopedia synthesis around the older triage principle.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; medium confidence.
Sources consulted:
- https://www.who.int/tools/triage — WHO defines triage as urgency-based sorting and prioritization under emergency-care constraints.
Notes¶
[n1] Triage — sorting by urgency of need under limited capacity — originates in battlefield medicine; Dominique-Jean Larrey, Napoleon's surgeon, is credited with organizing the treatment of the wounded by severity rather than rank, the same discipline a signal board applies to reports. ↩