Explaining Our Conference Code of Conduct for Admission

You can view our full code of conduct for Admission here

The first conference I attended was a global marketing event in the USA. I was a new employee of the company hosting the event. I was lucky enough to get a free pass to all the tracks as it fell in line with my training month. 

I don’t know if they had a Code of Conduct for this event. It’s not on the cached version of the website, and I didn’t know that codes like that existed at the time. Conferences were meant to be places where the ~real~ adults went to do business and share professional insights, after all. 

Between the buzz of getting a fast track into that world, and the glitz of the production that went with it, I felt like I was infiltrating a new caste of “grown-up” where everyone was as stiffly proper as a board meeting, intelligent as Sherlock Holmes under siege, and frivolous only when there was a shiny new hoverboard salesman parading around the smoking veranda. 

Needless to say, I was mislead. 

As with larger conferences like this, there were many stages, many speakers, many exhibition stands, and many after-parties. In a booth at one of the latter, I was sitting with some future colleagues and other employees, but soon, let’s call it “The Jagerbomb Impulse” came over them, so I said I’d stay behind to watch their bags. 

I didn’t realise that a lot of the other salespeople that were at the bar had brought along business partners and potential customers until I was joined in the booth by an Australian man who started asking me questions about the product. 

Immediately afraid that I’d ruined the sale since I’d only had three weeks of formal training I said, “I’m new, sorry.” He didn’t seem to mind. In fact, he kept asking. I wasn’t sure whether he hadn’t understood me (we had different accents and I was speaking feverishly) or if he wanted to give me a chance. 

After about three or four minutes of this I was looking over my shoulder every few seconds, wondering how on earth it could take so long to chug that godawful aniseed and Red Bull concoction. The last time I turned back, his hand was gripped around my knee and, as I said “I really should go get back to the guys”, it tightened. 

The guy I shared the plane over with came then, tipsily giggling, to tell me it was his round. I felt a weight drop from my thigh and walked over, smiling as hard as I could.

Was he a customer already? Was someone going to lose their commission? Was he going to leave a bad review? Who could he ask to find out who my manager was? I was peeling my mind apart looking for the answer to what I did wrong. To what could make me feel like I had done something so wrong. 

There was no one to tell.

You’re the first to hear it, in fact. Almost half a decade has past and, knowing what I know now, I don’t want that, or worse, to happen anywhere near me again. 

The New Story

A good Code of Conduct enables us to interact in a conference or event environment where we can relax and show our personal traits without fear of being harassed or victimised because of the things that make us who we.

Unverified impressions or people’s biases based on appearance, ability or belief are bad, and naïve, both in my experience and in the shared experience of the number of people who’ve opted into having Codes of Conduct. 

Any contemporary conference that doesn’t have a Code of Conduct might as well have a picture of a red flag that they link to from their website instead,  typified in the fact that many organisations and individuals refuse to speak at, attend or fund events that omit these codes.

And, if you think that these codes aren’t ever acted upon, this GeekFeminism timeline of incidents should give you an idea as to the number of (reported) issues at events and conferences.

Our Story

So, that’s why we have one, but here’s how we made ours in a bid to make sure it lived up to standards set by the events that we look up to:

In a previous post on this blog, I linked to a Medium article penned by Karolina Szczur. Her suggestion is that,

Often, [a] Code of Conduct is a bare minimum for determining whether conference organizers have thought about safety and inclusion at all.”

In the article she goes into depth on virtue signalling and the practice of copying and pasting that many conference Codes of Conduct have been guilty of defaulting to in the recent past. 

We tried to avoid that as much as possible by taking inspiration from multiple different sources and tailoring them to our needs. We also spent time thinking about how we would want to be included, and thinking about conferences we’ve previously attended and what we liked/disliked about those experiences. 

What we included

We like to think our Code of Conduct ended up as a pretty robust outline. However, as we’ll reiterate at the end of this post, we’re always open to further feedback

We covered the following:

  1. Who our Code of Conduct applies to,
  2. Why we’re enforcing our CoC,
  3. Definitions,
  4. Consequences,
  5. Reporting and Enforcement, and 
  6. Thanks.

This format allowed us to clarify what is and isn’t permissible, in simple terms, to avoid any misinterpretation or loopholes, and to cater for any situations that may arise that could reasonably be deemed misconduct.

That said there are some items that might require a little elaboration:

Key terms

