Software procurement
Verifier sign-off & gates
The human gate. A Verifier audits clmAI Procurement's review, clears every unverified item, and is the only party who can approve, subject to firm diligence gates.
What the Verifier does
A user with the Verifierrole reviews clmAI Procurement’s work on the request’s Legal review and Decision tabs. They:
- Audit the review: read each finding against its quoted source.
- Resolve unverified items: set a status for every row the agent left
Unverified, choosing from the statuses allowed for that item. - Confirm or override the recommendation: accept clmAI Procurement’s Approve, Approve (with conditions) or Reject, or substitute their own. Both the agent’s recommendation and the Verifier’s are retained.
- Confirm the review: stamping who verified it and when.
Every item is resolved before confirmation
Confirmation requires every row to be resolved first. The human clears each open item, which is the control that ensures every finding has been read and supported before the request moves on.
Approval gates
Confirming the review is one part of approval. On approval, clmSpace enforces a set of firm diligence gates. Approval proceeds only once every gate is satisfied, and you can preview the outstanding gates for a request at any time so there are no surprises at decision time.
- Human verification: a Verifier confirms the review. This gate is always enforced on every approval.
- Sanctions: every supplier is screened, and a clear sanctions check is always required to approve. This gate is always enforced on every approval.
- Criticality-driven controls: higher-criticality suppliers must carry the corresponding protections, for example a DPA and an adequate security posture, before they pass.
- Spend: anticipated spend is checked against policy.
The core gates are always enforced
Human verification and a clear sanctions check are mandatory on every approval and are applied to every request, every time. Where a documented business reason supports an exception to a criticality-driven control, an approver records it on the decision, and that rationale is kept for audit.
The decision
The approve or reject decision requires the Verifier role and moves the request to approved or rejected. The policy that gates approval is configurable per tenant.
One gate, two places
This is the same control philosophy as the obligation verification gate: AI proposes, a human stands behind it before it becomes authoritative.