Someone Tested Positive After Your S+ Event: An Incident Playbook

It is a Tuesday. The party was ten days ago and it went beautifully. Then someone messages you: they have tested positive, and they were there.

What you do in the next few hours decides whether your community remembers you as the organiser who handled it, or the one it happened to. Most people don't have a plan for this in advance. Here is one, so that when it happens you are following a procedure instead of improvising at midnight.

First, the reframe

Before any of the practical steps, take the thirty seconds to get your head right, because a panicking organiser makes every decision that follows badly.

This is not a verdict on your event. Infections travel through people, many STIs are asymptomatic for long stretches, and a room full of genuinely careful people can still pass something along. Nothing about receiving this message means you did something wrong or that your standards were too low.

There is also a selection effect worth understanding, because it changes how you should read your own history. You only ever hear about this if a guest knows who to tell and believes it is worth telling them, and a clear policy with a stated notification window is what creates that route. So if you have never received one of these messages, that does not establish that nothing has ever happened at your events. It may only mean nobody had a way (or felt comfortable enough) to reach you.

The first hour: what not to do

Every instinctive move in the first hour is the wrong one. Four things to actively not do:

• Do not post in the group chat. It feels fast and responsible. What it actually does is turn a health notice into a live conversation you cannot moderate, in front of people who will immediately start guessing who reported it.
• Do not ask the reporter who they were with. You are not running an investigation, and the moment you ask, you have made them a source of intelligence about other guests rather than someone doing you a favour.
• Do not reason your way to a shortlist. Your mental model of who interacted with whom is guesswork, and acting on it tells people you think you know things about their night that you do not.
• Do not promise anything you have not checked. Not timelines, not "this definitely was not passed on," not what a clinic will say. Everything you say in the first hour will be quoted back to you.

What you actually need to establish

The intake is short. You need four things:

• Which event they attended.
• What they tested positive for.
• Roughly when they tested.
• Whether they are willing to be named or described in the notice. Ask once, make the no easy, and take the answer at face value. How to handle this is worth getting right.

That is the whole list. What you must not ask for matters just as much: not who they were with, not what they did, and not proof.

Asking for proof feels like diligence and is actually the single most damaging thing you can do here. It converts someone who volunteered difficult information into a suspect being asked to justify themselves, and word travels. The next person in your community who gets a positive result will remember how this one was treated, and they will decide it is not worth it. You are not verifying a claim. You are relaying a warning, and the cost of relaying one that turns out to be over-cautious is far lower than the cost of never hearing about the next one.

Thank them, clearly and warmly. They did something that took nerve.

Deciding who to notify

The default answer is everyone who attended. Not a subset, not the people you think were involved, not the ones who were in a particular room. Everyone.

Three reasons, and they compound:

• Your reasoning is guesswork. You do not know who did what with whom, and you should not. Surfaces, shared spaces, and the simple fact that people move around a venue all make a tidy contact map fiction.
• A narrow list makes a claim about people. Sending a notice to eight of forty guests broadcasts your beliefs about what those eight were doing. That is an accusation dressed as a health notice.
• A short list is far more alarming. Being one of forty people receiving a routine, calmly worded heads-up is manageable. Being one of eight singled out is frightening, and frightened people start asking each other questions.

Some edge cases worth deciding in advance. If you ran two events inside the same window, notify both, since your guest lists probably overlap. Include people who arrived and left early; you do not know what happened while they were there. Include your crew, your door staff, and anyone else who was in the space. And if plus-ones came in on someone else's booking and you have no way to reach them, say so in the notice and ask people to pass it on.

This is also the practical argument for having a route back to your attendees decided before you need one. A ticket list gets you email addresses for whoever bought, which is not the same as everyone who came. If you use Play Safe for your door, everyone admitted is reachable for a notification window you set when you create the event, and you never hold a contact list you can read on your own.

Anonymity by default, disclosure by consent

This is the decision organisers get most wrong in both directions, so it is worth being precise. There are two rules and the order matters.

Rule one: without clear consent, the reporter is anonymous

If they have not explicitly agreed to be identified, you do not name them. Not in the notice, not in a follow-up, not in a private explanation to someone who is pushing hard for it.

This is not only about protecting one person's privacy, although that would be reason enough. It is about protecting the mechanism. If a reporter gets identified against their wishes even once, everyone in your community learns what happens when you tell the organiser, and nobody tells you again. You do not lose one person's trust, you lose the entire early-warning system, and you will not discover that you have lost it until the next time something goes unreported.

Rule two: with clear consent, pass it on, and say that they consented

Anonymity is a protection for the reporter, not an obligation on them. If they actively want to be identified, honour that, because it genuinely helps. An anonymous notice tells forty people that one of them was exposed to something. A notice naming a consenting person tells each of those forty people whether they actually interacted with them, which is the difference between a general warning and a decision someone can act on.

What they can consent to comes in two forms, and they are worth offering separately:

• A name. Simple, but only useful if guests know each other's names, which at a large or ticketed event they often do not.
• A description. "A tall woman with curly black hair, wearing a green harness." Frequently more actionable than a name, and some people are far more comfortable with one than the other. Offer both and let them pick either, both, or neither.

One thing to make sure they understand before they decide: a description is not automatically the softer option. At a sixty-person party it narrows things without naming anyone. At a gathering of twelve it identifies them completely. Say that out loud rather than letting them assume.

