Legal Project Management: Coordinate Work Across Entities | Alf

What is legal project management?

Legal project management is the use of project management methods to plan, run and review a piece of legal work with a defined objective and an end. The Project Management Institute describes project management as applying knowledge, skills, tools and techniques to meet a project’s requirements. Legal project management, often shortened to LPM, adapts that discipline to legal matters, where scope and timing are harder to predict than in most business projects. It gives the team a shared answer to four questions: what are we delivering, by when, with whom and at what cost.

The approach is well established in law firms, where clients ask for predictable fees, and in-house teams now apply it to their own work. Training and certification are available through bodies such as the International Institute of Legal Project Management. An in-house team does not need a certified specialist to benefit. It needs the habit of writing down scope, owners and milestones before the work starts, and of reviewing what happened when it ends.

How does legal project management differ from matter management?

Matter management records and tracks each matter: what exists, where it stands, which documents and deadlines belong to it and what it costs. Legal project management plans and steers a piece of work toward a defined result. The first is a register the department keeps permanently. The second is a method applied to work that has a beginning and an end.

The two complement each other. A project such as rolling out a new supplier code of conduct across eight subsidiaries may involve dozens of matters, each with its own documents and local counsel. Matter management keeps each of them in order. Project management makes sure they add up to the result the group asked for, on the date it was promised. Without the second, every matter can be well kept while the project as a whole runs late.

What are the four phases of a legal project?

A legal project moves through four phases: scope, plan, execute and review. Each phase settles specific questions and produces a short output that the next phase relies on. The table below sets them out for an in-house project that involves several entities.

Scope is where most later problems begin. A project whose boundaries were never written tends to grow — a phenomenon usually called scope creep. Changes are normal in legal work, and the answer is to approve them explicitly and record their effect on dates and budget. The review phase is the one most often skipped, because the team has already moved on. It is also the phase that turns one project into a better template for the next.

What changes when work crosses entities and jurisdictions?

Consider a typical cross-border project. The group decides to roll out a new supplier code of conduct in eight countries by the end of the year. Three months in, four subsidiaries have signed versions, two are waiting for a translation nobody ordered, and group legal hears about it from the procurement director. Four things made this harder: dependencies, responsibilities, validation steps and visibility. Within one team in one country, people settle these informally because they sit together. Across entities and jurisdictions, whatever is not written down is understood differently in each place.

Map the dependencies between entities

List what each entity needs from the others before it can act. A local version may depend on a group template, on a translation, on advice about local law or on a works council consultation where the governing law requires one. Put these dependencies in sequence, since they determine the real timeline. A plan that shows eight parallel country workstreams with no links between them is a list, not a plan, and it will not predict delays.

Name one owner per workstream and per entity

Each workstream needs one person who answers for it, and each entity needs one contact for the project. Shared ownership produces the translation nobody ordered. Write the names in the plan together with what each person may decide alone. Where a law firm handles part of the work, the principles used to coordinate outside counsel apply: a named in-house owner, a written scope and a recorded decision.

Agree on the validation steps before work starts

Decide in advance who validates what. Which changes to the group template can a local team make on its own? Which need group legal, and which need the business sponsor? Fix the answers at the planning stage, with a time limit for each validation. Otherwise approvals become the hidden critical path of the project, and the General Counsel learns about a delay only after it has already occurred.

Give the group one view of status

The General Counsel should be able to see, in one place, where each entity stands and what is blocked. That requires a common definition of each status, so that “done” in one country does not mean “drafted” in another. A short update at fixed intervals, built from the same fields for every entity, is enough. The view should also show decisions and changes, since those explain why the dates moved.

Which legal project management tools do you need?

You need fewer legal project management tools than the market suggests: a shared plan, a shared record of the work, a calendar of deadlines, a way to route approvals and a status report. Many teams start with a spreadsheet and a general-purpose project tool, and that can carry a first project. The limits appear when the plan is disconnected from the matters, the documents and the people allowed to see them.

When you compare options, look at how each one handles the points that matter in a group. Can a task be linked to an entity, a jurisdiction and a matter? Do permissions follow the sensitivity of the work? Is there a history of who validated what? Does the calendar alert the owner and someone else if the owner does not act? A collection of tools is not an operating model, and a project plan in one tool with documents in a second and approvals in email recreates the fragmentation the project was meant to control. The person best placed to make this choice is usually the legal operations manager.

