Pickers present options from a predefined catalogue. Great for pens with SKUs. They're not good for people or services.
The comparison is not a verdict on the alternative. It is a precise statement about where its design assumptions break down.
Catalogues work well when the category, supplier, and commercial model are already established. Reordering standard IT equipment or renewing a known service contract requires selection, not diagnosis.
Defined deliverables with fixed specifications are well-suited to catalogue selection. The requirement is clear, the options are bounded, and the choice logic is price and availability.
Meeting room bookings, stationery orders, standard software licences. Where the nature of the need is unambiguous and the channel is predetermined, pickers are efficient.
These failures are not edge cases. They are structural properties of the approach that become problems at enterprise scale with regulatory exposure.
When a manager needs help but cannot define whether that help should be permanent, contingent, a service, or an AI agent, the catalogue presents options they are not equipped to evaluate. The wrong selection enters the system with no record of why it was made.
Jurisdiction, budget, timeline, and the nature of the deliverable all influence which channel produces the best outcome. A catalogue cannot weigh these factors. It presents the same options regardless of context.
A picker records what was selected. It does not record why. When a regulator asks why a worker was classified as contingent rather than permanent, a selection receipt is not a Compliance File.
| Capability | Triage | Pickers and Catalogues |
|---|---|---|
| Starting point | Manager intent before any channel is considered | Predefined catalogue of options |
| Decision support | Algorithmic scoring across all five channels | None. Requester selects unaided. |
| Compliance output | Compliance File: intent, scoring logic, channel recommendation | Selection receipt only |
| Cross-channel routing | Permanent, contingent, services, outsourcing, AI agents | Catalogue contents only |
| Contextual adaptation | Questions adapt to jurisdiction, budget, and role type | Same catalogue for every request |
| Misallocation detection | Algorithmic scoring surfaces the correct channel regardless of requester assumption | Not possible. Selection is the outcome. |
| Audit readiness | Timestamped, immutable Compliance File for every request | No decision logic captured |
The manager opens the catalogue and selects from available supplier tiers. The selection is submitted. There is no record of whether permanent hire, a contractor, a consultancy, or an AI agent was considered. There is no scoring of relative cost or compliance exposure. The choice reflects habit and catalogue familiarity, not diagnostic accuracy.
Triage asks six questions about the deliverable, timeline, budget, jurisdiction, and whether the output is a service or a headcount. The algorithmic scoring engine weights the answers across all five channels. The recommended outcome is presented with ranked alternatives and a documented rationale. The Compliance File captures everything before any downstream system is involved.
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.