Dictating Legal Opinions and Advice Letters

State the question, number the issues, and verify every caveat before the letter is sent.

Voiskey Voiskey Team
Legal DictationLegal DraftingDictating Legal Opinions

State the Question and the Assumptions

Dictating Legal Opinions and advice letters begins with a question narrow enough to answer. Write the question in one or two sentences, then write the facts that are assumed, the documents that were reviewed, and the limits of the review. An opinion that answers a broad question with a broad answer is of little use to the client, who usually needs to decide something specific by a date. Separate the question you were asked from the related questions the client will face later, and note that those are outside the scope. A clear question and a clear scope protect both the client and the author, because the reader knows exactly what the letter does and does not decide.

Collect the facts and the documents before drafting. List the agreements, the correspondence, the filings, and the factual accounts that the opinion relies on. Note the date of each document and whether it is a final or a draft. Mark the facts the client has confirmed and the facts that remain unverified. If the opinion depends on a fact that could change, say so in the assumptions rather than burying it in the analysis. An opinion is only as strong as its stated assumptions, and a reader who can see the assumptions can judge how far the conclusion travels when the facts change.

Identify the governing law and the authorities that frame the question. Record the jurisdiction, the statute or regulation, and the leading cases. Note the version of the law in force on the relevant date, because an amendment can change the answer. If the question spans more than one jurisdiction, treat each one separately rather than blending the analysis. Mark the points where the law is unsettled and the points where the courts have taken different views. The legal framework belongs at the top of the outline so the letter can be organized around it rather than around the order in which the facts arrived.

Prepare the working file with the letter's structure. Create the sections: question, short answer, assumptions, facts, analysis, conclusion, and limitations. Place the source documents and the authority list beside the document. Decide who reviews the legal analysis and who reviews the commercial practicality and the tone. Note the client's deadline and the decisions the letter is meant to support. If the letter will go to a board or a counterparty, note the audience and the level of detail it expects. A prepared file with the structure already in place keeps a long opinion coherent from the question to the closing caveat.

Dictate the Analysis in Numbered Issues

Dictate the analysis issue by issue, each with a rule, an application, and a conclusion. State the rule with its source, apply it to the facts with specific references, and state the conclusion in one sentence. Keep the same order for every issue so the reader can follow the reasoning without effort. If an issue depends on another, say so at the start. Number the issues and use the numbers in the conclusion, so the reader can move between the analysis and the summary. A numbered analysis is easier to review, easier to update when the facts change, and easier for the client to quote when the client reports to a board.

Start with the short answer, then explain it. Clients read the first page and often nothing else. Give the conclusion in plain terms, with the confidence level stated honestly, then let the analysis support it. If the answer depends on an assumption, state the assumption in the short answer. If the answer differs by jurisdiction or by scenario, give each result briefly. Do not make the reader reach the end of a long letter to learn the answer. A short answer that is accurate and calibrated is the part of the opinion the client will rely on most, so it deserves the most careful drafting.

Apply the law to the facts with named references. For each element of the rule, name the fact that satisfies or defeats it and the document or account that supports the fact. Where the facts are contested, state both versions and explain which one the opinion assumes. Where the law is uncertain, describe the competing views and say which one the conclusion follows and why. Avoid the temptation to overstate certainty; a client who is told the answer is clear and later discovers a split will lose confidence in the whole letter. A careful application is more useful than a confident assertion.

Dictate the conclusion and the recommendations as separate parts. The conclusion restates the answer to each numbered issue in one sentence. The recommendations state what the client should do next, in order, with the decision the client needs to make and the date by which it should be made. If the recommendation depends on a fact the client must confirm, say so. If the matter requires a filing or a notice, name it. A conclusion without recommendations leaves the client with an answer but no plan, and a plan without a conclusion leaves the client without the reason for it.

Separate Advice From the Record

Keep the advice separate from the factual record. The record is what the documents and the client say. The advice is what the author concludes from the record and the law. When the two are blended, a reader cannot tell which statements are facts, which are the client's positions, and which are the author's recommendations. Use clear signposting: the facts section states what was reviewed, the analysis section states the reasoning, and the recommendations state what to do. This separation also protects the author if the facts later turn out to be incomplete, because the letter shows exactly what the conclusion rested on.

Attribute every factual statement to its source. Where a fact comes from a document, cite the document and the page. Where a fact comes from a client conversation, say so and date it. Where a fact is the author's inference, label it as an inference and show the steps. Do not present an assumption as a confirmed fact. A letter that mixes sources without attribution invites the reader to treat every statement as equally reliable, and when one statement proves wrong, the reader may distrust the rest. Attribution is not pedantry; it is what makes the letter usable months later.

State the limitations of the opinion in the body, not only in a footnote. Explain what was not reviewed, what was assumed, and what would change the conclusion. If the opinion does not address tax, regulatory, or foreign-law questions, say so. If the opinion is based on law as of a date, say so. A limitation that appears only in a final paragraph is easy to miss, and a client who misses it may rely on the letter for a purpose it was never meant to serve. Limitations stated early and repeated in the conclusion are easier to respect and easier to defend.

Keep the tone measured and the language plain. An opinion letter is not an advocacy document, even when the client would prefer a stronger position. State the conclusion with the confidence the analysis supports, and describe the risks without dramatizing them. Replace legal jargon with plain descriptions where the client will read the letter, and keep the technical terms the client will encounter elsewhere. A measured letter is more persuasive to a board, more useful to a counterparty, and more defensible if the matter is later reviewed by another lawyer, an auditor, or a regulator with fresh eyes and no stake in the outcome.

