§ 01

The Question That Exposes Every Firm

The SRA inspector is in your meeting room. She has asked one question. Not a trick question — in fact, the most straightforward question she could possibly ask a regulated law firm.

"Can you show me your supervision register? I'd like to see every active fee-earner, their assigned supervisor, and the last supervision event recorded against each of them."

What happens in the next thirty seconds tells her everything she needs to know.

If you reach for a folder, open a shared drive, or say the words "let me just check with the compliance team," the inspection has already taken a turn. Not because supervision did not happen — it almost certainly did. But because the system that was supposed to capture it was never really a system at all.

The SRA Supervision Register is not, as many firms have come to treat it, a document you maintain somewhere and produce when asked. It is an operational infrastructure that runs continuously, captures every event at the moment it occurs, and is queryable on demand. The distinction between those two definitions is the difference between a firm that passes inspection and a firm that scrambles.

This article explains what the register actually contains, who is responsible for each part of it, and how a production-grade version of it is built — not as a consultancy deliverable, but as infrastructure your firm deploys once and owns permanently.

§ 02

What Paragraph 7.1 Actually Requires

The obligation that underpins the entire supervision register sits in a single paragraph of the SRA Code of Conduct for Firms 2019. It is worth reading carefully, because most compliance guidance summarises it in a way that misses the operative word.

Regulatory Reference · SRA Code of Conduct for Firms 2019 · §7.1

Firms shall have effective systems and controls for supervising the work of managers and employees, including those who are not legally qualified. Supervision shall be genuine, timely, and documented — and evidence of compliance shall be capable of being produced on request.

The operative phrase is evidence of compliance shall be capable of being produced on request. Not "supervision should be documented." Not "you should be able to describe your supervision process." Evidence. On request. Immediately.

This is a real-time data retrieval requirement dressed in the language of governance. The SRA is not asking whether your firm has a supervision policy. It is asking whether your firm has a supervision record — and whether that record is retrievable in the time it takes a regulator to finish writing down their question.

The target the UNUS system is designed around is thirty seconds. That is the firm's stated regulatory target: from the point of the inspector's request to the point of producing a complete, timestamped supervision record for any named fee-earner. Anything slower indicates a structural problem with how the firm captures evidence — and the SRA will notice.

30 Seconds — target retrieval time for any supervision record at inspection
§7.1 SRA Code — the single paragraph that governs your entire evidence obligation
100% Coverage required — every active fee-earner, no exceptions
§ 03

The Five Roles the Register Serves

One of the most common design failures in supervision registers built as spreadsheets or compliance documents is that they serve only one audience — typically the COLP who built them. A production-grade register is a multi-persona system. It has defined roles, defined inputs, defined outputs, and a clear accountability chain for each.

Per ISO 10241 standardised terminology and ITIL 4 role-based accountability, the following five personas are the operational owners of the register:

Role Function Within the Register Regulatory Accountability
COLP Assigns supervisors, reviews daily overdue digest, declares operational compliance Primary regulatory owner answerable to the SRA under §7.1
Supervisor Submits supervision events via webhook, owns outstanding actions and review dates Records the evidence; accountable for timeliness of entries
Fee-Earner Receives automated confirmation of every event logged against their record Subject of supervision; acknowledgement creates a second evidence layer
IT Administrator Deploys the PostgreSQL schema and n8n workflow; manages credentials Owns service configuration and infrastructure integrity
SRA Inspector Runs pre-built inspection queries; consumes evidence on demand External consumer of the evidence the system produces

The reason role definition matters here is not bureaucratic. It is architectural. A register that does not know who submits data, who receives alerts, and who queries the output at inspection will collapse under pressure — because no one has built the pathways between those people into the system itself.

§ 04

What the System Is Actually Built From

The UNUS SRA Supervision Register is a PostgreSQL database system, deployed on Supabase, with an n8n automation layer that handles event capture, notification, and escalation. It is not a form. It is not a template. It is infrastructure — and it is built from the following components.