Where do AI agents fit in a legal project?

AI agents fit in the repetitive parts of a project: preparing a first draft of a local version, extracting dates and obligations, summarizing status across workstreams. They are useful to the extent that they work within the project’s rules. An agent should see only the matters it is permitted to see, and its output should pass through the same validation steps as a person’s work.

Plan this at the planning stage, like any other resource. State which tasks an agent may perform, on which data and who reviews the result. Record the review, so that the project file shows which outputs were checked and by whom. Treated this way, agents add capacity to a project without adding a new source of uncertainty about who did what. The more autonomous AI becomes, the more organizational context matters.

How Alf supports cross-entity legal projects

Alf is the operating infrastructure for global legal departments: it connects people, processes, knowledge and AI agents in one governed system. In Alf, each matter is handled in a dossier with its documents, its deadlines and a chronological history of every action and decision. Workflows and forms are configurable without code, so the validation steps agreed at the planning stage become the actual path the work follows. Features include approval workflows, a shared calendar with deadline alerts, access permissions at user, group or dossier level, document generation from templates and activity reports. For a cross-entity project, this gives the plan a direct link to the work it describes. The page on case management shows how matters are structured inside the system.

Alf also supports AI agents that operate within the context of each dossier — knowing what they are permitted to see, up to which threshold they may act and when a human must review the output. Validations and decisions are logged, so when a regulator, a client or leadership asks how AI was used on a matter, the record is there. Organizations including Air France, SNCF and ENGIE Home Services use Alf to run their legal operations across entities. The goal is to scale legal operations without scaling complexity. Legal project management does not require a large method or a new job title to start — only one project whose scope and owners are written on a single page and reviewed when it closes.

Frequently asked questions

Is legal project management only for litigation and M&A?

No. Large disputes and transactions are where the method became visible, because their budgets and timelines are large enough to make the absence of structure painful. The same discipline applies to any legal work with several steps, several contributors and a defined result.

In-house, typical candidates include policy rollouts, contract template updates across entities, the legal integration of a new subsidiary and regulatory compliance programs. What they share is a defined result, a deadline and contributors in several countries.

Do we need a dedicated legal project manager?

Not to begin with. A lawyer or a legal operations professional can lead a project if the role is explicit and time is set aside for it. The essential point is that one person is responsible for the plan, the status and the escalation when something is blocked.

A dedicated role makes sense when the department runs several cross-border projects at once. At that stage, coordination is a full-time activity. Some groups place the role within legal operations so that methods and templates are shared across projects rather than rebuilt each time.

What is scope creep in legal work, and how do we limit it?

Scope creep is the gradual expansion of a project beyond what was agreed, without a decision to expand it. In legal work it often comes from reasonable requests: one more jurisdiction, one more contract type, one more review round. Each addition seems small; together they move the deadline and the budget.

Limit it by writing the scope down, including what is explicitly excluded. When a new request arrives, treat it as a change: assess its effect on time and budget, and have the sponsor approve it explicitly. The project may still grow, and it will grow by decision rather than by accumulation.

How does legal project management help control outside counsel costs?

It makes the scope explicit before the firm starts. A written scope, with assumptions and deliverables, is the basis for a fixed or capped fee and for any discussion when the work changes. Without it, both sides argue from memory about what was originally agreed.

During the project, a change log shows which additional work was requested and approved. At the end, comparing the estimate with the actual result improves the next brief. The benefit is predictability more than a lower rate: the group knows what it is buying and can hold the firm to it.

How is legal project management different from legal operations?

Legal operations is the function that organizes how the department works over time: processes, tools, vendors, data and governance. Legal project management is a method for delivering a specific piece of work with a defined scope and end date. Project management is commonly listed among the domains that legal operations covers, alongside knowledge management, financial management and technology.

The two reinforce each other. Legal operations provides the templates, the tools and the rules that projects use. Each project, in turn, tests those rules in practice and shows where they need to change. A department that runs projects well generates the feedback that makes its operating model better over time.