Partner Contract Intelligence · Documentation
User Journey
The end-to-end path through Partner Contract Intelligence, from trigger to outcome.
← Partner Contract Intelligence- 1
Contract → triage
A partner agreement enters the queue un-analyzed. A reviewer opens it and runs Analyze. If the document is a scan, the OCR stage reads the page first; then clause analysis flags each clause's risk, extracts the commission rate, computes a composite risk score and a confidence, and assigns the triage band. The amendment register is built from the high-risk clauses. The contract is now triaged, and contract.analyzed is emitted on the event bus.
- 2
Triage → the rest of the ecosystem
That single analysis ripples outward. The contract.analyzed event and the contract's risk score feed Partner Performance Scorecards (#13), where the analyzed contracts' average risk becomes the partner's contract sub-score (100 − average risk). A high-risk or expiring contract surfaces in the amendment register for renegotiation, and a compliance sweep in #22 can check the contract against the active rate-parity and partner policies. No app holds a second copy of the contract — they read the one analyzed record and the one event.