Routing rules operate after a request has been submitted to a system. They read the fields the requester populated, apply conditions, and assign the request to a queue or a handler. The channel has already been selected. The routing rule does not question it. Triage operates at the step before.
The comparison is not a verdict on the alternative. It is a precise statement about where its design assumptions break down.
When the channel is known and correct, routing rules efficiently distribute volume to the right handlers. Routing an approved contractor requisition to the right supplier tier in a VMS is a legitimate use of rule-based distribution.
Routing rules govern spend approvals, manager escalations, and policy exceptions within a process that has already been correctly initiated. They manage flow within a channel, not selection between channels.
Conditional logic that triggers API calls, field mappings, or notification rules based on submitted data is an appropriate use of routing rules. The decision has been made. The rule manages the consequence.
These failures are not edge cases. They are structural properties of the approach that become problems at enterprise scale with regulatory exposure.
If a manager submits a request to the VMS that should have been a statement of work, the routing rule processes it as a contingent request. The misallocation entered the system before the rule was applied. No routing rule operates upstream of the channel decision.
Routing rule sets are written to handle anticipated cases. Requests that do not fit established patterns either fall to a default route or require manual handling. Complex people and services transactions frequently produce edge cases that rule sets were not designed to address.
A routing log records where a request was sent. It does not record why the channel was chosen, whether alternatives were considered, or how the classification decision was reached. It is not a Compliance File.
| Capability | Triage | Routing Rules |
|---|---|---|
| Operating point | Before channel selection, at point of manager intent | After channel selection, within a downstream system |
| Channel correction | Misallocation identified and corrected before submission | Not possible. Request is already in the wrong system. |
| Decision logic | Algorithmic scoring produces the channel recommendation | Conditional rules distribute an already-made decision |
| Novel request handling | Scoring model handles cross-channel complexity and edge cases | Rules fall to default or require manual intervention |
| Compliance output | Compliance File at point of origin | Routing log only. No classification rationale. |
| Misallocation rate impact | 40% misallocation reduced to single digits | No impact. Misallocation enters the system first. |
| Audit readiness | Decision logic documented before submission | Distribution record only. Channel choice undocumented. |
The manager selects the contingent channel based on assumption and submits to the VMS. The routing rule reads the submission fields and assigns it to the appropriate supplier tier. The routing has functioned correctly within the VMS. The channel decision was wrong. The error is now embedded in the system as a legitimate contingent request.
Before any system is involved, Triage presents six structured questions. The answers score 55% permanent and 45% contingent. The recommendation is permanent with a detailed rationale explaining why the tenure and deliverable characteristics do not fit contingent classification. The manager sees the scoring, accepts the recommendation, and the request routes to the ATS rather than the VMS. The Compliance File documents the scoring that produced this decision.
Worker classification enforcement is accelerating. IR35 in the UK, AB5 in California, the EU Platform Work Directive across Europe, and Scheinselbstandigkeit in Germany all require organisations to demonstrate that classification decisions were made through a systematic, documented process.
The question is not whether the decision was correct. It is whether the process that produced it was auditable. Projected enforcement activity exceeds $60B in fines and back-pay through 2028.