Legal Workflow Mapping: How to Document What Your Firm Actually Does

Jun 19

11 min read

Legal workflow mapping is the disciplined recording of how work moves through a firm, from the first enquiry to the closing of the file, including the steps that no procedures manual mentions. Most firms believe they know how they handle a conveyance, an estate administration or a commercial dispute. Ask three fee earners to describe the same process and the descriptions usually diverge. One records the engagement letter as the first step, another starts with the conflict check, and a third explains that in practice the secretary begins the file before either has happened. The workflow that exists is rarely the workflow that is written down.

The discrepancy matters for reasons that are specific to legal practice. A missed limitation date, an unsigned engagement letter, an unrecorded conflict check or a delay in banking client money is not an operational inefficiency alone; it can amount to professional negligence or a regulatory breach. A firm that cannot say who is responsible for each step, in what order and with what evidence, is unable to show a regulator, an insurer or a court that its systems are adequate. Mapping is therefore a risk management exercise as much as an efficiency one.

This article sets out a practical method for legal workflow mapping, suitable for a solo practitioner or a firm of several partners. It describes what to record, how to gather the information, how to analyse the result and how to convert a map into controls, templates and, where appropriate, software configuration. It does not assume any particular technology, and the method works with a whiteboard and a stack of index cards.

What a workflow map is, and what it is not

A workflow map is a structured description of a repeatable process. It identifies the trigger that starts the process, each step that follows, the person or role who performs it, the inputs and outputs, the decisions that cause the path to branch, the documents created or consulted, and the point at which the process ends. It may be drawn as a flowchart, written as a numbered list or built as a table. The format matters less than the discipline of completeness.

A map differs from a procedures manual, which prescribes what staff should do, and from a checklist, which prompts a person at the moment of action. A map describes and analyses. It supplies the evidence from which a manual and checklists can be written, and it exposes the points at which the actual practice departs from the intended one. Treating the map as a manual from the outset is a common mistake, because it encourages the author to record the process as it ought to be rather than as it is, and the exercise then loses its diagnostic value.

Why practitioners resist mapping, and why the objections fail

Three objections recur. The first is that every matter is different, so no process can be standardised. This confuses variation in substance with variation in procedure. The legal analysis in a contested probate may be unique, but the steps by which the file is opened, the client identified, the conflict cleared, the engagement letter signed, the fee estimate given and the file reviewed are common to every matter of that type. Mapping standardises those steps and leaves the judgement to the practitioner.

The second objection is that the firm is too small to need it. In a small firm, knowledge is held in a few heads, and the departure or illness of one person can halt the practice. A written map is the cheapest protection against that dependency. The third objection is the time required. A first map of a single process, produced by a practitioner and an administrator working together, can usually be completed in a few sessions. The cost of discovering an undocumented process during a regulatory inspection is greater.

Choosing which workflows to map first

A firm should not attempt to map everything at once. A sensible selection applies three tests: frequency, risk and pain. Frequency identifies processes that are repeated often enough for improvement to yield a return. Risk identifies processes where an error would have serious professional consequences. Pain identifies processes that staff find slow, confusing or dependent on one individual.

Processes that commonly score highly on at least one test include:

client intake, conflict checking and engagement;
opening, numbering and closing a matter;
handling client money, from receipt to application and reconciliation;
time recording, billing and collection of fees;
diarising of limitation periods, court deadlines and statutory time limits;
document preparation, review and execution;
file retention, archiving and destruction; and
onboarding and supervision of junior staff and trainee attorneys.

A useful starting point is the process that spans the most people. Intake and engagement usually do, and an error there affects everything that follows. Practitioners often find that a modest improvement in the first few steps of a matter removes problems that had been blamed on later stages.

A method for gathering the facts

The mapping method has four phases: scoping, observation, drafting and validation. Each guards against a characteristic error.

Scoping the process

Define the boundary of the process in a single sentence: where it begins, where it ends and what it covers. For example, the process of residential conveyancing for a purchaser might begin when an enquiry is received and end when the file is archived after completion and the registration of title. A map without a clear boundary expands without limit, and the exercise stalls. Record who owns the process, meaning the person with authority to change it, and who the other participants are.

Observation, not recollection

