Mersal The Approval Queue
Supervision at the point of consequence
A partnership carries the liability for everything the firm does. The name on the door answers for the work, whoever performed it. This is the professional bargain, and it does not change when the firm grows past the point where one person can watch every file.
The instinct, when the firm grows, is to watch harder. Longer status meetings. A partner copied on every message. This is supervision as surveillance, and it fails in both directions. Associates learn to perform activity rather than exercise judgment. Partners drown in visibility they cannot act on. The work slows, and the risk does not fall.
Structured approval solves the same problem from the other end. Instead of watching everything, a partner is asked to release the few decisions that carry consequence. The associate does the work. The partner authorizes the moment it becomes real.
What belongs in the queue
The test is simple. An action belongs in the approval queue when reversing it is expensive, when it binds the firm to an outsider, or when it commits the firm's professional judgment. Everything else should flow freely, because a gate on trivial work teaches people to route around gates.
Three moments almost always qualify:
- Opening a matter, because the firm accepts a duty and a potential conflict the instant it does.
- Issuing an invoice, because a serial number, once assigned, is a fixed statement about money owed.
- Releasing a document or filing under the firm's name.
In Mersal, associates cannot activate a matter alone; the role gate is enforced at the database, not merely in the interface, so it cannot be clicked past. Drafting, research, correspondence prep and task work carry no gate at all. Preparation is the associate's to run.
The release is the record
An approval that leaves no trace is a conversation, not a control. What makes structured release worth the friction is that the release itself is written down: who authorized, what they authorized, and when. Months later, when a client or an auditor asks how a matter came to be opened, the answer is a line in the record rather than a memory.
Mersal writes partner authorizations to an append-only audit ledger that database triggers protect from edit or deletion, for every role including administrators. The approval cannot be quietly rewritten after the fact, which is the only condition under which an approval means anything.
A queue is not a cage. It marks the short list of moments where the firm's name is actually at stake and asks a partner to stand behind them, then leaves the rest of the day alone. Done well, the associate gains room to work and the partner gains a record instead of a worry. That is the difference between a firm that is supervised and a firm that is merely watched. Trust is not the absence of a check; it is knowing exactly where the checks are.
Matters, conflicts, VAT billing, sealed receipts and the docket, in one defensible system.