A thousand hires is a thousand small orders, each needing the right kit for the right role in the right state.
New employees
Over about four weeks
Arriving in a stream rather than on one day, which is the part a spreadsheet process cannot absorb.
Packages each
Kit, uniform, safety
Contents differ by role and by state.
SKU per kit
One line to order
A kit is a single SKU to the buyer. Ordering for a new hire is one decision, not nine.
The five questions Section 9 asks
How employees are loaded and assigned products
Stage one · day 0–2
Pilot's HR system sends the roster it already keeps — employee ID, role, location, department, start date, approver. Nightly on a schedule from day one, by single sign-on once identity integration lands. Role decides the uniform package; role and state together decide the safety package, because Hi-Vis and FR requirements are not the same everywhere Pilot operates. Rows that arrive without a role are held and listed for Pilot's administrator rather than guessed at.
How managers approve, and how approvals are tracked
Stage two · continuous
A new hire's standard package is pre-approved by policy. Asking a manager to confirm a thousand times that a new employee needs the uniform they were hired to wear is a process that gets abandoned in week two. What routes to a manager is the exception: over allowance, a department charge, a restricted item. Each decision records who, when, and which rule fired, and an approval that ages past Pilot's threshold escalates on its own.
How inventory is managed before, during and after
Stage three · day −30 to +45
Before: a thousand hires against a known role mix is computable demand, and we stock the long-lead items to it. During: Pilot sees the same stock figures we do, with the date they were taken. After: demand reverts to replacement rates, and what happens to leftover wave stock is agreed up front rather than discovered. The row to watch is extended sizes. 2XL and above is where uniform waves quietly fail, and it is the first number we would put in front of Pilot.
How kits are assembled, packed, shipped and tracked
Stage four · rolling
Picked against the person rather than the order batch, so one parcel holds their polo, their vest in their size and their welcome kit. Decorated on our own floor. Packed in Pilot-branded outer with a packing list naming the employee and their location, and a returns label in the box. Carrier number pushed to the employee's order when the transfer is validated. A share of first garments will not fit. That is true of every program at this scale. What matters is that the exchange is started from the order page and costs the employee nothing.
How Pilot monitors it
Stage five · throughout
One view covering packages fulfilled, budget consumed, safety items issued and acknowledged, and the exceptions: backordered lines, approvals aging past threshold, employees imported without a role. Every row names an owner, ours or Pilot's, so the weekly call is about decisions rather than about whose number is right.
The standing program
Driver-direct ordering
Ordering from the cab
Phone-first, home delivery, personal allowance, no manager in the path for a standard replacement.
PPE
Stored, issued, recorded
Held in stock, issued against role eligibility, and recorded as issued to a named person on a date — which is what an audit asks for.
Recognition
On the same ledger
Service anniversaries, safety milestones and spot awards run as credit against a recognition budget, so the spend lands in the same reporting as everything else.
Inventory
One pool, not four
Uniforms, safety, swag and recognition draw on the same stock. A program per silo is how a company ends up holding four sets of the same polo.
A roster feed with role, location, department and approver. Allowance amounts by role. Approved artwork and a brand standard. Confirmation of safety requirements by state and role — that one is a compliance question we will not answer on Pilot's behalf.