The Evidence Problem No Consultant
Will Solve For You

The Morning the Inspector Arrived

You check your emails. Then a shared folder on the server. Then a spreadsheet that Sarah from the compliance team was maintaining — until Sarah left in October. Then a Word document that the previous COLP had started in 2022 and hadn't been updated since. Then your inbox again, because surely there's something in there from the supervisors confirming they'd done their reviews.

Forty-five minutes later, you return to the meeting room with a collection of fragments. An email here. A file note there. A supervision log that covers three months out of twelve, for two fee-earners out of nine.

The inspector writes something in her notepad.

You know what that means.

The Problem Was Never Supervision. It Was Evidence.

Here is the part that nobody talks about openly at Law Society events or in the SRA's own guidance documents, even though it is the most important thing you need to understand about regulatory risk in your firm:

And in the eyes of the SRA, an undocumented supervision event is not a supervision event. The obligation under SRA Code of Conduct for Firms 2019 §7.1 is not simply to supervise. It is to ensure that supervision is genuine, timely, and — critically — evidenced. The word "evidence" carries the full weight of regulatory consequence.

This is the distinction that most compliance approaches get completely wrong. They focus on the activity of compliance and ignore the infrastructure of proof.

This is why firms with good intentions and diligent partners receive the same inspection outcome as firms that never thought about supervision at all. The regulatory system does not reward effort. It rewards evidence.

What You Did Next — and Why It Didn't Work

After a difficult inspection, or after reading a file note from your SRA supervisor, or after attending a compliance seminar where someone mentioned that "supervision records" are a common gap, you did one of two things.

Either you hired a consultant.

Or you subscribed to a compliance SaaS platform.

Both are understandable decisions. Neither of them solved the problem.

The SaaS platforms are closer in spirit — at least they are operational. But they introduce a different set of problems. Your compliance data lives on someone else's infrastructure. Your audit trail is subject to another company's data retention policies. Your fee-earner records are in a third-party database that you cannot directly query, cannot customise, and cannot control. And every month, you pay a subscription fee for the privilege.

There is a question that very few compliance officers ask before signing the contract:

The answer, for most SRA-regulated firms, is yes. And that realisation changes everything.

Look Inward Before You Look Outward

This is the mindset shift that this article asks you to make. It is not dramatic. It does not require you to become a technologist. It simply requires you to ask one question before your next purchase decision:

Most UK law firms already have the foundational components. A database, or access to one. An email system. A practice management tool. The data about your fee-earners, your matters, and your supervisors already exists somewhere in your firm. It is fragmented, unstructured, and unqueryable — but it exists.

The compliance problem is not a data shortage. It is an architecture problem. You have the raw material. What you are missing is the structure that transforms that raw material into evidence.

This principle is the foundation of everything UNUS London builds. Not SaaS. Not consultancy. Database-first compliance infrastructure — deployed on your own stack, owned by your firm, queryable by your team, and producing evidence that belongs entirely to you.

What the SRA Supervision Register Actually Is

The UNUS SRA Supervision Register is the first system in the legal compliance stack. It is not a form. It is not a policy template. It is not a guide to supervision best practice. It is a production-grade PostgreSQL database system that you deploy once and that runs continuously, recording every supervision event for every fee-earner in your firm from the moment it goes live.

When the SRA inspector asks for your supervision records, you do not go looking. You run a query. In under 30 seconds, you produce a complete, timestamped, immutable record of every supervision event — the fee-earner, the matter, the supervisor, the date, the outcome, the actions required, and whether those actions were completed.

What the System Contains

The Infrastructure Belongs to You

This is the part that matters most, and it is the part that is most different from every other compliance solution you have been offered.

The SRA Supervision Register is not a platform. There is no login portal managed by UNUS London. There is no monthly fee gating your access to your own compliance data. There are no data retention clauses in a vendor's terms and conditions that govern what happens to your audit trail.

You deploy this system into your own Supabase project — which is your own PostgreSQL database instance, running on infrastructure you control. Your firm's data never leaves your environment. Your audit trail is yours. Your evidence is yours.

When an SRA inspection team arrives next year, you will not be calling your SaaS vendor's support line asking for an export of your data. You will not be explaining to the inspector that the consultant who built your supervision framework left the industry. You will open a dashboard on your own system, run a query against your own database, and produce evidence that your firm created, your firm owns, and your firm controls.

That is what compliance infrastructure means. And it is built once.

The System in Practice: A Different Tuesday Morning

That four-minute difference is not magic. It is architecture. It is the product of a decision you made — to treat compliance as infrastructure, not as a service you buy from someone else. To look inward at what you already had, and to build the one thing that was missing: structure.

This Is Not a Technology Project. It Is a Governance Decision.

If you are a COLP, an MLRO, or a Practice Manager reading this, you are not being asked to become a database administrator. The SRA Supervision Register is designed to be deployed by a compliance professional working with a basic understanding of database tools — or with minimal IT support. The setup guide maps every step. The workflow is pre-built. The schema is documented against every regulatory obligation it satisfies.

What you are being asked to do is make a governance decision before your next budget sign-off: to ask whether the solution to your evidence problem already exists within your firm's infrastructure, and whether the money you are about to spend on a consultant or a SaaS subscription could instead be invested in building something permanent.

The SRA Supervision Register is Mini Solution 1 in the UNUS London legal compliance stack. It integrates directly with Mini Solution 2 — the Client Matter Checklist Engine — and Mini Solution 3, the SRA Regulatory Readiness Report Generator, which produces a weekly signed-off governance report for the principal solicitor. Together, the three systems give you a compliance infrastructure that most SRA-regulated firms in the UK do not have.