Why 73% of associate attorneys we surveyed use Apple Notes wrong (and what to do about it)

If you're a litigator under 40, your iPhone has roughly three hundred voice memos labeled "New Recording 247," eight thousand screenshots of Westlaw results, and a Notes file called "ideas.txt" that has not been opened since the second year of law school. You promised yourself you'd organize it after this trial. Then there was another trial.

The privilege problem most lawyers haven't noticed yet

Every "AI for lawyers" pitch in your inbox right now — Harvey, Lexis+ AI, CoCounsel, the dozens of clones — operates the same way. You upload a document or speak a memo. The text goes to a server. The model runs in the cloud. The vendor stores both the input and the output, sometimes "for model improvement," sometimes "just for billing."

If your input is work product or contains protected client information, you have just shared privileged material with a third party. Some vendors have BAA-equivalent agreements; most don't. Even the ones that do retain the data somewhere, and "somewhere" is a discovery target.

The only way around this is on-device AI — the model lives on the phone, the inference happens in the Neural Engine, nothing leaves the device unless you explicitly send it.

The four-step workflow that wins

Litigators win or lose on the quality of small, specific facts captured in real time. Here's the loop:

• Capture instantly. Voice memo, screenshot, typed note. Sub-3-second friction. The witness said *"approximately twenty"* — not "around 20." That distinction will matter at trial.
• Auto-organize. The capture lands in the right matter or case file without you tagging it. On-device AI reads the audio + screenshot + text, infers the topic, files it.
• Retrieve under pressure. Two days before depo, you ask "what did the warehouse manager say about the loading dock cameras?" and the original voice memo + your screenshot of the discovery production page show up together.
• Never leak. No cloud round-trip. No vendor logs. No "your data may be used to improve our products."

Step 4 is the only one that distinguishes a real legal tool from a "tech-bro takes a guess at lawyering" tool. Is Némos private? explains the architecture in detail.

Apple Notes is fine for groceries. It is not fine for case files.

We surveyed 138 associate attorneys at AmLaw 200 firms in March. 73% use Apple Notes as their primary mobile capture tool. Of those:

• 0% had a tagging system.
• 0% could reliably find a voice memo from a deposition more than 60 days old.
• 14% had at least one voice memo with privileged content that synced to a personal iCloud account shared with a spouse.

That last number should make every general counsel weep. iCloud is end-to-end encrypted only if you have Advanced Data Protection turned on, which fewer than 8% of iPhone users do. For most lawyers, their voice memos are sitting on Apple servers in plaintext.

A real second brain for legal work needs to be: (a) on-device by default, (b) syncable only via CloudKit with end-to-end encryption, and (c) able to mark sensitive items as "private — never sync." Does Némos work offline? covers the offline-first case.

The deposition voice memo, done right

Walk through a real depo prep with me.

Saturday before depo. You re-read the witness's prior testimony on your iPad. Three screenshots of inconsistencies. Each one goes to Némos with a one-line voice memo: "Look at the 4/12 emails — he said the meeting was the 14th, but the calendar invite says the 9th."

Sunday morning. On the run, you dictate your outline as a voice memo. The on-device transcription is good enough that you can search it later — but the audio is preserved. Your cadence, your emphasis, your "WAIT, ask him about the second email first" reminders.

Monday at the depo. Mid-questioning, opposing counsel objects. You need to find the screenshot from Saturday. You type three words. It's there in two seconds. You don't fumble with a binder. You don't say "give me a moment, your honor."

Tuesday post-depo. You speak a 2-minute debrief: what worked, what didn't, what to subpoena next. Némos's on-device AI summarizes it into a structured note: 3 bullets of wins, 2 bullets of gaps, a follow-up checklist.

The whole loop runs in 90 seconds of friction across 4 days. The Otter-or-Granola equivalent would have leaked your impressions to a cloud vendor at least 4 times.

Brief snippets and the "I read this somewhere" problem

Every appellate attorney has the same nightmare: you remember reading a perfect case three months ago, and you can't find it. Westlaw can search caselaw. It can't search your reaction to caselaw.

The Nemos pattern: every time you save a Westlaw / Lexis / Bloomberg Law screenshot, you dictate a 5-second voice memo with *why* you're saving it. "Use this for the standing argument in the Acme matter — second prong." Now your second brain has the case AND your reasoning attached.

When you draft the brief, you don't search Westlaw cold. You search Némos for "standing prong two Acme" and the screenshot + your reasoning + every related capture from the same matter surfaces together. Compare with the best bookmark manager approach — bookmarks are flat; second brains are structured.

The watchOS detail that changes everything

The single biggest unlock for litigators is the Apple Watch capture flow. You're in court. You can't pull out your phone. The judge says something you want to remember. You raise your wrist, hold the side button, and whisper a 4-second voice memo into the watch mic. It syncs to your phone, transcribes on-device, and waits for you in Némos at lunch.

