HR SOP Examples: Hiring and Onboarding Procedures That Get Used

At one field services client, new hires waited up to 3 weeks for a company card, so they bought parts and gas on personal cards while the office chased receipts. That is what a missing HR SOP looks like: not a compliance gap, a slow leak. Here are five HR SOP examples built to stop exactly that kind of leak: a hiring pipeline for high-volume roles, day-one setup, equipment and access provisioning, the exit and knowledge handoff, and performance conversations that actually happen. Each comes from a real small business, and each exists because something expensive went wrong without it.

Key takeaway: HR SOPs guard two doors: the one people walk in through and the one they walk out of. Document the five procedures below, write each one from the person who actually runs it, and give every step a named owner and a trigger. Done right, any manager can run them without asking a single question.

What Is an HR SOP?

An HR SOP is a written procedure that lets anyone in the company run a people process, hiring, onboarding, provisioning, performance, or exits, the same way every time. It is the difference between "ask whoever did it last time" and a document with an owner, a trigger, and steps.

Most small businesses have no HR department to hold these processes. At a cleaning company that services 85 homes a day, the COO described the office team as one bucket: anyone who answers the phone. Scheduler, dispatcher, sales, finance, and HR were all blurred into it. The SOP stands in for the department you do not have.

HR procedures are also strange: each one runs rarely for any single employee but constantly across the company. You onboard a person once, and the company onboards people forever. That gap is why these processes feel too occasional to document and end up improvised every single time. The anatomy is the same as what real standard operating procedures look like in any other department; the subject is just people instead of invoices.

Example 1: The Hiring Pipeline for High-Volume Roles

One residential cleaning client runs on about 55 cleaning technicians, which makes hiring a constant process, not an event. A professional services firm we interviewed draws 500-plus applicants per posting, and screening them slows every hire. Volume is the tell. When a role turns over that often, hiring cannot live in the owner's judgment; it has to live in a pipeline.

A working hiring SOP covers five things:

• One approved posting per role, stored and reused, never rewritten from scratch
• Screening disqualifiers, the 3 to 5 rules that cut 500 applicants down to a shortlist
• A scored interview, same questions every time, graded on a written rubric instead of a feeling
• A defined offer step, who calls, what they may offer, and by when
• A named owner per stage, so no candidate ever belongs to nobody

The rubric is the piece most small businesses skip and the piece that pays. A staffing agency we work with grades every interview against a written rubric, then rehearses new reps with mock calls before a live customer ever hears them. Two recent hires beat veteran numbers almost immediately; one placed 22 workers in her first 10 days. If you fill the same role every month, the hiring pipeline is the first HR SOP to write.

Example 2: New Hire Day-One Setup

Without an onboarding SOP, every company defaults to the same plan: shadow someone. It feels like training, but it is the reason a new hire can take 6 months to reach competence: what they learn depends on who happened to be nearby. A day-one SOP replaces that lottery with a procedure that starts before the person walks in.

The scope is deliberately narrow: everything between the signed offer and the end of the first day. Accounts created, tools installed, a named person waiting at the door, and a first-day schedule that teaches the must-know layer only. On one client rollout we learned to put the must-read up front and gate the depth behind links, because demoing every screen just makes a new hire's mind spin.

Day one is the first mile, not the destination. The full arc runs about 90 days, and we lay it out in the new hire onboarding checklist for the first 90 days. Write the day-one procedure first anyway: it is small, it runs every time, and it sets the tone.

Example 3: Equipment, Cards, and Access Provisioning

Company cards are the classic case. At one field services company, card issuance had a built-in lead time and the order went in on the start date, so techs spent up to 3 weeks fronting company expenses on personal cards. Nobody decided that; it was the absence of a procedure, compounding weekly.

A provisioning SOP is mostly a table: every item each role needs (card, vehicle, uniform, phone, logins, keys), the lead time for each, and the person who orders it. The trigger is the important part. Order anything with a lead time on the day the offer is signed, not the day the person starts. The 3-week item goes first, and the same-day items can wait.

A new hire buying gas on a personal card is not a finance problem: it is an HR procedure nobody wrote down.

Provisioning failures are quiet, which is what makes them dangerous. Nobody escalates them; people work around them on personal cards, borrowed logins, and someone else's key fob. Every workaround is a cost that never shows up in a report.

Example 4: The Exit and Knowledge Handoff Procedure

At a field services company, the bookkeeper resigned, and the exit surfaced a harder truth: none of the payroll and commission process she ran was ever documented. She is training her own replacement over screen shares in her final 3 weeks. One session took 85 minutes just to describe the weekly commission run, and the owner, watching his own process for the first time in years, realized it was a 3-day job every week.

An offboarding SOP has the parts everyone remembers, access shutoff, property return, final pay, and the part almost everyone skips: the knowledge handoff. Schedule recorded walkthroughs of the person's recurring tasks in the first week of notice, not the last. Rank the tasks by damage, and start with the ones only this person can do. With no notice at all, the procedure compresses to an emergency 2-week version: highest-risk knowledge first, intensive recording sessions, documents done before the last day.

