Section 1
The artifact: the fill-in SOP template
Every delegable compliance task fits one template. Fill it in once per task and you have converted head-knowledge into a procedure a junior can run. The design goal is penalty-proofing: build in the checks and the escalation points so a mistake gets caught before it becomes a fine. SOP: [Task name] Two fields do the penalty-proofing. Escalation points are the safety valve: they name the specific moments where a judgment call appears, and they instruct the doer to stop and route it up rather than guess. A junior filing a routine return is safe; a junior deciding whether an unusual transaction is taxable is not, so the SOP says "if the transaction is not on the standard list, stop and ask." Definition of done is the catch: it forces evidence, a filed confirmation, a reference number, a checked box, so "I think I did it" is never good enough. Here is the same template filled for a common task, as a model: SOP: Monthly receipt capture and pre-close
Section 2
The artifact: the fill-in SOP template (continued)
Section 3
The artifact: the delegation RACI table
An SOP tells one person how to do one task. A RACI table tells everyone who does what across all the tasks, and it is what stops delegation from turning into abdication. RACI stands for Responsible (does the work), Accountable (answers for it, one person only), Consulted (gives input), Informed (kept in the loop). The trap owners fear, handing off a task and having it silently fail, is exactly what a clear Accountable column prevents: the owner stays accountable even when a junior is responsible. Notice the Accountable column is the owner on every row, including the rows a junior or the advisor is responsible for. That is the point. Delegating the work does not delegate the accountability. The owner still confirms it happened. What the owner stops doing is the work itself.
Section 4
The three-question delegation test
Not every task is safe to hand down. Before you write an SOP for a task, run it through three questions. • Is the procedure stable. If the task is done the same way every time, it can be written as an SOP. If it changes with circumstances in ways that need expertise each time, it is judgment work and does not delegate cleanly to a junior. • Are the judgment points isolable. Can you name the specific moments where a decision is required and route them to escalation, leaving the rest as procedure. If judgment is threaded through every step, the task stays with someone who has that judgment. If judgment appears at two or three named points, the junior runs the procedure and escalates those points. • Is failure catchable before penalty. Is there a definition-of-done check and a review step that catches an error before it becomes a fine or an assessment. If yes, the task is penalty-proofed for delegation. If a mistake would go straight to a penalty with no catch, add a review step before you hand it down or keep it. A task that passes all three, stable procedure, isolable judgment, catchable failure, is safe to delegate with an SOP. A task that fails one is either kept, kept with added checks, or routed to a specialist rather than a junior.
Section 5
Worked shape: an owner hands down the stack
Take an owner who does all the compliance admin himself because "a junior would get it wrong." He runs the delegation test across his stack. Receipt capture, invoice issuing, calendar upkeep, and document archiving all pass: stable procedures, judgment isolable to a few escalation points, failure catchable at a review step. He writes an SOP for each and assigns them to a junior, staying Accountable on every row of the RACI. VAT return filing and annual accounts fail the test, judgment threaded throughout, so those stay with the Steuerberater, with the owner Accountable and Informed. Payroll prep passes with an added check, so the junior preps and the owner confirms before it goes to the provider. Within a month the owner has moved four tasks off his desk to a person costing a fraction of his time, kept the two genuinely expert tasks with the expert, and retained accountability on all of them. Nothing blew up, because the SOPs isolated the judgment and the review steps caught errors before they became penalties. The work he kept is now only the work that genuinely needed him, which was always a small slice of the stack he had been carrying whole.
Section 6
The models under the kit
Two disciplines sit under the templates. The first is a task-decomposition read from operations: a task that looks indivisible usually is not. Break it into procedure and judgment, and the procedure, typically the bulk of the hours, can move to a cheaper resource while the judgment, typically a few decision points, stays with the expert. The SOP's escalation field is where the decomposition lives. Delegation fails when owners treat the task as one lump and conclude the whole thing is too risky to hand off. The second is a RACI/accountability read on organization design. Delegation collapses into either micromanagement or abdication when the roles are unstated. Naming exactly one Accountable person per task, and keeping it the owner for compliance, resolves the fear that drives owners to hoard the work: they can hand off responsibility without handing off accountability, which is the specific thing they were unwilling to lose. The structure makes the handoff safe, so the reluctance to delegate loses its basis.
Section 7
What the kit cannot see
It cannot substitute for a competent junior. An SOP makes a task learnable; it does not make an unreliable person reliable. The kit assumes you have, or will hire, someone who follows a written procedure and escalates when told to. If you do not, the constraint is hiring, not delegation design. It also cannot delegate the tasks the rules reserve for a qualified professional. Some filings must be done by, or under, a Steuerberater or another qualified party, and no SOP moves those to a junior; the RACI routes them correctly rather than pretending they are delegable. And it depends on your escalation points being complete: if you miss a judgment point when writing the SOP, a junior will run past it, so the first few cycles need the owner reviewing closely to find the escalation points the first draft missed. Treat the initial SOPs as drafts to harden through use, not as finished the moment they are written.
Section 8
The fitness test
You have built a real delegation kit if every recurring compliance task that passes the three-question test has an SOP with numbered steps, named escalation points, and a definition of done, a RACI table names exactly one Accountable person, the owner, for each task, and the judgment-heavy tasks are routed to the specialist rather than pushed onto a junior who cannot carry them. You have not, if compliance still lives in your head and on your desk because "a junior would get it wrong." Most of it is procedure, and procedure written down with isolated escalation points and a review step is safe to hand to a cheaper person. Keep the judgment. Delegate the procedure. Stay accountable for both. The work that genuinely needs you is a small slice of the stack you have been carrying whole.