Dictation can produce a first draft of a client email, but the lawyer must approve the meaning and recipient before sending it. A fluent rewrite can turn “we have not agreed” into “we agreed,” remove a condition, or make a tentative view sound like a commitment. Open the correct matter and draft field, use the firm's approved formatting path, then read the final email against your instructions and source documents. Do not send straight from the first transcription.
For lawyers using a generative AI formatter, the ABA's Formal Opinion 512 discusses competence, confidentiality, communication, and the need to review output under applicable professional duties. The ABA's Formal Opinion 477R summary discusses reasonable efforts to protect client information in electronic communication and circumstances requiring stronger precautions. These opinions are guidance about lawyer conduct, not approval of SuprFlow or a universal rule for every jurisdiction. Check the firm's client agreement and local rules.
Practice with a fictional instruction
Use a test matter, not a real client's email address. Imagine an internal instruction that says: “Tell Casey that we received the proposed extension. We have not agreed to it. We can discuss it after reviewing clause seven with the partner. Do not promise a completion date.” Dictate a draft into a local note or a test message:
Dear Casey, we received the proposed extension. We have not agreed to it. I will review clause seven with the partner before we discuss a response. I cannot confirm a completion date yet. I will follow up after that review.
Now compare the dictated result with the instruction, phrase by phrase. Did “not agreed” survive? Is review of clause seven still a precondition rather than an accomplished step? Did the draft avoid promising a date? Does “I will follow up” accurately describe the assigned action? If any answer is uncertain, edit the email manually and seek the normal matter review. Never infer that grammatical polish preserved the legal position.
Before you dictate into a real matter
- Choose the approved destination. Open the correct client and matter in the firm's email or practice-management system. Check which compose field has focus; ordinary SuprFlow insertion briefly uses the Mac clipboard and pastes into the focused app. A focus change can put text in the wrong draft.
- Choose the approved data path. SuprFlow performs speech recognition locally and defaults to local cleanup. Cloud API formatting sends transcript text and instructions to a selected provider or custom endpoint. Ollama can be local or remote depending on its configured endpoint. A firm must decide what is permitted for this client's information before the dictation begins.
- Check local copies. The app retains recent raw, cleaned, and formatted transcriptions on the Mac. Its optional clipboard-history feature is separate from the brief system clipboard paste; third-party clipboard tools and device backups may retain more. Follow the firm's retention and device rules.
- Dictate a draft, then stop. Say short, complete sentences. Separate the fact, the current legal view, any condition, and the next action. Do not ask a formatter to infer missing advice or deadlines.
- Review the material words and attachments. Compare the output with instructions, source documents, and any partner review. Read negations, qualifications, names, dates, clause numbers, figures, deadlines, and who owns each action. Check attachment filenames and versions separately; dictation does not attach or validate them.
- Verify recipients immediately before Send. Check To, Cc, Bcc, domain, and whether the thread includes unintended parties. Apply the firm's confidential-email or secure-portal procedure when required. Save or file the final communication under the matter's record rules.
This workflow is deliberately different from dictating an attendance note. A note records a reviewed account for the matter file; a client email communicates outward and adds recipient, transmission, and commitment risks. A local speech model addresses only one part of either workflow.
A final thirty-second read
Read the email from the client's point of view. Highlight every sentence that could be understood as advice, an agreement, a deadline, or an instruction. Confirm its basis and intended strength. Then compare the recipient list with the matter record and inspect the attachments. If the email includes privileged or highly sensitive content, use whatever transmission method the firm and client have approved. The required review may be longer than thirty seconds; the point is to perform an explicit final pass, not to rush it.
Questions people ask
Does on-device transcription make a dictated client email confidential?
It keeps the speech-recognition step on the Mac in the current SuprFlow release. Optional hosted formatting, local history, clipboard tools, the destination email system, recipients, and backups still need review. Trace the data path for the actual configuration.
Can I use an AI formatter to make the email more professional?
Only if the firm permits that provider and this data class. Review every material change before sending. Tone improvement does not authorize a change to advice, conditions, or facts.
Should I paste directly into the real email composer?
That depends on firm workflow. A controlled draft outside the Send-ready composer can make review easier. If you dictate into the composer, verify focus, recipient, thread, content, attachments, and any required second review before sending.
Related guides
- Offline dictation for lawyers
- Dictate a client-call attendance note
- Choose local or cloud formatting
- Where does my dictation go?
- Does SuprFlow use the clipboard?