Multi-document review

Techniques for prompting LOIS for Word Composer to analyze multiple related contracts at once, including cross-document comparison and consistency reviews.

Multi-document review involves analyzing several related documents together – like a master agreement with its amendments, or multiple vendor contracts for comparison. The challenge is maintaining context across documents while identifying patterns, conflicts, and opportunities.

Common multi-document scenarios

1. The Amendment Chain Master agreement plus multiple amendments over time. You need to understand the current state of the relationship and catch any conflicts.

2. The Document Family Related agreements that work together – MSA, SOWs, DPA, SLAs. Each document references others, and terms must align across all of them.

3. The Vendor Comparison Multiple proposals or contracts from different vendors. You need to identify the best terms and understand your options.

4. The Version Evolution Redlined versions showing negotiation progression. Track what changed, what was accepted, and what’s still open.

Core techniques

Technique 1: The current state analysis

When dealing with amendments, first establish what’s actually in effect:

"Here's an MSA and three amendments. What are the current operative terms for payment, liability, and termination?"

This creates a baseline before analyzing further.

Technique 2: The conflict finder

Identify where documents contradict each other:

"Compare these documents and identify any conflicting terms. Show which document would control and why."

Conflicts often hide in details like notice periods, pricing, or technical specifications.

Technique 3: The best terms extraction

When comparing options, pull the optimal provisions:

"From these three vendor agreements, identify the most favorable terms for each key provision and create a composite 'ideal' agreement."

This shows you what to negotiate for.

Technique 4: The evolution tracker

Understand how positions have changed:

"Show how the liability provisions evolved across these three redline versions. What did each side concede?"

This reveals negotiation dynamics and remaining sticking points.

Managing document relationships

A. Hierarchical analysis

Understand which documents control:

Master Agreement (controls generally)
└── Amendment 3 (modifies payment only)
└── Amendment 2 (modifies liability only)  
└── Amendment 1 (superseded by Amendment 2)
└── SOW 1 (subject to MSA except pricing)

B. Cross-reference mapping

Track how documents connect:

MSA Section 8 → References DPA
DPA Section 3 → Requires SLA metrics
SLA Exhibit A → Defines MSA service levels
SOW Section 2 → Modifies MSA pricing

C. Temporal organization

Arrange documents by effective date:

1. Original MSA (Jan 2020) - Baseline
2. Amendment 1 (Jun 2020) - Added new services
3. COVID Amendment (Mar 2021) - Temporary changes
4. Amendment 2 (Jan 2023) - Restored normal terms
5. Current SOW (Oct 2024) - Active project

Common multi-document prompts

A. For amendment reviews

"I have an MSA and five amendments. Please:
1. List what each amendment changed
2. Identify any amendments that conflict
3. Summarize the current operative terms
4. Flag any provisions that are now unclear"

B. For vendor comparisons

"Compare these three vendor contracts:
Create a table showing: Vendor | Price | Payment Terms | Liability | Termination | Recommendation"

C. For document family reviews

"Review this MSA, DPA, and SLA together:
- Do all termination provisions align?
- Are there any conflicting obligations?
- What happens if we terminate one but not others?"

D. For precedent analysis

"Here are five similar deals we've done. What terms did we usually accept? Where did we typically push back? What's our pattern?"

Advanced strategies

A. The waterfall analysis

Trace how terms flow through documents:

Step 1: "How does the MSA define 'confidential information'?"
Step 2: "How does the DPA modify this for personal data?"
Step 3: "Do the SOWs add any additional categories?"
Step 4: "What's the complete picture across all documents?"

B. The scenario testing

Run hypotheticals across documents:

"If we terminate for breach, walk through what happens according to:
- The MSA termination clause
- The DPA data return requirements
- The SOW milestone payments
Show the complete termination process."

C. The composite building

Create unified views from scattered provisions:

"Pull all data protection obligations from all documents into one comprehensive list. Note source document for each."

Managing complexity

A. Chunk by topic

Don’t try to analyze everything at once:

First pass: Payment terms across all documents
Second pass: Liability provisions across all documents
Third pass: IP ownership across all documents

B. Create summary documents

Build working documents as you go:

"Create a single-page summary of operative terms pulling from all documents"

C. Use visual organization

Request structured output:

"Show as a table with documents as columns and terms as rows. Use ✓ for present, ✗ for missing, and note conflicts in red"

Common pitfalls

• Lost in details Don’t get buried in minor inconsistencies while missing major conflicts.

• Assuming alignment Never assume related documents were coordinated. Always verify.

• Version confusion Always confirm which versions are current and operative.

• Missing integration clauses Check how documents incorporate (or don’t incorporate) each other.

Quality control for multi-document review

A. The completeness check

"Have we reviewed all documents that could affect this deal?"
"Are there any referenced documents we haven't analyzed?"

B. The consistency verification

"Do our conclusions change if we change the order of documents?"
"Which document controls if there's a conflict?"

C. The practical test

"Can we actually operate under these combined terms?"
"What happens in common scenarios under these documents?"

Tools and techniques

A. Document labeling

Always label documents clearly in prompts:

"[MSA-2020]: The master agreement states..."
"[Amendment-2023]: But the amendment modifies this to..."
"[Current-SOW]: The active SOW requires..."

B. Change tracking

Monitor what’s different:

"Track changes between Version 1 and Version 2:
- Added: New data protection section
- Deleted: Automatic renewal
- Modified: Payment terms from 30 to 45 days"

C. Priority setting

Focus on what matters:

"Ignore formatting differences
Focus only on substantive business terms
Prioritize conflicts that affect active obligations"

The key insight

Multi-document review isn’t just about reading more papers – it’s about understanding how documents work together as a system. The relationships between documents often matter more than individual terms.

Success requires both seeing the forest and the trees: understanding the big picture while catching crucial details that could cascade across documents.

Remember

Every multi-document review should answer three questions:

1. What’s the complete current picture across all documents?
2. Where do documents conflict or create gaps?
3. What’s the practical impact of operating under all these documents together?

Take time to map relationships before diving into details. A few minutes understanding document hierarchy and connections saves hours of confusion later.