Department of One Playbook · Documentation and delegation

Document one recurring task so someone can take it over

Write a bounded task note with authorised inputs, access, completion checks and an exception route, then try it with the person taking over.

Published

Contexts: people administration, documentation, delegation, backup

A recurring task can look simple to the person who remembers every exception. “Update the starter list” might conceal which source is approved, who can see it, which changes are authorised and what to do when the information disagrees. A list of clicks will not transfer those decisions.

Choose one bounded task and write enough for someone else to attempt it. The useful test is whether an available person with agreed access can produce the intended result and recognise when to stop. You do not need to document the whole department first.

Pick an output with a clear boundary

The situation below is illustrative. An office administrator prepares the weekly status of administrative arrangements for confirmed new starters. HR provides the authorised source and retains responsibility for employment records and decisions. The administrator coordinates already agreed office tasks; they do not approve appointments, change personal details or grant access.

The output is a short status record for each authorised starter reference: which administrative tasks are arranged, which are waiting and who acts next. The example uses a synthetic reference, START-17, without personal data. Actual records must remain in the organisation’s agreed location with authorised access.

The task has a 30-minute preparation window on Thursday afternoon. If it needs longer, the person doing it records the remaining work and asks the manager to agree the next step. A backup is not expected to absorb an unlimited task.

Write the note around the decisions

The following is a worked task note. Replace its role labels and record locations with confirmed arrangements in your own workplace; do not leave an assumed contact or permission for the reader to discover during an absence.

Task note: prepare the starter administration status

Purpose and output: update the existing status record for the starters HR has authorised for the coming week. Each open task should have a state, next action and responsible role. Preparation complete means that status is clear; it does not mean all arrangements or the person’s onboarding are complete.

Time and trigger: Thursday’s agreed 30-minute window, after HR supplies the authorised list. If the list is missing, request it from the HR contact and tell the manager that preparation is waiting. Do not reconstruct it from informal messages or an old copy.

Inputs and access: the current authorised starter references, the existing administration checklist and permission to update its status fields. Confirm access before handing over. The note names the record location but contains no passwords or copies of private staff information.

Steps:

  1. Confirm which version of the HR source applies to the coming week. If two sources disagree, stop the affected item and ask HR which is authoritative.
  2. Open the existing checklist for each authorised reference. Do not create a second record if one already exists.
  3. Check the administrative tasks within this role’s scope. In the example, these are the office welcome information and confirmation of who will handle the planned arrival. Other owners retain their own tasks.
  4. Record confirmed arrangements and missing decisions. A message asking someone to take a task is not confirmation that they accepted it.
  5. Give each outstanding item a next action and responsible role. Refer exceptions to the agreed HR contact or manager rather than deciding them yourself.

Completion check: every authorised reference is accounted for, open items have clear next actions and owners, and the source version and review date are recorded. Tell the manager if the time window ended before that check was complete. Do not mark a task arranged when its owner has not confirmed it.

Exceptions and limits: HR decides missing or contradictory starter information. The manager resolves unavailable task owners and capacity conflicts. Work outside the administrator’s permissions stops at that boundary; the task note does not grant additional authority.

Show what a usable result looks like

For synthetic record START-17, a sufficient status could say:

  • Welcome information: prepared from the approved material; next action is the agreed review by the office manager.
  • Arrival arrangement: awaiting confirmation from the receiving role; manager to resolve cover if it remains unaccepted.
  • Preparation status: checked against this week’s HR source; open questions recorded. Arrival arrangements are not yet complete.

The wording distinguishes preparation from completion and a request from an accepted commitment. Another person can tell what remains without reading an entire message history. Add only details the authorised task needs.

Try the handover while both people are available

Agree a short trial with the person who may take over, inside both people’s working time. First check that they have the necessary permissions and can find the source records. Then let them attempt the bounded task from the note. Use synthetic or appropriately authorised material for any demonstration.

Ask where they had to guess: a missing location, an unexplained state or a decision without an owner. Amend those gaps and repeat the completion check. Do not measure success by how often they ask questions; a well-timed question can reveal a decision the original operator was making from memory.

If the person lacks time, access or authority, record that as unfinished cover. The manager must decide what changes or what service pauses. A readable note helps someone perform agreed work; it cannot make an unavailable person into a backup.

Keep one maintained version

Name the role responsible for maintaining the note and keep it with the task’s existing records. When a real exception changes the routine, update the relevant step or escalation instruction. Retire superseded copies so a future reader can identify the current version.

Start with this one task. A tested, bounded note is a useful piece of continuity. An ambitious documentation project that nobody has time to try is still a proposal for future work.