Set objectives, gather deciding facts, and rehearse voice notes before the hearing.

Voice Notes for Court preparation begin with a clear statement of what the hearing must achieve. Name the hearing type, the issues the bench will decide, and the outcome you are asking for. Write the objective in one sentence and place it at the top of the notes file. Then list the three points that must be understood even if everything else is forgotten. A hearing is short, and a set of notes organized around a single objective is easier to rehearse than a folder of observations. If the matter has several issues, split the notes into sections and give each section its own objective. This first-minute discipline saves hours of unfocused preparation later in the week.
List the questions the bench is likely to ask and your shortest honest answer to each. Start with jurisdiction, service, and any procedural condition, because these are the questions that can stop a hearing before the merits. Then move to the issues in dispute and the facts that decide them. For each question, record the answer, the source, and the page where the source appears. Do not write answers you cannot support from the record. If an answer depends on a document that may not be admitted, note the fallback position. A prepared question list turns nervous energy into a structured rehearsal and prevents long pauses at the lectern.
Decide what not to say. Most hearing preparation notes grow because the drafter includes every fact in the file. Set a rule: an item belongs in the notes only if it supports an element, answers a likely question, or rebuts an anticipated objection. Everything else stays in the file for reference. This rule keeps the notes short enough to read in the minutes before the hearing. It also prevents the common problem of a speaker who has too much material and no clear sequence. Write the rule at the top of the file and apply it as you dictate, so the notes stay usable under time pressure.
Prepare the working file in the app you use for case notes. Add a heading with the case name, the hearing date, the courtroom or remote link, and the names of the people attending. Keep the exhibit list, the witness list, and the key authorities beside the notes. Decide who will review the notes and when. Note the time available for argument and any limit on the number of authorities or exhibits. If a colleague will attend, agree on signals for time and for documents. A prepared file with the logistics at the top lets the notes serve the hearing rather than distract from it.
Build a fact spine before you dictate argument. The fact spine is a short ordered list of the events that decide each issue, each with a date and a source. Keep it to the events a judge must understand, not every event in the file. For each entry, note the exhibit or statement that supports it. If two sources conflict, mark the conflict and your position. Read the spine aloud and check that the story makes sense in order. A fact spine that survives a read-through becomes the backbone of both the notes and the oral presentation, and it keeps the speaker away from facts that do not matter.
Prepare the exhibit and witness tables in the same file. For exhibits, record the number, the description, the date, and the point it proves. For witnesses, record the name, the role, the topics they address, and the exhibits they authenticate or explain. Mark the exhibits that must be admitted for an element and the witnesses whose availability is uncertain. If an exhibit may be challenged, write the basis for admission and the response. These tables are the part of the notes you will consult most often during the hearing, so keep them short and make the numbering match the court's records exactly.
Record the procedural history in a compact block. List the filings, the orders, and the deadlines that led to the hearing, with dates. Note any condition the court has already decided, so you do not reargue a settled point. Note the relief already granted or denied, and the language the order used. If a prior order limits the issues, quote the limiting language. A procedural block prevents two common errors: repeating an argument the court has rejected and missing a condition the court expects you to address. Keep it to one screen so it can be scanned in the minutes before the hearing begins.
Identify the opposition's strongest points and write your response to each. Do not write a response to every argument; focus on the three that could change the result. For each, state the point in its strongest form, then your answer, then the source. If the answer depends on a fact you cannot prove, say so and describe the fallback. This exercise is uncomfortable, and that is why it improves preparation. A speaker who has already said the hardest question aloud is calmer when the bench asks it, and the notes give a direct route to the answer instead of a search through the file.
Dictate the argument in short runs rather than one continuous speech. A run is one point: the claim, the supporting fact, the authority, and the requested conclusion. Speak one run, stop, and check that it stands alone. Then dictate the next. This shape matches the way a judge listens and the way the notes will be read. Keep each run to a few sentences and use the same order every time, so the structure is predictable. When you rehearse, you can drop a run without breaking the rest. Use transitions that name the next point, such as turning to the second element.
Speak in complete sentences and avoid reading a script aloud. A script produces a flat delivery and a stiff note. Instead, dictate the run as you would say it to the bench, then edit the text into note form with short phrases and line breaks. Keep the verbs active and the subjects concrete. If a sentence needs a comma splice to survive, it is probably two points and should be split in two. Read the run aloud again after editing; if it stumbles, the note is wrong, not the speaker. Notes that survive a spoken read are the notes you can trust at the lectern.
Handle authorities as you dictate. Say the case name, the year, the proposition, and the pin cite, then mark the proposition in your own words. Do not paraphrase inside a quotation. If you are unsure of a citation, leave a placeholder and mark it for checking rather than guessing. Keep the number of authorities for each run small; a run with five cases is a sign that the point is not yet clear. Place the full citation in a reference list at the end of the file and use a short form in the spoken run. This separation keeps the spoken notes readable and the citations easy to verify.
Dictate the closing request as its own run. State the order you want, the terms you want in it, and the reason the record supports it. If the court has discretion, name the factors and tie each to a fact. If the request has alternatives, state the preferred order and the fallback. Read the closing run last in every rehearsal, because it is the part most likely to be rushed. A clear, specific request is easier for a judge to grant than a general appeal for relief, and the run gives you the exact words when the hearing reaches its end.
Rehearsal is where notes become a performance. Read the notes aloud in real time and mark every place where you slow down, look away, or lose the thread. Then edit that passage. Voiskey supports this loop: it is an AI voice typing app for the desktop, and you press a shortcut, speak a revised run, and the text appears at the insertion point in the notes file. It removes filler words, stutters, false starts, and self-corrections, so a rehearsal comment becomes a clean instruction. Download Voiskey before the rehearsal week and dictate revisions directly into the notes you will carry into the hearing room.
Time the rehearsal against the slot you have been given. If the notes run long, cut a run rather than speaking faster. Mark the runs that can be dropped without losing the request. If the hearing includes questions, rehearse the answers separately and keep them short and specific. Record the rehearsal, listen once, and note where the argument lacked a source or a clear transition. Do not rehearse in front of a mirror only; speak toward a listener who can stop you and ask a question, because that is the condition the hearing will create. A timed rehearsal with interruptions is worth several silent readings.
Edit the notes into a form you can scan at a glance. Use short headings, numbered runs, and bold labels for facts, authorities, and requests. Keep the full sentences in the rehearsal version and the fragments in the lectern version, but make sure the fragments still make sense when read at speed. Put the exhibit numbers next to the facts that use them. Put the page numbers next to the quotes. A lectern version that requires turning three pages to find an exhibit number will cost time you do not have. One page per issue is a useful limit for the packet.
Check the notes against the record one more time after editing. Confirm that every fact in the notes has a source, every authority is cited fully correctly, and every exhibit number matches the court's own list exactly. Remove any note that cannot be supported. If a correction changes the argument, update the request as well. Save a clean version labelled with the hearing date. Voiskey learns names, jargon, acronyms, and spelling preferences, which helps keep case-specific terms consistent across rehearsal drafts, and it adapts punctuation and formatting to notes. Download Voiskey when the team wants a repeatable rehearsal routine.
Assemble the packet the night before. Include the lectern notes, the fact spine, the exhibit and witness tables, the key authorities, and a one-page summary of the request. Add the logistics: the time, the courtroom or remote link, the names of the people attending, and the contact for any last-minute change. Put the most important page on top. A packet that is assembled in the morning is a packet with a missing page. Keep a spare copy in a second location and confirm that the version matches the one your colleague holds. The packet should let you walk in with the notes in hand and nothing left to print.
Write a five-line opening you can say without notes. The opening should name the matter, the issue, the request, and the first fact that supports it. Rehearse it until it is automatic and can be delivered at a steady pace. A confident opening buys attention for the rest of the argument and covers the moment when nerves are highest. Keep the rest of the notes for the substance. After the opening, move to the first run and follow exactly the order you rehearsed. If the bench interrupts, answer the question, then return to the run you were on by naming it. The packet and the opening together make the first two minutes predictable.
Prepare for questions that arrive early. Some judges ask about the remedy before hearing the facts, and some ask about jurisdiction before anything else at all. Keep a short answer card for each of these questions at the front of the packet. Each card should have the question, a brief answer in two sentences, and the source with its page. When a question arrives, give the short answer first and the detail only if asked. A speaker who answers briefly and accurately earns time to develop the argument. A speaker who answers at length loses the thread and the room.
After the hearing, dictate a debrief while the detail is fresh. Record what the bench asked, what it seemed to accept, what it questioned, and what you would change in the notes. Note the ruling and any date the court set for the next step. Save the debrief with the packet so the next hearing in the matter starts from experience rather than memory. Update the fact spine and the question list for the next stage. Over several hearings, a consistent packet, a rehearsed opening, and a written debrief turn preparation into a repeatable process that improves with each appearance.
Voiskey is an AI voice typing app for the desktop. Press a shortcut, speak a run of argument or a question answer, and the text appears at the insertion point in your notes file. It removes filler words, stutters, false starts, and grammar slips, so rehearsal comments become clean notes. You still verify every fact, authority, and exhibit number against the record before the hearing.
Yes. Voiskey learns names, jargon, acronyms, and spelling preferences, which helps when hearing notes repeat a case name, a defined term, or an exhibit label across many revisions. A fact spine and exhibit table still fix the accepted forms, and the drafter reads each one against the record. The spoken draft reduces repeated typing while the tables keep the spellings stable.
Press a shortcut and speak a run of argument into the notes file, and text appears at the insertion point. Voiskey removes filler words, stutters, and false starts and adapts punctuation and formatting to the notes. Polish is the pass where you check sources, trim runs, and time the rehearsal. At up to 220+ words per minute, the routine leaves more room for the spoken practice that actually prepares a speaker.
Yes. Voiskey is system-level, so text appears at the insertion point in whatever app or text field holds the notes. You speak revisions directly into the lectern draft and restate a run in the same place, with no separate suite to open. The workflow is Speak-Polish-Type-Edit, so the notes you rehearse are the notes you carry into the hearing.

Download Voiskey for Mac and Windows and turn hearing preparation into rehearsed, verifiable voice notes.
Use it across macOS, Windows, iOS, and Android