Context layering

How to build rich, multi-dimensional prompts in LOIS for Word by layering company, deal, and counterparty context for nuanced legal contract analysis.

Context layering means building your prompt with multiple levels of relevant information. Instead of dumping everything into one paragraph, you strategically add different types of context to create a complete picture for the AI.

Think of it like building a legal argument – you start with the facts, add the applicable law, consider the business context, then apply everything to reach a conclusion.

This guide builds on the foundational context elements covered in Context Essentials. Start there if you’re new to providing context in prompts.

Why context layering matters

Single-layer prompts produce generic results. When you layer different types of context, the AI can:

• Balance competing considerations appropriately
• Make nuanced recommendations based on multiple factors
• Avoid solutions that work legally but fail practically
• Produce output that’s immediately actionable

The context hierarchy

Build your context from broad to specific:

Layer 1: Foundation context

Who you are and what document you’re reviewing.

I'm the vendor reviewing a customer's MSA
Document type: SaaS subscription agreement

Layer 2: Environmental context

The business and regulatory landscape.

Industry: Healthcare technology
Regulations: HIPAA compliance required
Market: Highly competitive, many alternatives

Layer 3: Relationship context

The specific dynamics of this deal.

Customer: Fortune 500 company
Leverage: Low - we're in competitive RFP
History: No prior relationship
Deal size: $2M annually

Layer 4: Specific constraints

Your particular requirements and limitations.

Must-haves: Limitation of liability at 12 months fees
Cannot accept: Uncapped indemnification
Internal requirement: 30-day payment terms
Timeline: Must close this quarter

Layer 5: Strategic context

What you’re trying to achieve beyond this document.

Goal: Establish foothold in healthcare market
Priority: Get referenceable customer
Trade-off: Will accept some risk for logo value

Building effective layers

Start broad, get specific

Don’t start with minutiae. Build context naturally:

• Poor layering: Starting with “Section 8.3(b) needs revision” before explaining the document

• Good layering: Start with the big picture, narrow to specific issues

Make connections between layers

Show how different contexts relate:

We're a startup (Layer 1) in a regulated industry (Layer 2) 
negotiating with a risk-averse bank (Layer 3) 
but we need this deal to close our funding round (Layer 4)

Don’t repeat information

Each layer should add new context, not restate what’s already there.

Keep layers relevant

Every piece of context should influence the analysis. If it doesn’t matter to the outcome, leave it out.

Advanced layering techniques

The tension layer

Add conflicting requirements to get nuanced recommendations:

Context: We need strong IP protection (Layer 1)
But: We have no leverage (Layer 2)
And: They won't accept our standard terms (Layer 3)
So: Need creative alternatives that achieve protection without looking aggressive

The precedent layer

Add historical context that shapes current decisions:

Base context: Reviewing vendor agreement
Historical: Previous vendor had data breach
Impact: Board requires enhanced security terms
Application: Need provisions beyond standard

The cascade layer

Show how one context affects another:

Primary: We're a government contractor
→ Triggers: FAR/DFARS requirements
→ Which means: Specific flow-down clauses needed
→ Resulting in: Less negotiation flexibility

Common layering patterns

For regulated industries

1. Basic deal structure
2. Regulatory requirements
3. Industry standards
4. Specific compliance needs
5. Enforcement trends

For complex negotiations

1. Party positions
2. Business relationship
3. Leverage dynamics
4. Non-negotiables on both sides
5. Potential trade-offs

For risk assessment

1. Document type and purpose
2. Your risk tolerance
3. Counterparty’s profile
4. Historical issues
5. Business impact of risks

When to use context layering

Essential for:

• Multi-party agreements with competing interests
• Regulated industry contracts
• High-stakes negotiations with complex dynamics
• Situations where business and legal needs conflict
• Documents requiring board or executive approval

Overkill for:

• Simple NDAs with standard terms
• Routine amendments
• Low-value, low-risk agreements
• Standard playbook applications

Common mistakes

• Information dumping Don’t add every possible detail. Each layer should serve a purpose.

• Wrong order Starting with specifics before establishing basics confuses the AI.

• Contradictory layers Make sure your contexts align. Don’t say “no leverage” then “push hard for our terms.”

• Missing critical layers Forgetting regulatory context in a healthcare deal makes the whole analysis useless.

Practical example

Here’s a well-layered prompt:

Layer 1 - Foundation:
I'm reviewing an MSA as the vendor (software company)

Layer 2 - Environment:
Financial services industry
SOC 2 Type II required
Highly regulated customer

Layer 3 - Relationship:
Customer: Top 10 US bank
Our position: One of 5 vendors in RFP
Leverage: Low to medium

Layer 4 - Constraints:
Must have: Liability cap at annual fees
Cannot accept: Audit rights to our other customers
Board requirement: No uncapped indemnity

Layer 5 - Strategy:
This is our entry into financial services
Need one referenceable bank customer
Willing to invest in compliance for long-term relationship

Task: Review terms and suggest minimal changes that protect our core requirements while maximizing chance of winning the deal.

Remember

Context layering isn’t about providing more information — it’s about providing the right information in the right order. Each layer should add a dimension that changes how the AI approaches the problem. Without layers, you get legally correct but practically useless advice. With proper layering, you get recommendations that work in the real world.