Why a code of conduct belongs on your event page
Use the policy to state three things: the behaviour you welcome, the behaviour you will not tolerate and how someone can raise a concern. Place that information alongside the event details you want attendees to consult before arrival.
The free Event template starts with editable Text, Links and Contact sections. That is enough to publish a short policy. You can add more Text sections if you want to separate the code from other event details such as schedule or directions. The wording, the behaviour rules and the reporting path are yours to write and keep current. QREasy only provides the space to host them.
Decide what behaviour to encourage and what you will not tolerate
A useful policy is short and plain. Try to settle on two short lists before you draft: one for behaviour you want to encourage and one for behaviour you will not tolerate. Examples of the first list might include respectful language, following venue rules and looking out for fellow attendees. Examples of the second might include harassment, intimidation or persistent unwanted attention.
Review the two lists against the arrangements your team can actually provide. Remove ambiguous wording and identify which contact will handle questions or concerns about the policy.
Choose who receives concerns and how attendees can reach them
Pick someone on your team who has agreed to respond during and after the event, and name that role or contact in the policy. List channels that person or team actually monitors, such as an event email address or phone number.
Add those details through the Contact section that comes with the Event template. Visitors who use those details reach the named channel directly. If your named contact changes, edit the Contact section and publish the page again.
Draft the policy as answers to questions a reader would ask
Once you have your two lists and your contact, draft the policy as if each line is the answer to a question. Possible headings: expected behaviour, what we will not tolerate, raising a concern. Write each one in plain language, the way you would explain it to a friend attending for the first time.
A fill-in structure to adapt rather than copy could include these fields. Treat them as scaffolding, since your own wording will read better than any template language.
- Expected behaviour: [short list, e.g. respectful language, follow venue rules]
- We do not tolerate: [short list, e.g. harassment, intimidation]
- Raising a concern: contact [name] at [email] or [phone] during or after the event, by [channel such as in person, message or call]
Read the page from a fresh perspective and remember it is public
Before you publish, read the page as if you were arriving for the first time. Can a first-time attendee find the policy without scrolling past three other blocks? Is the reporting path unambiguous, with both a name and a working channel? Does the wording read like something you would say out loud?
Anything you publish on a hosted QREasy page becomes reachable by anyone on the public web. The page is not attendee-only and a link shared privately does not restrict access. If you would rather not list a personal phone number on a public page, choose an email address or a shared mailbox you control, and check that the wording still tells attendees what to expect.
Place each part using the Event template Text and Contact sections
Open the free Event template preview to see the layout before you start. To begin your own page, use the creation route for the free Event template. The Text section is where the policy itself lives. The Contact section is where the named person and their working channels go. You can arrange these alongside the event details you already want to share, and you can add further Text sections if your policy grows.
You can draft everything, review it from a fresh reader's view and publish when ready. Place the policy Text section before the Contact section so the reporting path is easy to find.