CoC definitions

  • Neurotype is a relatively newly accepted phraseology (penned in the 90s) and, as such, doesn’t have a hard and fast definition in medicine or psychology. In fact, according to Very Well Health, “[neurotype] doesn’t describe a particular personality, trait or set of abilities.” Typically, we think about neurotype in the affirmative and conditional versions of the word:

    • Neurotypical refers to an individual who is of typical developmental, intellectual, and cognitive abilities. In other words, it’s not used to describe individuals who have autism or another condition on the autistic spectrum, or another developmental or experiential difference (e.g. dyslexia, epilepsy, cognitive differences acquired by trauma or the influence of mind/brain altering substances, or other external factors.)

      • This does not imply that being “neurotypical” is the only “normal”, “right” or “healthy” type of brain or mind an individual can have. 

    • Neurodivergent or neurodiversity refers to an individual or group of individuals whose neurocognitive functioning diverges from dominant societal norms.

      • This definition by Wired is a great way to comprehend this type of diversity: “One way to understand neurodiversity is to remember that just because a PC is not running Windows doesn’t mean that it’s broken. Not all the features of atypical human operating systems are bugs.”

  • ‘Dead’ names are the names given at birth to trans* and non-binary individuals which no longer describe them. 

  • Reverse “-isms” are unacceptable because of the differences between prejudice and privilege.

    • A reverse “-ism” could take the form of a white person calling a person of colour “racist”, or a cis person calling a trans* person “cisphobic”, for example.
    • The issue with these sentiments is that, while anyone can be prejudiced towards anyone else for anything, there is an imbalance of privilege associated with a person claiming a reverse “-ism”.
    • This makes traditional “-isms” significantly more harmful than simple prejudice as it reinforces a historical superiority based on the deprivation of others. That deprivation has taken many, very real, forms for those individuals or members of their community in the past (e.g. abuses of criminal justice, economic inequality, hate crimes, etc.)
    • The privileged person has no experience of these in the same forms. For example, a white person calling a black person racist would struggle to find an example of the systemic persecution of white people by black people.
    • The only way these traditional “-isms” can come about is if the person guilty of perpetrating them comes from outside of the underprivileged communities they are attacking. Ergo, that privileged person is condoning a superiority founded on the person they are being racist (etc.) towards being of less worth, which can never be ethical. 
    • For further elaboration, I recommend On Race-Isms, particularly this article.

Broader Inclusion

As Karolina mentioned in the article above, the CoC should only be part of a broader inclusion effort at conferences, so we have asked our attendees additional questions post-purchase to cater for dietary requirements, clothing, accessibility requirements, and consent to being photographed. 

Thanks to a swift (and deserved) calling out by Florian from RustFest, we have a clear accessibility policy now live on the site which includes:

  • Details of our venues’ accessibility,
  • Details of accessibility for our talks,
  • Details of food and drink accessibility, and
  • Details of free tickets available if any guest wishes to be accompanied by an assistant.

Admission Accessibility

Where we got guidance

Throughout our announcements about Admission, we’ve reiterated that we’ve spent five years with a front row seat to some of the most influential and inspiring conferences on the planet. 

A large part of that has been working with emotionally (and otherwise) intelligent, respectful, innovative folks who aim to create inclusive, remarkable experiences. Here are a few that we took guidance from for this year’s Code of Conduct:

Brighton Ruby/Andy Croll

Andy, upon opening Brighton Ruby, goes beyond “just be nice to everyone.” He repeatedly says that he wants people to feel able to approach him with complaints, and shares his personal phone number, email, and Twitter handle.

To mirror this, at Admission, any member of our production, volunteer, or security team will be trained touch points attendees can express concerns to, which we will discuss at the time of the conference.

Particularly, Andy’s reinforcement of how to behave if you are the individual who is being called up on an infringement of the code of conduct is important, and there are three key quotes in his outline that explain a reasonable response:

  1. “Own it. Say sorry.”
  2. “If you are corrected, this isn’t about you. Suck it up, frankly.” And,
  3. “‘I am sorry you were offended’ is not a good apology.”


The Django community is a highly diverse one, but they admit it’s “one of [their] huge strengths, but it can also lead to communication issues and unhappiness.” This lead them to create one of the most referenced code of conducts in the tech conference industry.

You’ll see a lot of themes of theirs echoed in ours, particularly their insistence that those involved in their community be “careful about the words their choose.” We used this notion to inform how we defined topics, phraseology, and objects that are acceptable, and those that aren’t


I appeal to you twice throughout this post to let us know if you see any way we could improve on our Code of Conduct, but that’s meticulously defined as the process of creating a “living document” out of a code like this by the team behind XOXO.

XOXO’s policy is an archetype of how to explain the behaviour what’s acceptable at a conference. We leaned heavily on their examples used to define harassment.

Geek Feminism 

Geek Feminism also provided guidance for us regarding harassment, as well as a way by which we could aptly express our commitment to prioritising marginalised people’s safety over privileged people’s comfort. Further to this, we adopted some language from their consequences section. 


JSConf provide one of the first open-source Codes of Conduct that I became acquainted with which can be found here. While this template has been aptly elaborated upon by numerous conference, we also took inspiration from the JSConf AU Code of Conduct, particularly around confidential reporting of incidents and definitions of what a harassment-free experience looks like.

What the results were (so far)

We’ve had the pleasure of securing Kim Crayton as a speaker for Admission. She heads up #causesascene, an organisation focused on the strategic disruption of the tech scene for the benefit of marginalised individuals therein. 

She took to Twitter to share her thoughts, as did a few others:

It’s heartening to see such a positive response to the efforts we’ve put in so far and we will strive to make our actions speak as loudly as the words that have gone into creating this document

We were humbled to also get this feed back from Gilles Demarty, the Regional Coordinator of IxDA:

It’s my hope that the above information clarifies and reinforces what we want to achieve with our Code of Conduct. An admission (ha!) before we go, though: we don’t think there’s ever going to be a perfect code of conduct, but we strive towards it anyway. Given that this is a conference for organizers, please call us on our omissions, and feel free to let us know what’s worked for you in the past.