Contract terms checked against policy

Upload a contract & Chip pulls out the four terms you named, checks each one against your SLA policy & cites the clause so you can check its work.

Use case

Extract the notice period, any liability cap, the renewal mechanics and any indexation clause, check each against our SLA policy, and cite the clause for every finding so I can check it.

What Chip asked

Chip reads what is already in your workspace first. On an extraction build it then asks the one question that decides its shape:

When a PDF comes in, do you want the fields filled in automatically, or just a place to store the file and type into?

Say "just a place to store it" & you get a bare form; say "automatically" & Chip builds a pipeline that reads the document itself. For this ask, one row is one term.

What got built

• An upload that starts the work. Attach a PDF & the upload itself is the trigger, so nobody has to kick anything off.
• A table of findings. One row per term, each carrying its clause reference & one of three labels: within policy, outside policy or not covered.
• A list grouped by document, with policy conflicts sorted first, so the conflicts are the first thing you see.
• Nothing lost. A file Chip cannot read stays visible & marked, so you can try again.
• Documentation, written as it built. Your intent in your own words, an overview of every piece & a decision record for each judgement call.

Chip rehearses a new pipeline against your real data before it hands you the switch.

How it runs now. Drop a contract in & the findings appear, conflicts first, each with the clause to check. What you do about an outside-policy term stays with you.

Try it

Attach a contract PDF & paste this:

Extract the notice period, any liability cap, the renewal mechanics and any indexation clause from each contract I upload, check each against our SLA policy and cite the clause for every finding so I can check it.