Operations & Systems

Operations Handover for a Small Team: Leave the Next Person a Working Runbook

The report is due tomorrow.

The person taking over has the folder link, a recording, and a message saying everything should be straightforward.

They still cannot tell which export is current or whether they have permission to send the result.

That is the handover to fix.

Transfer one responsibility at a time. Give the receiving person a procedure, the current state of the work, and a way to demonstrate readiness. Keep the boundary narrow enough to test.

The operations handover checklist below uses a fictional weekly request report. Every role, deadline, file label, and operating rule belongs to that example. Adapt the method to your own work before using it.

Define the Responsibility Before Writing the Steps

Name the output in one sentence: the reporting coordinator prepares a reviewed summary of open requests for the operations lead.

Then name the boundary. The coordinator checks the reporting period, assembles the draft, records unresolved data issues, and requests review. The operations lead approves distribution. The coordinator cannot change source records or expand the audience.

This boundary belongs beside the instructions. Otherwise, a receiver can follow the procedure and still exceed the authority being transferred.

The broader task delegation framework covers choosing responsibilities. This handover starts after that choice, when a particular person needs to perform a particular task.

Write four fields before describing any software:

Field Fictional example
Responsibility Prepare the weekly open-request summary
Receiving person The assigned reporting coordinator, named in the internal assignment
Start condition Reporting period closed and the source export available
Acceptance Receiver completes a supervised run, explains stop conditions, and obtains the lead's handover decision

A role label keeps this public example anonymous. In the real assignment, resolve the receiving person and backup explicitly. An unfilled role is still an open handover item.

Acceptance also needs a date and a scope. A successful practice run can support readiness for routine reporting. It does not establish readiness for every exception.

Build a Runbook Around an Observable Output

AWS describes runbooks as procedures for a specific outcome. Its guidance includes permissions, tools, error handling, escalation, ownership, and validation by another team member. That provides a useful starting structure for this reporting example. AWS runbook guidance.

The following runbook is an editorial template, not an AWS requirement for small businesses.

Outcome: A draft summary that identifies the reporting period, source export, open-request count, unresolved exceptions, and review status.

Inputs: The approved request export, reporting-period definition, previous approved summary, and current blank template.

Access: Read permission for the source and template folders. Write permission for the draft folder. Permission to request review.

Authority: Prepare a draft. Record discrepancies. Escalate blocked inputs. Distribute only after the designated lead approves the specific version.

Store the procedure where the receiver can open it with their own account. Give it an owner, a revision date, and a link from the recurring task.

The existing SOP documentation article covers organizing procedures. For this transfer, keep one canonical runbook and link supporting material from it.

Establish Access Without Sharing Credentials

List the resource, required permission, approving role, and request route. Link to the team's approved access process. Leave passwords, recovery codes, private keys, and session links out of the document.

Have the receiver request their own access before the practice session. Test the permissions the task uses, including reading the source and saving a draft. Opening the application alone proves neither.

If a permission is missing, record the blocked step and the role responsible for resolving it. Do not borrow the outgoing person's session to make the demonstration pass.

Access approval and handover acceptance are separate decisions. The person who approves a folder permission may have no authority to approve report distribution.

Write the Normal Procedure as a Sequence

For the fictional report, use these steps:

  1. Confirm the reporting period against the recurring assignment.
  2. Open the approved source location with your own account.
  3. Confirm the export's extraction time and reporting period match the assignment.
  4. Save a working copy in the designated draft folder.
  5. Record the source filename and extraction timestamp in the draft.
  6. Apply the documented definition of an open request.
  7. Compare the resulting count with the source rows.
  8. Record exclusions and unresolved discrepancies in the exception section.
  9. Save the draft with its period and version.
  10. Request the operations lead's review through the approved channel.
  11. Record the review outcome against that version.
  12. After approval, distribute through the authorized route and retain the completion record.

Add the exact filter definition to the internal procedure. A phrase such as “remove irrelevant rows” leaves the receiver to invent a rule.

For this example, the agreed rule is to include requests marked open at period close. Requests with an unknown status stay in an exception list. The receiver does not silently classify them.

Show What Is Live Right Now

A runbook describes the recurring path. The current work record tells the receiver where this instance stands.

Keep both visible. A perfect procedure cannot tell someone that the export is late today unless the current state records it.

Here is a fictional transfer record:

Item State at handover Next action Responsible role
Current period 2026.10.26 through 2026.11.01 Verify the export covers this interval Reporting coordinator
Draft Not started Begin after source check Reporting coordinator
Source export Latest available file ends before period close Request a corrected export Data owner
Exception One request has no status Confirm classification or retain as unresolved Data owner
Next deadline 2026.11.02 at 10:00, America/New_York Submit draft for review Reporting coordinator
Approval Pending Review the exact draft version Operations lead

These dates illustrate the record format. They are not a recommended reporting schedule.

