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.
Four passes over the package, in order. Each one depends on the previous.
Master agreement, SOWs, amendments, exhibits, side letters and prior executed versions are gathered and read as one related set.
Defined terms, parties, dates and obligations are located in every document and linked to their source clause.
Each mapped element is checked across documents. Where the package states two different things, that becomes a named exception.
Every exception gets the conflicting clauses attached, an owner and a next step — then it is tracked until closed.
These are not subtle drafting issues. They are terms the business is operating under incorrectly, and none of them are visible from inside a single file.
Amendment 2 moved net-30 to net-60. The master and two SOWs still say net-30. Finance is paying to whichever one they happened to read.
A quarterly reporting requirement sits in Exhibit D. It never made it into the obligations register, so nobody has reported in two years.
A liability cap everyone still quotes was replaced at the second amendment. The number being relied on has not applied for eighteen months.
The body references Exhibit C in three places. There is no Exhibit C in the executed package.
Effective date, renewal window and notice period do not reconcile, so nobody can say with confidence when notice is actually due.
"Services" means one thing in the master and something materially narrower in a later amendment. Both definitions are live.
Contract review examines a single document, usually against a playbook and usually inside a word processor. Package reconciliation reads a master agreement together with its SOWs, amendments, exhibits and prior versions, and surfaces where those documents contradict each other. They answer different questions and are complementary.
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.
Anywhere the governing terms are spread across more than a handful of documents. A standalone NDA needs nothing. A master agreement with six SOWs, four amendments and a set of exhibits is exactly where value shows up.
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.
It becomes a named exception with the conflicting clauses attached, an assigned owner and a next step. It stays open and tracked until someone closes it, rather than sitting in a report nobody actions.
How contract package reconciliation works end to end, and where it sits next to a review tool.
The definition, the method, and the discrepancies that only exist between documents.
Encryption, access control, audit trail, and an honest account of what we are certified for.
Master agreement, every amendment, every exhibit. We will show you where it disagrees with itself — free, in one business day.
Card required to start · No migration · Findings in one business day