# How to Hire Hourly Employees

> Applicant tracking systems were built to coordinate several people around one hire. Most frontline hiring is done by one person whose real job is something else. Here is a process that fits the second case.

Author: Kariaa Research
Published: 2026-08-08
Category: Guides
Reading time: 11 min read
Canonical URL: https://www.kariaa.com/reports/how-to-hire-hourly-employees

---

import { FlowSteps, CompareColumns, RankedList, Takeaways, FAQ } from "@/lib/report-charts";

A restaurant owner needs four people before the weekend. A home-care agency has
eleven open caregiver requisitions and one office manager who also runs payroll,
scheduling and complaints. A machine shop needs a welder who can pass a coupon
test, and has needed one for five months.

None of these people are recruiters. Hiring is a task that arrived on top of
their actual job, and it arrives again every few weeks. The software industry's
answer to hiring, the applicant tracking system, was not designed for them, and
the mismatch is not about price.

## What an ATS is actually for

**An applicant tracking system is a coordination tool for organizations where
many people touch one hire.** That is the problem it solves. A recruiter sources,
a coordinator schedules, a hiring manager interviews, a second panel interviews
again, an approver signs off, and someone needs a record of all of it months
later. The system exists so that six people can act on the same candidate without
having to talk to each other.

Most frontline hiring has one person touching the hire. The coordination problem
the software solves does not exist, and what remains is the overhead: a
requisition to configure, a workflow to define, stages to move people through,
and a login to remember between bursts of activity six weeks apart.

The result is familiar to anyone who has watched it happen. The system gets
configured once, used for one role, and abandoned. The next hire runs in a text
thread and a spreadsheet, because that is where the work actually is.

**The failure is not indiscipline about tooling. It is a tool built for a
different shape of problem.**

## The five things a hiring process has to do

Strip away the software and a hiring process does five things. Every one can be
done without an ATS, and skipping any one is what makes hiring feel chaotic.

<FlowSteps
  steps={[
    { label: "Write the role down", sub: "Once, properly" },
    { label: "Reach people", sub: "More than one channel" },
    { label: "Screen against the role", sub: "Same order, every time" },
    { label: "Check what must be true", sub: "Credentials, authorization" },
    { label: "Hand off to the first shift", sub: "Where hires are lost" },
  ]}
  note="None of this requires software. It requires the same five steps in the same order every time."
  caption="The irreducible hiring process"
/>

Naming them makes the process auditable by one person. When a role has been open
for two months the question is not what the dashboard says. It is which of the
five is failing, and each fails in a recognizable way.

## Step one: write the role down once, properly

Most frontline job posts are written in ten minutes and describe the employer
rather than the job. They lead with company history, list duties in the abstract,
and bury the facts a candidate actually decides on.

**A candidate deciding whether to apply is answering four questions, and a post
that does not answer them is filtered out before it is read.** What does it pay.
Where is it, precisely. What hours, on what days. What is required on day one
that I either have or do not.

Pay is the one most often omitted and the one that costs most. A post without a
range competes against posts with one, and the person reading both has no reason
to spend effort finding out. Where a range genuinely cannot be published, a floor
is the next best thing.

The rest is subtraction. A caregiver post listing fourteen requirements is
usually describing a wish, and every item past the real minimum removes people
who could do the job. Write the requirements that would actually cause you to say
no. Put the others in a separate list, where they belong.

## Step two: reach people through more than one channel

**Posting a role is not sourcing it.** Posting reaches people currently looking on
the board you posted to. In frontline and skilled trades that is a minority of
those who could do the job, and frequently not the strongest of them. A good
welder with steady work is not refreshing a job board.

The channels that matter here are unglamorous and mostly not software.

<RankedList
  items={[
    {
      label: "Referrals from current staff",
      note: "Consistently the highest-converting channel in frontline work and the one most often left to chance. A standing, specific, paid referral offer behaves very differently from a poster in the break room.",
    },
    {
      label: "Past applicants you already have",
      note: "People who applied for an earlier opening and were not hired for reasons that no longer apply. Most operators never contact them again, which makes this the cheapest source of qualified candidates in the building.",
    },
    {
      label: "Job boards",
      note: "Necessary, with a ceiling set by who is actively looking this week. Best treated as one input rather than as the strategy.",
    },
    {
      label: "Local and trade-specific channels",
      note: "Union halls, training programs, community colleges, trade associations, local language-community groups. Slower to build, and they reach people no board reaches.",
    },
    {
      label: "Passive outreach",
      note: "Contacting people who are not looking. The hardest to run, and the only one that reliably reaches the strongest candidate in a tight market.",
    },
  ]}
  caption="Sourcing channels for frontline roles, roughly by yield per unit of effort"
/>

The practical rule is that a role open longer than a month is almost never
failing at screening. It is failing at reach, and adding a second board rarely
fixes it, because the second board draws from the same pool as the first.

## Step three: screen in the same order every time

Screening without software is not screening without a method. The method is an
order of operations, and the order matters more than the tooling.

**Check the disqualifying facts first, the hard-to-teach abilities second, and
the trainable skills last.** Most people do this backwards. They read the whole
application, form an impression, and then discover the candidate cannot work the
shift the role exists to cover. Ordering the checks means expensive judgment is
only spent on people who could actually take the job.

That is covered properly in [How to Screen Job
Applicants](/reports/how-to-screen-job-applicants), including how to write
pass and fail conditions down so two people screening the same pile arrive at
the same shortlist.

