Hospital Uniform Program Checklist: From Sizing Census to Reorder Point

1. The Sizing Census

Everything downstream depends on knowing how many wearers you have, in which sizes, in which roles. Collect it properly: name, department, role, garment types required, and size — measured or self-declared against a size chart, not guessed from last year's spreadsheet. Expect the distribution to be wider than intuition says; a program graded XS to 3XL exists because real workforces need XS to 3XL. Record the census as data you will reuse: at every reorder, the question "how many medium coats?" should be answered by the census, not by walking the wards.

While collecting sizes, capture the embroidery data in the same pass — name spelling, credential, title, department. Re-collecting name spellings later, from memory and email threads, is where embroidery errors are born.

2. Sets Per Wearer (The Par Decision)

A wearer needs enough sets to cover the laundry cycle with one set in reserve. The arithmetic is simple: sets per wearer = sets worn between laundry collections + sets in the laundry + one spare. A hospital collecting laundry twice a week, with staff on five shifts, typically lands at three to four sets per wearer for daily-worn items (uniforms, underscrubs), fewer for coats that are worn over clothing and washed less often. Socks and other consumables run on their own, faster cycle — plan them as multiples, not sets: they are the first item to run short and the cheapest to overstock.

3. Buffer Stock

Buffer is the stock that absorbs reality: new hires, size exchanges, losses, damage, and the wearer whose size changes. A practical starting point is 5-10% of the total issue, weighted toward the middle sizes where volume concentrates and toward the items with the fastest churn. Buffer belongs on your shelf, in your size system — a buffer held "at the supplier" is not a buffer, it is a lead time. Record buffer separately from issue stock so its depletion is visible before it is gone.

4. The Specification File

Before the first order, assemble the file that every future order will cite: fabrics and weights, colors by department, size grading, embroidery files with placements and thread numbers, labels and packaging, and the approved sample reference. This file is what converts a reorder from a negotiation into an instruction. Ask for the sample-retention arrangement in your order terms — the approved pre-production sample kept as the standard — it is the single practice that most separates stable programs from drifting ones. The embroidery side is covered in our embroidery guide; garment specification in how to choose a lab coat.

5. Lead-Time Planning

Plan orders backwards from need, using production lead times you can verify: samples 7 days, trial orders 14 days, small orders 21 days, bulk production 35 days from China lines (plus freight, plus your internal approval time — the two additions everyone forgets). Large planned programs can use the 90-120 day Myanmar schedule for volume pricing of time instead of money. Then set reorder points: the stock level at which a reorder is triggered, calculated as consumption during lead time plus buffer. When buffer stock of medium coats falls to the reorder point, the order goes out — not when the shelf is empty.

6. Quality Gate and Review Rhythm

Inspect what arrives against the approved sample — fabric, shade, sizes, embroidery — before it is issued, and keep one sealed reference set from the first order as the comparison standard. (Our shipments are AQL 2.5/4.0 inspected before dispatch, and SGS or ITS third-party inspection is available where your procurement rules require it.) Finally, review the program on a cycle: census drift (joiners, leavers, role changes), buffer depletion, and the items generating complaints. A one-hour review per quarter is the whole cost of a program that never makes the agenda of a management meeting — which is exactly where a uniform program wants to be.

The program structure behind this checklist — one supplier across coats, uniforms and accessories — is set out on our hospital uniforms page.

Failure Modes This Checklist Prevents

It is worth naming the failures explicitly, because each one maps to a line above. The empty shelf: no buffer, so a new hire waits five weeks for a coat — prevented by items 3 and 5. The drifting reorder: a slightly different shade or a moved logo, because the specification lived in someone's memory — prevented by item 4. The name-error embroidery: spellings collected casually and never verified — prevented by the data discipline in items 1 and 4. The invisible shortage: socks and caps consumed silently until a department cannot dress its team — prevented by par levels per item class in item 2, and by reviewing consumption in item 6. None of these failures requires a bigger budget to avoid. They require the decisions to be written down once, in one file, before the first purchase order — which is the entire content of this checklist.

A Note on Ownership

Every item on this checklist decays without an owner. Somebody — uniform coordinator, procurement officer, head nurse with the spreadsheet — has to own the census, the buffer and the reorder points as named responsibilities, reviewed when they change roles like any other handover. Programs with a named owner survive staff turnover; programs owned by "the department" discover their state during the next shortage. Write the owner's name on the specification document itself. It is the cheapest line in this entire checklist, and the one that keeps all the others true.

Related Guides

• How to Choose a Lab Coat
• Lab Coat Embroidery Guide
• Underscrubs Fabric Comparison