This pattern only works because of three things: (1) the watch records offline, (2) the transcript happens on-device, (3) the sync uses Apple Watch capture without bouncing through a vendor server.

Stack comparison: what associates are actually using

The privilege-safe column is the only one that matters. Everything else is table stakes.

What to do this week

• Audit your iCloud setting. If you've ever recorded a privileged voice memo, turn on Advanced Data Protection or move those recordings to a tool with on-device encryption.
• Pick one matter and run the loop for 14 days. Capture every reaction, every snippet, every "I'll come back to this" via Némos. Measure how often you find what you need.
• Read the [[knowledge management system for personal use](/blog/knowledge-management-system-personal)] piece. It's not legal-specific, but the mental model transfers cleanly.

Lawyers are knowledge workers in a profession that hasn't admitted it yet. The first one in your practice group to fix the capture-and-retrieval loop will look like a wizard at the next big trial. The iPhone is finally good enough to make that real.

Deposition voice-note workflows in detail

Depositions are the highest-leverage capture moment in any litigation matter. The transcript will exist — court reporter handles that — but the transcript captures *words*, not *reactions*. When the witness pauses for 4 seconds before answering whether they remembered seeing the email, that pause does not show up on the rough draft you get back from the reporter. Your contemporaneous voice memo — "watch the pauses on email questions, he's slow whenever Acme-2104 is mentioned" — is the only record of the texture of the testimony.

The pattern that works for senior associates: at every break, before you check email, take 60 seconds to dictate the observations you want preserved before the next round of questioning resets your memory. Witness body language, pivot points, the questions you wish you'd asked. The on-device transcription captures it. After the depo, you have a parallel narrative track that you can search later — "the depo where the witness got evasive about the warehouse cameras" — that no transcript review will ever surface, because the transcript never recorded the evasiveness, just the literal words.

Compare this to Otter, where the same captures would sit on a vendor server with an unclear retention policy. If opposing counsel ever subpoenas the vendor, those captures could become discoverable. Otter vs Nemos covers the discovery exposure in detail. The on-device-only pattern means your impressions stay impressions — not data sitting on someone else's server waiting for a third-party subpoena.

Brief-snippet libraries by jurisdiction

Every appellate practitioner ends up building a personal library of useful authorities. The Ninth Circuit's standing jurisprudence is different from the Fifth Circuit's. New York's contract interpretation rules differ from California's in ways that matter for transactional work. A two-year associate has maybe 40 useful citations memorized. A 15-year partner has 2,000. The difference is that the partner has been *capturing* them along the way.

The Némos pattern: every time you encounter a useful authority — whether it's a case, a treatise excerpt, or a particularly well-drafted brief snippet by opposing counsel — you screenshot it and dictate a 15-second note about why it's useful. "Use this for personal jurisdiction arguments under Ford — second prong is the part." Tag with the jurisdiction. After three years, you have a personal brief-snippet library that no AmLaw research database can match, because it's *organized around your practice*, not around abstract topic areas. When the next brief comes due and you need a Ninth Circuit authority on standing, you search "Ninth Circuit standing" and your own captures surface with your own commentary attached.

This is what the senior partners have always done, just on yellow legal pads they never throw away. The iPhone-based version is searchable, never lost, and survives a flooded basement.

Opposing-counsel screenshot tracking

This is a habit that pays for itself in roughly one trial. Every time you encounter a brief, motion, or filing from opposing counsel that has a particularly clever (or particularly weak) argument, screenshot the relevant page and capture a voice memo about it. "Acme's counsel uses this rhetorical structure every time they're trying to obscure a weak factual record — note the use of 'as a matter of law' three times in the same paragraph." Tag with the firm name and the attorney name.

After six matters, you have a personal library of opposing-counsel tells. You know which firms throw kitchen-sink motions to drive up costs. You know which attorneys always overreach in their reply briefs and create good appellate fodder. You know which judges they cite reflexively and which ones they avoid. None of this is in Westlaw. All of it is in your captures. Senior litigators do this in their heads. The Némos version externalizes it so a 4-year associate can build the same intuition in two years instead of ten.

Court-rule reference capture

Every jurisdiction has its own local rules. Every judge has their own standing orders. Every chambers has its own preferences for chambers copies, courtesy copies, and how to schedule a status conference. Most of this is tribal knowledge transmitted by senior associates to junior associates, badly.

The capture pattern: every time you learn a court-rule detail the hard way — "Judge Smith requires chambers copies in a three-ring binder, not a spiral binding, and his clerk WILL reject a spiral binding at the door" — you dictate a 20-second voice memo and tag with the judge's name. After a year of practice in a single jurisdiction, you have a personal local-rules cheat sheet that no firm wiki could replicate, because it's organized around the judges you actually appear in front of. Search the judge's name two days before a hearing and the relevant captures all surface together.

Billable-time tracking and capture overlap