The most reliable method is to observe the work and to examine the documents it produced, rather than to ask people how they believe it is done. Take three or four recently closed files and walk through each from first to last, noting the date of each document and event. The file reveals when the engagement letter was in fact signed, when the conflict check was recorded, how long each stage took and where the file waited. Then interview the people who did the work, using the file as a prompt. The interview should ask what happened, what was awkward and what the person would do if the usual route was unavailable. Questions about hypothetical or ideal practice should come last.

Drafting the map

Record each step as a short sentence beginning with a verb: receive the enquiry, run the conflict search, issue the engagement letter. For every step, capture the following information:

the actor, expressed as a role rather than a name;
the trigger, meaning what causes the step to start;
the action performed;
the output, whether a document, a record or a decision;
the system or location in which the output is kept;
the expected time, and the actual time observed on the sample files; and
any decision point, with each branch labelled.

Where an actual step differs from what the firm's rules require, record both. Do not correct the map as you draw it. The gaps are the findings.

Validation with the people who do the work

Present the draft to the participants and ask them to mark errors. Staff will correct a map that misrepresents their work more readily than they will volunteer information at the start. A validated map carries the authority of those who must live with it, which is a precondition for any later change.

What to record at each step: a worked example

The following table shows the form of a fragment of a map for the intake stage of a general matter. It is an example of the technique and not a prescription for any firm's process.

Step	Role	Output	Record kept in	Decision or risk
Receive enquiry and record basic details	Administrator	Enquiry record	Client and contact register	Is the enquiry within the firm's practice areas?
Run conflict search against existing clients and adverse parties	Administrator, reviewed by fee earner	Search result with date	Conflict register	Any hit requires partner review before work begins
Verify client identity and record source of funds where required	Fee earner	Identification record	Client file	Compliance with anti money laundering obligations
Prepare and issue engagement letter with fee basis	Fee earner	Signed engagement letter	Matter file	No substantive work before signature, save urgent protective steps recorded in writing
Open matter, assign number and fee earner	Administrator	Matter record	Matter register	Limitation and key dates diarised at opening

Even this short fragment reveals the typical findings. The firm may discover that the conflict search is performed after the engagement letter, that identity verification is recorded in a personal folder rather than on the file, or that limitation dates are diarised by individual fee earners with no second check. Each finding suggests a control, and each control can be added to the map as a step with a named owner.

Analysing the map: bottlenecks, handoffs and rework

A completed map should be examined through four questions.

Where does work wait?

Elapsed time is nearly always larger than working time. A file may take an hour of attention but sit for a week awaiting a signature, a reply or a review. Mark the points on the map where the file waits and ask why. Common causes are dependence on a single approver, requests sent by a channel the recipient does not monitor, and no rule on when a follow up must occur.

Where does responsibility pass from one person to another?

Handoffs are the commonest point of failure. Each passage of a file from a secretary to a fee earner, or from a fee earner to a supervising partner, risks the loss of information and the assumption that the other person will act. Wherever the map shows a handoff, specify what is passed over, in what form and how receipt is confirmed.

Where is work repeated?

Rework arises when the same data is entered twice, a document is redrafted because the first version was based on incomplete instructions, or a task is repeated because the outcome was not recorded. Each repetition is a candidate for a template, a standard form or a single point of data entry.

Where does the process depend on memory?

A step performed only because a particular person remembers it is a latent risk. Examples include renewal of a statutory filing, a chase of an overdue disbursement and the monthly reconciliation of client accounts. Convert each such step into a diarised task with an owner and a trigger.

A simple responsibility matrix, commonly called a RACI, can sharpen this analysis. For each step, identify who is responsible for doing the work, who is accountable for the outcome, who must be consulted and who must be informed. Only one person should be accountable for each step. Where a step has no accountable person, or two, the map has located a defect.

Translating the map into controls and standard documents

A map has value only when it changes how work is done. The conversion has four parts.

Checklists. Convert each stage into a short checklist used at the point of action and retained on the file. A checklist that records who completed each step and when is also the evidence of compliance in a regulatory inspection or an insurer's enquiry.
Templates. Where the map shows that a document is created repeatedly, prepare a controlled template with approved wording and clear fields for the variable items. Version control of templates matters; a superseded engagement letter circulating on a shared drive is a recognised source of error.
Deadlines and reminders. Transfer each time sensitive step into a calendar or task system that sends a prompt to a named person and escalates to a supervisor if it is not completed.
Review points. Specify where supervision occurs, who conducts it, what the reviewer examines and how the review is recorded. Supervision that is not recorded cannot be shown to have occurred.

