Historical Clause Recommendations
Historical Contract Recommendations (HCR) helps contract reviewers make informed redlining decisions by using language from previously negotiated contracts. HCR is enabled at the playbook-level, allowing administrators to control whether historical contract intelligence is available during Redline review for contracts associated with that playbook.
During redline review, HCR analyzes relevant historical agreements to identify how similar clauses were negotiated in the past and presents a synthesized clause recommendation based on that historical data.
If a rule is configured for the clause, HCR also evaluates the recommended language against that rule and identifies any resulting risk. This allows reviewers to consider both historical negotiating patterns and the organization's defined contract policies when reviewing a clause.
How it works
- During Redline review, HCR checks each clause to see if there's enough historical data to make a recommendation.
- It looks for signed contracts that match on Contract Type, Company, Industry, and Region (full match). If no contract matches on Company, it tries again using just Contract Type, Industry, and Region (fallback).
- From the matches, it picks up to five contracts that contain the clause, skipping ones that don't. It prefers active contracts over expired ones, and only looks back three years.
- If it doesn't find matching contract, it stops. No recommendation is shown for that clause.
- For each of the five contracts, it uses the latest amended version of the clause, not the original signed version, if it was changed later.
- If a rule exists for that clause type, it checks the recommended clause against the rule and shows any risk it finds. If no rule exists, it skips this step.
- The reviewer sees this as a Historical Precedents card next to the regular rule-based card. They can apply it, apply the other one, apply both, or apply neither.