Hourly and industrial
Fill this week's shifts from workers you have already placed
A warehouse client calls on Monday needing forty pickers by Wednesday night. Everything on this page exists to make that a solved problem rather than a scramble.
Surhires runs a high-volume hourly desk: bulk import and parse hundreds of applications, filter by travel radius, transport access, shift availability and licence class, then reach the shortlist by WhatsApp and SMS. Workers who finished an assignment stay in a re-book pool you call first.
By Surhires Editorial · Published · Reviewed
The number that runs this desk is cost per filled shift
A permanent desk measures itself in fees. A blue collar desk measures itself in filled shifts, and the arithmetic is unforgiving: a small margin multiplied by a large number of hours, minus whatever you spent to find the person. Spend forty pounds acquiring a picker who works one nine-hour shift and never answers again, and that fill lost money before payroll ran.
That is why almost everything on this page is about reducing the cost of the next fill rather than improving the quality of the last one. The three levers are throughput, reach and reuse. Throughput means screening two hundred applicants without spending two hundred minutes. Reach means the shortlist actually answers. Reuse means the worker you placed in March is the worker you place in September, at no acquisition cost at all.
Surhires is built around those three. It does not attempt to make a warehouse fill feel like an executive search, because that is not the job.
Volume screening is a throughput problem, not a judgement problem
On a professional desk the constraint is depth: you read the resume properly because getting it wrong is expensive. On an hourly desk the constraint is speed. Three hundred applications land against a picking role and the only questions that matter are whether the person can physically get to the site, whether they are free for the shift pattern, and whether they hold whatever ticket the site requires. Everything else is noise until those three are answered.
Bulk import takes a folder of resumes or a job board feed and parses all of them at once, writing structured fields rather than a text blob. The list view then filters on those fields directly. A recruiter is looking at a shortlist of nineteen within minutes of the applications landing, and the two hundred and eighty-one who did not match are still in the database, tagged, for the next role that suits them.
- Bulk resume upload and parse, with duplicate detection running during the import rather than after it
- Knockout fields set per requisition, so an applicant missing a required licence never reaches the recruiter's list
- One-click bulk actions from the list: tag, pool, message or move two hundred records at once
- Applications from a job board feed parsed into the same structure as an uploaded resume
Geography and transport decide who can actually take the shift
Postcode matching is not the same as travel radius, and travel radius is not the same as whether somebody can get to a distribution park for a six a.m. start. A worker eleven miles away with a car is closer, in every sense that matters, than a worker four miles away with a bus route that starts at seven.
Candidate records carry a home location, a maximum travel distance the worker themselves set, and a transport field: own vehicle, public transport only, willing to use the site shuttle, or dependent on a lift. Search runs on all of them together. A six a.m. shift at a site with no early bus service can be filtered to drivers before a single message goes out, which prevents the most common and most expensive failure on this desk: a confirmed worker who simply cannot arrive on time.
Shift patterns are the real requisition, not the job title
Two roles called warehouse operative can be entirely different jobs. One is a rotating four-on-four-off pattern including nights. One is Monday to Friday, six until two. The worker who suits one may be unable to take the other, and the job title tells you nothing.
Requisitions on this desk carry the pattern as a structured field: days, start time, duration, whether nights are included, whether weekends are included, and the assignment length in weeks. Candidates carry the same field as availability. Matching runs on the overlap. It also means a client who describes a role loosely gets asked the right question at intake, because the field cannot be left blank on a requisition that is about to be broadcast to four hundred people.
Licences and tickets expire, and the expiry is most of the work
Counterbalance and reach truck licences, CSCS cards, HGV categories, forklift refresher dates, food hygiene certificates, right-to-work documents: on an industrial desk these are not attachments, they are the thing that makes a worker placeable this week rather than next month. And they all expire.
Every ticket is a typed record on the candidate: class, issuing body, issue date, expiry date and the scanned document. Expiry generates a reminder before it lapses rather than a discovery on the morning of a shift. Search treats a licence class as a facet, so a request for four counterbalance drivers with a live card returns exactly that, and a card that expired last Tuesday takes its holder out of the result rather than out of the client relationship.
- Typed licence and ticket records with class, issuer, issue date and expiry
- Expiry reminders raised as tasks on the desk before the document lapses
- Right-to-work and working-rights document capture with the same expiry handling
- Required-at-stage rules so a worker cannot be booked to a site missing a mandatory ticket
This workforce answers a phone, not an inbox
Email response rates on an hourly desk are poor and it is not a mystery why. A picker finishing a night shift is not opening a laptop. They are looking at a phone, and the message they will answer is a WhatsApp or an SMS, usually within minutes.
Surhires treats messaging as the primary channel rather than a bolt-on. A shift offer goes out to a filtered pool as a templated WhatsApp or SMS message, replies land against the candidate record rather than in somebody's personal phone, and a yes moves the worker onto the booking without retyping. The reply handler classifies inbound answers so a recruiter reads the fourteen people who said yes rather than scrolling ninety threads.
Consent and opt-out handling sit underneath all of it. Opt-in is captured on the record with the date and channel, STOP and unsubscribe keywords are honoured automatically, and suppression is enforced at send time. Whether a given campaign is lawful still depends on how you configure and send it, and on your own carrier registration where US SMS is involved.
The re-book pool is worth more than any sourcing channel
A worker who completed an assignment for you, turned up on time, and was not a problem on site is the single most valuable record in the database. They are pre-screened by the only test that counts, which is that they actually did the job. Sourcing a replacement costs money; calling them costs nothing.
Talent pools hold these workers by site, by client, by shift pattern and by ticket. Every completed assignment writes back to the record: which client, which site, which dates, whether they finished, and a simple internal reliability marker. When Monday's forty-picker request arrives, the first action is a broadcast to the pool that worked that site last quarter, and it is normal for that broadcast alone to close most of the requirement before any advertising spend happens.
This is also the number an owner should watch. The proportion of fills coming from re-books rather than new sourcing is a direct measure of whether the desk is compounding or churning.
What this is not, and where the boundary sits
Surhires is recruitment software. It is not a payroll engine, a timesheet and rostering system, or an umbrella company platform. It holds the worker, the booking and the client relationship through to the placement record and the first invoice; it does not calculate holiday accrual, run a PAYE cycle, or price an award.
For most hourly desks that means Surhires sits in front of a payroll or timesheet system rather than replacing it, and the placement record is the handover point. Naming that boundary matters more here than on any other desk, because the compliance and pay obligations attached to hourly work are real and belong to systems built for them.
What you get
Bulk resume import
Upload or feed hundreds of applications at once, parsed into structured fields with duplicates caught inline.
Knockout filters
Per-requisition required fields remove non-viable applicants before a recruiter opens the list.
Travel radius search
Home location, worker-set maximum distance and site postcode evaluated together.
Transport access field
Own vehicle, public transport, shuttle or lift-dependent, filterable for early starts.
Shift pattern matching
Days, start time, nights and weekends stored on both the requisition and the worker.
Licence and ticket records
Class, issuer, issue and expiry dates with the scanned document on the candidate.
Expiry reminders
Tasks raised before a card lapses rather than a discovery on shift morning.
WhatsApp and SMS broadcast
Templated shift offers to a filtered pool, with replies landing on the record.
Reply classification
Inbound yes, no and question replies sorted so recruiters read decisions, not threads.
Opt-in and suppression
Consent captured with date and channel; STOP and unsubscribe enforced at send time.
Re-book pools
Workers grouped by site, client, shift pattern and ticket for first-call broadcasts.
Assignment write-back
Every completed booking records client, site, dates and completion on the worker record.
Reliability markers
A simple internal marker for turned up, completed and would re-book, visible on search.
Mobile recruiter app
Book, message and confirm workers from a phone when the desk is not at a desk.
Fill-rate reporting
Fills by client and site, and the share coming from re-books rather than new sourcing.
Questions recruiters ask
Can we book the same worker onto repeat shifts without re-entering everything?
Yes. A worker who has completed an assignment carries their site history, tickets, pattern and transport on the record, so a repeat booking is a selection rather than a data-entry exercise. Broadcasting a new shift to a pool of previous workers at that site is a single action from the list view.
Does Surhires handle timesheets and payroll for hourly workers?
No. It is recruitment software, not a payroll or rostering system. It holds the candidate, the booking, the placement record and the first invoice. Hours worked, holiday accrual, awards and pay runs belong in a payroll or timesheet system, and the placement record is the handover point between the two.
How do we stop sending shift offers to people who asked us not to contact them?
Opt-out is stored on the candidate record with the date and channel it came through. STOP and unsubscribe keywords are honoured automatically and suppression is applied at send time rather than at list-build time, so a worker who opts out after a campaign is queued still does not receive it.
What happens when a licence expires mid-assignment?
The expiry date is a typed field, so a reminder is raised on the desk before it lapses and the worker is flagged on any requisition that requires that class. Whether the worker can remain on site is a decision for you and your client; the product surfaces the fact in time for that conversation to happen.
Can we run this across several branches with different client lists?
Yes. Requisitions, clients and pools are scoped by team, and visibility follows the permission model rather than a personal filter. Multi-entity and multi-brand configurations sit on the Enterprise plan, where a group running separately branded branches can keep the data separated while reporting rolls up.
Is there a candidate limit that a high-volume desk would hit?
The Starter plan caps at five hundred candidates, which a busy hourly desk will pass quickly. Professional and Enterprise are not capped on candidate count. Search behaviour at very large database sizes is something we test rather than assume, and Enterprise accounts are sized during onboarding.
Do workers need an account to confirm a shift?
No. A shift offer sent by WhatsApp or SMS can be confirmed by replying, and the reply handler moves the record. A candidate portal exists for workers who want to update availability, phone number or documents themselves, but it is optional and nothing in the booking flow depends on it.
Keep reading
- Reach candidates on the channel they actually read
- Turn a resume backlog into records you can search
- The lists you rebuild every month, built once
- Work the desk from the platform you carry
- Every candidate conversation on the candidate record
- Run a contract book on margin, not on fee
- Know why you hold every candidate record, and for how long
See it against your own reqs
Bring one live role and three resumes. In twenty minutes you will see the match scores, the shortlist and the placement invoice that comes out the other end.