Contract package reconciliation is the process of checking a master agreement against all of its related documents — SOWs, amendments, exhibits, side letters and prior versions — to find terms that conflict, obligations that were superseded, and provisions that appear in one document but not another. It differs from contract review, which examines a single document on its own.
Master agreement, SOWs, amendments, exhibits, side letters and prior executed versions are read as one related set — not as separate files.
Terms, obligations, dates and defined language are compared document to document to find where the package disagrees with itself.
Each discrepancy becomes a named exception with the source clauses attached, an owner, and the next step required to close it.
Free. Card required to start. Findings back in one business day.
The contract review category is well served. Those tools read one document against a playbook and redline it, usually inside Word, and several do it very well. Lexara solves the adjacent problem they were never built for.
| Capability | Contract review tools | Lexara |
|---|---|---|
| Reviews one document against a playbook | Yes | Yes |
| Flags risky or non-standard clauses | Yes | Yes |
| Redlines inside a word processor | Yes | No |
| Reconciles across the full document package | No | Yes |
| Detects conflicts between a contract and its amendments | No | Yes |
| Surfaces obligations spread across related documents | No | Yes |
| Finds superseded provisions still being relied on | No | Yes |
| Assigns the next step to resolve each discrepancy | No | Yes |
Comparison describes the contract review category as generally marketed. Lexara is designed to sit alongside a review tool, not replace it.
An amendment changed the payment window. The master agreement and two SOWs still state the original.
A reporting requirement lives in an exhibit nobody ever added to the obligations register.
A clause everyone still operates under was replaced two amendments ago.
The body references Exhibit C. There is no Exhibit C in the executed package.
Effective dates, renewal windows and notice periods that do not reconcile across documents.
A defined term meaning one thing in the master and something narrower in a later amendment.
Contract review tools analyse one document against a playbook, usually inside a word processor. Lexara reads the whole package together and finds discrepancies that only exist between documents — an amendment that changed a payment term the master still states differently, or an obligation in an exhibit that no one tracked.
No, and we would not recommend that. If you have a review tool that works inside Word for first-pass review and negotiation, keep it. Lexara handles the cross-document question that tool was never built to answer.
Always. Lexara surfaces discrepancies with the source clauses attached so a lawyer can judge them quickly. It does not render legal conclusions, and every finding traces back to the specific language that produced it.
Anywhere the governing terms are spread across more than a handful of documents. A standalone NDA does not need reconciliation. A master agreement with six SOWs, four amendments and a set of exhibits is where the value is.
Master agreement, amendments, exhibits, the lot. We will show you where it disagrees with itself — free, in one business day.
Card required to start · No migration · Answer in one business day