Then label it clearly in the notice. This part is not optional and it is easy to skip. If you pass on a name or a description, the notice must say that the person chose to share it. Without that line, recipients may assume you outed someone, and you have done exactly the damage rule one exists to prevent, only now in public and with your name on it. With that line, the same information reads as what it is: someone being unusually generous so that other people can look after themselves.

How to ask

Ask once, plainly, and make the no easy: "Some people choose to let us share their name or a description so that others can work out whether it is relevant to them. Completely your call, and no is a perfectly good answer." Then take the answer at face value. If they hesitate, decline, or simply do not respond to that part, that is a no and you do not raise it again.

Record what they agreed to, specifically. "Name yes, description no" is a different consent from "share whatever helps," and in three weeks you will not remember which one you were given.

One more case worth planning for: often, people appreciate credit for having done the responsible thing, and they have earned it. If they do not want to be identified in the notice, give that recognition privately and generously instead. Tell them plainly that they did the right thing and that it mattered.

What to send

Three templates. Adjust the specifics and send them close to as they are: plain, unhurried, and free of speculation.

The general notice

When the reporter has consented to being identified

Use this only when they have clearly agreed, and include only what they agreed to: the name, the description, or both. The consent sentence is what separates a helpful notice from an outing, so do not drop it to save a line.

If they have also agreed to share context beyond their identity, such as roughly when they think they were exposed or which nights they were present, add it in their own words where you can. Extra detail is only worth including when it helps someone decide what to do.

The follow-up, one to two weeks later

Send this even if nothing further has happened. Silence after a notice becomes its own rumour, and closing the loop is what makes the whole thing feel handled rather than abandoned.

Across all three, the same rules apply. No speculation about how or where. No reassurance you cannot back, including any version of "the risk is very low," unless you are quoting something specific. And no apology phrased in a way that implies fault, because "we are so sorry this happened at our event" invites the reading that your event caused it. "We wanted you to know as soon as we did" is the tone you want.

If you are unsure about the testing timing to include, our guide on how STI testing works covers window periods per infection, and how to disclose an STI is a useful thing to link for anyone who now needs to tell their own partners.

What to say publicly

Usually nothing. There is an important distinction between notifying the people who were there and announcing something to a scene, and organisers under stress tend to collapse the two.

A public post converts a health notice into gossip. It reaches hundreds of people for whom it is not actionable, it invites speculation from people who were not even present, and it puts a target on whoever the community decides the reporter must have been. None of that protects anyone.

The narrow exceptions: if attendees are actively spreading misinformation, if the story is already circulating in a distorted form, or if there is a genuine safety reason more people need to know. Even then, keep it to a short factual statement with no detail that could identify anyone. Note that this holds even if the reporter consented to being named in the notice: agreeing to be identified to the sixty people who were in the room is not the same as agreeing to be identified to a public feed, and you should assume it was the first unless they have told you otherwise.

If it leaks anyway, do not deny it and do not investigate who leaked it. A calm, brief acknowledgement is enough: yes, we sent a notice to everyone who attended, this is a normal part of running events responsibly, and we are not discussing individuals.

What you owe attendees, and what you don't

Deciding this in advance is what lets you hold a line calmly when someone is demanding more at 1am.

You owe them: a prompt notice, accurate information, clear guidance on what to do next, and a straight answer when they reply with a question.

You do not owe them: the identity of a reporter who has not consented to being named, a list of who else was notified, a guarantee it will not happen again, a refund for an event that already took place, or a public accounting of how you run your event. Someone will ask for at least one of these, usually the first, and usually framed as a right. It is not.

"I understand why you are asking, and we do not share that" is a complete answer. You can repeat it as many times as necessary.

The week after

Expect follow-up questions and prepare one answer rather than improvising each time, because inconsistent answers are what make people think something is being hidden. Point people toward testing timing and their own clinician rather than answering clinical questions yourself; you are an organiser, not a doctor, and saying so is not a cop-out.

Then, once it has settled, ask whether anything in your policy actually needs to change. Sometimes the answer is genuinely yes. More often the answer is that the system worked: someone told you, you told everyone, people got tested.

Resist the urge to overhaul anything in the first 48 hours. Policy written in a panic is almost always too strict, gets quietly unenforced within two events, and leaves you worse off than before, because now your community has learned that your rules are mood-dependent. If you do decide to change something, our guide on writing a health policy for your event covers how to raise a standard without splitting your community.

Why handling this well builds trust

Here is the part that is easy to miss. A guest has no way of knowing whether an event has ever had an incident, so "this has never happened here" is neither something you can credibly claim nor something they could verify. What they can see, and remember, is how you behaved when it did.

Think about what your attendees actually learn from a well-run notice. They learn that you have a way of reaching them. They learn that you will use it even when it is awkward and even when it might cost you ticket sales. They learn that if they are ever the person with the bad news, they will be thanked rather than exposed. That is worth more than any promise in a listing, because they have watched you do it.

You cannot prevent every incident, and an organiser who thinks they can is one bad Tuesday away from finding out otherwise. What you can do is decide, in advance and calmly, exactly how you will behave when it happens. Write it into your policy, tell your crew, and then put it out of your mind.

Preparation is what turns the worst night of your organising life into the thing people cite when they recommend you to a friend.