💸 $38.9k fee award · 💬 Client facts · 📝 Copilot

A client’s beautifully written reply can still leave you hunting for the facts. This week, one litigation team explains the problem, a New York court puts a price on citation cleanup, and a new toolkit counts the work after the AI draft. There are material Copilot, Harvey and Legora updates too—coffee first, source documents close.

💬 Start with the work

Client instructions, familiar office tools and learning on real tasks: begin with the job your team actually needs to do.

💬 Your client’s polished reply may leave the facts out

Stevens & Bolton’s litigation team says it is beginning to receive AI-written replies to requests for client instructions. A fluent narrative can smooth over uncertainty or omit details that matter when checked against documents and witness evidence. This is a practitioner observation, with no measured cost or failure rate. Its useful distinction: AI may help organise the papers, but lawyers still need the client’s own account of what happened. Ask for both the chronology and its underlying records.

Source: Stevens & Bolton

📝 Copilot’s 20+ legal skills reach general availability

Microsoft has made more than 20 legal skills generally available in Copilot, including tracked redlines, playbook review and drafting in Word, plus multi-step work in Cowork. Partner plugins are beginning to roll out; defined-term navigation is still a preview due later this month. Microsoft reports users kept roughly seven in ten proposed edits. That is acceptance data from its own rollout, not a legal-accuracy score. Your review still decides what survives.

Source: Microsoft

🎒 Duane Morris pairs AI training with practice champions

Duane Morris pairs live AI-and-library research training with twice-monthly extended orientation through June and practice-group AI champions. Talent chief Diane Downs also describes an experiment at her previous firm: few used a live-coached conversation simulator, while a later private AI version drew engagement. These are self-reported choices, not measured learning gains. The design question is where juniors can practise, get feedback and keep learning after induction.

Source: Thomson Reuters Institute

🧪 Put the handoffs to the test

Measure the review and rework, then look closely at who can approve an agent’s next step.

🧪 Test the AI draft—and the work needed to fix it

SuperTech’s new downloadable toolkit offers an eight-dimension scorecard for evaluating legal AI. Start with one task and one tool, time the human baseline, then have a senior and junior lawyer score the same task independently. Include prompting, checking and rewriting when judging value. Developed through a programme with three law firms and academic input, it is a practical testing framework, not an independent product ranking; its suggested targets are not measured savings.

Source: SuperTech WM

📥 Legora Intake starts in the Slack thread

Legora Intake is available in Slack: the agent asks for missing details, creates an assigned legal task and prepares work from the team’s playbooks and precedents. Lawyer review is the default, but teams can preapprove routine request types for automatic completion. That exception deserves as much attention as the demo. Decide which requests may go back without another review, and who owns them. Microsoft Teams, email and MCP access are planned.

Source: Legora

🧭 Harvey gives agent tasks a reviewer and a next step

Harvey’s Legal Work Orchestration puts tasks, inputs and designated reviewers around a matter, so an agent’s output has somewhere to go for approval. Tasks, comments and notifications are rolling out now; reusable templates are in early access. The concrete change is the handoff: a partner can review a consent matrix before the next task begins. Harvey’s prediction that agents will handle more workflow steps is a forecast, not an observed productivity gain.

Source: Harvey

⚖️ The record has consequences

A fee award, an expert’s chat history and judicial safeguards show why the evidence trail deserves attention.

💸 False citations lead to a $38,877.59 fee award

A 9 October order in Flycatcher v Ozmos awards $38,877.59 in fees and costs against lawyer Steven Feldman, following February sanctions for false AI citations and lies about their origin. The award covers lawyers who investigated the misconduct, plus the later fee dispute. More time was claimed for fee proceedings and negotiations than for addressing the original misconduct. This is a New York federal case-specific award, with a reminder that the repair bill can keep growing.

Source: U.S. District Court, Southern District of New York (via Justia)

⚖️ An expert’s AI log needs a content-by-content review

Hunton’s new analysis of a 29 September Nevada federal ruling separates an expert’s discoverable ChatGPT case summaries from protected prompts, draft-report material and deposition preparation. The distinction is what the expert considered in forming an opinion versus material used to prepare the report or testimony. There is no blanket shield for AI chats here. Discuss expert AI use early, preserve the record and review each part by purpose; the Nevada court did not find that hallucinations had occurred.

