Uniform Order Form Template
Collect sizes, personalization, and approvals for staff or team kit — one submission per wearer, one clean sheet for the supplier.
Time to order your kit. Sizes go straight to the supplier, so double-check against the size chart before submitting — exchanges are slow once printing starts.
Used to sort the delivery boxes — write it as your manager announces it.
Embroidered exactly as typed — check spelling twice.
Orders are cross-checked against each manager's roster before printing.
Uniform programs fail at the edges: the new hire nobody sized, the embroidery that spells "Jonh," the box of 4XL polos no one ordered. The fix is pushing data entry to the person who knows the answers — the wearer — while keeping an approval checkpoint so the company only pays for kit it authorized. This form does both, and the supplier gets one clean sheet instead of forty hallway conversations.
Why these fields. Wearer name and team/department are the sort keys for the day boxes arrive — deliveries get distributed by department, so the label tells people to write the department name the way their manager announces it, not a personal abbreviation. Pieces are a multi-select of your actual kit list; top and bottom sizes are separate dropdowns because bodies are not symmetric and "L" means nothing for pants — the bottom-size list ends with a "not ordering pants" option so shirt-only staff aren't blocked. The personalization field is capped at 20 characters and warns it embroiders exactly as typed, which is the cheapest typo insurance ever written. The approving-manager field is the governance layer: names get cross-checked against rosters before the purchase order goes out, so ghost orders die quietly.
What we left out. Home addresses — company kit distributes through managers, and collecting forty home addresses creates privacy obligations with zero logistical benefit. Also price display: wearers don't pay, the company does, and unit costs on the form only invite commentary the procurement team doesn't need.
Who uses this. Operations and HR teams kitting new cohorts, sports clubs collecting sizes before the season, trade crews refreshing workwear annually, and franchises standardizing kit across locations where each site manager approves their own list.
Make it yours. Replace the pieces with your real kit and the size runs with the manufacturer's actual chart — link the chart in the intro text. Turn on duplicate prevention (one submission per device) to stop double orders, and set a close date so the batch goes to the supplier on schedule. Export the CSV and pivot by department, then by size: that two-level table is the exact format uniform suppliers quote from. For seasonal reorders, duplicate the form and archive last season's — response history doubles as your sizing record.
Money never touches the wearer. The ending says the company settles centrally — employees should never wonder whether submitting a size costs them anything. Procurement pays the supplier invoice on account, exactly as it does today.
Frequently asked questions
Do employees pay anything when they submit?
No — the form collects sizes and approvals only. The company settles the supplier invoice centrally through procurement, as with any other equipment purchase.
How do I stop people submitting twice?
Enable duplicate prevention in Settings (per device or per IP). If someone genuinely needs a correction, they can contact the organizer and you can review both entries side by side.
What format does the supplier need, and can I produce it?
Suppliers want quantities by size per item. Export CSV and pivot on the size columns — the one-submission-per-wearer design means the export is already the raw tally.
Can I make sure only approved staff order?
The approving-manager field lets you cross-check against rosters before ordering. For tighter control, password-protect the form and distribute the password through managers only.