Case Context

What is Case Context?

• Who is involved (parties, people, counsel)
• What the case is about (facts, timeline, issues)
• What counts as relevant or important for review
• Where privilege is likely to arise
• Key collection details and additional notes

• Per case + organization: each (Case, Org) pair has its own Case Context.
• Shared across users: anyone in that case/org can see and edit the same Case Context (subject to locking rules).
• Structured: it’s stored as structured JSON and rendered as sections in the UI.
• Used by the AI: when enabled in the Prompt Generator, the AI reads Case Context to write better prompts for your review workflows.

When should I use Case Context?

• You are working on a litigation or regulatory matter and want the AI to stay grounded in the actual pleadings and key facts.
• Multiple lawyers or reviewers need a consistent understanding of:

• Parties, relationships, and roles
• The procedural and factual timeline
• Relevance guidelines and “hot doc” indicators
• Privilege rules and sensitive issues

• You want the AI to write prompt templates that are tailored to this specific matter (rather than generic litigation).

• A full memo or factum
• A replacement for your internal case strategy documents
• A place for privileged internal commentary about strategy (it should stay factual and review-focused)

How Case Context is structured

1. Parties & People

• Who the parties are (plaintiff/defendant/applicant/respondent/regulator, etc.).
• Key individuals (officers, employees, regulators, witnesses, etc.).
• Counsel and firms, where known.
• If it’s not obvious which party your firm represents, add a short note or mark it as unknown.

2. Description & Timeline

• A concise narrative of what the dispute or investigation is about.
• Key factual and procedural events, in rough chronological order, with dates or date ranges where available.
• Focus on pleadings and core background documents.

3. Relevance & Issues

• The main legal and factual issues in dispute.
• What kinds of documents, communications, or events are typically responsive or non‑responsive.
• Indicators of “hot” or especially important documents.

4. Privilege Indicators

• Who is (or may be) counsel, in‑house or external.
• Typical privilege scenarios in this matter (e.g., internal investigation, board materials, regulator correspondence).
• Any special privilege rules or caveats (e.g., joint defense, common interest).

5. Collection Details

• Custodians, sources, and date ranges that are actually in this Nuix case, if known.
• Any gaps or limitations you know about (e.g., missing mailboxes, limited backup tapes).
• This field is often blank early on; that’s okay.

6. Additional Notes

• Any other contextual information useful for reviewers that doesn’t clearly fit into the other sections (e.g., jurisdictional quirks, reputational sensitivities, known weak spots).
• Keep it factual and review‑focused, not argument.

• Open Questions are shown in the yellow follow‑up box after generating Case Context from documents. These are what you should provide to expand case context further. 
• Last Updated is automatically set when you save structured context; it’s used by the agent but not edited directly.

How to open and view Case Context

1. In the Noticia Go sidebar for your Nuix Discover case, look for the Case Context icon (stacked layers).
2. Click the icon to open the Case Context modal.
3. At the top you’ll see:

• A short description of what Case Context is and how to use it.
• A status indicator (Empty / Draft / Needs Input / Ready / Error).
• Badges showing the number of selected documents and Context docs.

Editing Case Context manually

1. Open the Case Context modal.
2. Ensure you have the editing lock:

• If another user is editing, you’ll see a read‑only notice.
• Try again later if you cannot obtain the lock.

3. Fill in or update the text areas for:

• Parties & People
• Description & Timeline
• Relevance & Issues
• Privilege Indicators
• Collection Details
• Additional Notes

4. Click Save in the bottom button row.

• The frontend builds a structured JSON object (contextJson) from your edited fields.
• The backend:

• Stores that structured JSON in the Case Context table.
• Builds a plain‑text version (contextText) in a fixed heading order so it can be used in other flows.
• Marks the status as Ready (unless otherwise overridden).

Building Case Context from documents

1. In Nuix Discover, select documents in the case.
2. In Noticia Go, open the Case Context modal.
3. Make sure:

• You are connected to Nuix Discover (Noticia Go must be running inside the case).
• You hold the Case Context lock.

4. Use the “Add to context” button (Layers icon) in the bottom button row:

• This sends the selected docs’ extracted text plus current context to the Case Context agent.
• The agent returns an updated contextJson, contextText, and any follow‑up questions.

• The structured fields are refreshed with the AI’s updated summary.
• The yellow follow‑up box appears if the agent has questions (for example, “Which party do you represent?” or “Can you provide the pleadings?”).
• The Source documents list shows which Main IDs/doc IDs are currently linked to Case Context, with their titles.

Viewing source documents linked to Case Context

• Each item shows:

• Title (from the case, if available), or mainId if no title could be retrieved.
• Below that, in small grey italics, the doc ID.

Follow‑up questions from the agent

• This box contains any clarifying questions the agent has about the matter (each on its own line).
• These are not editable fields; they are prompts to help you improve your Case Context.
• Once you’ve answered them by updating the relevant sections and/or adding better documents, you can:

• Click Dismiss questions if they’re no longer useful, or
• Regenerate Case Context from new documents, which may update the follow‑ups.

Locking and concurrency

• When you open the modal and acquire the lock, you see the editor in editable mode.
• If someone else is editing:

• You’ll see a read‑only notice and cannot make changes.

• Locks have a timeout; if a user abandons editing, others can acquire the lock later.

Using Case Context with the Prompt Generator

• In the Prompt Generator modal, you’ll see a checkbox:

• Include Case Context
• When enabled, the generator uses the current Case Context to draft prompts tailored to your matter (e.g., review prompts that know who the parties are and what issues matter).

• Keep Case Context reasonably up‑to‑date before using the generator for production prompts.
• When revising strategy significantly (new pleadings, new key rulings), update Case Context and then re‑generate your prompt templates.

Best practices

• Always prioritize pleadings (statements of claim/defense, applications, motions) and core orders.
• Use the Add to context button with those documents first.

• Write for experienced Canadian litigators, not lay readers.
• Avoid narrative repetition; keep each section short and punchy.
• Focus on what helps reviewers decide relevance, issue linkage, and privilege quickly.

• Only include what is clearly supported by pleadings and key documents.
• If something is uncertain or contested, note that explicitly in Additional Notes, not as a confirmed fact.

• Use the Privilege Indicators section for clear rules and patterns.
• Don’t mix privilege notes into general relevance guidance where they might be overlooked.

• This is for high‑value context (e.g., reputational risk, public‑facing facts) that helps reviewers understand why a document matters.
• If a note clearly belongs in another section (e.g., a key event with a date), put it there instead.

• When the agent asks questions in the yellow box, either:

• Answer them in the structured fields, or
• Provide the missing documents (e.g., pleadings) and regenerate.

• Dismiss follow‑ups only once they’re handled or clearly not needed.

Troubleshooting

• I save, but the fields revert

• Ensure you’re saving without backend errors and that you hold the lock.
• The Save button now sends structured fields (contextJson) to the backend and they should persist; if they revert, confirm the backend is reachable and the status shows success.

• I see an error about documentTitle in GraphQL

• The Case Context feature now uses the title field on the GraphQL Document type as documented in Docs/API-docs.md.
• If you still see a documentTitle error, it likely means you’re on an older build or connecting to an environment with a different schema; contact support with the exact error.

Summary

• Built from pleadings and a small set of key documents.
• Edited via a structured, section‑based modal.
• Persisted per (case, organization) and used by the Prompt Generator for smarter, matter‑aware prompts.