What makes a process document survive a change of staff
Abstract
Executive support work often depends on knowledge that lives with one person. This article applies public internal-control and configuration-management guidance to process documentation, explains how to select what deserves a document, and sets a test for whether the document is actually used. It separates operational documentation from policy and records-retention requirements. The aim is a small set of current documents that a colleague can follow under pressure [1][2][3].
Methodology
The review uses federal internal-control standards, NIST configuration-management guidance, and NIST cybersecurity guidance as public sources. It treats documentation as an operational control and measures use through observation and retrieval tests. The method does not assume that a longer document is a better one and does not create legal or records-retention advice. It focuses on the processes a support desk can describe and test itself [1][2][4].
Why undocumented work leaves with the person
A support desk carries a large amount of tacit knowledge. The assistant knows which approval is needed before a payment, which contact prefers a call, and which report always needs a manual adjustment. That knowledge is efficient while the person is present and expensive when they leave. The office often discovers the gap during a handover, when there is no time to reconstruct it [1][2].
Turnover is not the only trigger. A secondment, a leave, or a reorganization can break the continuity of a process. A document that explains the work gives the next operator a starting point and gives the departing person a way to transfer knowledge deliberately. The purpose is continuity, not surveillance of the individual [2][3].
A departing employee often has little time to write everything down. The office should capture the critical processes before the notice period, not during it. A regular review of single-owner tasks makes that possible. The best time to document a process is while the person doing it still has time to explain the exceptions.
The office should also record the reason a process exists. A step that looks redundant may be there because of a past audit finding or a client requirement. Without the reason, a new operator may remove the step in good faith. A short purpose note protects the control while allowing the method to change.
Choose the processes worth documenting
Not every task needs a document. Start with the processes that are repeated, time-bound, or dependent on a specific system or approval. A monthly payment run, a board pack cycle, and a travel booking sequence are stronger candidates than a one-off introduction. Rank them by the cost of getting them wrong [1][2].
Include the processes that only one person knows even if they are not frequent. A rare but critical task, such as a regulatory filing, can cause the most damage when the owner is unavailable. Keep the list short enough to maintain. A handful of living documents is better than a library that nobody updates [2][3].
Ask the person who does the work which steps they would struggle to teach in a single session. Those steps usually contain the hidden decisions that a generic procedure misses. Add them to the candidate list even if they seem minor. The test is whether a competent colleague could complete the task without a phone call.
Write for the next operator
Write the document for someone who knows the organization but not the task. State the purpose, the trigger, the required inputs, and the expected output. Describe the steps in the order they happen and name the systems and approvals involved. Avoid references to knowledge the reader may not have [1][3].
Include the exceptions that cause the most trouble, such as a missing approval or a system outage. Explain what to do and who to contact. Put the decisions that require judgement in a separate note from the mechanical steps. The reader should be able to tell where they can act and where they must escalate [2][4].
Use screenshots sparingly and label them with the step they support. A screenshot can become obsolete after a system update, so pair it with text that explains the purpose. Do not rely on an image to carry a required instruction. The document should still work when the image is out of date.
Keep the document close to the work
A document stored in a distant folder will not be used during a busy day. Put it where the work happens, such as a link from the task list, the calendar entry, or the system dashboard. Use a consistent template and a clear title. The document should be findable in seconds, not through a search that returns ten versions [1][2].
Give each document an owner and a review date. Record the version and the date of the last change. When a system or a policy changes, update the affected document rather than creating a parallel note. A small set of current documents is easier to trust than a large set of uncertain ones [3][4].
Link the document to the task rather than expecting people to remember its location. A short URL, a QR code on a printed checklist, or a pinned link in the team channel all work. Review the links when a system changes. A document that cannot be found is effectively undocumented.
Keep a single index of the process documents and their owners. The index should show the title, the owner, the last review date, and the system it depends on. It does not need to contain the documents themselves. A one-page index makes gaps visible before an absence or an audit.
Set an owner and a review date
Name the person accountable for the document's accuracy, even if someone else writes it. The owner should review it after a process change, a system change, or a significant incident. Set a review date that reflects how often the work changes. A quarterly review is reasonable for a fast-moving support process [2][3].
Use the review to remove steps that no longer apply. A document that accumulates exceptions becomes harder to follow. If a step is consistently skipped, ask whether the process or the document is wrong. The owner should be able to explain the difference between a real requirement and a habit [1][4].
The review should include the person who performs the task, not only the owner. They will notice a step that no longer matches the system or a workaround that has become normal. Give them a simple way to suggest a correction. The document then improves between formal reviews.
Measure whether the document is used
Ask a colleague who does not normally perform the task to follow the document and complete it. Watch where they hesitate or need to ask a question. That observation is a better test than asking whether the document is clear. Fix the step that caused the hesitation [1][2].
Review the document after the next real handover or absence. Note the questions the backup had to ask and add the answers where they belong. If the document was never opened, the problem may be its location or its length. A used document is evidence that the control works [3][4].
A document that is used should show signs of use: comments, corrections, and links from other procedures. If it has none, ask whether the work has changed or the document is in the wrong place. Do not assume that silence means the document is correct. The measure of documentation is the work it enables, not the page count.
Retire a document when the process it describes no longer exists. A stale procedure can be worse than none because it sends a new operator down an obsolete path. Record the retirement in the index and keep the last version only if a record-retention rule requires it. A clear end date is part of good documentation.
Key findings
- Document repeated, time-bound, or single-owner processes first, ranked by the cost of failure [1][2].
- Write for a reader who knows the organization but not the task, including common exceptions [1][3].
- Store the document at the point of work and give it one owner and a review date [2][3].
- Test the document by having someone else perform the task from it and fixing the hesitation [1][2].
- Review after a real handover and remove steps that no longer match the work [3][4].
Sources
- Standards for Internal Control in the Federal Government (GAO-14-704G), U.S. Government Accountability Office
- Guide for Security-Focused Configuration Management (SP 800-128), National Institute of Standards and Technology
- NIST Cybersecurity Framework, National Institute of Standards and Technology
- Records Management, U.S. National Archives and Records Administration