Reading the code of conduct before you need it

Most professional conferences of any size publish a code of conduct — a short document on expected behavior, what counts as harassment or misconduct, and how to report it. Almost nobody reads it at registration, when reading it costs nothing and changes nothing about the day. Almost everyone who ever needs it is trying to find it for the first time in the middle of an uncomfortable moment, on a phone, at a venue, without knowing whether the page they're looking at is even current.

It isn't boilerplate — it's an operating document under pressure

A conduct policy reads like standard legal language until the moment it's the thing you're actually relying on, at which point three details matter a great deal: what behavior it actually names, who has the authority to act on a report, and whether reporting is anonymous or requires putting your own name on it. Those details vary by organizer and by event, which is exactly why reading the summary once, in a calm moment, is worth the few minutes it takes — it's a document meant to be understood in advance, not parsed for the first time while something is actively going wrong.

Know the contact before you need the contact

Some events route conduct reports through the registration desk; others name a specific person, a separate hotline, or an email address disconnected from the organizer's day-to-day staff. None of that is obvious from the badge, and asking at the desk in the moment you need it adds a delay and an audience to something that usually calls for neither. The organizer's own registration page or conference app is almost always where the current contact lives — worth a bookmark alongside the accessibility request that the same kind of advance reading tends to surface, since both are details most attendees never look for until they're the one who suddenly needs them.

It's for you before it's a crisis, too

The policy isn't reserved for the worst case. It also covers the smaller frictions that are common enough to be ordinary: a vendor who won't stop pitching past a clear no, a comment at a reception that crossed a line without anyone involved needing a dramatic word for it, a colleague whose attention stopped being welcome three exchanges ago. Where the essay on vendor hospitality argues for asking your own compliance contact when a policy is silent, the conduct policy is usually the opposite case — not silent, just unread. Knowing it's there, and what it actually says, is what turns an uncomfortable moment into a known procedure instead of an improvised one.