Office Manager Handover Checklist for Hybrid Teams

An office manager handover checklist should show what must keep running, when the next action is due, who has accepted it, and where the instructions live. For a hybrid office, add a separate onsite contact for duties that require someone in the building. Before signing off, ask the receiving person to try the first real task using their own access.

Use the checklist and copyable duty record below for leave cover, a permanent replacement, or a job share. The aim is a usable operating brief: enough detail for the next person to keep the office working and know when to ask for help.

Set the scope before collecting the details

Start with the office or offices covered, the handover period, the outgoing owner, the receiving owner, and the manager who can resolve gaps. Name what remains with IT, Finance, building management, reception, or People Ops. Ask that manager to confirm the proposed allocation of work.

• Leave cover: identify duties and deadlines that fall during the absence, plus anything that must be prepared before the owner returns. Agree what can wait.
• Permanent replacement: include ongoing routines, less frequent renewals, supplier relationships, open improvements, and where the role documentation will be maintained.
• Job share: agree when responsibility changes hands, which queue both people use, and how the next person sees unfinished work.

The University of Iowa's knowledge transfer guide groups information into responsibilities, processes, projects, resources and records, and contacts. It explicitly allows local adaptation. The checklist below applies that broad structure to everyday office operations; it is an editorial template, not a tested performance benchmark.

Office manager handover checklist

For each applicable item, record its receiving owner, next due date, procedure link, and any unresolved issue. Mark an item not applicable with a short reason rather than leaving it blank. Keep the checklist in the shared location the cover will actually use.

The office and its recurring routines

• Opening and closing: identify the authorised onsite role, the current building procedure, the relevant service contact, and who covers each required day. Keep restricted access instructions in their approved location.
• Reception, visitors, and deliveries: list expected arrivals, named hosts, delivery windows, collection points, and the fallback if the usual contact is away. Use the office visitor checklist for individual visits.
• Cleaning, maintenance, and supplies: record service days, the issue-reporting route, open tickets, stock locations, ordering steps, and any booking or order due during the cover period.
• Rooms and shared equipment: point to booking instructions, known faults, temporary room restrictions, support contacts, and the fallback people should use while a fault remains open.
• Building notices and established procedures: link to the current building information and emergency instructions, and identify the responsible specialist contact. Confirm who receives updates during the handover period.

Open work, dates, and decisions

• Calendar: list scheduled visits, team events, maintenance appointments, recurring orders, and less frequent renewals. Include the time zone when there is any ambiguity.
• Supplier work: record the latest confirmed arrangement, purchase or booking reference, supplier contact, internal approver, next action, and due date. Link to the actual agreement or ticket.
• Finance coordination: identify invoices awaiting action, the approved purchasing route, the person who can approve spending, and what the cover may request. Confirm authority separately with the relevant owner.
• Unfinished issues: state what has happened, what is still unknown, who is waiting for a response, and the next check. Label a provisional date as provisional.

People, systems, and communication

• Access and records: check the receiver can open the necessary folders, queues, calendars, and supplier tools through approved accounts. Arrange changes with the system owner; do not paste credentials into the handover.
• Contacts and escalation: give a role and contact route for the building, IT, reception, Finance, and the approving manager. Explain which issue goes to whom and how to find a backup.
• Request channel: state where colleagues should send office requests, who watches it, and how unresolved messages pass between people. Include the return or review date in the cover notice.

Keep detailed procedures at their maintained source. The handover should identify the current version and the next action, rather than making a second manual that will need separate updates.

Copyable office manager handover template

Copy this header into your shared document, then repeat the duty record for each routine or open item. A small office may need only a few records; a multi-office role may need a separate section for each location.

• Handover scope: [office/location]; [leave cover, replacement, or job share]; [start and end, or review date]; [last updated].
• People: [outgoing owner]; [receiving owner]; [manager confirming the allocation]; [location of the shared request queue].

Duty record: repeat as needed

• Duty and required result: [what must happen, and what a completed cycle looks like].
• Timing: [frequency or trigger]; [next exact date/time and time zone]; [latest useful point for escalation].
• Current position: [last completed action and date]; [open issue]; [confirmed or provisional information].
• Next action: [specific step]; [receiving owner]; [when they have agreed to do it].
• Onsite requirement: [what needs physical presence]; [named onsite contact]; [coverage date/time]; [accepted backup].
• Instructions and access: [current procedure or ticket]; [record location]; [system owner]; [receiver access checked on date].
• Decision boundary: [what the cover is authorised to decide]; [what needs approval]; [approver and contact route].
• People to contact: [internal owner]; [supplier/building contact]; [existing reference]; [escalation route].
• Acceptance and return: [receiver confirmation]; [test completed]; [remaining gap with owner and date]; [hand-back or review point].

For a discrete piece of project work, the async handoff template gives a shorter sender-and-receiver note. Use the office record here when the responsibility repeats or depends on building coverage.

Confirm onsite cover separately from task ownership

