Desktop Procedures in Banking That Survive a Handover

Desktop Procedures That Survive a Handover

42% of institutional knowledge is unique to one person. Desktop procedures a newcomer can follow keep bank operations stable after a handover.

Alexander Kiel

Business Analyst · Banking & Wealth Management

16.10.2025 · 8 MIN READ · PROCESS OPTIMISATION

ON THIS PAGE

1. Find Knowledge Held by One Person

2. Write Desktop Procedures for a Newcomer

3. Record Exceptions and Judgement Calls

4. Test With a Newcomer

5. Give Each Procedure an Owner

6. Plan the Handover Period

Sample case: Knight Capital

In short

FAQ

When an experienced employee leaves, much of what they know leaves too. A Panopto survey of US workers found that 42% of institutional knowledge is unique to the individual. Employees already spend 5.3 hours a week waiting for help or insights from colleagues. Desktop procedures are meant to close that gap before the next handover.

German supervisors expect them. MaRisk requires banks to run their business on written organisational guidelines such as manuals, work instructions or workflow descriptions. It also states that the absence, resignation or departure of staff should not lead to a persistent operational disruption.

Yet many desktop procedures are written once, stored in a shared folder and never opened again. Could a new colleague in your team run tomorrow's process from the documents alone?

Illustrative example of 40 recurring tasks in an operations team: 26 have a desktop procedure, 15 were updated after the last process change and only 8 have been tested by someone new to the task

STEP 1

Find Knowledge Held by One Person

Start with the people, not the documents. List every recurring task in your team and mark who can do it today without help. Tasks that only one person can perform, or that only one person understands when something breaks, are your key person risks. In older structures, I have often found key knowledge held by one person who shares only half of it, because they see the rest as obvious. Rank them by what a missed day would cost: late payments, failed reconciliations or missed regulatory deadlines.

In the Panopto survey, 60% of respondents found it difficult to get vital job information from colleagues. Gallup estimates that replacing an employee can cost one-half to two times their annual salary. MaRisk adds that staff members and their deputies shall possess the expertise and experience needed, so a deputy who has never done the task does not count.

✓

List every recurring task and who can do it alone

✓

Mark tasks with only one trained person as key person risks

✓

Rank those tasks by the cost of one missed day

Which tasks in your team would stop tomorrow if one colleague called in sick?

Keep in mind: A name in the deputy column is not cover. Ask when the deputy last performed the task on their own.

STEP 2

Write Desktop Procedures for a Newcomer

Write each procedure for someone who knows the bank but not this task. Use one numbered action per line and name the exact system screen and field. Show what a correct result looks like. Put the purpose and the cut-off time at the top, so the reader knows why the task matters before the first click.

Readers scan rather than read. Jakob Nielsen found that on an average web page users read at most 28% of the words, with 20% more likely. New hires in the Panopto survey spent up to 3.5 months learning on their own. My article on as-is process mapping shows how to capture the steps before writing them down.

✓

Write one action per numbered line, starting with a verb

✓

Name the system, screen and field for every entry

✓

Show a screenshot or sample of the correct result

Would a colleague from another team understand your desktop procedures without asking for help?

Keep in mind: Abbreviations feel obvious to the writer. Spell out every system name and internal term once, or add a short glossary.

STEP 3

Record Exceptions and Judgement Calls

Most procedures describe the normal day. Handovers fail on the unusual one: a rejected file, a missing price or a client instruction that arrives after the cut-off. For each task, list the most common exceptions, what the expert does in each case, whom they call and when a problem must be escalated.

The Basel Committee expects banks to plan for disruption. Its principles call for forward-looking business continuity plans with scenario analyses and for training to ensure that staff can effectively execute contingency plans. Judgement calls are easier to hand over when the reasons are written down, as described in my article on keeping a decision log.

✓

List the most frequent exceptions for each task

✓

Write who decides, who is informed and when to escalate

✓

Record the reason behind each workaround the expert uses

What does your team do when the daily file arrives late or incomplete?

Keep in mind: An undocumented workaround is a hidden control. Write it down or remove it, but do not let it leave with its owner.

STEP 4

Test With a Newcomer

A procedure is finished only when someone else can follow it. Ask a colleague who has never done the task to run it from the document while the author watches without helping. Every question or pause marks a gap. Fix the text, then repeat the test with a second person.