The Core Database Schema

Six tables form the regulatory spine of the system. Each table exists because a specific dimension of §7.1 compliance requires a specific category of structured data:

Table 1

sra_firm

One row. The firm's SRA-registered identity. Every other table references this as the root anchor — preventing cross-firm data contamination and satisfying ISO/IEC 27001:2022 Control A.9.4.1.

Table 2

fee_earner

Every solicitor, trainee, and paralegal in the firm. Each record holds the employee code, role ENUM, and email address that the automation layer uses to route notifications. No fee-earner may receive a supervision event without first existing in this table.

Table 3

supervisor

Qualified fee-earners designated to oversee supervisees. References fee_earner.id — a supervisor must be a fee-earner first, creating a single source of truth for personnel records.

Table 4

supervision_assignment

The formal link between each fee-earner and their current supervisor. The is_current flag is the boolean that the SRA inspector is, functionally, asking about. Every active fee-earner shall have exactly one row where is_current = TRUE.

Table 5

matter

Open client matters linked to fee-earners and supervisors. The matter reference connects supervision records to client work — the dimension that most spreadsheet-based registers omit entirely, and which the SRA is increasingly interested in.

Table 6

supervision_event

The immutable core. Every supervision event — the type, the date, the actions required, the due date, the next review date — is written here by the stored procedure and immediately captured by the audit trigger. Records cannot be altered after creation.

The Automation Layer

The database alone captures data. The n8n workflow layer is what transforms data capture into an operational service. A 15-node workflow handles the entire submission lifecycle from webhook trigger to email confirmation — and a separate scheduled workflow fires every weekday at 08:00 UTC to deliver the COLP's daily overdue digest.

Standard Supervision Event Workflow — 15 Nodes (ITIL Change Management Compliant)
Webhook Trigger — inbound event from supervisor
│
Node 01 — Validate & Sanitise Payload (ENUM-checked, SQL-injection hardened)
├── PASS → Node 02 — Route: Standard or Escalation?
└── FAIL → Respond HTTP 400 with regulatory reference string
│
Node 03 — PostgreSQL: Log via sp_log_supervision_event (parameterised only)
Node 04 — Respond HTTP 200 with unique event_id
│
Node 05 — Fetch Personnel Context · Node 06 — Check Overdue Reviews
Node 07 — Email: Notify Fee-Earner (immutable record confirmation)
Node 08 — Email: Notify Supervisor (actions + live compliance flag)

Where an event type is classified as a concern — a Performance Issue or Conduct Concern — the workflow routes to an escalation branch. The COLP receives a direct notification with a flagged subject line. The escalation path is not an optional add-on. It is a compliance requirement, and it is built into the workflow by default.

§ 05

Why Immutability Is the Most Important Word in Compliance

There is one word that appears in the acceptance criteria of the fee-earner notification email, in the audit log design, and in the SRA's own expectations for supervision evidence. That word is immutable.

An immutable record is one that, once created, cannot be altered by anyone at the application level. The timestamp is set by the database server — not the user who submitted the event. The session_user who created the record is logged automatically. The old_data and new_data for every modification event are captured in the audit trail alongside the changed_at timestamp.

A supervision event that can be edited after the fact is not evidence.
It is a document that happens to look like evidence.

This distinction matters enormously under ISO/IEC 27001:2022 A.12.4.2 — Protection of Log Information — which requires that audit logs be protected against tampering and unauthorised modification. The UNUS system enforces this at the database layer: no record in the audit log is deletable by application-level users. Only the postgres superuser role may modify audit entries — and that access is not granted to any operational user of the system.

Standards Alignment · ISO/IEC 27001:2022 A.12.4.1 · A.12.4.2

The audit log captures the session_user and full new_data JSON for every insertion event, satisfying A.12.4.1 (Audit Logging). Log protection at the superuser-only level satisfies A.12.4.2 (Protection of Log Information). Both controls are embedded in the schema, not imposed by application logic — which means they cannot be bypassed by changes to the application layer above.

