Chat with Docs
What is Chat with Docs?
Chat with Docs lets you ask questions about a case's Paginated and Indexed Bundle in plain English and get an answer sourced directly from the documents — with a citation showing exactly which page it came from, so you can check it yourself in seconds.
Think of it as a faster way to interrogate a bundle you'd otherwise search manually — not a replacement for reading the records, but a way to get to the specific fact you need without paging through hundreds of scanned documents.

How to access Chat with Docs
Chat with Docs is available from the documents panel, on any case where a Paginated and Indexed Bundle has been generated. Look for the 'Chat with document' menu item in the Document menit - it opens a two-panel view: your conversation on the right, the source PDF on the left.

What to ask
Chat works best for questions that can be answered directly from what's in the bundle:
- "What did the GP note about [symptom] on [date]?"
- "Is there a referral letter in the records?"
- "What was the patient's [test result] on [date]?"
- "Summarise the treatment for [condition] across all the records."
- "Give me a timeline of [event] from first presentation to resolution."
There's a 500-word limit per question - enough for a detailed question, not for pasting in a document.
Checking the answer
Every factual answer comes with a citation - click it and the right-hand panel jumps to that exact page in the bundle. We'd encourage you to check citations, especially early on, so you can get a feel for how reliable they are before relying on them for anything that matters.
What it won't do
Chat with Docs answers only what's documented in the case records. By design, it will not:
- Say whether care was appropriate or amounted to negligence
- Give a view on the strength of a claim or prospects of success
- Recommend treatment or medication
- Draft letters, documents, or anything beyond reporting what's in the records
If you ask something in this territory, you'll get a message explaining why it can't answer and, where possible, what to ask instead. This is expected behaviour, not a bug — if it ever does one of the things above instead of declining, please tell us straight away (see Feedback below) rather than waiting for the end-of-pilot form.
"Not found in records"
If chat says something isn't in the records, that's a real answer, not a failure — it means a search was done and nothing relevant turned up. It will not guess or fill in a gap from general medical or legal knowledge. If you think something should be there and isn't, that's exactly the kind of thing worth flagging as feedback.
The disclaimer
You'll see a disclaimer in the chat panel at all times: answers are based on the documents in this case only, this isn't legal or clinical advice, and you should always verify against the source records. It's there permanently, not a one-time pop-up — your professional judgement stays the responsibility of the person reviewing the case, same as it always has been.
A few things to expect, since this is an early Pilot version
- Response times vary - some questions answer in a few seconds, others (especially "summarise everything about X") can take noticeably longer. If it seems stuck, give it a bit more time before assuming something's wrong - but if it's been over a couple of minutes with no change, that's worth flagging too.
- One bundle per session — you can't currently ask questions across multiple bundles or cases at once.
- Peristence of the chat - when you close the chat window, the conversation disappears.
- Nothing here is saved as a note or chronology entry automatically — if you want to keep something, copy it into your usual working document for now.
Feedback
Your feedback directly shapes what gets built next. About three weeks after you start, either complete our short feedback sheet or we'll schedule a feedback call with you — whichever suits you better.
If you have an urgent issue or something stands out while you're using it before then (good or bad) — especially anything under "What it won't do" above behaving unexpectedly — don't wait for that: flag it to Helen Renshaw (helen.renshaw@finlegal.io) straight away.