The only exit procedure that will exist on the day someone resigns is the one you wrote before they did.

That commission run is also a warning about where HR borders on finance: a process like that belongs in your accounting SOP examples years before anyone gives notice, so the handoff becomes a review instead of an excavation.

Example 5: Performance Conversations on a Calendar

One electrical contracting owner told us he kept a struggling coordinator for years. The role had gone quiet, projects stalled, and the owner ended up working as his own coordinator's assistant, all reminders and pushing. His explanation was honest: the company was not built for turnover, so the underperformance was tolerated by default.

He also had core values framed on the wall, words like integrity, and admitted they had changed nothing about how anyone was hired, coached, or let go. Wall art does not manage performance. A calendar does. A performance SOP fixes a cadence (quarterly is plenty), a fixed agenda (score the role against its real responsibilities, bring examples, agree on one change), and a written follow-up.

A performance conversation that is not on the calendar is a conversation that is not happening. When the difficult conversation at that company finally happened, the fix on the table was not discipline. It was structure: post project updates in a shared channel on a rhythm, so silence becomes visible before it becomes a crisis.

---

How Do You Write an HR SOP?

You write an HR SOP by recording the person who actually runs the process and building the document from that recording, never from a template or a manager's memory. The method asks for about 2 to 4 hours of the practitioner's time per process.

1. Name one owner. Every HR process gets exactly one name next to it. If provisioning belongs to everyone, it belongs to no one, and the receipts pile up.
2. Record the practitioner. Do not ask anyone to write down how they do their job. Watch the person who runs onboarding actually run it, narrating on a screen share. Reality beats memory every time.
3. Capture three things. The purpose (why the process exists), the decision points (where judgment happens: what disqualifies a candidate, who approves an exception), and the step-by-step exactly as performed.
4. Write action headers. Open every step with a verb, and hold it to the glance test: a reader mid-task should glance at any step and know what to do.
5. Test on the next run. The next hire, the next exit, the next review cycle is your test. Fix what broke and ship the update the same week.

The sourcing matters more than the formatting. A procedure written by a manager from memory reads fine and fails in the field, which is why the rules in how to write SOPs your team will actually follow apply double here: the reader of an HR SOP is often a person on their first day, the least equipped reader in the building.

Which HR SOP Examples Should You Build First?

Build for the door that is busiest right now: the hiring pipeline if you fill a role every month, the exit handoff if one person holds a process nobody else can run. When we studied 16 small businesses across 68 roles and 461 process areas, an average of 27% of the work was documented, and half the role areas had nothing at all. HR almost always sits in the empty half, so sequencing is the whole game.

Use the symptoms to pick:

Read the middle column as a diagnostic. Whichever row made you wince is your first build. A staffing company we worked with had its customer service team cut to 2 people overnight and suddenly needed hiring for roles not even posted yet; by then you are writing the SOP during the emergency. And if HR is genuinely not your bottleneck, start wider with the first 5 SOPs every small business should document and circle back.

Do not build all five at once, and do not build the ones your calendar does not justify. If you hire twice a year, a saved posting and a scored interview cover it, and a full pipeline SOP is overhead nobody will maintain. Build the procedure the business is paying for right now, and let the next symptom tell you what comes after.

Interviewing the people who hold these undocumented processes and turning what they say into SOPs and training a new hire can follow is the work we do at The Systems Effect. You can start smaller than that. This week, pick one door: if you are hiring, write the pipeline; if someone could leave, write the exit handoff. One procedure, one owner, tested on the next real run.

Frequently Asked Questions

What HR SOPs does a small business need?

Start with five: a hiring pipeline for the roles you fill most often, a day-one setup procedure, an equipment and access provisioning checklist, an exit and knowledge handoff procedure, and a performance conversation cadence. They cover the two moments HR exists for, arrival and exit, plus the management rhythm in between. You do not need an HR department to run them. You need one named owner per procedure.

What should an onboarding SOP include?

An onboarding SOP should include a trigger (the signed offer), a named owner, the accounts and equipment provisioned before day one, a first-day schedule, and the must-know layer of training for the first week. Gate the deeper detail behind links so the new hire is not buried on arrival. End it with a completion check: the hire performs the core tasks rather than just watching them. Day one starts an arc that should run about 90 days.

How do you write a hiring SOP for high-volume roles?

Define the stages (posting, screening, interview, offer), then write the movement rules between them: 3 to 5 disqualifiers that screen fast, a scored interview rubric, and a named owner with a deadline for every stage. The rubric is what saves you at volume; at 500 applicants per posting, unscored interviews collapse into gut feel. Keep one approved posting per role instead of rewriting it every opening. Test the SOP on the next real vacancy and fix whatever candidates snag on.

What is an offboarding SOP?

An offboarding SOP is the procedure a company runs when someone leaves: access shutoff, property return, final pay, and a structured knowledge handoff. The handoff is the part that protects the business: recorded walkthroughs of the person's recurring tasks, scheduled in the first week of notice and ranked by the damage each would cause if it left with them. Written in calm times, it turns a resignation from a scramble into a checklist. Improvised in the final days, it usually captures a fraction of what the person actually knew.