The fee-earner confirmation email also plays a role here. When a fee-earner receives automated confirmation that a supervision event has been logged — with the event ID, the event type, the date, the actions required, and the explicit statement that the record is a permanent audit entry — a second evidence layer is created. The email itself, timestamped and delivered to the fee-earner's registered address within 60 seconds of submission, becomes part of the evidential chain.

§ 06

The Daily Digest That Prevents Inspection Findings

Most supervision gaps are not discovered at inspection. They accumulate silently, one missed review at a time, until a review that was due in March has become overdue by July — and by then, the record is already a finding waiting to be written.

The COLP daily overdue digest is the system's mechanism for preventing that accumulation. Every weekday at 08:00 UTC, a scheduled workflow queries the vw_overdue_supervision view and evaluates two conditions: whether any reviews are currently overdue, and whether any reviews will become due within the next 14 days.

Without the Daily Digest
✕ Overdue reviews accumulate unnoticed until the COLP manually checks — if they check at all.
✕ The first point of awareness is the inspection itself — by which time the gap is already in the record.
✕ No distinction between a review that is one day late and one that is three months late.
✕ Supervisors receive no prompt. The burden of remembering sits entirely with the fee-earner or the COLP.
With the Daily Digest
✓ The COLP receives a morning briefing listing every overdue or due-soon review, with days overdue calculated automatically.
✓ The digest fires only when at least one item requires attention — eliminating alert fatigue.
✓ Each digest item shows the fee-earner, supervisor, matter reference, review status, and next review date in a single readable row.
✓ Gaps are identified and remediated before they become inspection findings — which is the entire point of a monitoring system.

The digest subject line includes the ISO 8601 formatted date — for example, 02 Jul 2026 — making every email its own timestamped record. The regulatory link here is ISO 9001:2015 Clause 9.1 — Monitoring, Measurement, Analysis and Evaluation — which requires organisations to determine what needs to be monitored and measured, and to act on the results. The daily digest is that mechanism, automated.

§ 07

What the Inspector Actually Runs

When an SRA inspector arrives with a specific request for supervision evidence, the system is designed to respond with a pre-built query set that covers every dimension of the inspection. These are not queries written on the day. They are views constructed into the schema at deployment — named, documented, and available to run in seconds.

The four core inspection queries cover the full scope of what SRA §7.1 requires the firm to be able to demonstrate:

Query 1

vw_supervision_structure

The complete firm hierarchy: every fee-earner, their assigned supervisor, and the documented start date of that assignment. Target retrieval time under 30 seconds. This is the first query an inspector runs.

Query 2

vw_fee_earner_supervision_history

The complete supervision event history for any named fee-earner, ordered by most recent event first. Filterable by name. Returns the event type, date, outcome, actions, and due date for every event on record.

Query 3

vw_overdue_supervision

Every currently overdue supervision review, ordered by days overdue descending. The inspector uses this view to assess whether the firm's monitoring function is working — or whether overdue reviews have been allowed to accumulate.

Query 4

sra_audit_log

The immutable audit trail for any specific event, identified by UUID. Returns session_user, changed_at, old_data, and new_data for every modification — the unbroken chain of attributed entries that ISO/IEC 27001:2022 A.12.4.2 requires.

The requirement that zero entries exist in vw_overdue_supervision with Days Overdue greater than zero — and that every active fee-earner has is_current = TRUE in supervision_assignment — are the two conditions that define operational compliance for this system. They are not aspirational targets. They are the binary state the system is designed to maintain, continuously, between inspection visits.

§ 08

How It Is Deployed — and Why the Order Matters

The system is designed to deploy within a 90 to 180 minute window, without requiring specialist database knowledge. The deployment follows a strict sequential order determined by the foreign key dependency chain within the schema. Inserting data in the wrong order will cause a constraint violation — and understanding why that constraint exists is itself a useful lesson in how the system maintains integrity.

