Workforce Orchestration needs the right score.
composerID ships with the Enterprise tier of every Triage deployment. It's a portable decision record published into every system of record.
One contract, one thread of accountability — from diagnosis to system of record.
Decision intelligence interrogates every workforce request — perm, contingent, SoW or outsourced — and prescribes the channel with the evidence attached. www.addtriage.com
Every Triage deployment includes composerID. Destinations are enabled by tier — start standalone, add downstream connections as the programme proves value.
Requisitions, work orders, contracts and envelopes are created in the systems you already run — each one carrying the Intent ID back to the decision that caused it.
Triage is the front door for the requests that have no catalog — the channel is chosen by diagnosis, not by whoever typed the request. composerID is how that decision reaches the systems that execute it.
Triage decision intelligence works the request over — outcome, constraints, urgency, risk — and recommends the channel with a confidence score and the rationale on record.
The decision becomes a portable Intent Record anchored by a single traceable Composer ID, with the Defence File — evidence, alternates considered, approvals — attached. Immutable, URI-safe, yours.
composerID publishes into the right system(s) of record — idempotently, with the ID written into every object it creates. Webhooks and reconciliation keep the record truthful after go-live.
A single Intent ID links the decision, the evidence, the execution, and the audit trail across every system it touches. The same intent reaches different destinations — without re-keying, without losing context.
Ask “why did we engage this supplier through this channel?” six months later, and the answer is still attached to the object.
Enterprises run different processes by region, business unit, category, and channel. The Channel Map defines how intent becomes action, so the same decision routes to the right destination every time.
The Compliance File is an evidence bundle that travels with the decision. The URL is written into the system-of-record object on publish; where supported, the PDF is attached directly.
Triage keeps the canonical copy in its own store — so portability remains even if you change VMS vendor or tenant configuration.
Destinations across HRIS, ATS, VMS, ERP, CLM and S2P, plus the platforms Triage connects to for decision intelligence.
Preventable errors are prevented before execution — the channel decision is made once, well, and travels with the work.
One consistent request experience across channels, even when the back-end tools differ by country or business unit.
Evidence, overrides and timestamps ride the audit spine. Months later, one query by Composer ID explains the whole engagement.
The decision record survives vendor and tenant changes — swap a destination by swapping a mapping profile, not by re-implementing.
Start standalone. Add downstream connections as the programme proves value.
No integrations needed. Magic links, SSO, embedded intranet. Every request generates a Compliance File from day one.
One downstream integration. RESTful API posting to VMS or HRIS. Intent-ID handoff to your system of record.
Multiple integrations. Pull data from enterprise datasets into the question flow. Reporting APIs for BI platforms.
Bi-directional sync. External market data. Portfolio analytics. Custom connectors for any enterprise system.
See how Triage connects to your existing VMS, HRIS, ERP and procurement systems — and turns every decision into a portable asset.