SmartSplitAI Contract Analysis Supports Contract Packages with Appendices

Most business contracts aren't single files. They're a main agreement plus appendices: a statement of work, a payment schedule, a delivery specification, a supplemental agreement signed later. The numbers that matter most — prices, deadlines, specifications — are often in the appendices, not the main body. Missing them during review means missing the substance of the deal.

SmartSplitAI Contract Review supports contract package analysis: you upload the main agreement together with its appendices, and the system processes them as a single unit.

What's included in a package

When uploading, you can attach alongside the main agreement:

• Appendices and specifications. The statement of work, technical requirements, product specs — documents that contain the concrete parameters of the deal.
• Schedules and timelines. Milestone plans, interim delivery dates, key deadlines that may be stricter than the main text.
• Supplemental agreements. Amendments and addenda signed separately that modify the original terms.
• Form documents. Acceptance certificate templates, report formats, order forms — templates that become binding once the contract is signed.

How it works

The system accepts a set of files in supported formats — DOCX, text-layer PDF, TXT — and merges them for analysis. The algorithm identifies the main agreement and links appendices through cross-references: file names, in-text mentions, appendix numbering.

After analysis, you receive a unified output where:

• Obligations from the main agreement and appendices are consolidated into a single table — you see who owes what to whom across the full document set.
• Dates from the schedule are cross-checked against deadlines in the main text — if the appendix says one date and the contract body says another, the discrepancy is flagged.
• Amounts from specifications are reconciled with the total contract price — if the line items in the spec don't add up to the price stated in the agreement, the system notes it.

Why this matters

Without package analysis, you risk missing:

• A specification with prices that differ from the main agreement. The body says $45,000 total; the line items in the spec add up to $52,000.
• A schedule with tighter deadlines than the main text. The body says "60 days"; the schedule says "Phase 1 in 20 days, Phase 2 in 15 days."
• A supplemental agreement that changes payment terms from post-payment to partial advance — attached as a separate file, not absorbed into the main body.

Each of these is a real business risk. Package analysis addresses it: the system sees the full document set, not just the main file.

A real scenario

A company signs a website development contract. The main file is an 8-page agreement. Attached: a technical specification (15 pages), a milestone schedule (2 pages), and an acceptance certificate template.

Without package analysis: only the main agreement is uploaded. The AI checks the general terms — parties, price $45,000, deadline 60 days, liability. But the specific requirements from the spec (responsive design, CRM integration, three-language support) aren't analyzed. The phased delivery schedule isn't factored in.

With package analysis: the system sees the full set. Deadlines from the milestone schedule are included. Spec requirements are cross-referenced against the scope. If the spec calls for CRM integration but the body says "website development" without detail, the discrepancy is flagged.

File formats in a package

A package can contain files in different formats: the main agreement in DOCX and an appendix as a text-layer PDF. The system handles mixed-format packages correctly.

The restriction: scanned PDFs and photos are not supported — for the main agreement or appendices. If an appendix exists only as a scan, it needs to be converted to an accepted format first.