How Triage compares to classification tools, VMS intake, and manual processes.
| Capability | Triage | Classification Tools | VMS Intake |
|---|---|---|---|
| Captures intent at origin | ✓ | ✗ | ✗ |
| Routes across all channels | ✓ | ✗ | Contingent only |
| Compliance File generation | ✓ | ✗ | ✗ |
| 60-second completion | ✓ | ✗ | ✗ |
| Deterministic scoring | ✓ | Partial | ✗ |
| Jurisdiction playbooks | ✓ | ✗ | ✗ |
| Manager attestation | ✓ | ✗ | ✗ |
| AI agent routing | ✓ | ✗ | ✗ |
| Zero IT to launch | ✓ | ✗ | ✗ |
| Services/SoW coverage | ✓ | ✗ | ✗ |
| Change management | ✓ | ✗ | ✗ |
| Rate intelligence at origin | ✓ | ✗ | Post-decision |
Every other tool in the market operates downstream of channel selection. Triage is the only platform that captures intent at the point of origin.
Classification tools assess after a channel is selected. Triage diagnoses before any channel is chosen.
Regulators want evidence of the decision, not the destination. Triage provides both.
VMS covers contingent. Triage covers permanent, contingent, services, outsourcing, and AI agents.
Your VMS, CMS, ERP, sourcing engine, and orchestration platform each serve a purpose. Triage ensures the requests that reach them are correctly classified from the start.
Your VMS processes correctly classified contingent requests. Triage ensures every request that reaches it belongs there.
ERP records costs after commitment. Triage operates before the commitment, ensuring spend was correctly incurred.
Contract management begins after the commercial model has been agreed. Triage ensures the model was correct before any contract is drafted.
Autonomous sourcing optimises supplier selection within a channel. Triage determines whether that channel was correct before sourcing begins.
Orchestration coordinates execution across systems. Triage diagnoses the channel before any system is involved.
Pickers, forms, decision trees, chat interfaces, and routing rules each have legitimate uses. This section explains where their design assumptions break down for complex people and services transactions.
Catalogue selection assumes the requester already knows the right channel. Triage diagnoses intent before any option is presented.
Forms collect data. They do not score it, weight it, or produce a defence of the classification decision.
Binary branching forces a single path. Complex workforce transactions require weighted scoring across multiple simultaneous factors.
Conversational UX is a delivery format. The scoring engine behind the questions is what produces an auditable Compliance File.
Routing rules distribute requests that have already been submitted. Triage operates before submission, at the point of intent.