Include work that is waiting on someone else. State the last confirmed action and the next required response. Avoid entries such as “handled” when the evidence shows only a request for help.

Attach links to the internal work items rather than pasting entire conversations. The receiver needs the latest decision, its source, and the unresolved question.

Put Stop Conditions Beside the Steps They Control

The receiver needs to know when continuing would create an unreliable output or exceed their authority.

For this fictional responsibility, stop distribution when the period is wrong, access is insufficient, source freshness is unresolved, or approval is missing.

A stopped distribution does not require abandoning the whole task. The coordinator can prepare an explicitly incomplete draft while waiting for the missing input. The lead decides whether that draft has a permitted use.

Write escalation contacts by role in the public template. In the internal version, connect each role to the current directory entry and the team's approved contact route.

Condition Immediate action Escalation role Evidence to retain
Export is stale Hold distribution Data owner Expected period and observed timestamp
Count cannot be reconciled Mark discrepancy in draft Operations lead Source version and comparison result
Access is denied Stop the blocked step Access administrator Resource and requested permission
Approval is absent Keep the report in draft Operations lead or designated backup Draft version and review request

Define the backup before the outgoing person leaves. “Ask whoever is available” leaves the escalation owner unresolved.

Walk Through the Procedure With the Receiver

Use a safe sample first when a live run could affect other people. Identify which steps are simulated and which permissions remain untested.

The outgoing owner demonstrates the sequence while the receiver follows the written runbook. The receiver marks every missing decision, unexplained label, and ambiguous location.

Record these gaps where the document owner can resolve them. A recording can supplement the runbook, but the written procedure still needs the missing information.

Google's on-call chapter describes training checklists, mentoring, practice sessions, and learning when to ask for help. Its examples concern service operations, not this fictional office process. The relevant lesson here is to pair documentation with supported practice. Google SRE on-call chapter.

During the walkthrough, ask the receiver to explain why the period and source checks come before the report calculation. That question tests their understanding of the sequence without requiring them to memorize every click.

Let the Receiver Run the Written Procedure

Reverse the roles for the next attempt.

The receiver performs the task from the document. The outgoing owner observes. If the receiver needs a missing instruction, record it before giving the answer.

For the fictional report, the receiver should produce a draft, trace its count to the source, identify the unresolved status, and request review. They should also recognize a deliberately stale sample export.

Use a sample for the exception exercise. Do not corrupt live data to test whether someone notices.

Record the result as a bounded observation:

Receiver completed the routine sample and identified the stale-source stop condition. Distribution permission remains untested. A supervised live cycle is still required.

That statement describes what happened in the example. Replace it with the observed result of your own session.

A document alone cannot establish readiness. Neither can a polite acknowledgment in chat. The accepting lead needs evidence of the work performed and a clear list of remaining gaps.

Make Acceptance and Maintenance Explicit

Keep the acceptance decision beside the transfer record. Name who accepts the handover, what they accepted, and which exceptions remain outside scope.

If the receiver cannot complete a critical step, record the handover as pending. Assign a resolution owner and another practice date. Do not turn an unfinished access request into a completed training checkbox.

After acceptance, the new responsibility owner maintains the runbook. The operations lead remains accountable for deciding changes to scope, authority, and output requirements.

Use a short change record:

  • What changed in the procedure.
  • Which step or output changed with it.
  • Who reviewed the change.
  • What execution confirmed the revised instruction.
  • Which unresolved gap still needs an owner.

The asynchronous communication guide supplies broader communication context. For this handover, put durable decisions in the task record and use messages to point people to them.

Review the procedure when an input, tool, permission, or approval route changes. Give the next routine review a date too. A review date is a prompt to inspect the document, not proof that it is current.

Copy This Handover Checklist

Use this blank worksheet for one responsibility. Keep internal links and personal access details inside the approved workspace.

Handover field Fill in before acceptance
Responsibility and boundary Output, included steps, excluded decisions
People Outgoing owner, receiving person, accepting lead, backup
Start condition Trigger and required inputs
Access prerequisites Resources, permissions, request route, approving role
Runbook Canonical procedure link, owner, revision date
Current work Latest confirmed state and unfinished items
Next deadline Date, time, time zone, required output
Exceptions Stop conditions and escalation roles
Practice evidence Sample or live run, observer, result, gaps
Acceptance decision Accepted scope, unresolved restrictions, decision owner
Maintenance New document owner and next review date

Start with the responsibility most likely to leave someone asking what happens next. Complete one transfer before expanding the packet into a department manual.

Leave a procedure the next person can run.

Sources

Topic map: Records, access, and continuity

Articles in this cluster, then the 3 clusters that share the most topics with it.

This cluster: Records, access, and continuity

Neighbor: Business reporting and statistics

Neighbor: Spreadsheets, CSV files, and data handoffs

Neighbor: APIs, webhooks, and automation