Legal Intake: How In-House Teams Structure the First Step

Legal requests arrive through direct email, messaging, meetings, and local spreadsheets. Each route leaves a request outside the department’s shared workload view. The lawyer who should handle a vendor question from a European subsidiary is already managing a similar matter for another entity. The applicable policy sits in a folder no one outside the central team can find. The request either stalls or gets handled inconsistently.

Legal intake fixes this. It is the defined entry point that gets the facts to the right lawyer, in the right entity, with the right context, before real work begins. Understanding what legal intake is, and how to structure it across a multi-entity group, is the starting point for any legal operations model that scales.

What is legal intake for an in-house legal department?

Legal intake is the structured process by which a legal department receives, records, assesses, and routes a new request before any legal work begins. It is not a law firm’s prospective-client screening process. An in-house team already supports the business stakeholders sending requests. Its intake process does not decide whether to take on a client. It decides how the organization should handle a specific request, which lawyer or team should own it, and what information is needed to act.

The distinction matters because in-house intake is a demand management function as much as an administrative one. Without a structured entry point, the department cannot see how many requests concern one entity, which jurisdictions generate recurring work, or where capacity is missing. Intake makes that demand visible and manageable.

How does legal intake start the matter lifecycle?

Intake is the first operational step of the matter lifecycle. Everything downstream depends on it: planning, execution, tracking, and reporting all rely on the quality of what intake captures. A request that arrives without a named entity, a clear objective, or a deadline forces every subsequent step to compensate for what was not collected at the start.

Triage sits inside or immediately after intake

Triage answers the questions that determine what happens next: Is the request urgent? Which legal specialty does it need? What risk does it carry? Who should review it? Once the team accepts defined legal work, a matter record keeps the work and its history in one place. An intake review can end in several ways: the request is assigned to an in-house lawyer, returned for more information, referred to a standard workflow, escalated to senior counsel, or sent to outside counsel. Some requests are logged as issues to monitor rather than opened as full matters. The outcome of triage determines which path applies.

Intake gives legal a view of demand

Without a structured entry point, legal demand stays scattered across inboxes, chats, meetings, and personal memory. The department cannot easily see volume by entity, recurring request types by jurisdiction, or where capacity is under pressure. Intake makes that demand visible at the group level. A global report on matters shows request volume by entity, jurisdiction, category, owner, urgency, and status. It also shows where requests are waiting for information and where local teams receive repeated questions that could be handled by a standard workflow.

How does a request move from submission to planning?

An in-house request moves through a defined sequence: submission, confirmation, information gathering, classification, review, assignment, and handoff. The method of submission matters less than the outcome: one reliable record that names a business owner, a jurisdiction, a risk level, a deadline, a responsible lawyer, and a next step. The first response should confirm receipt, state whether legal needs more information, identify who is reviewing the request, and set a clear timeline for the next update. This stops the same request from being sent to several lawyers at once.

Submission and confirmation establish the record

A form can require basic information before submission. An email can start the process too, but someone must then copy its contents into the department’s intake record. The record should capture the request, its date, its owner, and its supporting documents from the moment it arrives. Missing information should trigger a focused follow-up, not a long exchange about facts the requester has already supplied.

Review turns a request into a plan

After submission, the reviewer works through four checks. First, the matter profile: the affected entity, jurisdiction, request type, deadline, business owner, known risks, related matters, and available documents. Second, classification: legal subject, urgency, complexity, risk, business impact, and the required workflow. A routine request may follow a standard path; a high-risk or time-sensitive one may go straight to senior counsel or a subject-matter expert. Third, capacity: active matters and current availability. A lawyer who handled a similar issue may be the right owner, but existing deadlines may require a different resource. Assigning work the team cannot absorb creates a second problem. Fourth, the internal or external route: whether the work stays in-house or goes to outside counsel. Internal expertise, local law, urgency, workload, strategic importance, and the need for independent advice all bear on that choice. The route and the reason for it should both be recorded.

What should a legal intake form capture?

An intake form should gather enough to assess ownership, urgency, risk, scope, and next steps. It should not ask every requester for the same depth. Conditional questions appear only when the request category makes them relevant. A short opening screen reduces friction for the requester while giving the legal team what it needs for first review.

Core fields for every request

