Markdown Editor

Legal Matter Intake and Triage Template (CLOC Core 12)

Intake channel and separate urgent routes, intake form fields, risk tiers 1 to 4, service levels, routing by request type, matter log, reporting measures

법무 운영표준CLOC Core 12 (Service Delivery Models, Practice Operations)matterintaketriage

사용법: Use it to give the business one front door to the legal team and route each request to the right resource. Fill the risk tiers and service levels with the general counsel first, matched to real capacity. The main pitfall is a long form that pushes people back to emailing lawyers directly.

미리보기

Legal Matter Intake and Triage: [Legal department or team]

A front door for an in-house legal team: the intake form, the risk tiers, the routing rules that send each request to the right resource, the service levels by tier and the reporting that shows whether the process works. Structure informed by the Service Delivery Models and Practice Operations areas of the CLOC Core 12 (Corporate Legal Operations Consortium, What is Legal Operations guide, August 2020). Replace every [bracketed] value and every row marked Example. This is a documentation format, not legal advice.

Document control

FieldValue
Document ID[LEG-OPS-INT-001]
Version[1.0]
Status[Draft / Approved]
Owner[@legal-operations-manager]
Approved by[@general-counsel]
Intake channel[Form URL / ticket queue / mailbox]
Last updatedYYYY-MM-DD
Next reviewYYYY-MM-DD
Classification[Internal]

Revision history

VersionDateAuthorChange
1.0 (Example)2026-10-30Legal operations managerFirst issue

1. Scope and principles

All requests for legal work from the business go through intake, including contract reviews, advice questions, disputes, regulatory contacts, policy reviews and corporate actions.

Separate routes, not the general queue:

  • Emergencies (dawn raid, arrest, regulator on site, serious incident): call [duty lawyer number] at once.
  • Whistleblowing reports go to the confidential channel in compliance/whistleblowing-policy, never to the general queue.
  • Suspected personal data breaches go to the incident process and privacy counsel (compliance/personal-data-breach-assessment).

Principles: one channel; one owner per matter; tier by risk, not by seniority of the requester; tell the requester what happens next; measure and adjust.

Privilege: requests for legal advice should be addressed to the legal team and marked as such. Whether a communication with in-house counsel is privileged depends on the jurisdiction and the forum; ask legal before sharing advice outside the team.

2. Intake form

FieldMandatoryNotes
Requester name, team, cost centreYesCost centre feeds spend reporting
Request typeYesContract, advice, dispute or claim, regulatory, employment, IP, corporate, policy, other
Short descriptionYesWhat do you need and why
Counterparty or people involvedYes for contracts and disputesUsed for conflicts and sanctions checks
Value at stakeYesContract value or amount in dispute, best estimate
Deadline and reasonYesBusiness deadline, external deadline, or none
DocumentsFor contractsLatest draft in editable format
Regulator, court or government body involvedYesYes or no
Personal data, safety or reputational impactYesYes or no, with one line
Business approverFor contracts above [USD 50,000]Named sponsor

3. Risk tiers

TierCriteria (any one is enough)Typical examples
Tier 1 CriticalRegulator, court or law enforcement involved; threatened claim above [USD 250,000]; safety or serious reputational risk; external deadline within 2 business daysRegulator letter, claim form served, product safety issue
Tier 2 HighContract value above [USD 250,000] or off playbook; new market or product; employment dispute; deadline within 5 business daysEnterprise deal on customer paper, grievance with legal claim risk
Tier 3 StandardContract within playbook; advice question with internal impact; value [USD 50,000] to [USD 250,000]Supplier agreement on our paper, policy question
Tier 4 Self-serveNDA on our template, signed unchanged; value below [USD 50,000]; questions answered by published guidanceMutual NDA, FAQ question

3.1 Service levels

TierAcknowledgeFirst substantive response (Example)Default owner
Tier 11 hour, 24x7 by phone1 business dayDuty lawyer, general counsel informed
Tier 21 business day3 business daysSpecialist lawyer
Tier 31 business day5 business daysContract manager or lawyer
Tier 4AutomaticSelf-serve template or guidance link at once; check within 2 business daysLegal operations

Business days exclude weekends and public holidays where the owner works. The clock starts when the request is complete (all mandatory fields and documents).

4. Routing

Request typeTier 4Tier 3Tier 2Tier 1
ContractTemplate and playbook T0Contract manager (legal-ops/contract-review-playbook)Commercial lawyerHead of commercial legal
AdviceGuidance libraryLawyer on rotaSpecialist lawyerGeneral counsel
Dispute or claimn/aLitigation counselLitigation counsel, consider outside counselGeneral counsel, outside counsel, legal hold (legal-ops/legal-hold-notice)
Regulatoryn/aComplianceRegulatory counselGeneral counsel and outside counsel
EmploymentHR policyEmployment lawyerEmployment lawyerGeneral counsel
Volume work (for example NDAs at scale, contract migration)n/aAlternative legal service provider under frameworkn/an/a

Outside counsel are instructed only under the outside counsel guidelines (legal-ops/outside-counsel-guidelines), with a budget for matters expected to exceed [USD 25,000].

5. Matter log

Matter IDReceivedTypeTierOwnerFirst response dueStatus
MAT-2026-0201 (Example)2026-10-05 (Mon)Regulatory: data protection authority letter1General counsel2026-10-06Open
MAT-2026-0202 (Example)2026-10-06 (Tue)Contract: enterprise customer paper, ACV USD 410,0002Commercial lawyer2026-10-09Open
MAT-2026-0203 (Example)2026-10-08 (Thu)Contract: supplier on our paper, USD 80,0003Contract manager2026-10-15Open
MAT-2026-0204 (Example)2026-10-08 (Thu)Mutual NDA on template4Legal operationsSelf-serveClosed same day

The example due dates assume no public holidays in the period; adjust for local holidays.

6. Reporting and review

MeasureDefinitionTarget (Example)
Volume by type and tierRequests opened per monthTrend only
First response within service levelShare of requests meeting section 3.190%
Cycle timeRequest complete to matter closed, median by typeTrend down
Self-serve shareTier 4 requests closed without a lawyerTrend up
Work sent outsideMatters with outside counsel or providers, and spendWithin budget (legal-ops/legal-spend-budget)
Requester satisfactionShort survey on closure[Target]

Review questions every six months:

  • Which request types grow fastest, and can templates or guidance absorb them?
  • Which tier misses its service level most often, and is it capacity or incomplete requests?
  • Which work could move to a lower-cost resource without raising risk?

Standard and licence note

Structure informed by the CLOC Core 12 functional areas, in particular Service Delivery Models and Practice Operations, as described in the Corporate Legal Operations Consortium guide What is Legal Operations (August 2020), cited by name only; see https://cloc.org/what-is-legal-operations/. No text is copied from CLOC material. Tiers, thresholds and service levels are examples, not values set by CLOC or by any law. The organisation and matters are fictional. All text is original wording. This is a documentation format, not legal advice.

Template licence: MIT.

관련 템플릿