Skip to main content
Triage is a decision intelligence platform for workforce and services. composerID connects its decisions to the systems that carry out the work. Triage helps people explain the work they need, answer the right questions and apply their organisation’s policies. It identifies mismatches and supports a recommendation across five channels: permanent, outsourced, contingent, services via SoW and AI agents. Country screening, drafting and reporting can support that journey where configured. The result is a recommendation and a record of how it was reached. One Intent ID links that decision to what happens next. The reference connects the records; the answers and evidence stay behind it.

​
Four clear jobs

The destination system keeps its own record number, approvals and delivery process. The Intent ID is the shared reference back to Triage. Use Intent ID for the reference and composerID for the integration platform; they do not introduce two business identifiers.

​
Choose how far to connect

Compare the four sizes. Conductor is arranged separately; it is not a fifth integration size.

​
What “one field” means

The integration centres on one shared decision reference. It does not require the downstream system to receive the questionnaire or reproduce Triage’s decision logic. Some vendor operations also require a template identifier, an owner or native request fields before they can create a record. Those requirements must come from agreed client configuration or the destination’s normal intake. A one-field reference does not mean every vendor accepts a one-property API request. The present sandbox also demonstrates richer request payloads; the narrow launch-and-reference journey must be tested for the selected platform.

​
What a template promise means

Opening a published template, creating a request from it and creating a new template definition are three separate capabilities. A vendor may support one and restrict another. The platform assessment records them separately, alongside documentation and test-environment access.
The commercial model above defines the intended service. The Intent API currently runs against mock destinations in the hosted reference sandbox; a documented vendor field does not establish a live connection. Manuscript has its own API and programme access. Conductor’s initial source adapter is implemented, but its operational API is not yet deployed. Each platform needs its own configuration and test evidence.

For commercial teams

Explain S, M, L and XL through the customer’s next step.

For implementation teams

Choose the API, webhook, middleware or manual connection path.

Platform assessment

Check documentation, templates, sandboxes and access evidence.

Conductor and Triage Desk

Understand operational oversight and its current build status.