Hargrove Law Group

No agent retains case-specific information between sessions. Every agent interaction begins with a fresh context. Case details are loaded from Clio at the start of each session and discarded at the end.

Why: Attorney-client privilege extends to all systems that store case information. An AI agent that retains case details across sessions becomes a discoverable repository. Opposing counsel could theoretically subpoena agent logs. The firm's ethics counsel flagged this in week 1.

Failure mode: Agent retains a client's injury details from a prior session. That data persists in a log file on a shared server. During discovery in an unrelated case, opposing counsel requests all electronic records. Case details from another client surface in production. State bar complaint filed.

Scope: All 4 agents. No exceptions. Session isolation is mandatory.

The deadline tracker agent pulls statute of limitations dates, filing deadlines, and discovery cutoffs from Clio in real time. It never caches dates. Every check is a live query.

Why: The deadline tracker cached statute dates on Monday and checked against cached data through Friday. Between Monday and Wednesday, a paralegal corrected a statute date in Clio after discovering the incident date was wrong (patient's fall occurred 3 days earlier than initially reported). The cached date was now 3 days too late. The agent did not flag the upcoming deadline because it was comparing against the old date.

Failure mode: Cached statute of limitations is 3 days wrong. Agent shows "42 days remaining" when actual remaining time is 39 days. Attorney does not prioritize the case. On day 39, paralegal notices the corrected date and realizes the statute expires tomorrow. Emergency filing at 11 PM. Case value: $340K. If missed, that is a malpractice claim.

Scope: All deadline tracking. Real-time queries only. No caching.

Demand letter drafts include a mandatory "Attorney Review Required" header and a checklist of factual claims the attorney must verify. The agent highlights every dollar figure, date, and medical diagnosis as requiring verification.

Why: The demand letter agent pulled a medical expense total from case notes that included an estimate for future surgery. The estimate had been revised downward by $18,000 after a second opinion, but the case notes had not been updated. The draft demand letter overstated damages by $18K.

Failure mode: Attorney reviews the draft but trusts the damage calculation. Sends the demand letter with inflated damages. Insurance adjuster catches the discrepancy during negotiation. Attorney's credibility is damaged for that case and potentially for future cases with that adjuster.

Scope: All demand letter drafts. Every factual claim flagged for verification.

The intake screening agent classifies potential cases as STRONG, VIABLE, WEAK, or DECLINE. It provides reasoning for each classification but does not communicate decisions to potential clients. An attorney reviews all classifications before any client contact.

Why: Case evaluation requires legal judgment that the agent cannot reliably provide. A case the agent classified as WEAK (slip-and-fall at a big-box retailer with minimal medical records) turned out to have strong liability because the store had been cited for the same hazard three times. The agent had no access to prior citation records.

Failure mode: Agent classifies a case as DECLINE. Receptionist tells the potential client the firm cannot help. Client goes to a competitor and settles for $280K. The firm discovers the missed opportunity months later when the settlement is reported in legal news.

Scope: All intake screening. Agent classifies; attorney decides.

The intake agent screens and classifies. The demand agent drafts letters. The deadline agent monitors dates. The comms agent schedules client updates. No agent crosses into another agent's domain.

Why: In week 5, the demand letter agent started including deadline references in its drafts ("this demand must be resolved before the statute expires on [date]"). The deadline agent also flagged the same case in its morning report. Attorney received the same deadline from two sources with different urgency framing. One said 45 days, the other said 43 days (because they calculated from different reference points).

Failure mode: Two agents report conflicting deadline information. Attorney trusts the more optimistic number. Paralegal trusts the other. Neither confirms with Clio directly because both assume the agents already checked. Confusion wastes 2 hours of billable time at $350/hr.

Scope: All four agents. Strict domain separation.

The comms scheduling agent arranges client update calls but never generates the content of those updates. It schedules the call and provides the attorney with a case summary from Clio. The attorney delivers the update.

Why: Client communications in a PI firm carry legal weight. An imprecise statement about case progress ("we expect to settle by August") can create client expectations that become the basis for a grievance if not met. Only attorneys make representations about case outcomes.

Failure mode: Comms agent sends a scheduling email that includes "we have good news about your case." Client interprets this as a settlement offer. Arrives at the call expecting a check. Attorney was actually calling to discuss a strategy change. Client feels misled.

Scope: All client communication content. Agent schedules only.

The demand letter agent has read-only access to Clio case data. It cannot update case notes, modify statuses, or add documents. Only attorneys and paralegals write to the case file.

Why: In week 3, we considered giving the demand agent write access so it could log its drafts directly to Clio. Ethics counsel vetoed it. AI-generated content in the case file without attorney review could be discoverable as attorney work product with no attorney actually having reviewed it.

Failure mode: Agent writes a draft demand letter directly to Clio. Opposing counsel subpoenas the case file. Draft contains preliminary damage calculations the firm never intended to disclose. Numbers become a negotiation anchor that works against the client.

Scope: All case management system access. Read-only for all agents.

The deadline agent generates a daily report at 5 AM listing all deadlines within 90 days, sorted by urgency. Items within 14 days are marked CRITICAL. Items within 30 days are marked WATCH. The report goes to Marcus and the paralegal team.

Why: Before the agent, deadline tracking was a shared spreadsheet updated by paralegals. Two near-misses in one quarter prompted the AI implementation. The 90-day window catches items that are far enough out to plan but close enough to matter.

Failure mode: Without the daily report, deadlines are tracked ad hoc. A paralegal goes on vacation. Her cases are redistributed but two deadlines are not transferred to the coverage paralegal's tracking sheet. Both deadlines pass. One is a discovery cutoff. Evidence is excluded. Case value drops by an estimated $75K.

Scope: All active cases. Daily reporting with no exceptions.

When the intake agent classifies a new case as STRONG, it triggers the comms agent to schedule an initial consultation within 48 hours. The trigger is a state file update, not a direct agent-to-agent call.

Why: Speed matters in PI intake. A potential client who waits 5 days for a consultation is likely shopping competitors. Before the trigger, average time-to-consultation was 4.2 days. After implementation, it dropped to 1.8 days. The firm attributes 3 new signed cases in the first month to faster response.

Failure mode: STRONG case classified on Friday afternoon. Without the automated trigger, the scheduling request sits in an email until Monday. Client calls two other firms over the weekend. By Monday, client has retained a competitor.

Scope: Intake-to-consultation pipeline for STRONG-classified cases.

All four agents write status updates to individual state files. Marcus reviews a compiled summary at 7 AM before the daily team huddle at 7:30 AM. Stale state files (not updated in 24 hours) are flagged at the top.

Why: Marcus needs 15 minutes of context before the huddle. Reading four separate agent outputs takes 25 minutes. The compiled summary takes 8 minutes and highlights only items requiring action.

Failure mode: Without compilation, Marcus skims agent outputs unevenly. Misses a WATCH deadline that should have been discussed at the huddle. Paralegal does not learn about the deadline until the next day. One day of planning time lost.

Scope: Morning operations. All four agents feed into one compiled summary.

Demand letter drafts use the firm's established template structure and tone. The agent does not experiment with novel legal arguments or creative formatting. If the fact pattern suggests a non-standard approach, the agent flags it and defers to the attorney.

Why: Insurance adjusters read thousands of demand letters. They recognize standard, professionally structured letters as coming from competent firms. A creatively formatted letter or an experimental legal argument can signal inexperience, even if the content is sound.

Failure mode: Agent drafts a demand letter using a narrative style instead of the firm's established format. Adjuster perceives the firm as inexperienced. Initial counteroffer is 40% lower than expected. Attorney spends two additional months negotiating to reach the same number a standard letter would have achieved.

Scope: All demand letter drafts. Template compliance checked before attorney review.

Client update calls are scheduled between 10 AM and 3 PM on Tuesday through Thursday. Mondays are for internal case review. Fridays are for court appearances and depositions. The comms agent never schedules outside this window without attorney override.

Why: Attorneys need uninterrupted blocks for case preparation and court appearances. Early implementation allowed the comms agent to schedule calls at 8 AM and 4:30 PM. Attorneys were arriving at court unprepared because they had been on a client call until 15 minutes before their appearance.

Failure mode: Comms agent schedules a client call at 8:15 AM. Attorney's deposition starts at 9:00 AM. Call runs long. Attorney arrives at deposition flustered and underprepared. Opposing counsel notices and pushes harder on key points.

Scope: All client communication scheduling. Hard scheduling windows enforced.

The intake agent asks 7 standardized screening questions before classification. If a potential client cannot answer 3 or more questions, the case is classified as INCOMPLETE rather than WEAK. Incomplete cases get a 48-hour follow-up, not a decline.

Why: Trauma patients often cannot recall details during the first call. A car accident victim called 2 days post-accident and could not provide the other driver's insurance info, the police report number, or the exact location. Agent classified the case as WEAK. Attorney overrode it. Case settled for $195K.

Failure mode: Traumatized potential client provides incomplete information. Agent classifies as WEAK or DECLINE. Firm turns away a strong case because the agent prioritized data completeness over human context.

Scope: All intake screening. INCOMPLETE classification added in week 4.

The stale-data deadline incident (C002) taught us that any system relying on cached legal dates is a malpractice risk. We now audit the deadline agent weekly by comparing its output against a manual Clio pull. Discrepancy rate must be 0%.

Why: A single missed deadline can result in a malpractice claim that exceeds the case value. The $340K near-miss cost 0 dollars only because a paralegal caught it by coincidence. The expected cost of that failure mode is too high for any tolerance above zero.

Failure mode: Deadline agent reports 42 days remaining. Manual check shows 39 days. Three-day discrepancy on a case worth $340K. If no one catches it, the statute expires. Client sues the firm. Insurance premium increases. Bar complaint filed.

Scope: Weekly audit of all deadline agent outputs against Clio source data.

We initially gave the demand letter agent access to all 85 active case files so it could learn from prior letters. It began cross-pollinating facts between cases. A draft for one client included medical details from a different client's file. The draft never left the firm, but it exposed a systemic risk.

Why: When an AI has access to multiple case files simultaneously, it can blend facts. In a law firm, blending client facts is a confidentiality violation even if it never leaves the building. Each case must be an isolated context.

Failure mode: Demand letter for Client A includes a medical procedure that happened to Client B. Attorney catches it during review. But if the attorney had been rushing and sent it, opposing counsel would see medical details for a different patient. HIPAA violation, ethics violation, and potential criminal liability.

Scope: All agent access to case data. One case per session. No cross-case access.

The comms agent sent a scheduling email to a client who had been non-responsive for 60 days. The client had actually retained another firm and not informed us. The scheduling email went to an opposing party's client. The new firm filed a motion alleging improper contact.

Why: Former-client status must be checked before any automated outreach. The comms agent did not verify case status before scheduling. Clio showed the case as "active" because no one had updated it after the client switched firms.

Failure mode: Automated outreach to a former client who is now represented by opposing counsel. Motion for sanctions filed. $4,500 in legal fees to respond. Managing partner's time consumed for two weeks. Reputation damage with the local bar.

Scope: All automated client outreach. Case status verified in real time before every communication.

No agent provides legal advice, case assessments, or settlement recommendations to clients. Agents process data and generate drafts. Attorneys exercise legal judgment.

Why: The unauthorized practice of law is a criminal offense in North Carolina. An AI system that provides legal advice to a client without attorney supervision exposes the firm to criminal liability, bar discipline, and malpractice claims simultaneously.

Failure mode: Client emails asking "Should I accept their offer of $85K?" Comms agent responds with "Based on similar cases, $85K appears below the expected range." Client relies on this and rejects the offer. Settlement falls through. Client sues the firm arguing the AI provided bad legal advice.

Scope: All agent interactions. Legal judgment is exclusively human.

Agents generate work product that is reviewed under attorney supervision. This preserves work product privilege. If an agent generates a document without attorney involvement in the process, the privilege may not attach, making the document discoverable.

Why: The firm's ethics counsel determined that AI-generated drafts are protected under work product doctrine only if an attorney directed the creation and reviewed the output. Documents generated autonomously by an agent without attorney direction may not qualify for privilege protection.

Failure mode: Demand agent autonomously generates a case evaluation memo without attorney direction. Opposing counsel argues the memo is not privileged because no attorney supervised its creation. Judge agrees. Internal case strategy is disclosed to the opposing side. Settlement leverage destroyed.

Scope: All agent-generated documents. Attorney direction and review required to preserve privilege.