← Back to sample work
Weekly Back-Office Runbook & Process MapBack-Office Operations

Standard documentation sample

Weekly Back-Office Runbook & Process Map

Document ID
004
Owner
Affordable Digital Solutions (ADS)
Effective date
June 15, 2026

1. Purpose

This runbook defines the recurring back-office work that keeps client records, trackers and reporting accurate. It lets a virtual assistant take over the account with no verbal handover.

2. Scope

Covers daily and weekly administrative operations: inbox triage, data entry, CRM hygiene, research logging and the Friday management report. Excludes client-facing sales calls and anything requiring signing authority.

3. Process map

TriggerActionOutputHandoff
New enquiry lands in shared inboxTag, log to CRM, send acknowledgement within 4 hoursCRM record with source and ownerAccount manager
Invoice receivedVerify amount against PO, file to Finance drive, log in trackerTracker row + filed PDFFinance
Research request submittedComplete against the research brief, log sourcesResearch sheet with source columnRequesting stakeholder
Friday 15:00Compile weekly report from trackersOne-page summaryOperations manager

4. Daily cadence

TimeTaskDefinition of done
09:00 – 09:45Inbox triageZero unread; every actionable email tagged and assigned.
09:45 – 11:30Data entry queueAll rows from the previous day entered and spot-checked.
11:30 – 12:30CRM hygieneNo duplicate contacts; every open deal has a next step and date.
14:00 – 16:00Research and documentationAssigned briefs completed with sources logged.
16:00 – 16:30End-of-day logDaily log updated; blockers posted to the ops channel.

5. Data-entry quality rules

  • Dates use ISO format (YYYY-MM-DD). No regional formats anywhere in a shared sheet.
  • Names are entered as they appear on the source document, not as remembered.
  • Currency values carry the currency code; no bare numbers in mixed-currency columns.
  • Every record includes a source column: document name, URL or ticket ID.
  • Blank means "not applicable"; unknown values are entered as UNKNOWN so gaps are visible.
  • Spot-check 10% of every batch of 100 rows before marking the batch complete.

Quality gate

A batch is only complete when the 10% spot-check passes with zero critical errors. One critical error means the whole batch is re-checked.

6. Escalation matrix

SituationEscalate toWithin
Conflicting data between two source systemsOperations managerSame day
Suspected duplicate payment or invoiceFinanceImmediately
Access lost to a tool or shared driveIT supportWithin 1 hour
Client requests work outside scopeAccount managerBefore starting the work

7. Weekly report contents

  • Volume: records entered, enquiries handled, invoices filed
  • Accuracy: spot-check pass rate for the week
  • Turnaround: average first-response time on enquiries
  • Open blockers with owner and age in days
  • Backlog count carried into next week
  • One process improvement observed during the week

8. Handover checklist

  • All trackers up to date to the last working day
  • Inbox triaged with no unassigned actionable emails
  • Credentials shared through the password manager, never over chat
  • Open blockers documented with context and next step
  • Recurring calendar tasks transferred to the incoming assistant

9. Revision history

VersionDateSummary of changes
1.02026-03-09Initial runbook published.
1.12026-06-15Added quality gate, escalation matrix and handover checklist.

Document ID: 004 · Sample prepared for portfolio review. Client names and figures are anonymised.