Writing prompts for legal research questions that return usable answers
By the ChamberOne team 4 minute read
Think of the last time you handed a research task to a new trainee with a single line: 'Look into limitation for this.' You got back four pages on the wrong jurisdiction. An AI tool behaves the same way. It will answer the question you typed, not the one you meant. A good prompt does not need tricks. It needs the things a careful partner would put in an email: where, when, what happened, what you need back and what you are worried about. This article shows how, with worked examples for associates and paralegals.
Key points
- State the jurisdiction, the date, the relevant facts and the form of answer you want.
- Ask for sources with section or paragraph numbers, and open every one before relying on it.
- Ask for the strongest counter-arguments, not just support for your view.
- Record the prompt and the answer on the file, and treat the output as a lead, not as advice.
Say where the question sits
Law is local. A tool trained on material from many countries will happily blend them. State the jurisdiction at the start, and the court or tribunal if it matters. If the issue is governed by a particular statute, name it. If you do not know which statute applies, say that, and ask the tool to list the candidates for you to check.
Add the date. The law as it stood when the events happened may differ from the law today. Say whether you want the position at the time of the events, the current position, or both.
Give the facts that change the answer
Include the facts that a lawyer would need to see, and leave out names and confidential details. Say whether the parties are individuals or companies, whether there is a written contract, what was agreed and when, and what went wrong. Facts that look minor, such as who signed or where something was delivered, often decide the point.
If the facts are uncertain, say so. 'Assume the letter was received on the fifth but the client says it arrived later' produces a more useful answer than a tidy version that hides the doubt.
State the form of answer you need
Tell the tool what shape you want. A two-paragraph overview for a partner is not the same as a table of elements with the test for each. Ask it to separate what it is confident about from what it is guessing, and to say when a point turns on facts you have not given.
Ask it to say plainly when it does not know. Without that instruction, a tool tends to fill gaps with plausible text.
Ask for sources, then go and read them
Ask the tool to name the statutes, rules and cases it relies on, with the section or paragraph. Treat that list as a set of leads, not as proof. Open each one in a trusted database. Does it exist? Does it say what the tool said? Is it from the right court and the right period?
A tool that cannot show a source is giving you an opinion. Do not put it into advice. If a citation cannot be found, assume it was invented until you find it.
Ask for the other side
Tools lean towards agreeing with you. Counter that by asking for the strongest argument against your position, the cases that cut the other way and the facts the other side would stress. Then ask what evidence would be needed for each side. This turns a one-sided answer into a map of the dispute.
A worked before-and-after
Before: 'Can a landlord keep the deposit for damage?' The answer will be generic, probably blending several systems.
After: 'Jurisdiction: England and Wales. Date: tenancy ended last month. Facts: assured shorthold tenancy, deposit held in a protection scheme, landlord claims for a damaged carpet and no inventory was signed at the start. Question: what can the landlord deduct and what must they show? Form: a short list of the issues, the legal source for each, what evidence matters, and the arguments for each side. Flag anything you are unsure about, and give the statute section or case for each point so I can check it.'
The second version takes two minutes more to write and saves an hour of reading the wrong material. It also gives you a checklist you can verify line by line.
- 'Can a landlord keep the deposit for damage?'
- The answer will be generic
- It will probably blend several systems
- Names the jurisdiction, date, facts, question and form of answer
- Takes two minutes more to write
- Saves an hour of reading the wrong material
- Gives you a checklist to verify line by line
A second example: narrowing a broad topic
Before: 'Summarise the law on restraint of trade.' After: 'I am advising an employer in India on a one-year post-employment non-compete for a senior sales manager. Set out the main legal tests that a court would apply, the points on which the employer's position is weak, and the points on which the employee's position is weak. Identify the statute and the leading authorities you rely on, and tell me which parts of your answer I should treat as most uncertain.'
Notice that the second prompt names the client position, the type of clause and the reader's need. It would produce a different answer for an employee, and rightly so.
Follow-up prompts that sharpen the answer
The first answer is rarely the last. Treat the exchange as a conversation with a trainee and press on the weak points. Ask 'what would change your answer if the contract were oral?' or 'which of these points depends most on a case from a different court?'. Ask it to restate the rule in one sentence, then to give the exception, then to say how a court has treated the exception.
When the tool gives a confident statement, ask how sure it is and what it is relying on. Sometimes it retreats at once, which tells you the first statement was thinner than it sounded. Sometimes it repeats the point with a source, which gives you something to check. Both responses are useful.
Finally, ask it what it would need to know to give a better answer. The list is often a good guide to the facts you should take from the client next.
Habits that keep it honest
- Keep a record of the prompt and the answer on the file, so a supervisor can see how you reached a view.
- Run an important question twice, in different words, and compare. Differences point to the shaky parts.
- Never paste client names or confidential documents into a tool your firm has not approved.
- Treat the output as a research memo from a bright but unreliable trainee: useful, and not yet advice.
- Keep the prompt and the answer on the file
- Run an important question twice, in different words
- Treat the output as a memo from a bright but unreliable trainee
- Paste client names or confidential documents into an unapproved tool
- Put an answer into advice when the tool cannot show a source
This article is general information about the law, legal practice and technology, current when it was published. It is not legal advice. Laws and guidance change: check the sources linked above and take advice on your own circumstances from a lawyer qualified where you are.
Read next
How to check AI legal research before you rely on it
A routine for tracing every AI-suggested authority to its source, confirming it is still good law and testing the proposition it is cited for.
5 minute readGeneral chatbots versus legal research tools: what differs and why it matters
How general chatbots and legal research tools differ on sourcing, links, jurisdiction coverage and currency, and when a general model will do.
5 minute readRetrieval-augmented generation explained for lawyers
A plain explanation of how AI answers from a document set, why it reduces but does not remove fabricated content, and what to ask vendors.
5 minute read