Supervision in writing is what separates a firm that can describe its process from a firm that can prove it happened. Supervision that only exists as an idea is not supervision a regulator can verify. It needs to be written down in a way that shows real direction, management, and control, on the specific matter in question, not as a general assurance offered after the fact.
What should supervision in writing actually capture?
The specific instructions given for a task, who reviewed the output, what changes were made before it was used, and who signed off on the final version, exactly the record described in the article on documenting supervision. Each of these elements needs to exist for the specific piece of work, not as a general policy statement covering delegated work in the abstract.
A firm that can produce this record for any file, on request, is demonstrating something a general policy document cannot: that the supervision described actually happened, consistently, on real matters rather than as an aspiration.
Why does this level of detail matter so much?
It is the difference between being able to say supervision happened, and being able to show exactly how it happened on a specific matter, if ever asked, a principle confirmed in Mazur v Charles Russell Speechlys LLP [2026] EWCA Civ 369. The Court of Appeal’s ruling made clear that an unauthorised person can carry out conduct-of-litigation work on behalf of an authorised individual, but only where that individual genuinely retains responsibility, which is precisely what a written record of instruction and review demonstrates.
Without supervision in writing, a firm is relying on the word “supervised” doing a lot of work it can’t actually support if challenged. With it, the firm has something concrete to point to.
How does this fit into daily working practice?
As a natural by-product of instructing and reviewing work properly, not as a separate administrative burden layered on top, exactly as structured on the How It Works page. A case management system that requires sign-off before a task moves to “complete” generates this record automatically; a firm relying on verbal instructions and informal review has to reconstruct it after the fact, which is both slower and less reliable.
Firms using Clio, LEAP, Osprey, or Actionstep are usually well placed to build supervision in writing directly into existing task workflows, since the infrastructure for timestamped assignment and approval already exists within these systems.
What does a well-documented instruction actually look like?
Specific enough that someone reading it months later, with no other context, could understand what was asked and why. “Draft a letter before action” is thinner than “Draft a letter before action addressing the three heads of claim set out in the attached note, for review before it goes to the client.” The second version is supervision in writing that actually demonstrates direction, not just delegation.
This same specificity matters on the review side. A sign-off that simply says “approved” is weaker evidence than one noting what was checked and what, if anything, was changed before the work was relied on.
How does this connect to a firm’s professional indemnity position?
Supervision in writing is also what a firm’s own professional indemnity insurer would expect to see if a claim ever arose from delegated work. Delegated tasks still sit under the instructing firm’s own cover, not any separate arrangement with the provider, and a clear written record of instruction and review is exactly what supports that position if it’s ever tested.
This is one of several reasons the documentation habit is worth building early, rather than treating it as something to assemble only once a problem has already surfaced.
What should a COLP check for across the firm’s outsourced engagements?
That supervision in writing exists consistently, not just on a sample of files chosen to look good in a spot check. A COLP reviewing outsourced work should be able to pick any matter at random and find a written instruction, a reviewed output, and a sign-off, the same standard covered in the article on what to ask before instructing any outsourced provider. Consistency across the full caseload, not just the best examples, is what actually satisfies a regulator.
How does supervision in writing interact with confidentiality obligations?
The two work together rather than separately. A written instruction and review trail confirms who directed and checked the work; the confidentiality terms, covered in the article on what a confidentiality agreement should cover before any file moves, confirm who was authorised to see the underlying information in the first place. A firm’s engagement documentation should address both, since a regulator or insurer reviewing a matter would expect to see each addressed clearly rather than assumed.
According to the SRA Code of Conduct for Firms, firms must have effective systems and controls in place to ensure compliance, and written supervision records are one of the clearest, most checkable ways to demonstrate that a system actually functions rather than existing only on paper.
What’s the realistic starting point for a firm with no formal system yet?
A simple habit: every instruction gets a short written note, every completed task gets a recorded sign-off, and both live somewhere searchable rather than scattered across email threads. This doesn’t need new software or a compliance overhaul. It needs a consistent habit applied to every matter, which is the same discipline covered in the article on the first 30 days of an outsourcing engagement, where this habit is easiest to establish before old, less rigorous patterns take hold.
Does supervision in writing slow down a fast-moving matter?
Not meaningfully, once it’s built into the workflow rather than treated as a separate step. A short, specific instruction takes little longer to write than a vague one, and a recorded sign-off takes seconds if it’s part of the same review a fee earner was already doing before relying on the work. The perception that documentation slows things down usually comes from firms trying to reconstruct records after the fact, covered in the article on how conflicts of interest are avoided in outsourced legal support, rather than firms building the habit in from the start.
Want to see what a fully documented instruction looks like?
We’ll assign a dedicated paralegal to your matter for 7 days, no charge, so you can see the supervision record in practice before deciding anything.
Confidential · No obligation · Typically a 20-minute call
Frequently Asked Questions
Does supervision in writing need to be formal legal drafting?
No. A clear, dated instruction and a recorded sign-off are enough; formality matters far less than consistency and specificity.
Who is responsible for maintaining supervision in writing when work is outsourced?
Primarily the instructing firm, though a well-run provider’s own process should support and evidence the same trail.
Does the Mazur decision change what needs to be recorded in writing?
It reinforces the existing standard rather than creating a new one: retained responsibility needs to be demonstrable, which written instruction and review has always supported.
