Every contract, held to your standard.

Rivell learns your negotiating positions from the playbooks you already keep and checks every contract against them. You make each call, and the redline comes back in Word.

Try the demo See how it works

From your playbook to a finished redline.

  1. Teach it your positions

    Add the playbooks and clause libraries you already use, in Word or Excel. Rivell reads each entry into a position, and you approve every one before it is used.

    Commercial Contracts Playbook v4.2.docxEntry 1 of 25
    Source passage

    Liability cap

    Our positionAggregate liability is capped at the fees paid or payable in the 12 months before the claim.
    Fallback24 months' fees where the contract value is at least £250,000.
    Walk-awayUncapped liability, or a cap above two times the annual fees.
    ApproverTom Whitlock. Marcus Feld and Priya Raghavan for any increase.
    What Rivell read
    Topic
    Liability cap
    Preferred wording
    Fees for 12 months
    Fallback wording
    Fees for 24 months, contracts of £250,000 or more
    Walk-away wording
    Uncapped, or above two times annual fees
    Approvals
    Marcus Feld, Priya Raghavan
    Applies to
    MSA, order form
    Does this match the playbook source?EditApprove entry

  2. Drop in a contract

    Rivell reads the contract and works out which side you are on. Then it checks each clause against the positions that apply, even when the wording differs.

    Kestrel Assurance - Master Services Agreement.docxSupplier side
    1. 4Fees and paymentChecked, no issue found
    2. 9ConfidentialityChecked, no issue found
    3. 12Limitation of liabilityFlagged
    4. 13Term and renewalFlagged
    5. 15AuditNeeds your look
    6. 17Governing lawChecked, no issue found
    7. 19Force majeureChecked, no issue found
    Checked against your commercial playbook and clause library

  3. See the gap, make the call

    Each finding shows the clause, your position and the gap, with wording your team already approved. Accept it, edit it, keep the clause, or escalate it.

    Breaches walk-away · 12.4 Limitation of liability

    Unlimited liability for data protection claims

    What the contract says

    Nothing in this Agreement limits the Supplier's liability for any breach of Data Protection Laws, including regulatory fines.

    Your playbook

    Do not accept an uncapped data protection category. A separate cap of two times the annual fee is acceptable.

    The gap

    The clause leaves the Supplier exposed without limit for data protection claims, which your playbook marks as a walk-away.

    Suggested change

    Each party's liability for breach of Data Protection Laws shall not exceed two times the annual Fees.

    Approved organizational drafting · Clause library

    Approval required: Marcus Feld and Priya Raghavan

    AcceptEditKeep as draftedDismissEscalate

  4. Send back a clean redline

    Rivell writes your accepted changes into the original Word file as tracked changes, then reads the file back to check each one.

    MASTER SERVICES AGREEMENT

    12. Limitation of liability

    12.2 Each party's aggregate liability under this Agreement shall not exceed three times the annual Fees the Fees paid or payable in the 12 months before the claim.

    12.4 Each party's liability for breach of Data Protection Laws shall not exceed two times the annual Fees. Nothing in this Agreement limits the Supplier's liability for any breach of Data Protection Laws.

    13. Term and renewal

    13.2 This Agreement renews for successive periods of twenty-four (24) twelve (12) months unless either party gives notice.

    Kestrel MSA - Bramber redline.docxChecked against your changes Verified redline · 3 changes

One screen for every decision.

The findings, the contract with its tracked changes, and your decision, side by side.

The Rivell review workspace. On the left, ten findings for the Kestrel master services agreement. In the middle, the indemnities clause with tracked changes. On the right, the finding with the playbook position, the gap and the suggested wording. The Rivell review workspace. On the left, ten findings for the Kestrel master services agreement. In the middle, the indemnities clause with tracked changes. On the right, the finding with the playbook position, the gap and the suggested wording.
The review workspace, on the demo contracts.

Change the standard, and the review follows.

Rivell has no opinion of its own. It applies yours. Move the sliders and watch three contracts change their answer.

Your playbook

Payment terms

30 days
60 days

Invoices are payable within 30 days. A term of up to 60 days is acceptable as a fallback.

Kestrel AssuranceOrder form, clause 6.1

Invoices are payable within forty-five (45) days of receipt.

Vantage HealthServices agreement, clause 7.2

Invoices are payable within sixty (60) days of receipt.

Sablepoint AnalyticsMaster agreement, clause 5.3

Invoices are payable within ninety (90) days of receipt.

A simplified illustration. In a real review, Rivell judges the full wording of each clause against the text of your playbook, not a single number.

Built to earn a lawyer's trust.

Your playbook outranks old deals

A similar clause from a past deal never overrides your playbook. Rivell weighs each source by its authority before it looks at how similar it is.

Findings cite their sources

Each finding shows the clause, the position it was judged against, and the playbook and version that position came from.

Close calls come to you

A close call gets a second opinion. If the two opinions disagree, the clause is marked for your look instead of guessed.

No position is skipped in silence

Every position in your playbook gets a status: compared, not found in this contract, out of scope, or not compared. When a position was not compared, Rivell says why.

Most of the judgment comes from a System One model.

Jev, a System One decision model, judges each clause and says how sure it is. Close calls get a second opinion from a language model, and disagreements come to you. Fixed rules set severity and check the Word file.

See how the engine works

A clause goes to Jev. A clear answer becomes a finding, and rules set its severity. A close call goes to a language model for a second opinion. If they agree, it becomes a finding. If they disagree, it needs your look. Clear answer Close call Agree Disagree Clause 12.2 From the contract Jev judges it Against the positions that apply Finding Cites your playbook Second opinion From a language model Rules set severity Never model confidence Needs your look Never guessed

Open, and yours to run

Rivell is open source. You run it on your own infrastructure, so contracts and knowledge stay on your own servers. Today it reviews Word contracts in English, for one user on one machine. Read the code, or run it yourself.

View the source on GitHub

Made by Shridhar

Rivell is a personal project, built end to end from the engine to the interface. It explores how a System One decision model and a language model can share the work in a field where precision matters.

Shridhar on LinkedIn

See it on a real contract.

The demo follows a fictional software company through five contracts, from the first read to a checked redline. No sign-up needed.

Try the demo