Notice before the bot joins, retention set where legal can see it, and every summary held for the named owner who signs the record of what the room decided.
A call is joined, and the notice is played into the audio before a word is captured.
02
A notice is played, and RCW 9.73.030(3) puts that announcement inside the recording itself.
Reason
03
A bot tile shows, and Illinois and Massachusetts turn on concealment, not on consent.
04
A vendor retains audio to train on, and In re Otter.AI puts it outside the party exception.
05
A timer runs on a summary under hold, and FRCP 37(e)(2) turns on intent to deprive.
Decide
06
A summary reaches a regulated firm, and 17 CFR 240.17a-4(b)(4) covers inter-office memoranda.
07
A works council is asked, and BetrVG s 87(1) Nr. 6 gives it a veto, not a notice period.
Out
08
A room decided nothing, and that is recorded as no decision rather than resolved into one.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
Capture, notice and drafting belong to the agent. The record belongs to a named owner, and a wrong summary is amended on its face, never overwritten.
Example workflow
One meeting, notice to confirmation
AgentHuman
1Invitation receivedCalendar invitations, conferencing hooks, dial-ins or a direct request to attend
2Notice played and capture openedThe spoken announcement inside the audio, the attendees, the territories and the meeting class
3Transcript and summary draftedThe summary, the utterances under it, the speakers named and confidence
4Controls appliedNotice checks, territory checks, retention and hold checks and drafting confidence
No human action required
Stages 1 to 4 run unaided, and nothing is filed at any of them — the agent is drafting, and the owner lane opens at the confirmation gate.
5DecisionSplits at the confirmation gate
Routine internal meeting
Goes to the named owner to confirm.
Anything privileged or regulated
Adds a counsel read first.
Owner review
The summary is held with its notice, its transcript and the process record FRE 901(b)(9) calls for.
Confirm · Amend · Send to counsel review
Confirmed — by the named owner▼
6Workspace and archive records updatedOnly where write access and records policy allow it
7Outcome evaluatedNotice coverage, attribution accuracy, owner amendments and what review found
Amendments
Any amendment the owner makes is logged in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Confirming a summary as the record of a meeting.
Joining a call covered by legal privilege.
Setting the retention term for a summary.
Deciding that a room reached a decision.
Automation boundaryAgent acts unaided
✓Play the notice into the audio before capture opens.
✓Record the retention class and hold state that governs each summary.
✓Mark what the room left open rather than resolving it into a decision.
✓Hold the summary for the named owner who confirms it.
Nothing becomes the record except by a named owner, inside the agreed boundaries.
Judging whether a meeting may be recorded at all.
Feeding a summary into a performance review.
Suspending a retention timer under a legal hold.
Changes to notice, retention or attribution rules.
Example output
One meeting summary, annotated
No court has held a notetaker is a party, and In re Otter.AI is a district-level plausibility ruling that Lisota v. Heartland Dental cuts against; below is one summary as the agent leaves it.
Meeting summary · single callIllustrative example
Meeting
Recorded as
Notice
Evidence of record
Confidence
Held for
Pricing review, cross-functional
No decision recorded
Announced in audio
Transcript, 3 August 2026
Held unconfirmed
The named owner, by name
As receivedTaken from the audio and the transcript under it, and it asserts no decision the room did not reach.
What the record holdsAudio and noticeVerbatim transcriptAttendance record
Why no decision hereRecording that a room decided is a call the named owner makes.
ActionConfirmAmendSend to counsel review
What the score decidesBelow the configured threshold a summary picks up a counsel read before the owner sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every meetingFrom the notice that opened it
03Evidence
Where the summary is used
An escalation-summarisation agent compresses a thread for a stated reader; this one manufactures the record of what a room decided, and Kovel, 296 F.2d 918, does not reach it.
01Approved path
The record outlives the room
Retain nothing and a hold has nothing left to hold; retain everything and the cheapest record in the building becomes the easiest one produced against you.
02Human review
What was checked, and not found
No rule was found requiring an organisation to take meeting notes, requiring a summary to be accurate, or giving a participant standing to contest one that misreads them, and no decided case was found authenticating an AI summary or holding that a notetaker waived privilege.
04Build an evidence trail
The summary, the audio it came from and the notice that was played stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Conferencing platformsZoom · Microsoft Teams Google Meet · Webex · conferencing APIs
Calendar systemsGoogle Calendar · Outlook Invitations and attendee lists
Workspaces and archivesSlack · Confluence · Notion Where the summary is filed and read again
Agent
Meeting capture and summarisation
Plays the notice Drafts the summary Holds for the owner
Records and hold systemseDiscovery · records and archives Legal holds and retention classes
A class-level capture figure can read clean while privileged and counsel calls carry most of the owner amendments. Nestack reports the amendment rate by meeting class, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Privileged and counsel calls
8.2%
3.7×
Review
Regulated-firm internal meetings
5.8%
2.6×
Review
Works-council territories
3.6%
1.6×
Watch
Routine internal stand-ups
1.6%
0.7×
Normal
Bar: amendment-rate lift vs. routine-meeting baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a recorded decision costs
A loop shuts when the decision recorded that nobody made is a standing case. That suite is what the next summary written is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Amendment rate rises on privileged and counsel calls.
02Diagnose
The decision recorded in a room where nothing was decided, produced in discovery nine months on, is worked backwards until one cause is left standing.
03Improve
The change goes out numbered, and the summaries that forced it ride beneath.
04Verify
Nothing ships while one touched summary case is still red.
05Learn
The case is held, and the capture rules are rewritten alongside it.
Learn → DetectThe return edge. The next summary is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, summary drafting, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Meeting-class discovery and automation-boundary work.
02Conferencing, calendar and archive sources.
03Summary-to-evidence and retention-coverage mapping.
04Meeting audio intake.
05Notice, speaker and summary binding.
06Confidence scoring and review routing.
07Owner confirmation workflow.
08Workspace and archive integration.
09Notice and summary cases.
10Guardrails and retention controls.
11Capture-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne workspace, one quarterProductionProduction capture workflowAdvancedMultiple regions / meeting classes
Introduced at Pilot
Summary drafting to your capture rules✓✓✓
Named owner confirmation✓✓✓
Meeting-population baseline✓✓✓
Introduced at Production
Reporting by meeting class—✓✓
Counsel review workflow in your systems—✓✓
Approved write-back—✓✓
Calendar-and-archive integration—✓✓
Introduced at Advanced
Multi-territory notice rules——✓
Cross-team summary packs——✓
Large meeting estates——✓
Multi-jurisdiction capture controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, meeting volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your meeting classes and the notice each one carries→Notice capture and retention-class versioningWeek 1
02Representative recordings, transcripts and summaries→Notice binding, drafting logic and the summary baselineWeek 2
03Your records policy and the holds it names→Notice mapping, retention binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Conferencing, calendar and archive assessment, then integration setupWeek 2
05Summaries you would not want produced→Notice cases and failure-mode testingWeek 4
06What no summary may decide→Confidence scoring, review routing, guardrails and release controlsWeek 3
07A named owner who confirms the summary→Release to the named owner, and then pilot and production runsWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The widths are drawn from the work itself, so the fifth week carries a pair rather than a blank.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Meeting-class discovery, notice mapping and the automation boundaryW2Capture integration and the meeting-population baselineW3Summary drafting, retention logic and release controlsW4Evaluation suite, notice cases and failure-mode testingW5Archive integration, pilot summaries and targeted correctionsW6One meeting quarter run under the operations owner, then Agent Care handover
Reading the bandEach bar covers only the weeks its own work is named for, and week five holds two by design.
At the end of W6When the capture record validates, Agent Care takes the agent on.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Product AI agent
Build a meeting-notes agent around the retention setting nobody in legal has seen.
Nowak, C-434/16, reads a summary as accurate in light of its purpose, so the participant it misreads has nothing to correct. Show us your retention setting, the meetings legal does not know happened, and who confirms the record.
