# Event attire wording and release worksheet

Editable working copy in English. Confirm event-specific facts with the venue or event owner before publishing. Copy only the approved visitor-facing block into each language; this worksheet is not itself an attendee notice.

## 1. Fact and scope record

| Event edition / session | Date and time | Dress status: required, suggested or none | Applies to which part? | Confirmed venue or activity condition | Fact owner and confirmation time | Public wording approver |
| --- | --- | --- | --- | --- | --- | --- |
| [Event / segment] | [Local date and time] | [Choose one] | [Whole event / named segment] | [Only confirmed details] | [Name / date / source] | [Name / date] |

Before drafting, ask: Is any item an actual entry condition? Does it apply to every attendee? Are surface, weather exposure, walking distance, coat storage or changing facilities confirmed? If a fact is unknown, remove it from the public copy or mark it for owner review.

## 2. Public wording block

> **What to wear at [event or segment]**
> [Attire is required / suggested / unrestricted] for [precise event part].
> [One plain-language description with more than one workable example, if useful.]
> [One confirmed practical note about the actual venue or activity, if relevant.]
> [Descriptive contact link for a question the published wording does not answer.]

Delete bracketed prompts. If there is no dress code, a direct “No dress code; wear what works for you” may be enough. Do not copy an example from another event as if it were a venue rule.

## 3. Translation and channel release matrix

| Locale | Approved wording / reviewer | Event-page URL and section | Invitation linked or matched? | Reminder linked or matched? | Phone and keyboard check | Published check time | Correction owner |
| --- | --- | --- | --- | --- | --- | --- | --- |
| en | [Text version / person] | [URL / anchor] | [Yes / action] | [Yes / action] | [Result / device] | [Date / time] | [Name] |
| es | [Text version / person] | [URL / anchor] | [Yes / action] | [Yes / action] | [Result / device] | [Date / time] | [Name] |
| de | [Text version / person] | [URL / anchor] | [Yes / action] | [Yes / action] | [Result / device] | [Date / time] | [Name] |
| fr | [Text version / person] | [URL / anchor] | [Yes / action] | [Yes / action] | [Result / device] | [Date / time] | [Name] |
| ja | [Text version / person] | [URL / anchor] | [Yes / action] | [Yes / action] | [Result / device] | [Date / time] | [Name] |
| nl | [Text version / person] | [URL / anchor] | [Yes / action] | [Yes / action] | [Result / device] | [Date / time] | [Name] |

Do not rely on a literal translation of an attire label. Ask a language reviewer whether the requirement, formality and examples still mean the same thing to visitors.

## 4. Change and archive log

| Changed fact | Confirmed by / when | Live page corrected / when | Already-sent message needs correction? | Owner and channel | Post-event archive status |
| --- | --- | --- | --- | --- | --- |
| [Fact] | [Source] | [URL / time] | [Yes / no / reason] | [Name / channel / time] | [Past-event label or archive URL] |

A page edit does not change a previously delivered invitation. If a confirmed restriction changes, decide separately how to correct already-sent information.