Check Authorities, Limits, and Caveats

Verify every authority before the letter is sent. Confirm the case name, the year, the court, and the pin cite, and confirm that the authority is still good law. For statutes and regulations, confirm the section and the version in force on the relevant date. Do not rely on a summary or a memory. Voiskey helps during this pass: it is an AI voice typing app for macOS and Windows, and you press a shortcut, speak a correction, and the text appears at the insertion point in the letter. It removes filler words, stutters, false starts, and grammar slips, so a spoken correction lands as clean text. Download Voiskey before the citation pass and dictate fixes directly into the draft.

Check the assumptions against the client's instructions. Read each assumption aloud and ask whether the client confirmed it. If an assumption was not confirmed, mark it and decide whether to confirm it or to state it as a condition. An opinion that assumes a fact the client never agreed to is an opinion the client may not be able to rely on. Check that the facts section does not include a fact the assumptions exclude. The two sections should tell the same story, one by listing what was reviewed and the other by listing what was assumed for the purpose of the opinion.

Check the conclusion against the analysis, issue by issue. The conclusion should answer exactly the questions that were asked, in the same order, with the same confidence level. If the analysis found a split or an open question, the conclusion should say so rather than resolving it silently. If the recommendations depend on the conclusion, confirm that the dependency is stated. A conclusion that is stronger than the analysis is the most common defect in opinion letters, and it is the one most likely to be quoted back to the author when the matter later goes wrong in front of the client.

Record the verification and the open items. Keep a log with the date, the reviewer, the authorities checked, the assumptions confirmed, and the questions still open. Note any authority you could not obtain and the plan to obtain it. Note any fact the client still needs to confirm and the date by which it is needed. Voiskey learns names, jargon, acronyms, and spelling preferences, which keeps party names and defined terms consistent across the letter, and it adapts punctuation, formatting, and tone. Download Voiskey when the team issues opinions regularly and wants one style. A logged check makes the letter easier to update when the facts change.

Deliver the Letter and Track Follow-Ups

Deliver the letter with a short covering note that states the question, the answer, and the decisions the client needs to make. Do not send a long opinion without a summary; the client will read the summary first and may not reach the analysis. List the assumptions the client should confirm and the facts that would change the answer. If the letter includes recommendations, put them in order with dates. A short covering note that frames the letter helps the client act on it and gives the client a clear way to respond with the information the opinion still needs.

Walk the client through the letter when the matter is significant. Read the short answer, the assumptions, and the recommendations aloud, and pause for questions. Note the questions the client asks, because they often reveal an assumption the letter did not address. If the client's question is outside the scope, say so and offer to address it separately. Record the date of the conversation and the points discussed. A letter that is discussed in person is far more likely to be understood than one that is simply sent by mail, and the discussion often improves the next version of the opinion.

Track the follow-up items in a short register. List each item, the owner, the date it is due, and the effect on the opinion if it is not resolved. If a fact is confirmed, update the letter or issue a short supplement. If the law changes before the client acts, decide whether the letter needs an update and tell the client. An opinion is a snapshot as of a date, and a client who acts months later needs to know whether the snapshot is still current. A follow-up register keeps the letter connected to the decision it was meant to support.

Review the routine for the next opinion. Note which sections needed the most revision, which assumptions were hardest to confirm, and where the analysis and the conclusion drifted apart. Update the template, the assumption checklist, and the verification log. If a particular client or matter needs a different structure, record it for reuse. Keep a short lessons note with the matter file. Over several opinions, a clear question, a numbered analysis, and a logged verification pass produce letters that are faster to write, easier to review, and much more useful to the client who has to make a difficult decision under time pressure.

FAQ s

Voiskey is an AI voice typing app for the desktop. Press a shortcut, speak an issue or a recommendation, and the text appears at the insertion point in your letter. It removes filler words, stutters, false starts, and grammar slips, so the analysis reads as clean prose. It also adapts tone and formatting, while you still check every authority, assumption, and caveat before the letter is sent.

Yes. Voiskey learns names, jargon, acronyms, and spelling preferences, which helps when an opinion repeats party names, defined terms, and citation forms across many issues. A template and a definitions list still fix the approved forms. The spoken draft reduces retyping, and the reviewer checks each term and citation against the source before the letter is delivered.

Press a shortcut and speak the question, analysis, and conclusion into the letter, and text appears at the insertion point. Voiskey removes filler words, stutters, and false starts and adapts punctuation, formatting, and tone. Polish is the pass where you check authorities, assumptions, and limitations. At up to 220+ words per minute, the routine produces a complete draft for the review and client discussion.

Yes. Voiskey is system-level, so text appears at the insertion point in whatever app or text field holds the letter. You speak sections directly into the letter file and revise them in the same place, with no separate suite to open. The workflow is Speak-Polish-Type-Edit, so agreed changes land in the version the client receives.

Say less. Get more
Say less. Get more
Say less. Get more
Say less. Get more
VoiskeyVoiskey

Your voice, amplified.

Download Voiskey for Mac and Windows and dictate legal opinions from the question to the final caveat.

Use it across macOS, Windows, iOS, and Android

Use it across