> Source: https://mywaypoint.ai/docs/examples/contract-terms-against-policy
> Documentation index: https://mywaypoint.ai/llms.txt


# 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.**


## For

- [For Revenue](https://mywaypoint.ai/for-revenue)
- [B2B Software](https://mywaypoint.ai/industries/b2b-software)

## In

- [Microsoft 365](https://mywaypoint.ai/docs/integrations#microsoft-365)
- [Confluence](https://mywaypoint.ai/docs/integrations#confluence)
- [Notion](https://mywaypoint.ai/docs/integrations#notion)

## Use case

```prompt-request
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 builds

- **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.
- **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.