
How to Ask Better Questions in a Mock Client Interview
A mock client interview can go wrong even when the student has prepared a long question list. The difficulty is usually sequence. If every question is narrow, the client never gets to tell the story; if every question is broad, important dates, documents and contradictions remain unclear.
A better interview moves deliberately from purpose to narrative, then to chronology and focused clarification. Questions should be neutral enough to discover facts rather than manufacture them, while summaries and closing questions help the student check what has been understood.
This guide is for an LL.B student practicing a simulated interview. It is about learning how to gather and organize information respectfully; it is not a substitute for professional client-care rules or supervision in a real matter.
Know what the interview exercise is testing
A mock interview is not a contest to ask the most questions. The student is trying to understand the client's objective, chronology, actors, documents, risks, and missing facts while communicating respectfully. Keep the exercise instructions and any assigned role boundaries in front of you.
Start with the client's purpose
Open with a question that lets the client explain why they came: 'What would you like help with today?' or an equivalent prompt. This identifies the client's own goal before you impose a legal category on the story.
Use open questions to get the first narrative
Invite the client to tell the sequence in their own words. Avoid interrupting every sentence to chase a detail. The first narrative gives you a map; your later questions can fill gaps without destroying the order of events.
Move from broad to focused
After the narrative, narrow the inquiry by topic: dates, people, communications, money, documents, promises, actions, consequences. Focused questions should be driven by something the client said or by a fact needed to test a possible legal issue.
Use one fact per question
Questions containing several facts make it hard to know which part the client answered. Split them. A clean question such as 'When did you receive the notice?' is easier to verify than a compound question about receipt, response, witnesses and motive.
Ask neutral questions before leading ones
A mock interview should not train the student to put a preferred story into the client's mouth. Ask what happened before asking whether a particular interpretation is correct. If you need to test an inconsistency, identify it without accusing the client.
Clarify words that carry legal weight
Clients may use everyday terms such as 'owner,' 'guarantee,' 'fired,' 'agreement,' or 'notice' differently from legal documents. Ask what happened, what was written, who said it, and what document exists instead of treating the label as a verified legal fact.
Build a chronology aloud
Periodically summarize the sequence and ask whether you have it right. A short chronology check catches date errors, missing events, and assumptions. It also shows the client that you are listening rather than merely waiting for the next question.
Ask about documents and other sources
Find out what records may exist: messages, agreements, receipts, notices, orders, photographs, account records, or witnesses. In a classroom simulation, record the source without pretending that you have verified it unless the material is actually provided.
Ask the difficult question respectfully
Important facts can be embarrassing, unfavorable, or inconsistent. Explain why the information matters, ask directly without moral judgment, and give the client space to answer. Avoid dramatic phrasing that turns the interview into cross-examination.
Close by checking what you missed
Before ending, ask whether there is anything important you have not asked about, then summarize the client's goal and the main facts as you understand them. Identify what would need verification next rather than promising an outcome.
Review your questions, not just your confidence
After the simulation, mark each question as open, focused, clarifying, leading, compound, or unnecessary. The goal is to see whether the sequence helped the client provide better information, not whether you sounded polished.
A short mock interview sequence
Use a fictional client who says, 'My landlord threw me out even though I paid.' Start with the goal: 'What would you like to happen now?' Let the client give the story. Then clarify the tenancy, payment, dates, notice, possession, documents and any court or police involvement. Do not ask, 'So the landlord illegally evicted you without notice, correct?' That question contains your legal conclusion. Instead ask what happened, who was present, what was said, and what documents exist. At the close, summarize the timeline and list what would need checking before any advice could be given.
Listen for the answer that changes your next question
Interviewing is not a fixed questionnaire. If the client mentions a written notice, your next useful question may be when it was received and whether a copy exists. If the client says there was a court order, the interview should pivot to identifying and reviewing that order. Good questioning is responsive: each answer either confirms the current path or tells you to change it.
Use summaries as a questioning tool
A short summary can be more useful than another question. Say, in neutral terms, what you understand so far: the relevant dates, the people involved, the document mentioned, and the client's objective. Then ask what is wrong or missing. The client's correction may reveal a major misunderstanding. Summaries also slow the interview enough for both sides to notice gaps. Avoid turning the summary into advocacy. You are checking the facts you heard, not persuading the client to adopt your preferred version.
Apply this section to the exact context you are given. Use open, focused, clarifying and closing questions in a sequence that improves accuracy, rapport and issue identification. The purpose is not to add more material to memorize; it is to make the next attempt easier to check and improve.
Notice what you did not ask
After the simulation, read the notes as if another student had to understand the matter without speaking to the client. Mark every gap that matters to chronology, identity, documents, objective or a possible legal issue. Then write the question you should have asked. This is more useful than judging the interview by how confident it felt. A calm conversation can still miss critical facts, while an imperfect delivery can produce a strong information map.
The funnel interview sheet
Divide one page into GOAL / STORY / TIMELINE / PEOPLE / DOCUMENTS / GAPS / CLOSE. Limit yourself to two prepared questions in each box. During the simulation, add follow-ups only when the client's answer creates a real information gap.
Build one interview around a changing question plan
Begin with only five planned prompts: why the person has come, what happened, when the important events occurred, what documents or other sources may exist and what outcome the person hopes for. The purpose of this short list is to protect the structure without forcing the client into a script prepared by the interviewer.
During the first narrative, mark facts that need a second pass instead of interrupting every time a date or name is unclear. When the client finishes the first account, use the marks to build a chronology. Ask one fact per question and move from neutral clarification toward more focused questions only where the answer makes that necessary.
Use a summary at two points. Midway through, say in your own words what you understand about the sequence and invite correction. Near the end, summarize the main issue, documents and unanswered questions. A summary is not only polite; it is a diagnostic tool. If the client corrects your summary, the correction may be more important than another prewritten question.
Include one deliberately difficult question in the practice. It may concern a missing document, an inconsistency or an action the client appears uncomfortable discussing. Test whether the question can be asked without accusation. A useful form explains why the fact matters and leaves room for the person to correct the assumption.
After the exercise, review the questions that changed the direction of the interview. Which open question produced useful facts? Which narrow question arrived too early? Which answer should have triggered a follow-up that you missed? Revising the question plan from actual answers is more valuable than memorizing a longer list for the next mock interview.
Add a silence rule to the next practice: after an important answer, wait two or three seconds before asking the next question. Students often fill silence with a new question and accidentally cut off information the client was about to add. The pause also gives the interviewer time to decide whether the answer calls for clarification, chronology or a document question.
Test your questions for hidden assumptions. Rewrite 'Why did you ignore the notice?' as a neutral sequence such as 'When did you first see the notice?' followed by 'What did you do after that?' Neutral wording does not mean avoiding difficult facts; it means giving the answer a chance to establish what actually happened before the interviewer labels it.
At the end of the mock interview, ask the client role-player what question felt most helpful and what question felt confusing or judgmental. Then compare that feedback with your own notes. Communication quality is part of the exercise: a legally relevant question is less useful if its wording makes the person misunderstand what is being asked.
Before the next mock interview
The larger goal of practical legal training for students is not to look experienced before you are. It is to develop habits that make future work more accurate, ethical and easier to review. Use the method, seek feedback, and improve one observable part of the process at a time.
Related PLC practical-skills reading
For related context, see practical legal training at PLC and PLC's professional ethics guide. These links are supplementary; the method above should remain understandable without them.

