exclusive to Triage

Workforce Orchestration needs the right score.

The only integration layer for leaders managing workforce and services as a single, strategic asset.

Guided buying for procurement is simple: one S2P system for catalogue items. You’ll find them here:

Workforce orchestration is more complex; like the lines of a musical stave with many systems as notes on each line of the stave.

composerID plays one ID number into every system: business intake, workforce planning, services procurement + statement of work (SoW), outsourcing and contingent resourcing and even consulting and advisory.

The Channel Map

Plays perfectly with HR and Procurement.

composerID writes workforce decisions to dozens of different systems so the whole orchestra plays from the same sheet. See full coverage and status →

Upstream

Why do PO numbers have all the fun?

Purchase Order (PO) numbers are ubiquitous in purchasing: you can’t get paid without one. composerID takes the concept and applies it to human capital no matter what channel they come from.

Requestors can start in Teams, Slack or conversational triage. The questions arrive as cards in a thread to understand the need, then generate the composerID for all downstream orchestration. See it working →

How it works

Diagnose the request, then publish the decision.

Today, non-specialist requestors key data straight into expert systems of record: a harsh, out-of-tune cacophony. Triage handles the requests no catalogue covers, so the channel is chosen by diagnosis rather than by habit, and composerID is how that decision reaches the systems that execute it.

Test the request before you route it

Everyone enters one front door. Triage questions the request on outcome, constraints, urgency and risk, then recommends a channel with a confidence score and the reasons recorded.

Record the decision with one ID

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.

Publish it everywhere it must go

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.

With Triage

composerID ships only with Triage.

composerID is the integration layer of Triage, the decision-intelligence platform. Triage is the product you buy; composerID is how its decisions are published.

Every Triage deployment includes composerID. Destinations are enabled by tier: start with Triage alone and switch on the systems you need. See the tiers →

Give every system the same decision.

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.

Read the docs →Explore platforms