Tested written steps change outcomes. When a surgical safety checklist was introduced in hospitals in eight cities around the globe, deaths after major operations fell from 1.5% to 0.8% and major complications dropped from 11% to 7%, the Harvard Gazette reported. It worked because teams used it during each operation.

✓

Let a newcomer run the task from the document alone

✓

Note every question and pause as a gap to fix

✓

Repeat the test until a second person needs no help

When did someone outside your team last run one of your procedures without help?

Keep in mind: The author is the worst tester. They read what they meant to write, not what the page actually says.

STEP 5

Give Each Procedure an Owner

A procedure without an owner starts to age on the day it is written. Name one owner per procedure and add a version number and a review date. Keep all procedures in one place with read access for the whole team. Link updates to change: a new system release, a new report or a new regulation triggers a review.

MaRisk states that guidelines shall be swiftly amended in the event of changes to the activities and processes. The Basel Committee asks that policies are reviewed and revised as appropriate based on continued assessment and that change management procedures are subject to independent and regular review and update. My article on the four eyes principle shows how a second reviewer can confirm each change.

✓

Name one owner and a review date for each procedure

✓

Store every procedure in one place with version history

✓

Trigger a review with each system release or process change

How many of your team's desktop procedures were reviewed after the last system release?

Keep in mind: An annual review date alone is too slow. A change to the process should update the document in the same week.

STEP 6

Plan the Handover Period

A good document does not replace overlap. Plan the handover in three stages: the successor watches while the leaver runs the task, then the successor runs it while the leaver watches, then the successor works alone with the leaver on call. Agree the dates and sign-off criteria before the notice period starts to shrink.

Learning on the job takes time. The Panopto survey found that formal training for new hires lasts 2.5 months on average, while they may need up to 6 months to get up to speed. The Basel Committee expects that bank activities are conducted by staff with the necessary experience. A handover must build that experience before the leaver goes.

✓

Let the successor watch first, then run the task observed

✓

Agree handover dates and sign-off criteria in writing

✓

Keep the leaver on call for the first month-end alone

How long does a handover in your team last before the leaver's final day?

Keep in mind: Month-end, quarter-end and year-end tasks rarely fall inside the overlap. Walk through them on paper if needed.

Creating High Velocity Organizations | Steven Spear (Senior Lecturer @ MIT Sloan School of Management)

SAMPLE CASE

Knight Capital

Knight Capital was a US broker-dealer with an automated order router called SMARS. In late July 2012 it deployed new code to the router. According to the SEC, one of its technicians did not copy the new code to one of the eight SMARS servers. Knight had no written procedures that required a second technician to review the deployment.

On 1 August the eighth server still held old Power Peg code that Knight had ceased using in 2003. Before the market opened, the system sent 97 e-mail messages flagging an error, but no procedure told staff how to respond. The router then sent more than 4 million orders in 45 minutes while trying to fill 212 customer orders.

Knight suffered a loss of more than $460 million. In October 2013 it agreed to pay $12 million to settle SEC charges.

Key takeaway: One deployment step depended on a single technician and no written procedure required a second check. Write down every step and every warning signal and name who acts on each one.

"Knight Capital's failure to ask these questions had catastrophic consequences."

Daniel M. Hawke (Chief, Market Abuse Unit @ US Securities and Exchange Commission)

In Short

Desktop procedures that survive a handover rest on six habits: knowing which tasks depend on one person, writing steps a newcomer can follow, recording exceptions and judgement calls, testing with someone new, naming an owner for every document and planning an overlap before the leaver goes.

The result is a team that keeps running through resignations, sick leave and reorganisations, fewer errors in the first months after a handover and documents that auditors and supervisors can follow.

Frequently Asked Questions

What is a desktop procedure?

A desktop procedure is a step-by-step instruction for one recurring task, written for the person who performs it. It names the systems, screens, inputs, checks and deadlines. It also explains what to do when something goes wrong. Unlike a policy, which says what must happen, a desktop procedure shows how a specific team does the work from day to day.

What is the difference between a desktop procedure and an SOP?

A standard operating procedure usually sets the approved way to perform a process across a department or the whole bank. A desktop procedure goes one level deeper and describes how one role carries out its part, click by click. Many banks link the two, so that each desktop procedure refers to the SOP and the policy it puts into practice.

What should a handover document include?

A handover document should list the tasks being handed over, their deadlines and the desktop procedure for each one. It should also name open issues, pending client requests, key contacts, the system access the successor needs and known exceptions. Add the dates of the overlap period and the sign-off criteria, so both sides know when the handover is complete.