## Step four: check what has to be true before the first shift

For a large share of frontline roles something must be verifiably true before a
person can legally or safely start: a license, a certification, a clearance, work
authorization, a background check appropriate to the setting.

**The cost of checking these late is not the check. It is the shift you have
already built the schedule around.** A credential discovered to be expired the
week someone starts is a coverage problem rather than a paperwork problem, which
is the argument for moving it early rather than leaving it to onboarding.

[Employee Credential Verification
Checklist](/reports/employee-credential-verification-checklist) sets out what
to collect, when, and how to track expiry without a compliance system.

## Step five: the handoff nobody owns

The largest single loss in frontline hiring happens after the yes. A candidate
accepts, hears nothing for nine days, and does not appear.

This gap is structural rather than careless. The hiring burst ends at the offer,
the person who ran it returns to their real job, and nothing in the process is
responsible for the interval between acceptance and the first shift. Nobody
schedules silence. It is what is left when no step owns the time.

The fix is unglamorous: a named person, a scheduled contact before the start
date, and confirmation of the three facts a new hire needs, which are where to
be, when, and what to bring. The same mechanism produces interview no-shows,
and is examined at length in [How to Reduce Interview
No-Shows](/reports/how-to-reduce-interview-no-shows).

## What replaces the ATS

Nothing, in the software sense, for most operators. What replaces it is a written
process, one list, and a decision about who owns each step.

<CompareColumns
  left={{
    title: "What an ATS gives you",
    items: [
      { label: "Multi-person coordination on one candidate" },
      { label: "An audit trail across months and reviewers" },
      { label: "Requisition approval workflows" },
      { label: "Structured reporting across many roles" },
      { label: "Records for a regulated hiring process" },
    ],
  }}
  right={{
    title: "What frontline hiring actually needs",
    items: [
      { label: "One candidate list, current today" },
      { label: "The same screening order every time" },
      { label: "Credentials checked before the first shift" },
      { label: "A reply that reaches people who do not use email" },
      { label: "Someone owning the gap before day one" },
    ],
  }}
  caption="The mismatch is in the problem, not the price"
/>

The one place a tool earns its keep is reach and response, the two parts that do
not scale with effort. Sourcing beyond the boards is genuinely hard to do alone,
and so is replying to sixty applicants within a day when hiring is your third
priority.

That is the part Kariaa runs. Candidates build one verified profile, eight fields
ending with work authorization, and applications arrive already checked against
the requirements you set: marked passed or failed per requirement, with the
evidence and a confidence level, alongside an advisory fraud read. The shortlist
is a table you can sort and export, and moving someone forward is one of four
next steps, being a video interview, a set of questions, a booking, or a message.
Candidates reply in WhatsApp or Telegram, which is where this workforce answers.

For companies that would rather hand the search over entirely, [Kariaa's
recruiting service](/recruiting) runs the sourcing and screening and returns a
shortlist. The five steps above are what separates a search that closes from one
that stays open for five months.

<Takeaways
  items={[
    "An ATS solves multi-person coordination. Frontline hiring usually has one person, so the software adds overhead without removing work.",
    "A role open longer than a month is almost always failing at reach, not at screening. A second job board draws from the same pool as the first.",
    "Referrals and past applicants are the two highest-yield channels, and the two most commonly left to chance.",
    "Screen in a fixed order: disqualifying facts, then hard-to-teach ability, then trainable skills. Most people do it backwards.",
    "Check credentials and work authorization early. Found late, they are a coverage problem rather than a paperwork one.",
    "The largest loss happens after the offer. Give someone ownership of the interval between acceptance and the first shift.",
  ]}
/>

<FAQ
  items={[
    {
      question: "Do I need an applicant tracking system to hire frontline workers?",
      answer: "No. An ATS exists to coordinate several people acting on the same candidate, such as a recruiter, a coordinator, a hiring manager and an approver. Most frontline hiring is done by one person, so that coordination problem does not exist and the software adds setup work without removing any. A written process, one candidate list, and clear ownership of each step covers it.",
    },
    {
      question: "Why is my job posting producing no qualified applicants?",
      answer: "A role that stays open past about a month is usually failing at reach rather than at screening. Posting reaches people actively looking on that board this week, which in frontline and skilled trades is a minority of qualified people. Adding a second board rarely helps because it draws from the same pool. Referrals, past applicants and trade-specific channels reach different people.",
    },
    {
      question: "What should a frontline job post include?",
      answer: "The four things a candidate decides on: the pay range, the precise location, the hours and days, and what is genuinely required on day one. Omitting pay is the most costly omission, because the post competes against posts that include it. List only requirements that would actually cause you to reject someone, and separate everything else.",
    },
    {
      question: "In what order should I screen candidates?",
      answer: "Disqualifying facts first, meaning availability for the required shift, work authorization, and any license the role legally requires. Then the abilities that are hard to teach. Then trainable skills last. Screening in this order means detailed judgment is only spent on candidates who could actually take the job.",
    },
    {
      question: "Why do new hires not show up for their first shift?",
      answer: "Most often because nothing in the process owns the interval between acceptance and the start date. The hiring burst ends at the offer and the person who ran it returns to their other work, leaving days of silence that nobody scheduled. A named owner, a scheduled contact before the start date, and confirmation of where to be, when, and what to bring removes most of it.",
    },
  ]}
/>

---

*Written by the team at **Kariaa**. Learn more at [www.kariaa.com](https://www.kariaa.com).*