Processes & continuity

Your firm should not lose its memory when someone resigns

When knowledge lives in one person’s head, a staff change can become an operational reset.

STARK · 2 October 2026

A resignation should not erase the process

A capable employee remembers the exceptions. They know which attorney prefers which booking arrangement, which client is waiting for a reply and which prospect needs another call. Their experience makes the operation easier—until everyone realises that the process exists mostly in that employee’s head.

Staff changes happen. What makes them disruptive is having to reconstruct the work at the same time as replacing the person. A firm needs shared records and usable instructions before a handover becomes urgent.

Capture decisions people need to repeat

Useful SOPs describe the work as it happens: what starts the task, what information is needed, who owns it, what a completed step looks like and when it must be escalated. Include the recurring exceptions that an experienced colleague handles without thinking.

A document alone is not enough. Connect those instructions to the live work. Someone responding to a client request should be able to find the relevant context, current owner and approved next action without interviewing three colleagues.

Shared visibility supports a handover

The existing-client view below illustrates how open requests can be organised by matter, request type, assignment and status. It gives a replacement colleague a starting point. It does not replace the underlying records or the need to check what was communicated.

Avoid making clients restart their story because the employee they knew has left. Preserve the conversation and route it to the appropriate person, with permissions that reflect the sensitivity of the information.

The existing-client demonstration brings request ownership, matter context and status into a shared operational view. Demonstration data; not client results. Select the image to view it at full size.

A practical check for your firm

STARK begins by helping refine processes and SOPs before building automation. The support team is trained on the firm’s agreed process, so the operation can retain what people learn rather than repeatedly paying to rediscover it.

Choose a recurring task and ask a second colleague to follow its instructions.
Record the exceptions they had to ask someone else to explain.
Make outstanding work visible by owner and next action.
Review access and responsibility when a role changes.