BigHand Dictation Review for Lawyers
BigHand is one of the last remaining full-stack dictation and work-allocation platforms built specifically for law firms. If you have ever worked at an AmLaw 200 shop or a large UK/Commonwealth firm, you have almost certainly touched it — usually through a handheld Philips SpeechMike, a mobile app, or a workflow inbox that routes tasks to a secretarial pool. This review is aimed at partners and operations leads evaluating BigHand against newer speech-to-text options, and at solos wondering whether the enterprise tier is worth the friction.
What BigHand Actually Does
BigHand is not a single product. It is a suite. The relevant pieces for a dictation evaluation are BigHand Professional (digital dictation, workflow routing, and speech-to-text) and BigHand SmartNote (a newer AI-assisted note and dictation product). The traditional pitch: a lawyer dictates on a SpeechMike, iPhone, or Android device; the audio lands in a queue; a secretary or word-processing team picks it up, or the system transcribes it automatically; the resulting document is routed through DMS integration (iManage, NetDocuments, SharePoint).
What BigHand does genuinely well is the workflow layer. Assigning a dictation to a specific typist, tracking turnaround, load-balancing across a support pool, and reporting on who is producing what — that is where it earns its keep at firms with 50+ fee-earners. As a pure speech-to-text engine, its transcription quality is competitive but not category-leading; the reason to buy BigHand is not the ASR accuracy, it is the surrounding plumbing.
The mobile apps are functional and support the standard dictation controls (insert, overwrite, append), and the platform integrates with hardware from Philips and Grundig. Firms already invested in SpeechMike hardware will find BigHand the path of least resistance.
The Confidentiality Lens
This is the section that matters most for a legal audience, and it is the section BigHand's marketing pages talk about the least clearly. The honest answer is: it depends on which BigHand product and which deployment you choose.
Historically BigHand offered on-premises deployments where audio and transcripts stayed on firm-controlled servers. Today the strategic direction, per BigHand's own materials, is cloud-hosted delivery on Microsoft Azure. That means for most new deployments, dictation audio and generated transcripts travel to and are stored in Azure regions selected by BigHand, under BigHand's tenancy. Firms should ask specifically:
- Which Azure region hosts our tenant, and can we pin it (US, EU, UK, AU)?
- Is speech-to-text performed by BigHand's own models, by Microsoft Azure Speech Services, or by a third-party ASR vendor? Each answer creates a different set of sub-processors.
- What is the retention default for audio files and transcripts, and can we shorten it?
- Is any audio or transcript used to train models — BigHand's, Microsoft's, or anyone else's? Get this in writing.
- Will BigHand sign a DPA, and if you are a US healthcare-adjacent practice, a BAA?
BigHand publishes a legal and trust page and holds ISO 27001 certification, which is table stakes for enterprise legal software but not a substitute for reading the actual data processing terms. The subpoena question is the one lawyers routinely forget to ask: if a court served BigHand directly with a subpoena for your firm's dictation audio, what could they produce? For any cloud-hosted SaaS, the answer is: whatever is in their tenant during the retention window. The mitigation is short retention, customer-managed encryption keys where offered, and — for the most sensitive matters — considering whether that dictation should exist as a cloud audio file at all.
For the AI-assisted SmartNote product specifically, ask whether prompts and audio are processed by an in-tenant Azure OpenAI deployment (better) or routed to a shared model endpoint (worse). This distinction has become the single most important architectural question in legal AI procurement in 2025.
Disclosure: Basil, which publishes this review library, competes with BigHand in the meeting-notetaker category. BigHand's SmartNote and Basil overlap on the AI-summary use case, though our architecture is different — Basil runs on-device, which we explain on Basil for Law. For the traditional dictation-to-document workflow that BigHand Professional dominates, there is no direct Basil equivalent.
Ethics-Opinion Fit (ABA 512)
ABA Formal Opinion 512 (July 2024) set out the framework that now governs how US lawyers should evaluate any generative or AI-enabled tool: understand the technology, protect confidential information under Model Rule 1.6, get informed client consent where appropriate, and supervise the output. NYC Bar Formal Opinion 2025-6 built on this. BigHand can be deployed in a way that fits comfortably inside Opinion 512, but the burden is on the buyer, not the vendor, to verify.
The three questions Opinion 512 effectively forces you to answer for BigHand:
- Where does the data go, and who is a sub-processor? Get the current sub-processor list in writing and check it against your engagement letter disclosures.
- Is client data used for training? For pure digital dictation, this has historically not been an issue with BigHand. For AI features, insist on a contractual no-training term.
- Can you supervise the output? Dictation transcripts, especially AI-generated ones, contain errors. Opinion 512's supervision requirement means a human — the dictating lawyer or a trained secretary — needs to review before the document leaves the firm.
A separate consideration: the emerging caselaw on AI and privilege. In US v. Heppner (S.D.N.Y. Feb 2026), Judge Rakoff held that a litigant's chats with a public AI platform were not privileged. That decision does not directly implicate a firm-tenant SaaS like BigHand — the relationship is different — but it should focus the mind on any tool where content leaves your control. And Brewer v. Otter.ai (2025) is a reminder that class-action risk around recording and transcription is real. BigHand's dictation model, where the lawyer is the sole speaker and there is no covert third-party capture, sidesteps most of that risk cleanly. Its meeting-transcription features do not.
Workflow and Integrations
BigHand's real moat is integration. It ties into iManage and NetDocuments so completed documents land in the right matter workspace. It supports Active Directory / Entra ID for SSO. Its workflow reporting gives practice-group leaders visibility into secretarial capacity and turnaround times — data that is genuinely hard to replicate with a stack of point tools.
For firms still running a shared support model, this is where BigHand pays for itself. For firms that have moved to a self-service model where partners type their own documents in Word with Copilot, a lot of BigHand's value proposition falls away, and cheaper dictation-only tools become defensible.
Pricing and Who It's For
BigHand does not publish per-seat pricing. Expect an enterprise sales process, a multi-year contract, and a pricing model that combines named-user licenses with implementation and professional-services fees. The vendor's contact page is the starting point; there is no self-service tier.
Who should buy BigHand:
- Mid-size and large firms with an existing digital-dictation culture and a support pool that routes work.
- Firms already on iManage or NetDocuments that want tight DMS integration.
- Practice groups (litigation, real estate, private client) where dictation volume is high and consistent.
Who should not:
- Solos and small firms — the license floor and implementation overhead do not pencil out. Look at Philips SpeechLive or a lighter tool.
- Firms whose lawyers already type or use Word dictation and Copilot successfully.
- Firms that need meeting-transcription as the primary use case rather than one-way dictation — this is a different product category, and BigHand's SmartNote is newer than the incumbents.
Verdict
BigHand is a well-built enterprise platform that reflects two decades of learning the specific rhythms of law-firm document production. It is not exciting, and it is not cheap, and it is not the right tool for a five-lawyer boutique. It is the right tool for a firm whose competitive advantage still runs partly through a support floor and whose partners still hit the record button on a SpeechMike between meetings.
| Pros | Cons |
|---|---|
| Deep DMS integration (iManage, NetDocuments) | Enterprise-only pricing and procurement |
| Mature workflow routing and reporting | Cloud-hosted default requires careful DPA review |
| Broad hardware support (SpeechMike, mobile) | ASR accuracy is competitive but not best-in-class |
| ISO 27001 and enterprise security posture | Overkill for solos and small firms |
| Firm-tenant architecture avoids public-AI privilege pitfalls | AI features (SmartNote) require separate diligence |
For firms adopting BigHand alongside a meeting-capture tool, an on-device option like Basil keeps the two workflows architecturally separate — dictation to the DMS, meetings to the lawyer's laptop.
This review is for information only and is not legal advice.
Frequently asked questions
Is BigHand a cloud service or on-premises?
BigHand's current strategic direction is cloud-hosted delivery on Microsoft Azure, though on-premises and hybrid deployments have historically been available. Buyers should confirm the deployment model, hosting region, and sub-processor list in the DPA before signing.
Does BigHand use my dictation audio to train AI models?
For traditional digital dictation, this has not historically been a concern. For AI-enabled features like SmartNote, you should get an explicit no-training contractual term from BigHand covering both their own models and any third-party model providers used as sub-processors.
How does BigHand compare to Philips SpeechLive for a small firm?
Philips SpeechLive is typically the better fit for solos and small firms because it offers per-user subscription pricing without the enterprise implementation overhead. BigHand's value shows up at scale, where workflow routing and reporting justify the cost.
Does using BigHand satisfy ABA Formal Opinion 512?
No tool satisfies Opinion 512 on its own. The opinion requires the lawyer to understand the technology, protect confidential information, obtain informed consent where appropriate, and supervise output. BigHand can be deployed consistently with Opinion 512, but the diligence obligation stays with the firm.
Could a subpoena served on BigHand reach my client's dictation?
For any cloud-hosted SaaS, a subpoena served on the vendor could reach whatever data sits in the vendor's tenant during the retention window. Mitigations include shortening retention, pinning hosting region, and asking BigHand about customer-managed encryption key options.
Is BigHand's transcription accurate enough for court filings?
BigHand's ASR is competitive with other enterprise dictation tools but no automated transcription is accurate enough to file without human review. Under Opinion 512's supervision requirement, a lawyer or trained secretary should review every transcript before the resulting document leaves the firm.
Meeting notes with no server to subpoena
Basil transcribes and summarizes entirely on-device — privilege-safe by architecture. See Basil for Law →
This review is for information only and is not legal advice.