Wedding Dress Code Wording: What to Write (and What Guests Hear)

Somewhere right now, a guest is standing in front of an open wardrobe holding two shirts, reading the phrase "elevated garden formal" for the fourth time, and quietly losing faith in the English language. That is what unclear dress code wording does. It does not make people dress better. It makes them nervous.

Your wedding dress code wording has one job: tell people what to put on their body. Not set a mood. Not gesture at a colour palette that only makes sense once you have seen the venue. Just answer the question your guests are actually asking, which is some version of "am I going to be the only person here in a tie."

The short version.

Take the TL;DR above and stretch it into three clauses: the dress code name, the translation into real clothes, and one practical note about the venue, the weather, or the ground underfoot. Here is the shape to copy:

Three clauses. You can write the whole thing in the time it takes a kettle to boil, which is roughly three hours less than most couples spend on it.

Do you actually need a dress code?

Usually, but not always, and most guides skip the second half of that sentence.

You need one when guests cannot work out the formality from the invitation and the venue alone. A barn, a registry office and a hotel ballroom suggest three very different pairs of shoes.

You can skip it when you genuinely do not mind, and you can say that without flinching. Twenty friends in a pub function room do not need a dress code. They need the address and a rough idea of when food appears.

The trap is the middle ground: writing "no dress code, wear whatever" while quietly hoping nobody arrives in shorts. Guests can sense that, and they respond by over-dressing out of caution, which is its own small awkwardness. If you have a preference, write the preference.

Where the dress code actually goes.

Three places, each getting a different number of words.

• On the invitation. Bottom right corner, or centred under the venue and time. Two to four words. "Black tie." "Cocktail attire." "Formal attire requested." An invitation is not the place for footwear guidance
• On the details card, if you have one. One sentence, and the place where "requested" or "optional" earns its keep
• On your wedding website. Everything else. Put it on the schedule or event page, then repeat it in your FAQ, because those are the two places people look

That last one matters more than it sounds. A good FAQ quietly removes the same question from your messages over and over. Where do we park. Is there a dress code. Are children invited. When does the ceremony start. Not thrilling questions, which is exactly why they belong on the website rather than in your phone at 11pm. Our guide to writing an FAQ for your wedding website covers the rest of them. (Yes, someone will still text you to ask. It's tradition.)

The invitation gets four words. The website gets the rest. Photo via Pexels.

Wedding dress code wording for every level.

Copy these, swap the bracketed bits, move on with your day. Each one is written to sit on a website. For the invitation, take the first two or three words and stop there.

What you write vs what guests actually hear.

Here is the part most dress code guides leave out. Every phrase gets translated inside the guest's head, and the translation is rarely the one you intended. The moment someone reads "elevated garden formal", they open the group chat, and the group chat has collectively decided it is going to need a bigger boat.

One opinion worth having about all of this: write the dress code like a human. "Formal attire" is fine. "Summer garden formal with an elevated contemporary sensibility" is a cry for help. The test is simple. Read it aloud to somebody who has never seen your venue. If they can tell you what shoes to bring, it works. If they ask a follow-up question, you have written a mood board.

Everyone here read the same sentence and arrived at roughly the same answer. Photo via Pexels.

The four add-on lines that do the heavy lifting.

The label gets all the attention. These four sentences get the results, and almost nobody writes them.

1. The ground. "The ceremony is on grass, so flat shoes or block heels will make your evening considerably better." Say which one: lawn, gravel, cobbles or sand
2. The weather. "We are outside until sunset and it cools down quickly after, so bring a jacket or a wrap." Guests will not check the forecast for your venue. They will check it for their own town, which is not where your wedding is
3. The events. If it runs over a weekend, each event gets its own line. "Welcome drinks: casual. Ceremony and reception: cocktail. Sunday brunch: more or less whatever you slept in"
4. The one thing you would rather people skipped. One line, said kindly, and only if you genuinely mind. "The venue asks that we avoid trainers" hangs the request on the venue rather than on you, which takes the sting out entirely

I once spent an entire afternoon deciding whether "requested" sounded warmer than "preferred". It does. It also took an afternoon, and I would like that afternoon back.

Asking about colours without starting a war.

Two versions of this come up, and they need different handling.

The first is asking guests not to wear white. You are allowed to. Most people already know, a few genuinely do not, and one polite sentence costs less than an awkward photograph. "We would kindly ask guests to avoid white and ivory" is plenty. Put it in the FAQ on your website, not on the invitation.

The second is asking guests to wear your palette. Handle this one more carefully, because you are now asking people to spend money. Frame it as a preference and release them from it in the same breath: "If you happen to own something in sage or dusty blue, we would love that. If not, wear what you have. We would much rather you were there."

The word doing the work in both is "kindly". The word that ruins it is "must".

Every chair here is standing on grass. Mention the grass. Photo via Pexels.

Wording mistakes worth avoiding.

• The poem. If your dress code needs a metaphor, it is not a dress code
• The essay. Four paragraphs about your vision for the day. Guests read the first line and guess the rest, so put the useful part in the first line
• Contradicting your own venue. "Black tie" at a barn with a gravel car park sends people into a genuine spiral. Match the label to the place
• Hiding it inside an image. A beautifully typeset JPEG of your dress code cannot be read by a screen reader, cannot be found by search, and needs pinch-and-zoom on a phone. Write it as text
• Changing it quietly. If it moves from cocktail to black tie six weeks out, say so directly rather than editing the page and hoping. Somebody has already bought the outfit

If you are still setting the site up, our wedding website checklist lists the dress code alongside the other details guests look for, and the guide on how to create a wedding website covers where each of those details should live.

When to stop writing.

Stop when a guest could read your dress code once, on a phone, standing in a car park, and know what to wear. That is the entire bar.

You will be tempted to keep refining it. I have rewritten the phrase "smart casual" more times than I would like to admit, and I can report that the fourth version was not meaningfully better than the second. Nobody at your wedding will remember your wording. They will remember whether they felt appropriately dressed, which is a much lower and considerably kinder bar to clear.

Write the label. Translate it into actual clothes. Mention the grass. Then go and do something else, because your guests want to know what to wear, not what you meant.