Standard Operating Procedure

What a good SOP includes

• Title, ID and version, with an effective date.
• Purpose: one or two sentences on why the process exists.
• Scope: which sites, roles or cases it covers, and which it doesn't.
• Roles: who does each step (recruiter, coordinator, HR ops, hiring manager).
• Inputs and tools: the systems, forms and access required.
• Steps: numbered, one action per step, with decision points ("If the candidate is in California, go to step 7").
• Timelines and service levels: "within one business day of offer acceptance."
• Exceptions and escalation: who approves deviations.
• Records: what gets saved, where, and for how long.
• Owner and review date.

Write it for the person doing the task on their first week, not for the person who designed it.

HR SOP examples

Background check initiation (high-volume hiring)

1. Within 1 hour of offer acceptance, the recruiting coordinator triggers the background check package for the role in the screening system.
2. The system sends the standalone FCRA disclosure and authorization to the candidate.
3. If not completed in 24 hours, send an automatic reminder by email and text.
4. At 48 hours, the coordinator calls the candidate.
5. When results arrive, clear candidates are moved to onboarding; results needing review go to the designated HR reviewer, never to the hiring manager directly.
6. Any possible adverse action follows the pre-adverse action SOP.

Other common HR SOPs: requisition approval, offer letter generation and approvals, I-9 completion and reverification, new-hire system provisioning, leave requests, payroll changes, terminations and final pay, and personnel file maintenance.

SOP vs policy vs job aid

• An [HR policy](/glossary/hr-policy/) sets the rule and the reason: "Every new hire completes Form I-9 within the legal deadlines."
• An SOP sets the steps to follow the rule: who completes which section, in which system, by when, and what happens if documents are missing.
• A [job aid](/glossary/job-aid/) is a quick reference used in the moment: a one-page checklist of acceptable I-9 documents taped next to the scanner.

All three are needed. Policies without SOPs lead to every site inventing its own process. SOPs without job aids are too long to use mid-task.

Why SOPs matter in high-volume operations

When a contact center hires 300 agents a quarter across four sites, small process differences multiply. One site runs background checks before the final interview and another after the offer; one completes I-9 Section 2 on day one and another on day three. Each variation is a compliance risk and a source of candidate drop-off.

SOPs let you standardize, measure and improve. Once every site follows the same steps, you can compare time per step, find the bottleneck and fix it once. They also make automation possible: you can't automate a process that exists only in four people's heads. New recruiters and coordinators get productive faster when they can follow a documented process instead of shadowing someone for weeks.

How to write and maintain SOPs

1. Watch the task being done by an experienced person and write down every step.
2. Have a new person follow the draft without help. Every question they ask is a gap.
3. Remove steps that exist only out of habit.
4. Add screenshots for system steps and decision tables for branches.
5. Publish in one searchable place, such as an internal knowledge base, not scattered across shared drives.
6. Review at least annually and whenever a system, law or org structure changes.

Track version history. In an audit or a legal dispute, you may need to show which procedure applied on a particular date.

Common mistakes

• SOPs written once for an audit and never opened again.
• So much detail nobody reads them, or so little that they're useless.
• No owner, so they go stale.
• Mixing policy debates into procedures.
• Different versions saved in different places.