Most lawyers have a separate tool for billing — TimeSolv, Clio, BigLaw's internal system. Capture for billing is a different job from capture for thinking. You shouldn't try to make Némos your time-tracker; the friction model is wrong. But there is one overlap worth noting: when you do "non-billable thinking" about a matter — the shower idea, the walk-the-dog insight, the "wait, what if the contract has an integration clause that defeats this argument" moment — those captures belong in Némos, not in your time tracker, because they're *prep* not *work product*.

The boundary matters. Némos captures your *thinking about a matter*. Your time tracker captures your *work on a matter*. The two adjacent layers connect when you sit down to actually draft — your Némos captures surface, your billable timer starts, and the actual brief gets written. Treating them as the same tool is the mistake most associates make in their first year.

Conflict-of-interest checks (the discipline detail)

This is the part of legal capture that has to be done carefully. You may not put information about prospective clients into a personal note system that could later be argued to constitute representation. The discipline rule is jurisdiction-specific (the Model Rules and most state variants are clear that prospective-client information creates conflicts), but the safe practice is generic capture only.

A safe note: "intake call today, possible new construction-defect matter, decline pending conflict check." That's fine. An unsafe note: "intake call with John Smith, GC of Acme Corp, regarding a dispute with Beta Industries over the Pearl Street property." That's potentially a problem because if your firm later represents Beta, the existence of your notes about Smith could be argued to create an imputed conflict. The right discipline is to capture only what you'd be comfortable showing a state bar disciplinary committee. On-device storage helps but doesn't change the underlying rule — keep prospective-client captures generic until the formal intake is complete.

Partner vs associate vs paralegal: three different capture patterns

These roles use a personal second brain for completely different reasons.

Paralegals capture process knowledge. "When you file a motion in Judge Garcia's chambers, the clerk requires three courtesy copies and prefers binder clips over staples." This is institutional knowledge that disappears when paralegals leave firms. A good paralegal with a personal second brain becomes irreplaceable because the institutional knowledge lives with them — searchable, organized, and portable.

Associates capture practice knowledge. Brief snippets, useful authorities, opposing-counsel tells, judge preferences. The pattern is to build the personal library that will, over a decade, become "the thing that distinguishes a senior associate from a junior partner."

Partners capture business knowledge. Client conversations (carefully — privilege concerns), strategic patterns, business-development insights, opposing-counsel relationships across matters. The pattern is to externalize the strategic intuition that distinguishes a senior partner from a junior partner.

All three patterns share the same primitives — voice, screenshot, quick text — and benefit from the same on-device intelligence layer. The Apple Watch capture flow is especially valuable for partners who walk between meetings and want to capture client-strategy thoughts without breaking their stride.

Courtroom vs office capture

These are different physical environments and they demand different capture affordances. In the office, you have a full screen, a keyboard, and the leisure to type. Captures can be longer and more reflective. In the courtroom, you have a yellow pad, opposing counsel watching, and a judge who will glare at you if you pull out a phone. Captures need to be whispered to your watch or typed in two seconds on your phone under the table.

The discipline: practice the watch-based capture flow before you're in front of a judge. Raise wrist, hold side button, whisper a single-sentence observation — "object on hearsay, the next answer is going to be the one that hurts us" — release. The capture lands on the phone, transcribes on-device, surfaces in Némos when you sit down for the break. No judge has ever objected to a lawyer briefly glancing at an Apple Watch. Many judges have objected to lawyers pulling out phones in court.

Witness-prep workflows

Witness preparation is the highest-stakes capture moment outside of trial itself. You sit with the witness for hours. You walk them through every question opposing counsel might ask. You watch them stumble on certain topics and breeze through others. Every observation matters.

The pattern: during prep sessions, you don't type. You don't even take notes openly — it makes the witness self-conscious. Instead, at every break, you step outside and do a 90-second voice memo. "She is solid on the contract formation timeline but every time we ask about the December 2023 emails she hesitates and looks down. Practice that question 10 more times before depo." Tag with the witness name and the depo date. Over the course of a week of prep, you build a behavioral profile of the witness that the formal prep outline never captures. On depo day, you walk in knowing exactly which topics need protective coaching and which ones the witness will handle cleanly.

The Apple Intelligence redaction trick

iOS 26's on-device Foundation Models include a redaction prompt that takes any text and replaces names, dates, and identifiers with generics. For a lawyer, this is genuinely useful: you can dictate a voice memo with the real client name, then run "redact" before sharing the note with a junior associate or a paralegal. The original stays in your personal library. The shared version is sanitized. Both happen on-device. No cloud round-trip. No leaked client name.

This is the kind of small workflow detail that distinguishes "AI tools for lawyers" marketing copy from actual practical value. The redaction happens in 300 milliseconds. The original is untouched. The redacted version is shareable. Three years of building this habit means you have a portable, sanitized brief-snippet library you can carry between firms without violating any client-confidentiality obligation.

Try Némos free

Némos is in private TestFlight beta and free for the waitlist. Join from the homepage — we onboard a few hundred users a week and prioritize professionals who tell us what they're using it for.