How Many Uniform Shirts Per Employee to Order
PILLAR / Corporate Apparel
Three polos per employee is the floor for anyone wearing the shirt every workday. Five is the number that makes the program last a year without looking tired. Two is right only when the shirt comes out for an event and goes back in a drawer.
The quantity per head is not a budget decision first. It is a laundry decision. How many days a week does the shirt go on, and how often does that person actually run a wash. Answer those two and the number per employee stops being a guess.
The short answer
2 shirts
Occasional wear
A trade show weekend, a quarterly client visit, a photo day. One on the body, one clean in the bag.
3 shirts
Daily wear, working floor
One on, one clean, one in the wash. It survives a normal week. It does not survive a travel week.
5 shirts
Daily wear, built to last
One per workday. Each shirt rests six days between wears and goes through the wash roughly once a week.
01Three Is The Floor For Daily Wear
A person wearing the company polo five days a week needs three of them to get through a normal week without improvising. One is on the body. One is clean and hanging. One is in the hamper or the machine. That is the whole logic, and it is why three works and two does not.
Three has no slack in it. A missed laundry night, a lunch that lands on the placket, a night away from home, and your employee shows up Thursday in a shirt with somebody else's logo on it. Three is the number that keeps the program running. It is not the number that keeps it looking new.
The base of the program
David Polo, Navy
$76
Navy is the workhorse. It reads clean in an office, on a job site and in a booth, and it hides a day better than anything lighter. This is the shirt most programs build the count around.
- 84 percent nylon, 16 percent spandex
- Four way stretch, sweat wicking
- Classic athletic fit, firm collar, U cut hem
- Pre shrunk
02Five Is The Number That Makes It Last
Five shirts per person changes the program from something that functions to something that holds up. Every shirt gets a full week off between wears. Collars recover. The fabric is not going into the machine twice a week for fifty two weeks. And nobody has to think about laundry on a Sunday night to be dressed on Monday.
Five also gives you room to split colors, which is the part buyers underrate. A five shirt rotation does not have to be five of the same shirt. Three navy and two black, or three navy, one black and one white, covers the guy who is in a client meeting Tuesday and on a roof Wednesday. The logo stays constant. The shirt reads like a wardrobe instead of a uniform.
The jump from three to five is the single best place to spend money in a branded apparel budget, and it is cheaper than it looks once you understand what a decorated polo actually costs per piece at real quantities.
Rotation, shirt two
David Polo, Black
$76
Black is the one that goes anywhere. Pair two black with three navy and the rotation stops looking like a uniform by Wednesday.
Rotation, shirt three
David Polo, White
$76
White is the event shirt and the photo shirt. Keep one per person in the rotation and hold it for the days that get photographed.
0387 Washes A Year Against 52
Here is the arithmetic, and it is the only math in this post that matters. A five day workweek across a full year is 5 times 52, or 260 wears. Split those 260 wears across three shirts and each shirt goes through 86.7 washes, call it 87. Split the same 260 wears across five shirts and each shirt goes through 52. Same person, same year, same logo. Two shirts in the rotation cut each shirt's wash count by a third.
That is arithmetic, not a durability claim. What you do with it is your call. But every buyer who has watched a polo program go soft in month nine was running a three shirt rotation and did not know they had signed up for 87 cycles per shirt.
| Days worn per week | Shirts in rotation | Washes per shirt per year | What that means |
|---|---|---|---|
| 5 | 1 | 260 | Not a rotation. The shirt is in the machine every night and out of service the first time laundry slips. |
| 5 | 2 | 130 | Still brittle. One travel day or one spill and the person is out of clean shirts. |
| 5 | 3 | 87 | The working floor. Roughly two washes a week per shirt, with no slack for a bad week. |
| 5 | 5 | 52 | One wash per shirt per week. Every shirt gets six days off between wears. |
| 3 | 3 | 52 | A three day schedule with three shirts lands in the same place as five on five. |
| 1 | 2 | 26 | Occasional wear. Two shirts covers a weekly shift or a run of events with a clean spare. |
Wears per year equals days per week times 52. Washes per shirt equals wears divided by shirts in rotation, rounded.
A polo program does not fail because the shirt was wrong. It fails because there was only one of it.
04Two Is Right Only For Occasional Wear
Two per person is a real answer, just not for daily staff. It is the right number for the sales rep who pulls the branded shirt on for a quarterly client visit, the volunteer crew working a booth weekend, the office that wears company colors for one photo day and one charity run a year.
The logic is the same, scaled down. One is on the body and one is clean, because the second day of a two day event exists and nobody wants to be the guy repeating a shirt on camera. We build this count constantly for tournament and event work with clients like the WM Phoenix Open and AO, where the crew wears the shirt hard for a defined window and then the shirt goes away until next year.
The trap with two is scope creep. Order two for occasional wear, then let the shirt become the default Friday shirt, and you are back at 130 washes per shirt with a rotation built for 26.
05Ten To Fifteen Percent Over Headcount
Order more shirts than you have people. Ten to fifteen percent over headcount is the right buffer for most companies, and the reason is the person who starts in March.
Without a buffer, that hire either waits until the next order cycle in branded nothing, or gets a one off shirt bought retail that does not match the run. Both outcomes are visible in every group photo for the rest of the year. A 60 person company orders for 66 to 69. The extras sit in a box in the supply closet and get handed out on day one with the laptop.
Buffer stock is also where the sizing safety valve lives. Skew the extras toward the middle of the curve, Large and Extra Large, because that is where the miss happens. If you have not locked your size run yet, start with the size distribution math for a company order before you multiply anything by a per person count.
06One Per Person Is The Costliest Order You Can Place
Ordering one shirt per employee is the most common quantity mistake and the most expensive one, and it does not look expensive on the quote. It looks like the cheapest line in the budget.
Then week one happens. The shirt goes on Monday. It goes in the hamper Monday night. Tuesday the person wears their own clothes. By Thursday the branded shirt is an occasional thing, by month two it is a weekend shirt, and the program you paid for is a drawer item. You did not buy a uniform. You bought a giveaway with a logo on it, at uniform prices, and you will be asked to do it again next year because nothing about the first order stuck.
The fix costs less than the failure. Two more shirts per person turns a giveaway into a program that people actually get dressed in.
07One Reorder A Year Keeps Everyone In The Same Shirt
Build the replacement cadence into the plan before the first box lands. One scheduled reorder a year, placed in the same month every year, does two things. It refreshes the shirts that took the most wear, and it absorbs the hires you made since the last run.
Pull the reorder off a headcount snapshot, not off a hope. Count current staff, subtract what is still in the closet, add the buffer back to ten or fifteen percent. That is your number. Most programs reorder roughly a third of the fleet each year once they are past year one.
Order the reorder in one run rather than in trickles, because dye lots move between production runs and the fastest way to end up with two slightly different navies on one crew is to place four small orders across twelve months.
08One Layer Covers The Outdoor Half Of The Roster
Not every person on the headcount needs the same count of the same thing. Staff who work outdoors or start early want a layer, and a layer is worn over the polo rather than instead of it, so it does not change the polo count. One per person is genuinely enough here, because the quarter zip is not going through the wash on a polo schedule.
This is how a program stops looking like a t shirt order. Polos at three to five per head for everyone, one layer for the field crew and anyone who opens the building. We build exactly this split for outfits like Progressive Roofing, where half the roster is in an office and half is on a roof at six in the morning.
The layer the program adds
Alec Quarter Zip, Blue
$98
One per person for outdoor and cold weather staff. It goes over the polo, carries the same logo placement, and holds the program together on the mornings the polo alone will not.
0914 Days Or 45 Days, Two Different Clocks
Your per person count interacts with your calendar, so know which clock you are on before you commit to a quantity.
Logo embroidery on stock polos runs about 14 days from artwork approval to a packed box. That is the answer any time your date is inside six weeks. It is also the answer when you are topping up a buffer mid year or covering a hiring wave.
Full custom, built from the fabric up, runs about 45 days door to door, with production alone taking 30 to 35 of those days. That is the path when the fabric is woven or knit to your spec, dyed to an exact color, or carries an all over print from an original repeat pattern. Private label neck tags, branded insert cards and name level kitting live on this clock too. Never plan a full custom program against a stock embroidery timeline.
Whichever clock you are on, the quantity decision comes before the artwork decision, because quantity per head drives total pieces and total pieces drives the conversation about which decoration method fits the run, whether that is a chest crest, a sleeve hit, chenille, 3D puff, or a reflective, tonal or metallic heat transfer.
How many polos should I order per employee?
Three per employee is the floor for anyone wearing the shirt every workday, and five is the number that makes the program last. Two is enough only for occasional wear like events or quarterly client visits.
Is three polos per employee enough?
Three works for a normal week. One is on, one is clean, one is in the wash. It has no slack for a travel week, a spill or a missed laundry night, and each shirt goes through roughly 87 washes a year on a five day schedule.
How many uniform shirts per employee do I need for staff who only wear them at events?
Two. One on the body and one clean in the bag covers a two day event, a booth weekend or a quarterly client visit without anyone repeating a shirt on camera.
How many extra polos should I order for new hires?
Order 10 to 15 percent over headcount. A 60 person company orders for 66 to 69. Skew the extras toward Large and Extra Large, because that is where sizing misses happen most often.
What happens if I only order one polo per person?
The shirt gets worn once, it goes in the wash, and the person wears their own clothes the next day. Within two weeks the branded shirt becomes an occasional item and the program stops functioning as a uniform.
How often should we reorder company polos?
Once a year, placed in the same month each year, and in one run rather than several small ones. Count current staff, subtract what is still in the closet, and add the buffer back to 10 or 15 percent.
How long does a company polo order take?
Logo embroidery on stock polos runs about 14 days from artwork approval to a packed box. Full custom built from the fabric up runs about 45 days door to door, with production alone taking 30 to 35 days.
Start With The Headcount
Three things get you a real number: what the event is, how many people are on the list, and the date it has to land. We will come back with the per person count, the size run and the clock your project is actually on.
