How to document a recurring task so a coworker can take over

Define the task and when it needs doing

Start with one clearly named task, such as preparing a weekly status report. Describe its purpose in a sentence: who uses the result and what they need from it. Keep the scope narrow enough that your coworker knows where the task begins and ends.

Proposed opening checklist: record the following details before writing the procedure. Fill them with your team’s actual arrangements rather than leaving assumptions for the next person.

• Trigger: the day, request or event that starts the task.
• Deadline: when the result is due, including the time zone if relevant.
• Owner: who performs the task and who covers an absence.
• Recipient or reviewer: who receives or approves the result.
• Finish point: what must be saved, sent or recorded before the task is complete.

For temporary cover, specify which occurrences your coworker will handle. For a permanent transfer, include the full recurring responsibility and any unfinished work that affects the next cycle.

List the materials and access needed

Put prerequisites before the steps. Link to the source files, working template, relevant system and destination folder. Explain which file is authoritative if several similar versions exist. Replace vague directions such as “use the usual spreadsheet” with its exact name and location.

Include how your coworker obtains access and whom to contact if permission is missing. Keep passwords out of the instructions; point to your organization’s approved access process. If the task depends on another person supplying information, identify that person’s role and explain what input is expected.

Explain unfamiliar abbreviations on first use. A coworker may understand the department’s work while still being unfamiliar with the labels, folders and shortcuts you use every day.

Write the steps in the order they happen

Write the procedure while working through the task so you can capture small decisions you might otherwise overlook. Begin each step with an action verb. Name the object being changed and describe any check needed before continuing.

Proposed example sequence for a weekly status report, to adapt to your actual process:

1. Open the report template and save a working copy for the reporting period.
2. Gather updates from the named source files or contributors.
3. Enter the updates under the matching headings and flag missing information.
4. Check the reporting period, required fields and unresolved issues.
5. Request approval from the designated reviewer if approval is required.
6. Send the approved report to the specified recipients and save the final version in the shared folder.

Place decision rules beside the step where they matter. For example, explain whether missing input means waiting, sending a partial result or asking a reviewer. Avoid “handle as appropriate” unless you also explain the criteria for that decision.

Show a finished result and explain common problems

Proposed addition: link to a suitable completed example and explain what makes it acceptable. Identify the required sections, naming convention, destination and approval status. Use an example your coworker is authorized to view, or create a clearly labeled fictional example with sensitive details removed.

Add a short troubleshooting list based on problems you actually encounter. Pair each problem with a next action and a contact where necessary. Document unresolved issues separately so your coworker can distinguish normal instructions from a temporary complication.

Proposed prompts include: What happens when a source file is unavailable? Who resolves conflicting updates? What should the coworker do if approval has not arrived by the deadline? State where they should pause and who has authority to decide.

Walk through the handover and keep it current

Share the instructions before responsibility transfers and arrange a walkthrough. Invite your coworker to ask questions about unclear steps, missing context and decisions. Check that they can open the linked materials and understand whom to contact for help.

Proposed practical check: have your coworker follow the document during an appropriate task cycle while you are available. Record where they need an explanation, then add that explanation to the instructions. Check the resulting work against the completion criteria you established.

Keep one shared version. Add a document owner and a last-updated date, and revise the instructions when tools, contacts or steps change. Put the next due date and any current blockers in a separate handover note so routine instructions remain easy to reuse.

Sources

• How to write a handover document
• Handover checklist: Leave work without worrying + email templates
• Employee leaving? Here’s the process for writing a solid handover | Go1