The request basics include the requester’s name, role, department, and contact details; the legal entity or subsidiary involved; the country, regulator, or location connected to the issue; the request type drawn from a defined list; and a short summary of what happened and what legal help is needed. The scope and risk section covers the business objective, the deliverable (advice, contract review, policy approval, risk assessment, negotiation support, or another defined output), the deadline and the reason behind it, known exposure or sensitive data, and supporting documents such as drafts, notices, policies, or correspondence.

Conditional questions reduce friction without losing context

The form should identify the business decision-maker and the internal resources already involved. A vendor request may need procurement and information security. A customer agreement may need the commercial owner, finance, and the local entity representative. Keep the requested deadline separate from the legal deadline: a product launch, a board meeting, a renewal, a filing date, and a court deadline carry different consequences. Conditional questions then collect what each type of work needs. A dispute request may ask for the opposing parties and the court location. A privacy request may ask what data is collected, where it moves, and which entities process it. A contract request may ask for value, term, counterparty, template, and any non-standard provisions.

Who owns each step of the intake process?

Intake is a workflow, not a job title. A specialist can perform defined administrative steps. Legal judgment stays with the lawyer or other authorized legal resource responsible for the decision. Defining ownership before work arrives is what makes the process repeatable.

Lead counsel assesses the legal issue, decides whether specialist input is needed, and takes responsibility for the legal route. The legal operations manager maintains the intake rules, fields, permissions, reports, and the capacity view, and may coordinate dependencies and deadlines on complex work. The requester owns the business facts and the objective: the affected entity, accurate documents, the desired outcome, the decision-maker, and answers to follow-up questions. Legal cannot build a reliable plan around an unclear business objective. The intake specialist can collect information, check completeness, apply approved routing rules, schedule follow-ups, and maintain the record. That role does not extend to giving legal advice, deciding whether a legal position is acceptable, or overriding an escalation rule without counsel approval.

Define screening criteria before work arrives. Set them for risk level, urgency, monetary exposure, regulatory sensitivity, strategic importance, local-law requirements, and any request for an exception to a group policy. A request that crosses a defined threshold should move to counsel review, not sit in administrative screening.

How do legal teams classify requests and route them to owners?

Classification determines routing, and routing needs a named owner. Legal teams sort requests by the factors that change the response they need: risk, urgency, effort, strategic importance, legal specialty, entity, jurisdiction, and business ownership. Routing then links those factors to a named person, team, workflow, or external resource.

Issue log versus matter record

An issue log captures a question, an emerging risk, or a recurring problem that needs monitoring. A matter record fits when the team must manage defined legal work with an owner, tasks, documents, deadlines, approvals, or spend. Not every request that passes through intake becomes a full matter. The classification step determines which applies, and that decision should be recorded with a reason.

Handoff should preserve the full intake context

Whether work stays internal or goes to outside counsel, the handoff should preserve the decision history and everything already collected: the original request, the objective, the category, the urgency, the risk indicators, the deadline, the documents, prior decisions, and the requester’s contact details. If outside counsel receives a request without the entity, jurisdiction, objective, scope, and deadline, the department has passed on the administrative work and kept none of the legal context. The assigned lawyer should not have to search several systems to understand why the work arrived. This is where matter management and intake connect: the intake record becomes the foundation of the matter record.

How do global legal teams create a consistent intake entry point?

Global legal teams need one entry point with controlled local variation. The goal is to standardize the information needed for first review while keeping local rules intact: entity, jurisdiction, ownership, and escalation paths. One operating model, with variation at the local level where the law or the organization requires it.

A shared intake uses common fields for every request: requester, business unit, affected entity, request category, business objective, deadline, risk, and documents. Local fields capture the country, the legal owner, the regulator, the language, local approvals, and the jurisdiction-specific facts needed for assessment. Informal channels create visibility gaps. Requests sent by direct email, messaging, meetings, or local spreadsheets may never reach the global workload view. Map those channels first, before standardizing anything. The map shows where the process depends on personal relationships or local memory rather than a defined workflow.

Define local legal owners and escalation paths before launch. A subsidiary’s request needs a named owner and a clear route to the local lawyer, regional lead, or central expert. The route should state who can approve an exception to a group policy. Every request needs a minimum triage record, even when the final route is local: the requester, the affected entity, the jurisdiction, the issue, the objective, the deadline, the risk indicator, and the next owner. Ask detailed questions only where the category requires them. This is the foundation of a legal project management model that works across borders.

How Alf supports a governed intake workflow