Source: Hunton Andrews Kurth

🏛️ England and Wales sets boundaries for judicial AI

England and Wales’ judiciary has published its AI adoption position: approved tools must have UK data residency, enterprise data protection and disabled web access. Every output used in judicial work needs the responsible office holder’s review, verification and approval. A central steering group controls new tools, use cases and pilots. These are judicial adoption safeguards, not a new mandate for law firms; AI must not decide case outcomes or displace judicial reasoning.

Source: Courts and Tribunals Judiciary

🧭 Skills, careers and cross-border work

Competence proposals, implementation jobs and jurisdiction-specific access all change what teams need to plan for.

🎓 The SRA proposes AI checks in solicitor competence

England and Wales’ SRA proposes making AI explicit in solicitor competence: check research outputs against primary resources and supervise work involving technology. Legal Futures reports on the consultation, which opened on 8 October and closes on 3 December. These are proposed framework changes, not a new rule already in force. The practical question for partners is who can assess the work after the prompt—not just who has learned to use the tool.

Source: Legal Futures

🧑‍💻 Legal AI’s job ads want lawyers who can implement it

Best Law Firms’ review of Harvey and Legora job listings finds about 100 openings seeking legal experience, including roles helping customers train on and implement AI. Some US legal-engineer pay ranges start around $220,000. The article’s separate movement figures cover the first half of the year; they are not fresh October departures. For firm leaders, the career question is concrete: where does a lawyer who is good at implementation progress inside your own team?

Source: Best Law Firms

🌍 CoCounsel announces research across 100+ jurisdictions

Thomson Reuters announced a Multinational Profile bringing legal content from more than 100 countries and territories into one CoCounsel workflow. The rollout has its own geography: next-generation CoCounsel is live in the UK, with Australia, Singapore and other markets expected by the end of October. The profile rolls out through October in specified regions. Check your actual country and feature access before planning a cross-border workflow; source coverage is not universal availability.

Source: Thomson Reuters

💬 Community Spotlight

🔌 Keep the system, connect the AI

A law-firm contact reportedly sidestepped a software replacement by using Claude and MCP connectors to pull data from existing systems and prepare reports. The post describes reporting, rather than an agent changing records: a useful distinction before the demo becomes a purchasing decision.

Replies split between flexible access and a fragile dashboard. One operator who built a firm’s case system says the underlying software still owns data, permissions and exact deadlines. Another argues that recurring reports should become deterministic tools instead of fresh inference every time. These are implementation anecdotes, not a reliability test; the practical question is which parts need a model at all.

Source: r/legaltech

Key Insight: An AI interface still needs a dependable source system, explicit permissions and fixed tools for work that must be exact.

Key Takeaways:

• The reported workaround queried existing systems and produced reports; it did not execute changes.
• One firm operator keeps data, permissions and exact deadlines in the underlying case system.
• Commenters disagree about whether custom AI reporting is flexible access or fragile infrastructure.
• Repeated reports and calculations may be better served by deterministic tools than fresh inference.
• Dirty data and maintenance remain problems even when the interface becomes a conversation.

💬 More from the community

💬 Who pays for the chatbot’s follow-up?

A client says a five-day window for submitting AI-generated feedback reduced back-and-forth; others prefer normal hourly billing or a set number of revisions, and some favour bans. The useful discussion is about agreeing what follow-up includes before an AI question list lands. These are competing anecdotes, not a tested engagement clause.

Source: r/legaltech

🗂️ One matter hub before an AI chief of staff

A solo lawyer juggling 30 cases asks for an AI assistant. Replies split between custom builds and a simpler start: one matter system, consistent folders and a daily task view, then automate one bottleneck. The maintenance burden is part of the job; several commenters suggest getting human help before building another system to supervise.

Source: r/legaltech

🔎 A timeline still needs a missing-facts check

A litigator asks for agent workflows and mostly gets examples of prompting: timelines, fact summaries and first drafts. One commenter says broad timelines can miss important details even when pointed questions work well. Treat the thread as a reason to check completeness against the documents, rather than proof that a named tool handles the matter.

Source: r/biglaw