How to Write a Health Policy for Your Play Party (With Copy-Paste Templates)

Plenty of organisers have a health policy that has never actually been written down. It lives in your head, it gets explained slightly differently to different people depending on who is asking, and it collapses the first time someone with social weight turns up not meeting it.

Writing it down costs you about an hour and changes how the whole event runs. This guide covers how to choose your standard, three templates you can copy straight into a ticket page, the phrasing that causes arguments, and how to hold the line without turning your door into a checkpoint.

What a written policy does for you

This is worth framing selfishly, because the usual argument for a policy is duty and duty is not what gets things written. A published health policy does four concrete things for you as an organiser.

• It filters before the door instead of at it. Almost everyone who would not have met your standard simply does not buy a ticket. Door refusals drop close to zero, which is the outcome you actually want, because a refusal at the door is unpleasant for everyone in earshot.
• It removes the argument. When the rule is published, a guest who disagrees is disagreeing with a policy, not with the person standing in front of them at 11pm. That difference is enormous for whoever is working your door.
• It makes exceptions defensible. You cannot be consistent about exceptions until there is a baseline everyone knows. Without one, every exception looks like favouritism, and sometimes it is.
• It markets the event. This is the one organisers underestimate. A clear policy reaches the people who currently stay home, and that is a bigger group than the people it turns away.

Decide your standard before you write a word

There are five levels a policy can sit at, and choosing yours is most of the work. Writing it is the easy part afterwards.

• Silence. Nothing stated. Fine among friends, a real gap for a paid public event.
• A stated expectation. You say what you expect, you check nothing. Costs nothing to run, filters nobody, but it does set a norm, and norms genuinely move behaviour.
• Attestation. Guests confirm they meet a specific requirement. Most people will not actively state something untrue, so this filters more than it looks like it should.
• A checked threshold. A standard, checked at the door, based on what the guest reports about their own testing and activity. Filters the honestly-vague, which is the largest group.
• Documentary proof. You look at actual lab results. See the section below before you go here.

The comparison worth understanding is between the last two, because proof looks like the straightforwardly stronger option and is not. It is different, and it is worse in ways that matter.

A lab result verifies a document from a real lab on a real date. But it says nothing about the three weeks since that date, it is trivially defeated by a crop or a borrowed screenshot, and collecting it makes you the custodian of named health records on your personal device. A checked threshold cannot verify anything against a lab, but it does account for what happened after the test, it applies identically to everyone, and it leaves you holding nothing at all.

Neither catches a determined liar, and no policy should be judged against that standard. What both of them actually fix is the honest-but-vague case: guests who could not tell you with any confidence when they last tested or what it covered.

One piece of advice for anyone running their first few events: start at a stated expectation or attestation, and say out loud that you intend to move up. A bar raised on a published schedule keeps a community together. A bar sprung on one splits it.

The five clauses every policy needs

Whatever level you pick, cover these five things. This is also, not coincidentally, the checklist thoughtful guests use to judge you.

• The requirement. With a number. "Recently tested" is not a requirement, it is a mood. "A negative test within the last 90 days" is a requirement.
• The verification. How you check, stated plainly, including "we don't, we trust you" when that is the truth. Honesty here costs you nothing and buys a lot.
• The consequence. What happens at the door if someone does not meet it, and what happens to their ticket money. Refunds are where the real arguments happen, so decide in advance.
• The aftermath. Your notification window, and what you will do inside it. This is the easiest clause to leave out, because it deals with something you are hoping will not happen, and it is the one that most distinguishes a serious event.
• The data. What you collect, who can see it, how long you keep it. If the answer is "nothing, and nobody," say so, because it is genuinely reassuring.

On verification, it is worth knowing what the options actually cost you. Reading lab results means handling medical records. Ticking a box means handling nothing but also checking nothing. In between there is an app-based check: Play Safe scores a guest's own reported testing and activity history against a threshold you set, and at the door you see a pass or a fail rather than any underlying health data. It works offline, so a basement with no signal is fine, and it is free for both you and your guests. The one point at which you do see health information is afterwards: if an attendee reports a positive test inside your notification window, you see which infection, because you are the person relaying the warning to everyone else.

Template 1: the stated expectation

For events where you want to set a norm without checking anything. Copy, adjust the numbers, publish.

Three lines are doing the work here. The three months makes it a real ask rather than a gesture. The no questions asked ticket transfer removes the financial reason to come while symptomatic, which is the single most useful sentence in the whole template. And the notification paragraph tells guests you have thought past the door, which is what actually distinguishes you from the event down the road.

Template 2: attestation at purchase

For events that want a real filter without handling anything sensitive. Pair the text below with a required checkbox at checkout.

