Skip to content

Audit Long Agreements and Reports for Broken Cross-References

Before signing a 90-page contract or filing a regulatory brief, catch every 'See Section 14.4 (which was deleted)', circular definition, and unattached Exhibit C.

Copy the prompt and paste it into the AI assistant you already use.

Embarrassing structural defects hiding in last-minute deal PDFs

  1. 01

    Verify semantic match, not just section existence

    After inserting a new Section 8, 'subject to the cap in Section 9.2' still points to a real number—except 9.2 is now 'Notices', not 'Liability'.

  2. 02

    Cross-check Capitalized Terms in both directions

    Catch body terms typed as `Service Credits` when Section 1 defined `SLA Credits`, leaving your remedy technically undefined.

  3. 03

    Confirm referenced Exhibits actually contain content

    Countless executed contracts attach `Exhibit B — Pricing & SLA` at page 74 followed by a blank page reading `[Intentionally Omitted]`.

  4. 04

    Sweep for bracketed placeholders and drafter comments

    Hunt down `[●]`, `TBD`, `NTD:`, and `$XX,000` artifacts tucked inside deep schedules at 2:00 AM before closing.

How it works in practice

Draft Agreement Excerpts (Pages 4, 31, 62)

p.4: '"Permitted Subcontractors" means entities listed on Schedule 4.' p.31 (Sec. 11.3): 'Notwithstanding anything to the contrary, Indemnification under this Section is capped at the Super-Cap set forth in Section 9.4.' p.26 (Sec. 9.4): '9.4 Publicity and Logo Usage.' (Note: Super-Cap moved to Sec. 9.6 in Tuesday redline). p.62: Schedule 1, Schedule 2, Schedule 3 [Document ends—Schedule 4 missing].

Structural QA Defect Report

• Semantic Broken Ref (Sec. 11.3, p.31): Points to `Section 9.4` for 'Super-Cap', but Sec. 9.4 is 'Publicity' (Super-Cap appears shifted to Sec. 9.6). • Missing Attachment (p.4 / p.62): `Schedule 4 (Permitted Subcontractors)` is referenced in Definitions but omitted from the PDF.

Catches a wrong-section cap pointer that even Word field codes miss when manual numbers were typed.

Common questions

Why don't Microsoft Word cross-reference fields prevent wrong section numbers?

Lawyers and business teams type plain-text numbers ('Section 9.4') manually during fast redlines, so inserting a paragraph above silently shifts every target below.

How often does litigation erupt over missing contract schedules or broken refs?

Disputes over blank exhibits, undefined capitalized terms, and shifted liability cross-references are staple cautionary tales in commercial contract case law.

Does this structural check work on engineering specs and RFP submissions too?

Yes—catching 'see Architecture Diagram in Annex D' when Annex D wasn't uploaded saves RFP bids from instant non-compliant scoring.

Learn more

Related guides and background articles for this task