The firm should also decide the level of discretion that remains with the fee earner. A good process does not remove judgement; it identifies the decisions that call for judgement and limits the steps that need none. Prescribing every action produces a manual that staff ignore.

Preparing for automation and software configuration

Technology applied to an undocumented process tends to reproduce its defects at speed. A firm that has mapped its workflows is far better placed to configure software, because it knows what the system must do. When the map is complete, it can be used to define matter types, required fields, document templates, task lists with default owners and deadlines, approval stages and automated notifications.

The order of work matters. First simplify the process on paper, removing steps that serve no purpose. Secondly, standardise the steps that remain. Only then should the process be automated, and the automation should preserve a human checkpoint at each decision that calls for professional judgement. A conflict search can be automated; the evaluation of a conflict cannot. A reminder that a limitation date approaches can be automated; the decision whether to issue proceedings cannot.

The firm should also decide in advance how it will measure whether the change has worked. Qualitative measures, such as whether files are opened with all required documents, whether engagement letters are signed before work starts and whether reconciliations are completed on time, can be gathered by sampling files. A firm that wishes to track timing may record, for a sample of matters, the elapsed time between defined stages before and after the change. The firm should not adopt a target figure without a reliable baseline from its own records.

Common pitfalls in legal workflow mapping

Mapping the ideal. A map produced in a meeting room from the partners' understanding of the process will omit the workarounds that make it function. Insist on file review.
Excess detail. A map with hundreds of steps becomes unreadable. Group related actions into stages and prepare a more detailed map of a stage only where it presents a risk.
Ignoring exceptions. Urgent matters, repeat clients and matters transferred from another firm follow variations of the standard route. Record the principal exceptions and the rule for each.
No owner. A map that belongs to no one is not updated. Assign a named owner and a review date.
Treating the exercise as a one off. Practice areas change, rules are amended and staff turn over. A firm should review each map at fixed intervals and whenever a significant incident reveals a defect.
Confusing monitoring with surveillance. The purpose is to improve the process, not to penalise individuals. Staff who fear that the map will be used against them will describe the process as they think the firm wants to hear it.

Using the map for supervision, training and regulatory evidence

A validated map is useful beyond process improvement. It supplies the basis for onboarding new staff, who can see in a single document what happens on a matter and who is responsible for each stage. It supports supervision, since a supervising attorney can test whether the steps are being followed by sampling files against the map. It is also evidence of a system. Regulators in many jurisdictions expect a firm to show that it has procedures for the management of conflicts, client money, supervision and complaints, and insurers frequently ask about the controls that surround risk areas. A firm that can produce a current, dated and reviewed map, together with completed checklists from its files, is in a stronger position than one that can only assert that its staff know what to do.

The map also assists in handling complaints and negligence claims. When a client alleges that an instruction was not followed or a deadline missed, the firm can compare what the process required with what the file records. Where the process was followed, the file demonstrates it. Where it was not, the firm learns that early and can notify its insurer and the client in accordance with its professional obligations.

Practical next steps

Select one process to map first, applying the tests of frequency, risk and pain, and name an owner.
Define the boundary of the process in one sentence and list its participants.
Review three or four recently closed files for that process and note the actual sequence and dates.
Interview the people who did the work, using the files as prompts.
Draft the map with the actor, trigger, action, output, record location and decision points for each step, noting every gap between practice and the firm's rules.
Validate the draft with the participants and correct it.
Analyse waits, handoffs, rework and reliance on memory, and decide on the changes to be made.
Convert the changes into checklists, templates, diarised tasks and review points, and train staff in the revised process.
Set a review date, and repeat the exercise for the next process.

Firms should keep the maps, with their version history, in a location accessible to all staff, and should retain superseded versions so that the process in force at the time of any past matter can be shown.

How practice management software supports workflow mapping

Once a firm has recorded its processes, a practice management platform gives them operational form. Legalytech, a cloud platform for matters, clients, documents, billing, e-signature and a contract repository, allows a firm to hold its matter records, templates and task structures in one system, so that the steps on the map correspond to fields, documents and records on each file. Because pricing is per firm with unlimited users, a firm can give every member of staff access to the process without a cost consequence for each additional person.

This article is provided for general information only and does not constitute legal advice. Practitioners should consult the rules of their own jurisdiction and regulator.