Uniform Programs
Give staff a budget and a boundary they can order inside — so managers stop approving uniforms one order at a time.
1,000+
Healthcare organisations
60,000+
Garments supplied
40+
Years experience
95%+
Client reorder rate
Why this exists
In most organisations uniform control is exercised one order at a time. Someone asks, someone checks, someone approves. It works, but it puts a manager in the middle of every transaction and it makes the answer depend on who happens to be asked.
Allowances and approval rules move that control earlier. The decision is made once, as a rule, and every order after that is measured against it automatically.
Sign-off by hand
Every order routed to a manager
No spend limit
Nothing defining what is reasonable
Orders left waiting
Sitting in an inbox until someone acts
Inconsistent answers
Different approvers, different outcomes
Spend found late
Uniform cost visible only at invoice
Entitlement disputes
No shared record of what each person is due
Two controls
They are often spoken about together but they do different jobs, and most programs use both. The allowance decides what someone can order without asking. The approval rule decides what still needs a human to look at it.
A value or an entitlement held against an employee, applied automatically at checkout.
What happens to an order — approved automatically, reviewed, or sent to a named approver.
Set by employee, by role or by site, so a clinician and a receptionist can differ.
The approved range only — an allowance never opens up products you have not approved.
Annual, on a review cycle or on your own schedule — whatever your organisation already uses.
Remaining balance visible to the employee, and spend visible to whoever needs it.
In the portal
Where the staff ordering portal is used, allowances and approvals are applied as the order is placed. The employee sees what they have available, and the order either completes or goes to the person you nominated — without anyone chasing it.
Balance shown to the employee before they order
Allowance applied automatically at checkout
Orders inside the rules complete without sign-off
Exceptions routed to a named approver
Approval status visible rather than assumed
Spend recorded against the employee and the site
Ways to set it up
There is no single correct structure. What matters is that it matches how your organisation already thinks about entitlement, rather than forcing a new model on your managers.
Each person has a budget to spend across the approved range as they choose.
An entitlement expressed as items rather than dollars — two tops, one jacket, and so on.
No individual budget: staff order from an approved list and the organisation carries the cost.
Different entitlements for different roles or sites, inside one program.
What changes
The work does not disappear — it moves. Managers spend their time setting the boundary once instead of policing it continuously.
Before
Every order needs sign-off
Entitlement remembered informally
Managers asked what is allowed
Spend understood at invoice
Approvals depend on who is asked
After
Orders inside the rules complete on their own
Entitlement held against the employee
Staff see what they have before ordering
Spend visible as it happens
The same rule applies to everyone
Who keeps control
The most common hesitation is that automatic approval means uniforms leave the organisation without anyone looking. In practice it is the opposite — an order that completes automatically is one that has already been checked against a rule you wrote.
You decide what the allowance is, who it applies to, what sits inside the approved range and which orders still need a person. Those rules can be changed whenever your organisation changes.
Visibility
Most disputes about uniform entitlement come from two people holding different versions of the same fact. A shared record removes the argument rather than settling it.
Balance remaining per employee
Spend by site or role
Orders awaiting approval
What was approved, and by whom
Activity across the cycle
An entitlement held against an employee — either a value to spend or a set of garments they are due — applied automatically when they order from your approved range.
Yes. Some organisations set a budget, others define an entitlement as garments — two tops and a jacket, for example. Both are common.
No. They can differ by employee, by role or by site, and several structures can run inside one program.
That is your decision. An order beyond the allowance can be blocked, or routed to an approver rather than refused outright.
Only if you want it to. Orders that sit inside the rules can complete without sign-off, and you nominate which exceptions go to a person.
Yes. Where the staff ordering portal is used, the remaining balance is visible to the employee before they order.
On whatever cycle your organisation already uses — annually, on a review date or on your own schedule.
It applies to your approved range only. An allowance never opens up products you have not approved for that role or site.
Avery is cut for a contemporary, slightly tapered fit that flatters without restricting movement. Prefer a relaxed fit or planning to layer? Size up.
| Model — Women's | 5'7", wearing size S |
| Model — Men's | 6'1", wearing size L |
| Fit | True to size, tapered body |
| Length | Hip-length, V-neckline |
| Chest (CM) | Body Length | Sleeve | |
|---|---|---|---|
| XXS | 81–86 | 58 | 30.5 |
| XS | 86–91 | 60 | 31.5 |
| S | 91–97 | 62 | 32.5 |
| M | 97–102 | 64 | 33.5 |
| L | 102–107 | 66 | 34.5 |
| XL | 107–114 | 68 | 35.5 |
| 2XL | 114–122 | 70 | 36.5 |
| 3XL | 122–132 | 72 | 37.5 |
| 4XL | 132–142 | 74 | 38.5 |
