Custom Apparel Guide · 16 min read
Restaurant Staff Dress Code: How to Set Standards Your Team Will Actually Follow
Key takeaways
- Specific beats strict. A restaurant staff dress code that names exact garments, colors, and footwear gets followed. A vague "look professional" policy gets debated every shift.
- FOH and BOH need different rules. Front-of-house dress codes are about guest perception. Back-of-house dress codes are about heat, spills, and safety. Write them as two sections, not one.
- Branded garments make the policy self-enforcing. When you supply the shirt, the apron, and the hat, there is nothing left to interpret. Compliance becomes "wear what we gave you."
- Roll it out with a reason, not a memo. Teams push back on rules that feel arbitrary. Explain the why, give lead time, and cover the cost of core items.
- Plan for seasons up front. Approved summer and winter variants written into the original policy prevent the August t-shirt argument and the January hoodie argument.
- Steal the outline below. This guide ends with a copy-paste dress code structure you can adapt in an afternoon.
Most restaurant dress codes fail for the same reason: they were written to sound official instead of to be followed. A restaurant staff dress code that says "employees must maintain a neat, professional appearance" tells a new server almost nothing. Can she wear her black jeans? Is his gray hoodie fine under the apron in winter? Nobody knows, so everyone guesses, and the manager ends up relitigating the policy one awkward conversation at a time.
We work with restaurant and cafe owners every week at Arklavo, usually when they have decided to move from "wear something black" to actual custom restaurant and cafe uniforms. The pattern we see is consistent. The owners who struggle least with appearance standards are not the strictest ones. They are the ones whose policy is so specific, and whose garments are so easy to comply with, that following the dress code takes less effort than breaking it.
This guide walks through how to write that kind of policy: what to specify, how front-of-house and back-of-house standards should differ, how branded garments do the enforcement work for you, how to handle pushback, how to build in seasonal flexibility, and a copy-paste outline you can adapt for your own operation. One note before we start: this is practical guidance on writing and rolling out standards, not legal advice. Requirements around workplace policies vary, so run your final document past whoever handles that side of your business.
What should a restaurant staff dress code actually specify?
A restaurant staff dress code should specify five things: the exact garments allowed, approved colors, footwear standards, neutral grooming basics, and condition expectations. Each item should be concrete enough that an employee getting dressed at 6 a.m. can check themselves against it without asking anyone. If a rule requires interpretation, rewrite it.
Garments. Name the actual pieces, not categories. "Black Arklavo polo with logo, black or dark denim pants, no shorts" works. "Appropriate tops and bottoms" does not. If staff supply their own bottoms, define what qualifies: solid color, no rips, no athletic wear, full length. If you supply tops, hats, or aprons, say which supplied items are required per shift and how many each employee receives.
Colors. Restrict staff-supplied items to one or two colors, and pick colors that survive a restaurant environment. Black and dark navy hide splashes and hold up to industrial washing. White shows everything by lunch. If your brand colors are lighter, put them on the supplied garments you control (the embroidered polo, the printed tee, the apron) and keep the staff-supplied layer dark.
Footwear. This is the one section where you should be least flexible. Closed-toe, non-slip footwear is the standard across the industry for anyone working near kitchens, and slip-resistant soles matter on any floor that sees grease, water, or dish spray. Resources like OSHA cover workplace footwear and floor-safety considerations in depth. In the policy itself, keep it simple: closed toe, non-slip sole, clean, no canvas sneakers in the kitchen.
Grooming basics, kept neutral. The safest and most followable grooming standards are the ones tied to food safety and function rather than style: hair restrained or tied back when working with food, clean hands and trimmed nails, beard nets or restraints where your food-safety practices call for them, and minimal jewelry on hands and wrists around food and equipment. Avoid rules about hairstyles, hair color, or personal expression that have nothing to do with the work. They generate the most conflict and the least benefit, and they age badly.
Condition. A faded, stained shirt technically complies with "black polo" while undermining the entire point. Add one line: garments must be clean, unwrinkled, and free of stains, holes, and heavy fading, and damaged uniform items should be reported for replacement rather than worn. This line only works if replacing a worn-out shirt is genuinely easy, which is an argument for keeping spare stock on hand (more on that below).
How should FOH and BOH dress codes differ?
Front-of-house and back-of-house dress codes should be written as separate sections because they solve different problems. FOH standards exist for guest perception: staff should be identifiable, tidy, and on-brand. BOH standards exist for heat, spills, burns, and speed. Forcing both teams into identical rules makes the policy wrong for at least one of them.
A server's polo is a branding asset that guests look at for hours. A line cook's shirt is a heat-management and splash-protection tool that guests may never see. When owners write one blanket policy, they usually optimize for the dining room and quietly make life worse on the line, and BOH staff respond by ignoring the parts that do not work, which teaches everyone that the dress code is optional. Here is how the two typically split:
| Element | Front of house | Back of house |
|---|---|---|
| Primary goal | Guest-facing brand consistency | Function, comfort, and safety |
| Typical top | Embroidered polo or printed tee in brand colors | Breathable tee or work shirt, dark colors |
| Apron | Branded waist or bib apron, guest-visible logo | Heavier bib apron, coverage over style |
| Headwear | Branded cap or none, per concept | Hair restraint required near food |
| Footwear | Closed toe, non-slip, clean and presentable | Closed toe, non-slip, no exceptions |
| Branding priority | High: logo visible on top or apron | Lower: consistency matters more than visibility |
The apron deserves special mention because it does double duty across both teams. For FOH it is often the single most visible branding surface in the room, sitting at eye level on every table visit. For BOH it is protective gear first. Many cafes solve the whole FOH garment question with a quality branded apron over a plain dark tee, which keeps the staff-supplied layer cheap and simple while the supplied apron carries the brand. If your budget only stretches to one custom item per employee, the apron is frequently the right one.
One more FOH versus BOH note: crossover shifts. Plenty of small operations have staff who run food, then jump on the line, then bus tables. Give those roles the FOH standard as their base and add BOH requirements (hair restraint, apron swap) that activate when they cross the pass. Write it down so nobody has to improvise.
How do branded garments make a restaurant staff dress code self-enforcing?
Branded garments make a restaurant staff dress code self-enforcing by removing interpretation: when the business supplies the shirt, the apron, and the hat, compliance means wearing what was issued. There is no debate about whether a top is "close enough" to the standard, because the standard is a physical object hanging in the employee's closet.
Think about what a manager actually enforces under each model. With a written-only dress code, every shift starts with judgment calls: is that navy dark enough, does that logo tee count as plain, are those technically work pants. Each call is a small negotiation, and each inconsistent call erodes the policy. With supplied garments, the entire top half of the dress code collapses into one binary check. Wearing the issued polo or apron: compliant. Not wearing it: not compliant. Managers stop being fashion judges and go back to running service.
There is a second effect owners tell us about after the switch: supplied uniforms change how staff relate to the standard. A dress code written on paper is a restriction. A box of embroidered polos with the restaurant's name on them is equipment, the same category as knives and non-slip shoes. People push back on restrictions. They rarely push back on equipment, especially equipment they did not have to pay for. The garment also does quiet work on the guest side, since a matched team reads as an organized operation before anyone says a word.
Practical notes if you go this route, based on how we run it at Arklavo for restaurant clients:
- You do not need a big order to start. We have no minimum order quantity, so a six-person cafe can outfit its team the same way a 60-person restaurant group does. Order what your roster actually needs, plus spares.
- Order spares in the common sizes. Two or three extra shirts in M and L means a stained or torn garment gets swapped the same day instead of becoming a week of non-compliance. Spares are what make your "clean and undamaged" clause enforceable.
- Pick decoration for the job. Embroidery is the standard for polos and aprons: it holds up to repeated industrial washing and reads as quality up close. DTG printing suits multi-color designs on tees. Heat press works well for names, roles, or bold back prints. We do all three, and most restaurant orders end up mixing methods across garments.
- Proof before you pay. We send a free digital proof of your logo on each garment before any payment, which matters when your logo has fine detail that needs adjusting for thread.
- Timelines are short enough to plan around. In-stock blanks dispatch in about 2 days, and decorated orders are produced in 5 to 10 business days, so a dress code rollout scheduled three or four weeks out has comfortable margin. US shipping is free over $150, and we ship globally with a local-currency equivalent threshold.
If you are still choosing which garments fit your concept (counter-service cafe versus full-service dining room versus food truck), our custom restaurant uniforms guide breaks down garment choices, fabrics, and decoration by service style in much more depth than we can here.
How do you roll out a dress code without a staff revolt?
Roll out a dress code by explaining the reason, giving real lead time, covering the cost of core items, and enforcing it identically for everyone from day one. Most pushback is not about clothes. It is about surprise, cost, and fairness, and all three are within your control.
Lead with the why. "Guests need to be able to spot staff instantly on a busy Saturday" and "we are building a brand people recognize" are reasons a team can get behind. "Because I said so" is not. Present the new standard at a staff meeting, not in a group text, and show the actual garments if you have samples. A polo people can touch gets a warmer reception than a policy people can only read.
Invite input on the details, not the decision. The decision to have a dress code is yours. But letting staff weigh in on fit preferences, fabric weight, or whether the tee or the polo feels better on a 10-hour shift costs you nothing and converts your most vocal skeptics into co-authors. People rarely revolt against a standard they helped shape. This is also simply better product selection: your line cooks know more about what a shirt feels like at the grill than you do.
Handle the money question before anyone asks. If the business supplies branded tops, aprons, and hats, and staff only supply dark bottoms and non-slip shoes they mostly already own, the cost objection largely disappears. Whatever split you choose, state it explicitly in the policy: what the business provides, how many of each item, and how replacements work for normal wear versus lost items.
Give a real transition window. Announce the standard, hand out garments, and set a start date two to four weeks out. Then hold the date. A soft launch that keeps slipping teaches the team that the next policy will slip too.
Enforce it evenly, starting with management. The fastest way to kill a dress code is a shift lead who is exempt from it. Managers wear the standard first and best. When someone shows up out of compliance, the correction should be quiet, consistent, and boring: a private word, a spare shirt from the back, and a note if it repeats. The goal is a norm, not a punishment system, and norms are built by unglamorous consistency.
How should a dress code handle seasons?
Write approved seasonal variants into the original policy: a hot-weather uniform, a cold-weather layering rule, and a list of approved outerwear. If the policy is silent on seasons, staff will improvise in August and January, and their improvisations will not match your brand or each other.
The summer problem is heat, especially BOH. The clean solution is a warm-weather version of the same uniform: the branded tee replaces the polo, or a lighter-weight polo replaces the heavier one, in the same colors with the same logo. Define when the summer standard applies (by date range or manager call) so the switch is a policy event rather than a gradual unraveling.
The winter problem is the mystery layer. Staff get cold, staff grab whatever hoodie is in their car, and by February your carefully branded FOH team is wearing five different logos, none of them yours. The fix is to make the approved layer the most convenient one: a branded crewneck, quarter-zip, or fleece in your colors, issued or available to buy at cost. Add one line to the policy: "Only issued outerwear may be worn during service; personal jackets stay in the back." That single sentence, plus an actually comfortable branded layer, ends the hoodie problem permanently. Beanies deserve the same treatment for patio service, delivery runners, and food trucks: a branded beanie in winter keeps heads warm and keeps the brand on them.
Seasonal garments are also the easiest dress code upgrade to phase in. Plenty of our restaurant customers start with polos and aprons, then add crewnecks before their first winter and tees before their first summer, reusing the same logo files each time so the whole wardrobe stays consistent.
A copy-paste restaurant dress code outline
Use the outline below as the skeleton of your policy, replacing the bracketed items with your own specifics. It covers purpose, supplied items, FOH and BOH standards, footwear, grooming, seasons, and replacements in a structure short enough that staff will actually read it. Aim for one page.
- 1. Purpose. One or two sentences: "Our uniform keeps [restaurant name] staff easy to identify, presents a consistent brand to guests, and keeps everyone safe and comfortable during service."
- 2. Provided by the restaurant. List the issued items and quantities, for example: "[3] branded polos or tees, [1] branded apron, [1] branded hat, [1] branded crewneck (cold season)." State that issued items remain the standard uniform and how to request replacements.
- 3. Provided by you. "Solid [black] full-length pants or dark denim without rips or fading. Closed-toe, non-slip footwear, clean and in good condition."
- 4. Front of house standard. "Issued [polo] tucked or neat, issued apron tied at [waist], issued hat optional or required per [concept]. Logo visible at all times during service."
- 5. Back of house standard. "Issued [tee] or approved plain dark top, bib apron during prep and line work, hair restrained and beard restraint where required by our food-safety practices."
- 6. Grooming and jewelry. "Hair tied back when working with food. Clean hands, trimmed nails. Minimal jewelry on hands and wrists around food and equipment."
- 7. Condition. "Uniform items must be clean, unwrinkled, and free of stains, holes, and heavy fading. Swap damaged items for spares in [location] and tell your manager so we can reorder."
- 8. Seasonal variants. "Summer standard ([dates or manager call]): issued tee replaces polo. Winter: only issued outerwear ([crewneck or quarter-zip]) may be worn during service; personal jackets stay in the back."
- 9. Not permitted during service. "Shorts, open-toe footwear, athletic wear, personal hoodies or jackets, garments with other logos or printed messages."
- 10. Questions and exceptions. "If something here does not work for you, talk to [manager]. We would rather adjust the policy than have it quietly ignored."
Two notes on using this outline. First, item 10 is not filler. A named path for exceptions is what keeps individual accommodations from becoming public arguments, and it signals that the policy is meant to work for people, not against them. Second, resist the urge to add clauses every time something odd happens. A one-page policy that everyone knows beats a five-page policy that nobody has read, and most one-off situations are better handled with a conversation than an amendment.
Frequently asked questions
These are the questions restaurant owners ask us most often when writing or rolling out a dress code. The short answers are below; the sections above cover each topic in more depth.
Q. How many uniform sets should each employee get?
Three tops per full-time employee is the practical baseline: one on, one in the wash, one spare. Part-timers working a couple of shifts a week can manage with two. Aprons take more abuse, so two per person is sensible for BOH. Whatever you issue, keep a few spare tops in common sizes at the restaurant so a spill mid-shift never means a dress code exception.
Q. Should the restaurant pay for uniforms or should staff?
The cleanest arrangement is that the business supplies every branded item (tops, aprons, hats, outerwear) and staff supply generic items they would own anyway, like dark pants and non-slip shoes. This removes the cost objection during rollout and keeps the branded garments under your control. Rules on uniform costs and paycheck deductions vary by location, so confirm your approach with whoever advises you on employment matters.
Q. Can front-of-house and back-of-house have different dress codes?
Yes, and they should. FOH standards exist for guest perception and brand consistency, while BOH standards exist for heat, spills, and safety. Write them as two sections of one policy with a shared foundation (footwear, grooming, condition) and role-specific garment rules. Staff who cross between roles follow the FOH base plus BOH additions like hair restraint whenever they work the line.
Q. What footwear should a restaurant dress code require?
Closed-toe footwear with non-slip soles for anyone working in or passing through the kitchen, which in most restaurants means everyone. Kitchens combine grease, water, and speed, and slip-resistant soles are the single most protective line in the whole policy. Add "clean and in good condition" for FOH roles. Let staff choose the brand and style within those rules; the constraint is the sole, not the fashion.
Q. What do I do when someone shows up out of dress code mid-rush?
Solve the shift first, address the pattern later. Hand them a spare shirt or apron from the back stock so they can work compliant, then have a brief private word after service, not in front of the team. If it repeats, treat it like any other recurring performance issue through your normal process. The spare-stock habit is what makes this low-drama: you can fix the problem in thirty seconds instead of debating it.
Q. How strict should grooming rules be?
Tie every grooming rule to food safety or function and stop there: hair restrained around food, clean hands and trimmed nails, minimal jewelry on hands and wrists near food and equipment, beard restraints where your food-safety practices require them. Rules about hair color, hairstyles, or personal expression create the most conflict for the least benefit. If a grooming clause does not protect the food or the guest experience, it probably does not belong in the policy.
Q. How often should we update the dress code?
Review it once a year, ideally before you reorder garments, and otherwise leave it alone. Annual review catches things like a new patio season, a menu change that affects BOH workload, or a rebrand that changes colors. Constant small amendments train staff to ignore the document because it never stays still. When you do update it, reissue the whole one-page policy rather than circulating amendments.
Q. Is supplying branded shirts enough, or do I still need a written policy?
You need both, but the written part gets much shorter once garments are supplied. The shirts and aprons answer the biggest question (what to wear on top), while the written policy covers what garments cannot: bottoms, footwear, grooming, condition standards, seasonal rules, and replacements. A supplied uniform plus a one-page policy is the combination that runs itself. A policy without supplied garments leans entirely on daily interpretation, which is where dress codes go to die.
Put your logo on the uniform that enforces itself
Tell us your team size and garment picks, and we will send pricing plus a free digital proof of your logo on each piece before you pay anything. No minimum order, and decorated orders are produced in 5 to 10 business days.

Compare styles and prices in one place
Every blank, weight and decoration option side by side, with current listed prices.
The value pick from this guide


No minimum order. Free digital proof before anything is made.
No minimum order. See your logo on the real product first.
Every price is listed. Free proof before anything is made.
Ordering for a team?
Get a quote for your whole team
You have seen the prices already, so a quote here is arithmetic, not a sales call. Send your quantities, sizes and product and we total the program from the same listed prices in this guide. No setup fees, no minimums.
Get a QuoteEvery price is on the page. No form first.
No minimums, no setup fees, free proof.
Get a free quote
Priced from the listed prices on this page
Request sent
Keep browsing while you waitThat did not send
Something blocked the request on our side. Send it through the quote page and we will pick it up there.
Open the quote page