AI Context gives SimpleAI a permanent briefing on who you are and how your organization works. Your industry, your legal standards, your risk positions, your preferred tone and review style: set them once, and every AI interaction that follows reflects them automatically. Every chat response, every playbook review, every redline suggestion benefits from context you configured once.

This chapter covers the two layers that make up AI Context: Company Context, set by your admin, and User Context, set by you.

What AI Context is

AI Context is a set of persistent preferences that SimpleAI applies across every interaction. It's not a playbook rule and it's not a one-time prompt; it's background intelligence that travels with you.

Within AI Context, there are two layers:

Company Context is set by your organization's admin. It captures your company's identity, industry, risk posture, and legal standards. Every member of your team benefits from it automatically; they don't configure anything themselves.

User Context is set by you. It captures your personal preferences: your role, how you like the AI to communicate with you, how aggressively you want it to flag issues, and any jurisdictions or practice areas you specialize in.

These two layers combine. Company Context establishes the floor; your organization's non-negotiables. User Context personalizes the experience on top of that, within the organization's standards.

Company Context: set it once for the whole team

Company Context is configured in the SimpleDocs Settings panel by an admin. Once it's in place, every team member's AI outputs automatically reflect your company's standards without anyone needing to explain them individually.

The limit is 1,200 characters, which is enough to capture what matters most. The goal is precision, not comprehensiveness.

What to include

Company identity and industry.  Tell SimpleAI what kind of company you are, who you contract with, and what types of agreements you handle most often.

Example: “We are a mid-market healthcare SaaS company. Our contracts are primarily with US hospital systems and health plans.”

Jurisdictions and governing law.  Set your default jurisdiction and any regulatory frameworks that apply to your contracts.

Example: “Primary jurisdiction is New York. HIPAA compliance required in all vendor agreements.”

Legal tone and drafting style.  If your team values plain English, say so. If you prefer short, self-contained clauses, say that too.

Example: “Use plain English. Avoid archaic terms. Prefer short, self-contained clauses.”

Risk posture and negotiation positions.  State your default risk tolerance and your firm positions on key clauses. If there are things your company will never accept, put them here.

Example: “Moderate risk posture. Aggregate liability cap should not exceed 2x fees. Never accept unlimited indemnification.”

Legal entities and signing authority.  List your entities and clarify which signs which types of agreements.

Example: “Acme Inc. (US), Acme UK Ltd (UK). US entity signs all SaaS agreements; UK entity handles EMEA vendor contracts.”

Tip
Think about what you repeat most often. What do your attorneys re-explain to AI tools, to new hires, and to outside counsel over and over again? That's exactly what goes in Company Context.

User Context: personalize your experience

User Context is yours to configure, in your own SimpleDocs Settings. It doesn't affect anyone else on your team; it layers your personal preferences on top of the company standards your admin has set.

What to include

Your role and the work you do.  Tell SimpleAI what kind of agreements you typically work on and where you sit in the organization.

Example: “I’m Senior Counsel on the commercial team. I primarily review SaaS and technology licensing agreements.”

How you want the AI to communicate.  If you want concise, direct output, say so. If you’d rather have the AI explain its reasoning, ask for that.

Example: “Keep explanations concise. When suggesting redlines, always include a brief rationale. Always flag issues by severity: high, medium, or low.”

Your review posture.  Set this explicitly so the AI doesn’t over- or under-flag for your style.

Example: “Moderate review posture. Flag material risks and missing protections. Don’t redline minor style issues unless they create ambiguity.”

Your jurisdictions and practice areas.  If you specialize in EMEA transactions or regularly handle GDPR implications, put that here.

Example: “I focus on EMEA transactions. Flag GDPR implications in data processing clauses.”

Note
What User Context doesn’t do.  User Context personalizes your experience — it doesn’t override your organization’s standards. If your Company Context says aggregate liability can’t exceed 2x fees, your personal preferences can’t change that. The org’s floor always holds.

How the layers work together

When SimpleAI generates a response, it applies context in a clear priority order:

• Playbook or session-specific instructions:  anything set in the current session or a specific playbook rule. These always take precedence.
• Company Context: your organization’s standards, applied universally.
• User Context: your personal preferences, layered on top.
• AI Memory: behavioral patterns the AI learns over time (covered in the next chapter).

This order matters. Your organization’s non-negotiables are protected at layer 2 regardless of personal preferences. Individual flexibility lives inside that structure, not outside it.

What changes when context is in place

Redline suggestions align with your positions by default.  The AI doesn’t need to be told your liability cap stance or which entity signs vendor agreements. It already knows.

Chat responses reflect your company’s identity.  When you ask “what’s our standard position on indemnification?”, the AI answers relative to your actual standards; not a generic legal default.

Drafting uses your preferred style, governing law, and entity names.  You stop correcting the AI for using the wrong jurisdiction or legal tone.

New team members get consistent outputs from day one.  Company Context means the organizational standard is always the baseline, regardless of who’s doing the review.

Getting started

For admins:  Open SimpleDocs Settings and navigate to Company Context. Draft your context statement covering the five areas above. Keep it under 1,200 characters; precise beats comprehensive.

For individual users:  Open your personal settings and navigate to User Context. Think about what you re-explain most often when working with AI tools, and put that here. Start with your role, review posture, and any jurisdictions you specialize in.

‍