An executive assistant in iMessage.
Follow-ups and scheduling consume the gaps between meetings.
Est. deploy 2–4 weeksSee the walkthrough
Executive Assistance · Legal
Prepare attorneys before the first consult.
Attorneys reread long inquiry threads before meetings.
For: Intake attorneys and the team responsible for executive assistance in legal.
01 · The outcome
What good looks like.
The team has a privileged consult brief for the assigned attorney, with source evidence and an explicit approval before any external action. Track preparation minutes per consultation against a baseline; do not assume automation improves it.
A connected workflow that uses authorized inquiry notes, conflict status, and appointment context to summarize facts as allegations, link source messages, and list unanswered intake questions. It produces a privileged consult brief for the assigned attorney.
Where AI helps, and where a person decides.
AI can summarize facts as allegations, link source messages, and list unanswered intake questions. It drafts and organizes; it does not authorize spending, commitments, clinical decisions or customer communication. The intake attorney verifies the source facts and approves the final action.
Intake attorney is accountable. People approve customer-facing, sensitive, financial, and legally binding actions.
- Intake attorney: Capture the source and scope
- Intake attorney: Review the proposed outcome
- Intake attorney: Release only the approved version
- Intake attorney: Check the result and exceptions
A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
02 · The handoffs
How the work moves.
Every handoff has an owner. Select a step to open or close its detail.
Start when: A cleared consultation enters the next-day calendar. Connect only authorized inquiry notes, conflict status, and appointment context. The intake attorney confirms the request is authorized and in scope.
Ready when: The source reference, permissions and accountable owner are recorded.
Use the authorized records to summarize facts as allegations, link source messages, and list unanswered intake questions. Preserve the original language alongside the draft and label uncertain fields.
Ready when: Each proposed fact links back to a source, and missing information is visible.
Check a privileged consult brief for the assigned attorney against the original records and current policy. Correct errors and escalate exceptions to the qualified specialist; do not auto-approve.
Ready when: Intake attorney has recorded approval or a reason to hold the item.
After explicit approval, save a privileged consult brief for the assigned attorney in the system of record. Send only approved messages to verified recipients. Record the version and prevent duplicate delivery.
Ready when: The approved record is saved; any delivery is confirmed or placed in the retry queue.
Review preparation minutes per consultation each week, sample completed records for quality, and resolve held items. Change the rules only after reviewing actual errors and staff feedback.
Ready when: Exceptions have owners, the metric has a baseline, and corrective actions are assigned.
Sample record.
$ david run --workflow=legal-consult-prep
ILLUSTRATIVE RECORD / NOT LIVE CUSTOMER DATA
- Example
- Illustrative only — not a real client record
- Reference
- LEGAL-CONSULT-PREP-DEMO-001
- Trigger
- A cleared consultation enters the next-day calendar.
- Owner
- Intake attorney
- Prepared output
- a privileged consult brief for the assigned attorney
- Review status
- Awaiting human approval — no external action taken
- Missing information
- Owner to verify source completeness
- Measure
- Preparation minutes per consultation
Start with your tools.
Connect Clio, Microsoft 365, Document management system through approved APIs or controlled exports. Map record identifiers first; test permissions and field updates in a sandbox. Vendor names describe possible connections, not a guarantee of an available integration or license.
When things go wrong.
- A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
- Use only authorized sources and role-based access. Keep an audit trail of source records, drafts, approvals and delivery status; deduplicate retries.
- If an integration fails, a source is missing or confidence is low, pause the action and assign the original request to the accountable owner.
- For legal work, preserve privilege and confidentiality, check conflicts before substantive intake, and require a licensed attorney to approve legal advice, filings and engagement terms.
Try this week / no DAVID required
A useful first step.
This week, have your intake attorney time five examples of this work. Use redacted copies of authorized inquiry notes, conflict status, and appointment context to make a privileged consult brief for the assigned attorney manually, then list which fields required judgment.
What to measure.
- Preparation minutes per consultation
- Minutes of human handling per completed item
- Drafts needing substantive correction
- Exceptions unresolved beyond the agreed review window
Estimate your time back.
20.8
$11,232
03 · More workflows to consider
Related workflows.
Prepare every advisor meeting from current records.
Advisors switch between systems to build a briefing.
Est. deploy 4–6 weeksSee the walkthrough
Route every inquiry, 24/7.
Email, calls and webforms produce disconnected intake trails.
Est. deploy 3–5 weeksSee the walkthrough
Want this running in your business in 4–6 weeks?
Free 30-minute call. We'll tell you honestly whether AI fits, and where.