Workflows
Deviation detection
Every extracted obligation is automatically compared to the resolved standard for its scope. When the two disagree, the platform flags a deviation and writes a rationale.
The trigger
Deviation detection runs at the end of ingestion, and you can re-run it on demand for any agreement. For each obligation on the agreement, the analyser:
- Resolves the standard position for that kind of obligation at the agreement’s scope (see Scope dimensions).
- Compares the actual term against the standard.
- Records a deviation with its severity, direction and a one-line rationale.
Where deviations surface
- The Deviations tab in the workspace.
- On each Agreement view, as the “standard vs actual” block.
- In the renewal pack, as part of the risk summary.
- On the dashboard, as a portfolio counter.
Working a deviation
A deviation is either open or approved. Open means it is flagged and waiting for review. Approved means a human has accepted that this contract intentionally deviates from the standard. Approving a deviation acknowledges the gap; it leaves the standard and the obligation unchanged.
Deviations are scope-aware
A US-NY MSA with a 6-month liability look-back may deviate from your global standard but match your US-NY-specific entry. The detection uses the most specific applicable standard, so this kind of jurisdictional carve-out stays quiet when you hold the scoped entry in your playbook.