Legal Ops Agents: Intake and Monitoring
In Lessons 3 through 9, you used Anthropic's Legal Plugin commands and skills to review contracts, triage NDAs, assess compliance, manage IP, handle litigation, and prepare for meetings. Each was a single-task workflow. Now you will work with agents that manage entire processes end-to-end: receiving inputs, making routing decisions, and tracking progress across the contract lifecycle. The Agent Factory Legal Ops extension provides two such agents: the contract-intake agent and the legal-ops-router agent.
If you connected Gmail, Slack, and Atlassian MCP servers in Lesson 1, the Intake Agent can receive contracts via email, post routing notifications to Slack channels, and log matters in Jira. If not, the agent works with manually uploaded documents: you provide the trigger, the agent handles everything after.
What Legal Ops Agents Are
A Legal Ops Agent is a persistent, multi-step workflow that manages a legal process end-to-end -- accepting inputs, making routing decisions, tracking progress, escalating when deadlines approach, and maintaining state across interactions. This is fundamentally different from a document tool (which produces a single output and stops).
For example, a contract review tool takes a contract in and produces a redline report out -- one input, one output, done. A Contract Intake Agent, by contrast, receives the contract, classifies it, extracts metadata, runs the appropriate triage protocol, routes to the correct reviewer, sends communication templates, tracks SLA compliance, escalates if deadlines are missed, and -- when the contract is executed -- saves it to the repository, sets renewal reminders, and monitors obligations for the life of the contract.
The document tool reduces time on a single task. The Legal Ops Agent eliminates the coordination overhead across the entire process.
Why it matters: coordination overhead -- the chasing, tracking, escalating, and reporting -- consumes 40-60% of legal operations capacity. Automating it transforms the legal function structurally, not just incrementally.
Legal Operations Agents are not contract review tools or document generators. They are persistent, multi-step workflows that manage legal processes end-to-end, connecting to the organisation's systems, maintaining state across interactions, and executing the administrative and analytical work that currently consumes legal department capacity.
The distinction matters. A contract review tool produces a document. A Legal Ops Agent manages a process. It accepts an incoming contract, routes it for triage, tracks progress through negotiation, reminds the business owner when a response is due, updates the contract repository when executed, sets renewal reminders, and monitors obligations through the contract's life -- all without manual intervention at each step.
This is the transformation Anthropic's February 2026 release signals. As Artificial Lawyer reported, Anthropic described it as: "a meaningful step from AI as a chatbot to AI as a capable teammate across business functions." Above the Law was blunter: Anthropic had announced "I can haz enterprise value" -- moving from infrastructure provider to delivering complete workflows.
The organisation that simply installs the plugin has a better document review tool. The organisation that builds Legal Ops Agents has a transformed legal function.
Consider the difference in concrete terms. A legal department using the plugin as a document tool reviews contracts faster -- perhaps reducing a 4-hour review to 40 minutes. That is valuable. A legal department using Legal Ops Agents eliminates the entire coordination layer: the contract arrives, is classified, triaged, routed, tracked, escalated, filed, and monitored without a human touching the administrative workflow at any point. The attorney's time is spent exclusively on the 20% of work that requires professional judgment -- reviewing RED items, approving redlines, making strategic decisions about relationship management. Everything else is handled by the agent.
For legal teams in Pakistan and the GCC, this distinction is particularly consequential. Many mid-sized companies in Karachi, Lahore, Dubai, and Riyadh operate with lean legal teams -- often a single GC with one or two junior associates handling the full spectrum of commercial, regulatory, employment, and compliance work. These teams cannot afford the coordination overhead that larger departments absorb with dedicated Legal Ops staff. The agent architecture described below gives a three-person legal team the operational capacity of a team twice its size -- not by working faster, but by eliminating the work that should never have required human attention in the first place.
Agent 1: The Contract Intake Agent
Purpose: Manage all incoming contracts from receipt through execution and obligation monitoring -- without manual routing at each step.
Trigger: Incoming email to legal-intake@yourcompany.com (via Gmail/Outlook MCP) OR document uploaded to designated SharePoint/Drive folder OR web form submission.
Workflow:
1. Receive document
-> Extract metadata: counterparty, contract type, requesting
business unit, urgency, stated value
-> Log in contract tracking system (Google Sheets / SharePoint MCP)
2. Classify document type
-> NDA / Mutual CA -> run /triage-nda protocol
-> Vendor Agreement / MSA -> run /review-contract protocol
-> Employment / Contractor -> route directly to HR Legal queue
-> Unknown -> extract key terms; route to GC queue
3. Apply triage and routing
-> Tier 1: Notify business unit; route for authorised signatory
-> Tier 2: Notify reviewing attorney; attach triage summary
-> Tier 3: Notify General Counsel; attach full review; schedule call
if value > [GBP/USD threshold]
4. Track progress
-> Check status daily
-> Escalate if SLA breached (Tier 1: 1 day; Tier 2: 2 days;
Tier 3: 5 days)
5. On execution
-> Save to contract repository
-> Set obligation reminders
-> Set renewal calendar entry
-> Notify requesting business unit
Worked Example: Contract Intake at Gulf Digital Solutions, Dubai
Khalid Al-Mansoori is Legal Operations Manager at Gulf Digital Solutions, a 300-person enterprise software company headquartered in Dubai Internet City. Gulf Digital receives approximately 40 contracts per month across three channels: email to legal@gulfdigital.ae, uploads to a SharePoint folder, and Slack messages from business units.
At 09:15 on a Tuesday morning, the following arrives:
Email to legal@gulfdigital.ae:
From: Ahmed Qureshi, VP Sales Subject: Urgent -- New MSA from Etisalat Digital for review "Hi Legal, attached is the MSA from Etisalat Digital for our enterprise API platform deployment. Contract value AED 3,600,000 annually. They want to sign by Thursday. This is our largest deal this quarter. Please prioritise."
The Contract Intake Agent processes this automatically. The agent executes a five-step sequence. Your output will vary, but look for these sections:
| Section | Intent | What to Verify |
|---|---|---|
| Step 1: Document reception | Logs receipt with reference ID, timestamp, source channel, and requestor | Check that the reference ID is unique and the source is correctly identified |
| Step 2: Document type classification | Classifies the document type and selects the appropriate review protocol | Should route vendor agreements to /review-contract and NDAs to /triage-nda |
| Step 3: Metadata extraction | Extracts counterparty, contract type, business unit, urgency, deal value, governing law, and date | Verify all seven metadata fields are populated: missing fields should be flagged |
| Step 4: Triage and routing | Runs the appropriate review protocol and routes based on tier classification and urgency | Should apply the correct communication template (acknowledgement to business unit, escalation to GC for RED items) and halve SLA timelines for urgent requests |
| Step 5: Progress tracking | Activates deadline monitoring with escalation if no attorney action by the SLA deadline | Check that the escalation path is specified |
The specific metadata, triage results, and routing decisions depend on the contract you provide. Focus on whether the five steps execute in sequence and whether the routing matches the triage tier: particularly whether RED items with urgent flags bypass the normal SLA timeline.
The GC receives the escalation within minutes of the email arriving. Without the intake agent, the email would sit in the legal inbox until someone opened it, read it, realised it was urgent, and forwarded it manually. Typical delay without automation: 4-8 hours on a good day.
The Contract Intake Agent in the Legal Ops Extension:
The Agent Factory Legal Ops extension includes a pre-built contract-intake agent at agents/contract-intake.md. This agent auto-activates when you mention incoming contracts, contract routing, contract triage, new NDAs received, or legal intake. You do not need to invoke a command: the agent recognises trigger phrases and activates automatically. Below are the rules it follows:
## INTAKE SEQUENCE — EXECUTE IN ORDER
STEP 1 — IDENTIFY DOCUMENT TYPE
NDA / Mutual CA -> /triage-nda protocol
Vendor / MSA / SOW -> /review-contract protocol
Employment / Contractor -> HR Legal queue (no agent analysis)
Unknown -> extract key terms; GC queue with summary
STEP 2 — EXTRACT METADATA (always, no exceptions)
- Counterparty full legal name
- Contract type
- Requesting business unit and named contact
- Stated urgency / deadline
- Deal value (if stated)
- Governing law (if stated)
- Date received
STEP 3 — APPLY SLA RULES
Tier 1 (Standard Approval): complete within 1 business day
Tier 2 (Counsel Review): attorney response within 2 business days
Tier 3 (Full Review): attorney response within 5 business days
URGENT flag: notify GC immediately; halve all timelines
STEP 4 — COMMUNICATION TEMPLATES
Acknowledgement to business unit:
"Your contract request has been received and triaged.
Classification: [Tier]. Expected response: [date].
Reference: [ID]. Questions? Contact legal-intake@..."
Counsel notification:
"New [contract type] for your review. Counterparty: [name].
Triage summary: [attached]. Deadline: [date].
Business unit: [name]. Deal value: [amount if known]."
GC escalation:
"RED escalation: [contract type], [counterparty], [value].
[N] RED items identified. Triage attached. Business unit
requires response by [date]. Call recommended: [Y/N]."
## NEVER DO THESE
- NEVER approve a contract for execution — human authorised signatory only
- NEVER route a RED item to Tier 1, regardless of business pressure
- NEVER skip metadata extraction — required for compliance log
- NEVER send legal advice to the requesting business unit —
send routing decisions and timelines only; advice is for attorneys
PayGulf Technologies' Contract Intake Agent adds a regulatory classification layer that Gulf Digital's intake workflow does not require. Every incoming contract at PayGulf is classified not only by type (NDA, MSA, vendor agreement) and urgency, but also by regulatory impact: a dimension that non-regulated companies can skip entirely.
The regulatory classification asks three questions before standard triage begins. First: does this contract create a new outsourcing arrangement that must be reported to the DFSA? The DFSA requires notification of material outsourcing, and a new merchant processing agreement or technology vendor contract may qualify. Second: does the counterparty operate under SAMA regulation? If PayGulf is contracting with a Saudi-regulated entity, both regulators' outsourcing frameworks apply, and the contract must satisfy both sets of requirements. Third: does the contract involve access to, processing of, or storage of payment data subject to PCI DSS? If yes, specific data handling provisions are mandatory regardless of the contract's commercial terms.
The routing logic changes accordingly. A contract flagged as regulatory-impact is routed directly to Fatima (GC) regardless of its commercial urgency tier. A Tier 1 vendor agreement that would normally bypass attorney review entirely gets escalated to Tier 2 or Tier 3 if the regulatory classification triggers. The intake agent's acknowledgement to the business unit reflects this: "Your contract request has been received. Classification: Tier 2; Regulatory Review Required. This contract involves a potential outsourcing arrangement under DFSA rules. Expected response: 3 business days."
This adds processing time compared to Gulf Digital's workflow, but the alternative: discovering a DFSA notification requirement after the contract is executed: creates regulatory exposure that dwarfs the cost of a two-day review delay.
Agent 2: The Regulatory Monitoring Agent
Purpose: Track regulatory changes across relevant jurisdictions daily; assess impact on internal policies and contracts; produce weekly GC briefing.
The regulatory-monitoring skill in the Legal Ops extension auto-activates when you ask about regulatory changes, compliance updates, or regulatory briefings. The router skill detects the jurisdictions involved and loads the appropriate overlays before the skill executes.
Produce a weekly regulatory monitoring briefing:
Jurisdictions: UK, EU, US
Topics: data protection, AI regulation, employment law,
company law, sector-specific: SaaS/cloud
Period: since [last run date]
Output: weekly briefing with RAG status per area
Agent workflow:
- Searches official regulatory sources (ICO, FCA, SEC, EC, etc.) for updates in configured areas
- Summarises each development: jurisdiction, effective date, impact level (Immediate / Within 6 months / Monitor)
- Identifies which internal policies may need updating
- Flags which executed contracts may need amendment (searches repository for relevant clauses)
- Produces weekly briefing for General Counsel and Compliance Officer
Worked Example: Weekly Regulatory Briefing for DataBridge (Pakistan/UK)
DataBridge Ltd is a 200-person SaaS company incorporated in England with a development centre in Lahore, Pakistan. Their Compliance Officer, Priya Sharma, has configured the Regulatory Monitoring Agent to track both UK and Pakistani regulatory developments.
What to expect: The agent produces a weekly regulatory briefing. Your output will vary, but look for these sections:
| Section | Intent | What to Verify |
|---|---|---|
| HIGH PRIORITY items | Regulatory changes requiring action within 30 days | Should include effective dates, internal impact assessment, contract impact, and assigned owners |
| MONITOR items | Changes requiring attention within 6 months | Should include status, internal impact, and recommended timeline for action |
| AWARENESS items | Informational updates with no immediate action required | Should be brief summaries with no assigned owners |
| RAG status summary | Per-topic RED/YELLOW/GREEN classification across all monitored areas | Check that the RAG status matches the priority classification of each item |
| Governance footer | Confirmation that regulatory interpretations require attorney confirmation | Should be present on every briefing |
The specific regulatory updates depend on the jurisdictions configured, the date range, and the regulatory sources available via MCP. Focus on the three-tier structure (HIGH PRIORITY / MONITOR / AWARENESS) and whether each item includes internal impact assessment and contract impact. The teaching point is that a weekly briefing replaces 4-6 hours of manual regulatory research with a 20-minute review.
The Compliance Officer reviews this briefing in 20 minutes on Monday morning, forwards the HIGH PRIORITY items to the GC with recommended actions, and adds the MONITOR items to the quarterly compliance review agenda. Before the agent, producing this briefing took 4-6 hours of manual research each week.
Flashcards Study Aid
Try With AI
Setup: Use these prompts in Cowork or your preferred AI assistant.
Prompt 1: Reproduce
I am learning about Legal Ops Agents. For each of the following
legal automation scenarios, tell me whether it is a document tool
or a Legal Ops Agent, and explain why:
1. An AI that takes an NDA and produces a risk-rated summary
2. An AI that receives NDAs via email, classifies them, routes
standard NDAs for auto-signature and non-standard NDAs to
counsel, tracks response times, and escalates overdue items
3. An AI that drafts a DSAR acknowledgement letter
4. An AI that logs a DSAR, starts a 30-day countdown, sends
data discovery requests to seven departments, collates
responses, prepares a redaction checklist, drafts the full
response, and alerts if the deadline approaches
For each, identify what makes it a tool (single input/output)
or an agent (persistent, multi-step, state-maintaining).
What you are learning: The distinction between tools and agents is not about complexity of output -- it is about whether the system maintains state, makes routing decisions, and manages a process over time. Understanding this distinction determines whether you are automating a task or transforming a function.
Prompt 2: Adapt
I am building a Contract Intake Agent for a 50-person technology
company. Our legal team is just one General Counsel and one
paralegal. We receive approximately 15 contracts per month,
mostly via email. Our contract types are:
- SaaS vendor agreements (most common)
- NDAs with prospective partners
- Consulting agreements (we hire contractors)
- Occasional employment agreements
Design a Contract Intake Agent workflow for us. Include:
1. The triage tier definitions appropriate for a 2-person team
2. SLA timelines that are realistic for this team size
3. Communication templates for the business requestor
4. Escalation rules when the GC is on leave
5. The "NEVER DO THESE" safety rules
What you are learning: The Contract Intake Agent workflow must be calibrated to your organisation's size, team capacity, and contract volume. A 2-person team needs different SLA timelines and escalation paths than a 15-person legal department. The exercise builds your ability to adapt the pattern to your specific context.
Prompt 3: Apply
I am a Compliance Officer at a fintech company based in Karachi,
Pakistan, with clients in the UAE and UK. My Regulatory Monitoring
Agent has produced a weekly briefing with the following items:
RED: State Bank of Pakistan has issued new digital lending guidelines
effective in 45 days requiring enhanced KYC for all digital
loan products
YELLOW: DFSA (Dubai) consultation on crypto-asset regulation
closing in 3 months
YELLOW: UK FCA consumer duty rules — annual assessment due in
6 months
GREEN: SECP updated filing deadlines (administrative, no impact
on operations)
For each item:
1. What specific actions should I take this week?
2. Who in my organisation needs to know?
3. What contracts or policies might need updating?
4. What is the risk if I ignore it for 30 days?
What you are learning: A regulatory briefing is only useful if you can translate RAG status into specific actions, ownership assignments, and risk assessments. This prompt builds the skill of reading an agent's output and making the decisions that the agent cannot make for you -- because the agent reviews, but the attorney (and compliance officer) decides.
What You Built
- A Contract Intake Agent with five-stage workflow: receive, classify, route, SLA-track, escalate
- Document type classification across six contract categories with confidence thresholds
- A Regulatory Monitoring Agent producing weekly RAG-status briefings with action items and ownership
- Understanding of the agent vs. tool distinction: agents maintain state, make routing decisions, and manage processes over time
- Connector integration mapping (Gmail for intake, Slack for alerts, Atlassian for matter tracking)
Continue to Lesson 11: Legal Ops Agents; Calendar, Spend, and DSAR ->