Triage Compliance
Find risk while the decision can still change.
Compliance should not begin after a request has already become a contract. Triage checks the answers against each other as the work is described, flags mismatches in real time, and brings in country-specific assurance when the arrangement needs it.
A mismatch is a signal to investigate — not automatically a legal finding.
Yes — deliver the ERP cutover
Client manager
Milestones + acceptance criteria
The answers describe supplier outcome accountability and client task direction. Clarify how the work will operate before this request proceeds.
From one contradictory answer to the right assurance journey.
The first line of defence is the conversation itself. Triage can spot contradictions before the route hardens, then preserve the facts, evidence and actions needed for the relevant country review.
ERP migration delivery partner
Two answers describe different operating models. Ask how the work will actually be controlled.
Choose the journey from what already happened.
Preserve the diagnostic and override history rather than starting from a blank form.
Do not confuse an answer with proof.
One evaluation. Four independent questions.
One identified control needs attention.
Some evidence is present; one item remains missing.
Procurement to add scope-change control.
Approval remains a separate scoped decision.
Prerequisites can be complete without pretending the system itself has supplied an authorised decision.
Start with mismatches. Go deeper when the jurisdiction requires it.
Triage Compliance has two connected jobs: detect risky or contradictory combinations in the intake, and run the appropriate country assurance journey when the arrangement needs country-specific controls, evidence and review.
Question mismatch
Compare answers in real time. Surface contradictions, missing facts and combinations that need clarification while the request is still being formed.
Country assurance
Use jurisdiction, route history and lifecycle stage to establish the additional facts, controls and evidence the arrangement needs.
Action & authorisation
Tell people what needs attention, who owns the next action and whether a separate authorised decision exists — without disguising a model output as legal permission.
Give requestors an action. Give Compliance the evidence.
The underlying evaluation should not change because the audience changes. What changes is how much of it each person needs to see.
What needs attention?
Explain the concern in plain language, give the next action, name the owner and say when it needs to happen.
Why did the model say that?
Show applicable tests, established and unresolved facts, evidence state, controls, sources, overrides and exact release identity.
Does someone need to intervene?
Use the mismatch and assurance state to decide whether the request can continue straight through or needs human support.
Compliance is different before the contract, before the work and during the work.
Early idea
Help shape the arrangement before commitments exist. The emphasis is on design and safeguards.
Contract drafting
Use the draft as evidence and align wording, responsibilities and controls with the arrangement being designed.
Agreed, not started
Run a readiness check: have the required controls, evidence and approvals actually been put in place?
Work underway
Compare actual practice with the recorded arrangement and identify remediation where behaviour has drifted.
Unknown is not safe. Missing evidence is not guilt. A low score is not approval.
The product should preserve uncertainty rather than turn it into false precision.
Say what is unresolved
Unknown, conflicting, expired, not assessed and not applicable are different states and should stay different.
Separate received from verified
A document can exist without proving operational practice. A draft control can exist without being implemented.
Record who can approve
Ready for approval and Approved to start are different states. Authorisation needs its own scoped record.
Build the first line of defence into the conversation.
Find contradictions at intake, apply the right country assurance where needed, keep evidence and actions visible, and make approval an explicit decision rather than an assumption.
Country content frameworks
How we write, trace, version and review.
Framework references and implementation status. Jurisdiction reviews are pending.
- ISO 37301
- ISO/IEC 31010
- DDI
- DMN (planned)
- ISO 24495-1 (testing planned)
- ELI / ECLI
- SemVer
- W3C PROV
- ISRS 4400 (review structure)