A person can own a supplier booking remotely while someone else meets the supplier at the office. Record both roles. Check the specific day and time, the required access, and whether the onsite colleague has accepted the task. A usual office day alone is not a handover confirmation.

Cambridge's job-share case study describes an administration team using a shared email account with flags and a handover document completed after each shift. That is one institution's example of making outstanding work visible across a change of owner. It does not establish one universal system for hybrid offices.

Use a work location calendar to find possible onsite cover, then confirm the arrangement directly. If there is no suitable cover, bring the gap to the responsible manager before treating the duty as transferred.

Run a first-duty acceptance test

Choose the next actual duty, such as receiving a delivery or following up a maintenance ticket. Ask the receiving person to work through these steps while the outgoing owner is still available. Use a walkthrough where carrying out the action would create an unnecessary booking or purchase.

1. Find the current instructions and latest status without relying on the outgoing owner's private inbox or memory.
2. Open the required records using the receiver's approved access, and check any physical access through the building's normal process.
3. Explain the next step, its deadline, and the person who must be onsite, if anyone.
4. Explain what can be decided independently and what requires an approver. Locate the support or escalation contact.
5. Record acceptance, or write the remaining gap with a named owner and a date to resolve it. Recheck the affected step once fixed.

Use specific confirmation: “I can open the booking, the onsite host has agreed, and I know who approves a change.” If access is still missing, state that condition explicitly and agree interim cover. A read receipt tells you less than a demonstrated next step.

Worked example: two office days, different cover

Consider a fictional office manager taking one week of leave. A printer engineer is due on Tuesday morning, and a stationery delivery is due on Thursday afternoon. The covering coordinator works remotely on Tuesday and is onsite on Thursday.

The coordinator accepts ownership of both bookings. For Tuesday, a separately authorised onsite colleague agrees to meet the engineer and follows the existing building arrival process. The coordinator keeps the ticket reference and supplier contact, while the usual Finance approver retains approval of any additional charge.

On Thursday, the coordinator can receive the delivery personally. The duty record identifies the drop-off point, order reference, and what to do if the delivery is incomplete. Each task now has an owner and a workable onsite arrangement.

If Tuesday's host changes plans, the coordinator follows the recorded backup route before confirming arrival to the engineer. The shared booking record receives the change so that the manager returning from leave can see what happened.

Tell colleagues where office requests should go

Send a short notice once the coverage is accepted. Keep operational detail in the shared brief and link to it. Here is a copyable message:

Office support cover: [office], [dates]. [Name] will coordinate requests through [channel or shared inbox]. Onsite contacts are listed in [coverage brief] for the relevant days and duties. For [type of issue], use [existing support route]. [Approver] remains the contact for [approval type]. Please add new requests to [queue] so the cover can track them. The next ownership review or hand-back is [date].

For a permanent replacement, replace the temporary dates with the effective change date and ongoing owner. For a job share, explain when responsibility changes and where the next post holder finds open requests.

Hand back the changes, not the whole document

Admin Avenues' cover guidance recommends detailed delegation notes and a debrief when the original owner returns. Build that return into the brief at the start, so the cover knows which updates to keep.

Use this short hand-back note. Link each entry to the maintained record, and ask the returning owner to confirm any responsibility moving back.

• Completed: [duty or request]; [outcome]; [record link].
• Still open: [current position]; [next action]; [owner]; [due date].
• Changed: [booking, supplier arrangement, procedure, or contact]; [confirmed change and source].
• Awaiting decision: [question]; [approver]; [decision needed by].
• Access and temporary cover: [changes to review with the responsible system or building owner]; [follow-up owner and date].
• Ownership returned: [duties accepted back]; [exceptions continuing with cover]; [confirmation date].

For a permanent replacement, use the same record at the agreed review point to resolve outstanding gaps. For a job share, keep a compact change log between shifts instead of repeatedly sending the full role description.

Keep the weekly office plan visible

Officedays helps colleagues share planned office days in Slack and supports scheduled weekly prompts. Its office-day planning features can help a covering coordinator see when colleagues plan to be onsite and ask the right person about a duty. Keep the accepted cover arrangement and responsibility record alongside that plan.

Start with the next duty that could fall between owners. Write its record, confirm the onsite arrangement if needed, and run the acceptance test. Extend the brief to the remaining routines once the first record is usable.

Sources and methodology

Sources were checked on 27 October 2026. This is an operational guide built from first-party institutional and professional guidance, with newly authored templates and one fictional example. It reports no survey findings, measured savings, or original Officedays research. The suggested fields and acceptance test are editorial recommendations to adapt to your existing procedures.

• University of Iowa knowledge transfer: current HR guidance and template categories. Publication date is not stated; the setting is a US university.
• University of Cambridge administration case study: an undated UK job-share account, used only for its documented queue and handover practices.
• Admin Avenues cover guidance: undated Australian professional guidance on preparation, delegation, authorisation, and hand-back. It is advice, not an effectiveness study.