Conditional Workflow Routing

Conditional routing exists because uniform review is either too slow or too shallow. A contract above a value threshold needs legal; one below it does not. A policy touching clinical practice needs a clinician; a travel policy does not. The condition is usually evaluated against metadata — value, category, department, jurisdiction, risk rating — which makes the quality of routing a function of the quality of classification. Routing built on fields nobody maintains degrades silently: documents take the default path, reviewers stop seeing what they should, and nobody notices until something reaches publication that should have been stopped.

Because classification in Centralpoint is applied during ingestion using the organization's own dictionary rather than being entered by hand at upload, the attributes routing depends on are populated consistently. Data Triggers evaluate the conditions explicitly rather than burying them in code, so the rule that sent a document to legal is inspectable — and where AI assists in classifying or drafting, the routing conditions are evaluated on the governed record rather than on a model's impression of it.