Preparing Questions for a Client Conference

Left to run on its own, a client conference becomes a story. The client narrates, sympathetically and at length, and everyone leaves feeling the matter was discussed, yet the three facts you actually needed to pin down are still open and the client has gone home. Preparation is what stops a conference from being a conversation and makes it a working session. The tool is a set of questions, written in advance, where each one exists to settle something specific.

Tie every question to a decision it will inform

Before the meeting, list the decisions the matter faces in the near term: whether to file, what relief to seek, how to answer an allegation, whether a settlement is worth exploring. Then write questions backwards from those decisions, so each question earns its place. If you cannot say what a question will help you decide, it is curiosity, not preparation, and it can wait.

Know what would prove each answer

An answer you cannot corroborate is a lead, not a fact. For each question, note in advance the document that could confirm what the client tells you:

• The agreement, receipt, or message that supports the account
• The date or record that fixes a timeline
• The correspondence that shows what was said and when

Asking "is there anything in writing" in the moment is good; knowing beforehand exactly which writing you are hoping exists is better, because it turns a vague request into a specific one the client can actually fulfil.

Word disputed matters neutrally

When a fact is contested or unflattering, the phrasing of the question shapes the answer. A leading question invites the client to agree with your theory rather than tell you what happened, and a client who senses the answer you want will often supply it. Ask disputed matters in neutral terms, invite the client's own account first, and resist finishing their sentences. You are testing the case, not rehearsing it.

Keep the client's account apart from your interpretation

As you take notes, hold two things separate: what the client actually said, and what you make of it. The client's words are evidence you may have to stand behind; your reading of them is working theory that can change. Blurring the two produces a note that looks like fact but is really argument, and that note will mislead whoever relies on it later. Record the account plainly, then record your view of it as your view.

Assign ownership for every promised document

A conference typically ends with the client agreeing to send things: a copy of an agreement, a bank statement, a screenshot. These promises evaporate unless someone owns them. Before the meeting closes, list what was promised, who will provide it, and by when, and make sure the client knows precisely what is expected. A promised document with no owner and no date is a document you will be chasing the week before the hearing.

Leave the conference with a settled record

Close the meeting by confirming the answers you obtained, the documents still outstanding, and the next steps on each side. The record that comes out of a well-run conference should show what was asked, what the client said, what remains to be proved, and who is doing what next. Keeping that record and its follow-up items attached to the matter, rather than loose in a notepad, is the kind of organisation Juniorlawyer is built to support so nothing agreed in the room is lost afterwards.

Prepared this way, a conference stops drifting. Every question points at a decision, every answer has a way of being proved, disputed matters are asked cleanly, and the meeting ends with a clear record and owned follow-ups. The client still tells their story; you simply make sure it answers the questions the case actually needs.