Procurement orchestration helps hiring managers make bad decisions faster. Triage scores the request; composerID plays it into the systems that execute it — one Intent ID on every object.
Triage decision intelligence creates a score & composerID writes it to HRIS, ATS, VMS, ERP, CLM and S2P so the whole orchestra plays from the same sheet. See full coverage and status →
Intent is born where work is asked for — so the questions are asked there too. Upstream connectors Beta ask them inside Microsoft Teams, where the request already starts.
Microsoft Teams today (beta), Slack on the roadmap. The questions arrive as cards in the thread; each answer is fixed once it is given, and the decision comes back into the same conversation. See it working →
The Triage web intake asks the same questions, scores them the same way and keeps the same evidence trail. Chat reaches more requesters; the questions and the scoring are identical. The Triage interface →
composerID publishes the decision into the contractor, recruitment, finance, contract or sourcing system that runs it — one record per decision, each stamped with the Intent ID. See the publish pipeline →
Triage handles the requests no catalogue covers: the channel is chosen by diagnosis rather than by habit. composerID is how that decision reaches the systems that execute it.
Triage questions the request on outcome, constraints, urgency and risk, then recommends a channel with a confidence score and the reasons recorded.
The decision becomes an Intent Record anchored by a single Intent ID, with the Compliance File attached — evidence, alternatives considered, approvals. It cannot be altered once issued.
composerID publishes into each system that needs the decision and writes the Intent ID into every record it creates — idempotently, so a retry never doubles up. Afterwards it re-checks each record against the destination and reports what changed. The platforms page lists every destination and its status.
composerID is the integration layer of Triage, the decision-intelligence platform. Triage is the product you buy; composerID is how its decisions are published. One contract, and one evidence trail from diagnosis to the systems that execute the work.
Triage tests every workforce request — permanent hire, contingent, statement of work or outsourced — and recommends a channel with the evidence attached. www.addtriage.com →
Every Triage deployment includes composerID. Destinations are enabled by tier: start with Triage alone and switch on the systems you need. See the tiers →
Requisitions, work orders, contracts and signature packs are created in the systems you already run, each carrying its Intent ID back to the decision that caused it.