Outfitting fifty staff is a shopping trip; outfitting five thousand is a supply chain. Between those numbers sits every uniform program that ever embarrassed itself at rollout: sizes missing at the extremes, spares forgotten, reorders arriving in a different shade. Planning is the discipline that keeps the program boring, and boring is the highest praise a uniform rollout can earn. This guide sets out the planning math, from headcount models to issue cycles, for programs of literally any size.
It covers our work shirt and classic pique polo shirt production and how to get a quote structured for a phased rollout.
Start With Roles, Not Garments
The plan begins with the org chart, not the catalogue. Roles decide garments: the facilities crew needs reinforced workwear, client-facing staff need the polished polo, supervisors need a distinguishing variant, and each role’s environment answers the fabric questions before a single style is chosen. A headcount that says five hundred staff says nothing; a headcount that says three hundred and eighty warehouse, ninety drivers and thirty reception says everything.
Roles also decide quantities per person, because a driver issued two shirts and a warehouse operative issued five are both correctly served by the same program. Issue numbers follow the laundry reality of each role: how often the garment is worn, washed and expected back, which is arithmetic, not generosity. The arithmetic also decides dignity: roles that face the public daily are resourced first and replaced fastest when garments tire, because the program’s reputation is worn by its most visible people, and a faded reception polo argues against the whole proud estate.
The Garment Matrix: Who Gets What, Written Down
The role analysis becomes a document: the garment matrix, one row per role, one column per garment, quantities in the cells. It sounds bureaucratic until the first dispute: the matrix settles who was promised the fleece, which roles carry names, and where the hi-vis variant applies, without a single meeting. Every stakeholder signs the same matrix, and every later argument is a reading exercise.
The matrix also exposes the quiet inefficiencies: roles issued garments they never wear, premium fabrics spent on garments the public never sees, and the supervisor variant that multiplies styles beyond what production minimums forgive. Pruning the matrix before ordering is the cheapest saving in the whole long program, and it costs only plain honesty.
Small programs need the matrix too, in miniature: fifty staff still span roles, and the two-page version prevents the classic, avoidable small-fleet failure, where the order is one style in five sizes and the reality is four jobs in nine.
The Size Curve: Planning for Real Bodies
Every workforce distributes across sizes in a curve, heavy in the middle sizes, thin at the extremes, and the curve is where rollouts quietly fail: the mediums arrive in plenty while the 3XL wearer gets an apology. Planning orders against a curve built from the actual workforce where possible, from industry norms where not, and always with the extremes deliberately overweighted, because the cost of two spare large shirts is nothing beside the cost of one visibly ununiformed employee.
Sizing sessions earn their keep on larger programs: a fitting range travelling between sites, or a measured sample set held at each location, converts guesses into data and shrinks the exchange pile that otherwise eats the spare stock in week one. The exchange pile deserves respect as data: every swapped garment is a measurement the curve got wrong, recorded in the issue log and fed into the next wave’s forecast, so the program’s sizing literally learns its own workforce.
Spares, Joiners and the Buffer Nobody Budgets
Programs fail in the months after rollout, not at it. Staff join, leave, change size and lose garments; laundry eats a percentage; accidents eat another. A working buffer runs at ten to fifteen percent of headcount spread across the size curve, held as unbranded or branded stock according to the branding system, and replenished on a rhythm rather than in a panic. The rhythm is calendar-simple: buffer counted monthly, reorders triggered at a floor level rather than at empty, and a named owner for the stock, because buffers without owners evaporate into favours and emergencies within a single year.
The buffer is also where the reorder discipline lives: minimum reorder quantities agreed in advance, the branding file and approved samples held by the factory, and shade continuity protected by retaining the original dye-lot references, because a buffer that arrives in a visibly different navy is a new problem wearing the uniform of a solution.
Laundry Logistics: The Hidden Half of the Plan
The laundry decides more of the program than the catalogue does. A contract laundry’s temperature, chemistry and cycle length set the fabric and colour-fastness requirements, the issue quantities (garments in the wash are garments off backs), and the attrition rate the buffer must feed. Programs planned without the laundry’s actual specification are planned against a polite fiction.
Issue and return logistics ride along: who holds stock, who records exchanges, how soil and damage are honestly graded, and when a garment is retired rather than reissued. None of it is remotely glamorous, and all of it is the difference between a program and a pile of shirts in a cupboard that nobody owns.
Where staff launder their own garments, the plan changes again: care labels written for home machines, fabrics that forgive domestic temperatures, and issue quantities that respect the reality that a home wash happens when it happens.
Phased Rollouts and Pilot Groups
Beyond a few hundred staff, the wise program pilots: one site or one department first, worn and washed for a month, with feedback collected like evidence. The pilot catches the pocket in the wrong place, the fabric that fades at the laundry’s temperature, the size curve that guessed wrong, while the mistakes are still cheap. Choose the pilot group for honesty rather than enthusiasm: the crew most likely to complain is the crew most likely to teach, and a pilot among friends produces warm compliments, not corrections. What the pilot teaches is written into the main order, not carried as folklore.
Phasing also smooths production and cash flow: sites convert in waves, sizes are re-forecast between waves from real issue data, and the final wave is the most accurate order the program will ever place. The factory relationship matters here: a supplier who treats wave three’s corrections as cooperation rather than complaint is a supplier worth keeping.
Budgeting the Program: Cost Per Wearer Per Year
Uniform budgets mislead at the garment level and clarify at the wearer level: cost per wearer per year, counting issue quantities, buffer burn, replacements and branding, is the number that lets programs be compared truly honestly. The cheapest shirt in the tender often carries the dearest wearer-year, through exchanges, failures and emergency reorders at courier prices.
Phasing flatters cash flow honestly rather than cosmetically: the pilot’s cost is small, waves spread the commitment, and the re-forecast between waves cuts the dead stock that a single giant order guarantees in practice. Finance prefers programs whose second order is visibly smarter than their first, and phased planning is how that story gets told.
The tender itself should ask for the program, not the pieces: per-wearer pricing across the size curve, buffer and reorder terms agreed in advance, and shade-continuity commitments in writing. Suppliers who price the program reveal themselves quickly; suppliers who price only the shirt reveal themselves too.
Names, Branding and Leavers: The Identity Layer
Identity decisions belong in the plan, not down at the embroidery machine. Named garments personalize the fleet and complicate everything else: leavers take their names with them, new joiners wait for sewing, and the buffer can no longer be generic. Programs choose their compromise deliberately: names on a removable or re-embroiderable panel where fleets churn, permanent names where teams are stable, roles instead of names where privacy or turnover argues.
Branding interacts with phasing as well: branded buffer stock commits money to a design that may be refreshed, so some programs hold buffer unbranded and brand at issue, accepting a small delay to keep options open. The branding file from the placement planning travels with the program either way, and consistency across waves is checked against the held approved garments, not against photographs of them.
Lead Times: The Calendar Is a Specification
Programs are dated backwards from the day the fleet must appear: the new contract start, the rebrand launch, the venue opening. From that date the plan subtracts production, shipping, branding, distribution and the fitting exchanges after issue, and discovers that the order should have been placed last month. Made on paper, the discovery costs an earlier signature; in reality, air freight and apologies.
Factories fill around the industry’s known peaks and fabrics carry their own lead times, so a program competing for capacity in the busiest month pays in delay what it refused to pay in planning. The wave structure protects the date that matters most, the launch, by producing the visible roles first and letting the last wave trail the opening.
Ordering Uniform Programs at Scale
Brief the program as a program: role-by-role garment lists, the size curve and its source, issue quantities per role, the buffer percentage, the branding file, and the wave schedule. Quantities follow program planning at our standard minimum of 1,200 pieces per style in up to two colours, which suits phased production naturally: waves become production runs, and consistency is protected by approved references held across all of them.
Then measure the program like an operation: exchange rates, buffer burn, laundry loss and reorder shade matches, reviewed each cycle. A uniform program is never finished; it is only ever running well or running down, and planning is what keeps it on the right side of that line.
Frequently Asked Questions
How many garments should each employee be issued?
It follows the laundry cycle: staff who wash weekly through a service usually hold three to five tops, enough for wear, wash and reserve; daily-wash roles hold more. Trousers typically issue at two to three pairs. The right number is the one that never sends anyone to work in yesterday’s garment.
What spare ratio should a uniform program hold?
Ten to fifteen percent of headcount, spread across the size curve and held at the point of issue. The buffer covers joiners, size exchanges, losses and laundry attrition between reorder cycles. Programs that skip the buffer spend the savings on emergency small orders at worse prices.
How do we get the size distribution right?
Measure where you can: sizing sets at each site, or self-reported sizes checked against a sample fitting for a sample of staff. Where measurement is impossible, order against established workforce curves, overweight the extreme sizes, and re-forecast later rollout waves from the first wave’s real exchange data.
Should a large program roll out everywhere at once?
Rarely. A pilot group wearing and washing the uniform for a month catches fit, fabric and laundry problems while they are cheap to fix, and phased waves let each order learn from the last one’s issue data. Big-bang rollouts are faster on the calendar and slower everywhere.