Hiring another person should remove a defined block of work from your business. It often does something more expensive.
It adds a name to the rota, adds a worker to payroll, and leaves the block of work exposed anyway.
The missing stage is qualified coverage. It isn’t headcount. It’s the right person, with the needed skill, at the required location and time, who actually attends. A rota with every shift named can still fail at the opening check, the lunch rush, the handoff, or the closing task. Payroll then records the cost of a role the schedule never truly absorbed.
Very efficient way to buy the same problem twice.
The Demand Map
Open the requisition with four to eight weeks of work that hasn’t been completed reliably. Record the task, when it occurs, who performs it now, what happens when it waits, and whether it’s recurring or project-bound.
The unit isn’t “one extra person.” It’s orders per hour, service calls per day, reconciliations per month, opening hours, demand peaks, and the minimum qualified people you need at once.
Choose the interval that can show the shortage. Fifteen- or 30-minute blocks can reveal a telephone queue or lunch rush. Daily blocks can fit field work. Weekly blocks can fit bookkeeping or content production. A weekly average showing spare capacity can conceal a three-hour gap that stops the operation. Make the interval useful, not decorative.
Then test the proposed role in three passes:
- Remove or automate work that shouldn’t become a permanent duty.
- Reassign a coherent block to an existing employee and redesign the work left behind.
- Hire an employee or engage an outside service for the work that remains.
The role needs one primary outcome, three to six recurring responsibilities, and two to four capabilities required on day one. Those are operating bands, not law.
They prevent the familiar posting that asks one person to do bookkeeping, sales, customer support, purchasing, and the founder’s personal administration. That isn’t a role. It’s a scavenger hunt with payroll attached.
The Role Plan
Build the plan before you advertise. It forces the requisition, schedule, worker relationship, and payroll inputs to describe the same work.
| Uncovered task | Coverage window | Required skill | Schedule volatility | Worker relationship | Pay cost | Proficiency date |
|---|---|---|---|---|---|---|
| Named output that waits or fails | Demand interval, location, and minimum qualified presence | Required on day one; trainable items marked separately | Notice, changed hours, start-time consistency, swaps, and recovery time | Employee or contractor facts: control, tools, continuity, outside clients, and accepted result | Rate or salary, earning code, overtime/leave treatment, deductions, and employer charges | Observable task and supervision level, not “fully onboarded” |
O*NET’s distinction among tasks, work activities, work context, skills, knowledge, abilities, and experience requirements is useful here. It exposes whether a tidy title contains one occupation or several. Licences and credentials stay hard constraints when law, insurance, or the work requires them. The rest belong on a required-versus-trainable line.
Pay position needs the same discipline. BLS wage data give you the 10th, 25th, 50th, 75th, and 90th percentiles for the relevant occupation, location, industry, and experience level. An entry role may be compared with the local 25th percentile, while a scarce licence, an inconvenient shift, or immediate autonomy can move the reference toward the median or higher.
National averages and your last employee’s wage don’t tell a candidate what this shift costs to accept.
The Schedule Test
Total weekly hours aren’t coverage. For every demand block, record required people or labor-hours by skill and location, planned assignment when the rota publishes, assignment after changes, and attendance actually delivered.
That separates schedule construction from schedule execution.
The corpus’s invented seven-day example makes the point. 420 labor-hours of demand against 407 scheduled hours appears to give you 96.9% coverage. When 36 scheduled hours lack the necessary opening or equipment qualification, effective coverage is 371 hours, or 88.3%. If that missing time sits in nine peak intervals of 30 minutes, the weekly percentage isn’t the operating truth.
The exposed intervals are.
Stability is a separate control. The Department of Labor research synthesis treats employer-driven variation above 25% across the preceding month as an analytical boundary, and separates it from flexibility the worker chose.
A practical starting setting is committed hours published at least 14 days ahead, the next 7 days frozen except for genuine exceptions, and employer-driven weekly-hour variation kept below 25%.
That’s an operating setting, not a universal legal rule. Agreements and local scheduling laws can be stricter.
Don’t use a swap tool as a substitute for capacity. Track who initiated the change. A voluntary swap and a same-day employer cancellation can alter the same four hours while saying opposite things about your schedule. Track call-outs, late arrivals, no-shows, manager edits, and planned versus actual hours beside the published rota. Scheduled time and observed time aren’t synonyms.
The Relationship
Choose worker status before you post and before the first payment.
For U.S. federal tax purposes, the IRS groups the evidence under behavioral control, financial control, and the parties’ relationship. The federal wage-and-hour analysis uses six economic-reality factors. Neither a 1099 nor an independent-contractor agreement settles the facts.
Fixed recurring shifts, business training, company procedures, company tools, continuing supervision, personally performed core work, and permission needed to serve other clients all shape a role like employment. A contractor-shaped engagement specifies a result, permits independent methods, leaves room for other clients, and ordinarily ends with the project.
Don’t make this a points contest. The tests weigh the whole relationship, and other jurisdictions can apply different standards.
That decision changes your payroll design. An employee master needs effective-dated identity, work location, start date, pay group, rate or salary, tax profile, benefits, leave rules, bank instructions, and authorized deductions.
A rate change effective July 1 has to coexist with the rate used through June 30. Overwrite the old rate and your next correction becomes archaeology.
The Payroll Bridge
The worker has to cross six clocks: work-period start, work-period end, time-entry cutoff, approval deadline, payment release, and pay date. Add the workweek boundary for overtime and the remittance calendar for deductions. “Payroll date” is a phrase that has hidden more errors than it has solved.
Pay frequency is a parameter, not a label, and the deduction tables your jurisdiction publishes are keyed to it. British Columbia, for example, currently requires wages at least semimonthly and within 8 days after the pay period ends. Pay frequency doesn’t determine remittance frequency.
Close time by workweek as well as by pay period. Under the U.S. federal FLSA, the workweek is a fixed recurring 168-hour interval, and covered nonexempt employees generally receive at least 1.5 times the regular rate after 40 hours in that workweek.
A biweekly run can’t simply inspect whether somebody exceeded 80 hours.
British Columbia’s general rules currently use overtime after 8 hours in a day or 40 hours in a week, with double time after 12 hours in a day, and valid averaging agreements can span 1 to 4 weeks. Jurisdiction isn’t a footnote here. It selects the calculation.
Your register should preserve regular, overtime, bonus, commission, leave, and taxable-benefit earnings; pretax, statutory, and after-tax deductions; employee withholding and employer contributions; net pay by delivery method; off-cycle payments, reversals, and voids; and year-to-date amounts before and after the run.
A single gross-pay total can’t show whether new hires, overtime, a leave payout, a rate change, or an uncoded exception caused the movement.
Before the Next Requisition
Use the symptom to find the broken stage before you open another requisition.
The roster is full but a key task is uncovered → demand mapping or schedule construction is broken
Scheduled hours were counted without required skill, location, or the actual coverage window. Rebuild the demand blocks and calculate qualified coverage, not total hours.
The published rota looks covered but the day still breaks → schedule execution is broken
Compare published assignments with manager edits, swaps, call-outs, late arrivals, no-shows, and attendance. Repeated exposure by manager, day, role, or interval identifies the handoff that needs repair.
Payroll rises after hiring while output doesn’t → time or pay-code reconciliation is broken
Compare expected changes — new starters, rate changes, leave, benefits, bonuses, and overtime — with surprise reports for paid workers absent from that list, zero or negative net pay, new bank accounts, and deductions that appear or disappear.
A contractor works recurring business shifts like staff → classification is broken
Review the agreement against actual instructions, training, schedule control, tools, expenses, payment method, opportunity for profit or loss, permanence, benefits, and whether the work is central to your business. Record “requires classification review” until the applicable test is assessed.
New hires leave after training or once solo shifts begin → absorption is broken
Inspect the promised schedule, actual schedule volatility, named trainer, authority to decide, and proficiency task. A worker who needs approval for every routine exception has been hired into permanent dependence, not coverage.
Early retention is argued from stories → measurement is broken
Group actual starts by month or quarter, then measure 30-, 90-, and 180-day survival. Don’t put a recent cohort into a 180-day denominator before every member has had the observation period. Incomplete outcomes are censored, not retained.
The Control Loop
Run the comparison across every boundary: required coverage, scheduled assignment, actual attendance, approved time, frozen payroll register, payment instruction, bank settlement, general-ledger posting, liability, and authority acceptance.
“File generated,” “bank accepted,” and “employee paid” are different states. A payment your bank rejected remains an obligation even when the cash comes back.
Use exceptions with owners and ages. Time records need a worker, pay-period, and workweek match, so inspect missing punches, overlapping intervals, negative durations, implausibly long shifts, work during approved leave, and repeated manual overrides.
Replace missing evidence with scheduled hours and you haven’t repaired the record. You’ve renamed an assumption.
Headcount is an input. Qualified attendance is coverage. Payroll is a cost record. Reconciled time is the evidence for it.
Map the uncovered task before the requisition. Schedule the skill before the shift. Pay only the time your control trail can explain.