A code of conduct is a short document that says what behaviour is expected at an event, what is not, and who to tell when the second one happens. The document is the visible part. The part that decides whether it works is the response process behind it: a named team, a way to reach them that does not require finding them in a crowd, and an agreement made before the event about what they are allowed to do.
What the document has to contain
Three things, and they are short. A statement of the behaviour expected of everyone present. A list of behaviour that will not be tolerated, specific enough that a reader can tell whether something counts. And a way to make a report, with names and a contact route attached to them.
The specificity is what does the work. A document that says “be respectful” gives a response team nothing to stand on, because respect is contested and the person complained about will contest it. A document that lists unwelcome sexual attention, sustained disruption of talks, and deliberate intimidation gives the team something a reasonable person can be held to.
Length is not a virtue in either direction. Codes that run to several pages are rarely read, and codes of three sentences leave the team improvising. A page is usually enough.
The response team
The team is a small named group, agreed before the event, whose job during the event is to receive reports and decide what happens. Two or three people is typical for a regional conference. What matters is less the size than that they are named in advance, reachable during the event, and not all drawn from the same friendship group as the organisers.
The team needs agreed powers before the first report arrives. Can they ask somebody to leave a session? Can they revoke a ticket? Can they involve the venue’s own staff? An organiser who has to decide those questions while a distressed person waits has already lost the thread.
Reaching them
A contact route that requires finding a specific person in a crowded hallway is a route that does not exist. The routes that work are the ones a person can use without being seen to use them: a phone number printed on the badge, an email address that reaches all of the team at once, a staffed desk that is not the registration queue.
Badges are the most reliable carrier, because they are the one object everybody has on them all day. A number on the back of a badge is read by people who would never have opened the website.
What happens after a report
The team listens, decides, acts and records. Recording is the step most often skipped and the one that matters afterwards: a decision that exists only in somebody’s memory cannot be applied consistently to the next report, and cannot be explained if it is questioned later.
Outcomes range from a quiet word to removal from the event. The range is wide on purpose. A team whose only available action is expulsion will avoid acting at all, because expulsion is disproportionate to most of what is reported.
Publishing it
The code belongs on the website before tickets go on sale, not in a link added the week of the event. Speakers and sponsors read it as part of deciding whether to be associated with the event, and attendees who have had a bad experience elsewhere read it first.
Most events adopt an existing code rather than write one, which is sensible: the wording has been tested by other events and the reader may already know it. Adopting one still leaves the two decisions that cannot be borrowed: who the team is, and how they are reached.
Common questions
Does a small conference need a code of conduct?
The document scales down but the response process does not disappear. A fifty-person event still needs somebody named to receive a report and a route to reach them, because the alternative is that the report goes to whoever is standing nearest.
Can the organisers be the response team?
They can, and at a small event they usually are. The difficulty appears when a report concerns a speaker the organisers invited or a sponsor they signed, which is common enough to plan for. One person on the team who is not an organiser removes most of that problem.
What counts as a specific enough prohibition?
A test that works: could two people who disagree about a situation both read the line and agree on whether it applies? “Harassment” alone usually fails that test. “Following somebody around the venue after being asked to stop” usually passes it.
Should reports be published afterwards?
Numbers sometimes are; details almost never, because the reporter is identifiable from them in a small community. A short transparency note saying how many reports were received and how many led to action is the usual compromise.
What if the event is online?
The document changes very little and the routes change completely. Chat moderation, the ability to remove somebody from a call, and a contact address that is watched during sessions replace the badge and the staffed desk.