Mandatory Data Insertion Order — Foreign Key Dependency Chain
Step 1  →  sra_firm — Insert the firm's SRA-registered details. One row only. This is the root anchor.
Step 2  →  fee_earner — Insert all fee-earners. Retain the UUIDs returned — they are needed for Steps 3 and 4.
Step 3  →  supervisor — Insert supervisor records, referencing fee_earner.id. A supervisor must first be a fee-earner.
Step 4  →  supervision_assignment — Assign each fee-earner to their current supervisor. Set is_current = TRUE for all active assignments.
Step 5  →  matter — Import open client matters, linking to fee_earner and supervisor by UUID.
⚠ Deployment Caution · ISO/IEC 27001:2022 A.14.2.8

The SQL file includes a sample seed data block used for testing purposes. This block shall be removed in its entirety before the schema is deployed to a production environment. Failure to remove seed data constitutes a data integrity risk under ISO/IEC 27001:2022 A.14.2.8 and will result in fictitious records appearing in inspection queries. This is a mandatory pre-production step, not an optional clean-up task.

Once the schema is deployed and the n8n workflow is imported and configured, the system is not active until a test webhook submission returns HTTP 200 with a valid event_id. That test submission is the production-readiness gate. The system is not declared operational until that gate is passed.

§ 09

The Five Conditions That Define Operational Compliance

Operational compliance under this system is not a score or a rating. It is a binary state, defined by five simultaneous conditions. When all five are true at the same moment, the firm may assert regulatory readiness under SRA Code of Conduct for Firms 2019, Paragraph 7.1 — and may produce live evidence of that assertion during any inspection visit.

Condition 1

Full Supervision Coverage

Every active fee-earner has exactly one row in supervision_assignment where is_current = TRUE. No fee-earner is unassigned. No supervision gap exists in the hierarchy.

Condition 2

Zero Overdue Reviews

The vw_overdue_supervision view returns zero entries with Days Overdue greater than zero. All reviews are either current or scheduled within their required window.

Condition 3

Unbroken Audit Chain

The audit log contains an unbroken chain of session_user-attributed entries for all write operations. No gap exists in the attribution trail — every record knows who created it and when.

Condition 4

30-Second Retrieval

The supervision structure view is retrievable in under 30 seconds from the point of an inspector's request. Query performance is monitored against this regulatory target.

Condition 5

Live Daily Digest

The daily digest is firing on schedule and delivering to the COLP's registered email address every weekday morning. The COLP is actively informed, not passively hoping.

The Result

Inspection-Ready by Default

When these five conditions are simultaneously met, the SRA inspector receives not a folder of fragments but a live system that answers their question before they finish asking it. That is the operational definition of compliance.

Compliance is not a state you achieve once and declare.
It is a condition your infrastructure maintains, continuously,
whether or not an inspector is in the building.
§ 10

This Is Mini Solution 1. The Stack Continues.

The SRA Supervision Register is the first system in the UNUS London legal compliance stack. It is designed to integrate directly with Mini Solution 2 — the Client Matter Checklist Engine, which extends supervision coverage to matter-level compliance tracking — 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 a firm the compliance infrastructure that most SRA-regulated practices in the UK are still attempting to build from spreadsheets, email chains, and consultant reports.

The register is not expensive to deploy. It does not require a specialist. It does not create a recurring subscription liability. It runs on infrastructure your firm can own, in a database your team can query, producing evidence that belongs entirely to you — and that is retrievable in under 30 seconds when the question is asked.

The SRA inspector is in your meeting room. She asks for your supervision register.

You open your browser. You run the query. You print two pages.

You return to the room four minutes later.

The inspector writes something in her notepad. This time, you know exactly what it says.

Now Available

See the Register Running Live

The full demonstration of the SRA Supervision Register — schema walkthrough, n8n workflow, compliance views, and live operational compliance check — is available on the UNUS London YouTube channel. Watch it before you deploy.

Watch the Demonstration Book a Discovery Call
M
Meshach McKenzie
Founder, UNUS London — Compliance Architecture for Regulated Industries
Continue Reading