Alf is the operating infrastructure for global legal departments: it connects people, processes, knowledge and AI agents in one governed system. For legal intake, that means a single entry point that works across entities and jurisdictions, where the information collected at submission flows directly into the matter record without manual re-entry or system switching.

Alf’s features designed to support intake include configurable forms and workflows that require no code to set up, conditional fields that adapt to the request category, a shared calendar and deadline alerts, and a chronological history for each dossier from the moment it is started. Access rights can be set by user, group, or dossier, so a subsidiary’s legal owner sees what is relevant to them without accessing the full group workload. The Alf AI agent operates within the context of each dossier, and validations and decisions are logged so the department can respond when leadership or a regulator asks how a request was handled. Dossiers can be started directly from Outlook, keeping requests out of personal inboxes and inside the shared system. Organizations including Air France, SNCF, ENGIE Home Services, and CCI Paris Ile-de-France use Alf to run their legal operations.

The issue isn’t the volume of requests. It’s that the context needed to handle them is scattered across tools, inboxes, and local memory. Alf is built to make that context explicit and shared, so that every request, in every entity, starts from the same governed entry point. Scale legal operations without scaling complexity.

Frequently asked questions

What is legal intake in an in-house legal department?

Legal intake is the structured process by which an in-house legal department receives, records, assesses, and routes a business request before any legal work begins. It is the defined entry point for every request, regardless of how it arrives: by email, form, meeting, or messaging tool. The intake process turns an unstructured request into a record that names a business owner, a jurisdiction, a risk level, a deadline, a responsible lawyer, and a next step.

For a group operating across multiple entities and jurisdictions, intake is also a demand management function. It makes legal workload visible at the group level, shows where capacity is under pressure, and allows the department to apply consistent routing rules while respecting local legal requirements.

How is in-house legal intake different from law firm intake?

A law firm’s intake process handles inquiries from prospective clients. It collects enough information to understand the work, identify the parties, check for conflicts of interest, and decide whether to accept the matter. The firm is deciding whether to take on a new client relationship.

An in-house legal department already supports the business stakeholders sending requests. Its intake process does not decide whether to take on a client. It decides how the organization should handle a specific request: which lawyer or team should own it, whether it stays internal or goes to outside counsel, and what information is needed to act. The in-house intake process is a demand management and routing function, not a client screening function.

Who owns each step of the legal intake process?

Ownership at each intake step must be explicit before work arrives. The business requester owns the facts and the objective. An intake specialist or legal operations team can collect information, check completeness, apply approved routing rules, and maintain the record. Lead counsel or a subject-matter expert assesses the legal issue and determines the review level. Legal operations manages the capacity view and coordinates dependencies on complex work.

The intake specialist’s role does not extend to giving legal advice, deciding whether a legal position is acceptable, or overriding an escalation rule without counsel approval. Define screening criteria for risk level, urgency, monetary exposure, regulatory sensitivity, and exceptions to group policy before requests arrive. A request that crosses a defined threshold should move to counsel review, not remain in administrative screening.

How should a global legal team handle intake across multiple jurisdictions?

The goal is one entry point with controlled local variation. Common fields cover every request: requester, business unit, affected entity, request category, business objective, deadline, risk, and documents. Local fields capture the country, the legal owner, the regulator, the language, local approvals, and the jurisdiction-specific facts needed for assessment. Every request needs a minimum triage record, even when the final route is local.

Before standardizing anything, map where requests currently arrive, including informal channels such as direct email, messaging, meetings, and local spreadsheets. These channels leave requests outside the global workload view and make the process dependent on personal relationships or local memory. Define local legal owners and escalation paths, including who can approve an exception to a group policy, before the shared intake goes live.

How does Alf support a legal intake process across entities?

Alf is designed to provide a single intake entry point that works across entities and jurisdictions. Configurable forms and workflows adapt to the request category without requiring code. Access rights can be set by user, group, or dossier, so each entity’s legal owner sees what is relevant to them. Dossiers can be started directly from Outlook, keeping requests inside the shared system rather than in personal inboxes. Validations and decisions are logged throughout the process.

The information collected at submission flows into the matter record, so the assigned lawyer does not have to search several systems to understand why the work arrived. The Alf AI agent operates within the context of each dossier, and the system works across multiple models. Data is hosted in the European Union, encrypted at rest and in transit, with two-factor authentication and role-based access rights.