The paragraph refusing proof is not padding, it is the most important line in the template. Guests will helpfully send you screenshots of lab results if you leave any room for it, and once one arrives in your inbox you are holding medical data whether you asked for it or not. Saying "we will not open them" closes the door before it opens.

Template 3: a checked threshold at the door

For events that want the standard actually applied. Fill in the bracketed values.

The honest limits paragraph is the one to keep even if you cut everything else. Omitting it is the most common mistake in strict policies, and it causes two separate problems. It quietly promises a level of certainty that no system can deliver, which is a promise you will be held to if something goes wrong. And it encourages guests to relax their own precautions, which is the opposite of what a strict policy should do.

A note on asking for lab results

There is no fourth template, because the recommendation is not to.

If you collect test results, you are holding special-category personal data: health information, linked to real names, usually on a personal phone or in a personal inbox. Under the GDPR, which covers the EEA and the UK, health data sits in a specially protected category, and a leak can oblige you to report it to a regulator and to the people affected. The realistic breach scenarios are not dramatic ones. A lost phone. A shared laptop. An account someone else still has access to. An ex who knows your passcode.

Weigh that against what you actually gain, which is less than it appears. You are looking at an image on someone else's phone. You cannot tell whether the name was cropped in or the date was edited, whether it belongs to the person in front of you, or what has happened in the weeks since it was issued.

The alternative principle is simple: check a standard, keep nothing. If you are still set on documentary proof, two rules make it survivable. Look, never store: view it at the door, hand the phone back, write nothing down. And never accept anything sent to a personal account, because that is precisely how you end up with a folder of other people's medical records you did not want.

The wording that starts fights

Small phrasing choices cause most of the friction. Some before-and-after pairs:

• "Clean" becomes "recently tested negative." Clean implies its opposite, and the people it insults are exactly the people you most want testing and disclosing.
• "We reserve the right to refuse entry" becomes "if you do not meet the requirement we will offer you a refund or a ticket to the next event." The first sounds like a bouncer, the second sounds like a plan.
• "All attendees must present evidence of a negative screening" becomes "we will check one thing at the door, and here is what it is." Clinical language makes a party feel like a waiting room.
• "Be responsible and respect others" becomes "here is what we ask, and here is what we will do if something comes up." Moralising reads as judgment; specifics read as care.

If you want more on the tone that makes these conversations land, our guide on talking about sexual health is written for individuals but the principles transfer directly to event copy.

Publishing it

A policy nobody reads is a policy nobody follows. Put it in four places:

• The ticket page, above the buy button, not below it.
• The event listing, in short form.
• The confirmation email. This is the one organisers forget and the one people actually read, because it arrives when they are excited and paying attention.
• The door itself, printed and visible, so it is a shared reference rather than something your crew has to recite.

For listings with a character limit, two sentences will do: "We ask everyone to have tested negative within the last 90 days, and we check at the door. If anyone tests positive within four weeks after, we will let all attendees know anonymously."

One last check before you commit to the wording: read it back as a guest would. Attendees who take their own health seriously treat your policy as a signal about how the whole event is run, and they notice specificity, silence, and anything that sounds stricter than it turns out to be. Our companion guide on how attendees judge a play party's health policy is effectively the marking scheme they are using.

Enforcing it without becoming a bouncer

Decide in advance who makes the call, and make sure it is not whoever happens to be nearest. Brief that person properly: what the requirement is, what to say, and specifically that they are allowed to escalate to you rather than improvise.

Then the rule that matters more than any other: check yourself and your crew first, and visibly. A policy that quietly exempts the inner circle is worse than no policy at all, because everyone can see it, and it tells your guests exactly how seriously to take everything else you have written.

On exceptions: decide the categories in advance rather than case by case at the door. Someone in a closed relationship with a partner who tests. Someone whose last test was recent but fell outside the window by a week. Someone travelling from somewhere testing is genuinely hard to access. Write your categories down, apply them consistently, and never let an exception become a personal favour, because the moment one does, your policy is decoration.

Raising the bar across a season

If you want a stricter standard than your community currently meets, do not jump. Announce it one event ahead, and be specific about what changes and what does not.

The pattern that works: tell people at the previous event and in the follow-up email, publish the new requirement in full, and make the self-check available before tickets go on sale so nobody meets the new rule for the first time while standing at your door. Say plainly why you are doing it, and acknowledge that some regulars will need to change something to keep coming. That acknowledgement is what makes it feel like an invitation rather than a purge.

Done this way, a tightening bar is one of the strongest signals of a well-run event, and people talk about it. Done abruptly, it reads as a judgment on everyone who was there last time.

One last thing worth writing before you need it: a plan for what happens if someone does test positive after your event. That is the clause everyone skips and the one you will be most grateful for. We have written that playbook separately in what to do when someone tests positive after your event.