Lv.1 0 XP

Review Routing Design — Building the Human-in-the-Loop Pipeline

Core 6 min +25 XP
💡
THE ANALOGY

A hospital triage system designed as a process, not just a rule. Not just 'urgent patients go to emergency' — but a full pipeline: who does triage, what information they see, how long cases wait at each level, how escalation works, and how outcomes feed back to improve triage accuracy.

⚠️ EXAM TRAP — The Wrong Answer People Choose

Designing routing rules without designing the full pipeline — who receives the human review queue, what information they see, what actions they take, and how their decisions feed back to improve routing.

KEY POINTS
1 Routing is a pipeline, not just a rule — includes queue management, reviewer interface, action options, and feedback loop.
2 Reviewer information: provide extracted data + source document + specific uncertain fields + recommended action.
3 SLA per tier: auto-process = immediate, spot-check = same day sample, human review = defined SLA.
4 Feedback loop: reviewer decisions feed back to improve routing thresholds and confidence calibration.
5 Escalation path: items stuck in queue past SLA escalate automatically.