How to set up harassment reporting at a ticketed event

Someone approaches your ticket desk halfway through the evening and says another attendee won't leave them alone. They're worried about making a scene. Your volunteer wants to help, but the only instruction in their briefing was to contact management. Management is backstage, and the person they're reporting is still nearby.

Setting up event harassment reporting means deciding who receives that report, how the person gets support, and who can act while the event is running. You need a trained lead and deputy, reporting options people can actually use, and an agreed response that separates urgent safety decisions from a later investigation.

A code of conduct helps explain your expectations. The reporting arrangements make those expectations usable when someone needs you. This guide walks through the decisions to make with your venue, staff and specialist advisers, including what to publish, what to record and how to follow up after the audience leaves.

Decide what your reporting process covers

Start by writing down where and when your event's conduct policy applies. Include the activities you control, such as the paid programme, your networking reception and any official online discussion spaces. Be explicit about an afterparty if your team organises it. An attendee shouldn't have to guess whether the reporting contact still applies once the final session ends.

Describe the behaviour people can report in ordinary language. Examples might include unwanted sexual attention, discriminatory abuse, repeated contact after someone asks for it to stop, intimidation, stalking or unwelcome touching. Have your policy reviewed for the event's location and audience. A practical event rule and a legal definition of harassment aren't always identical.

Allow people to raise a concern when they're unsure what to call it. Asking an upset attendee to decide whether something qualifies before you'll listen creates an unnecessary hurdle. Your trained lead can establish what help is needed and which procedure applies.

The Python Software Foundation's event code of conduct guidance recommends explaining how reports are handled and what response people can expect. It also calls for instructions covering conflicts of interest. Use that principle when writing your own arrangements, with contacts and procedures that belong to your event.

Appoint a trained lead who has time to respond

Name a reporting lead and a deputy for each operating period. Choose people with suitable training in receiving disclosures, assessing immediate support needs and applying your conduct procedure. Being the most senior person on site doesn't automatically prepare someone for that conversation.

Give the lead enough time to do the job. If they're also calling stage cues or managing a busy bar, who takes over those duties when a report arrives? A name on a contact sheet provides little help when that person cannot leave their station. Plan relief as part of your staffing budget.

Agree what the lead can decide and when another person must become involved. They may coordinate support and recommend temporary arrangements, while a venue manager or security supervisor carries out authorised safety actions. Employment complaints may need a separate employer procedure. Write those responsibilities down before the event.

Cover breaks, shift changes and the period after doors close. The deputy must know when they've accepted responsibility and which unresolved matters need attention. Your event staffing plan should account for this coverage alongside the rest of the operation. Don't quietly add sensitive reporting work to a volunteer role that was advertised as checking tickets.

Budget for the arrangement you publish. Include training, relief cover, private space and any contracted specialist support when you're pricing the event. Ask suppliers what happens if the reporting lead receives another concern while already helping someone. Confirm the answer together. The deputy may need to respond at the same time, rather than simply cover a break. Agree who coordinates competing demands and how additional qualified help becomes available. A small event can use a straightforward process, but the operating commitments still need owners and resources. Review those commitments whenever the programme, venue or audience changes, because an arrangement agreed for one event may need adjustment for the next.

Provide an independent route for difficult complaints

Imagine the report concerns your reporting lead, your business partner or the sponsor paying for the reception. Where does the attendee go? If the answer is back to the same person, the published process has an obvious weakness.

Choose an alternative contact who can receive complaints involving the normal reporting team. For a small event business, that may require a suitably qualified external person or an arrangement agreed with the venue. Check their availability, independence and authority. A friendly adviser who hasn't agreed to respond during the event isn't a working alternative.

Publish that route alongside the main reporting instructions. Don't require the person making the complaint to explain a conflict to the individual they're avoiding. Internally, require staff to disclose relevant relationships and withdraw from decisions where they cannot act impartially.

Apply the conduct procedure to speakers, performers, exhibitors, contractors and sponsors within its stated scope. Agree the practical consequences through the relevant contracts and event rules. A junior staff member should know who can handle a complaint about a prominent guest without having to negotiate directly with that guest's commercial representative. Resolve that decision before the guest arrives.

Offer spoken and written ways to ask for help

Provide a staffed place where someone can ask for support, together with a written reporting option. The place needs clear signs, an accessible route and staff who know how to contact the lead privately. The written option might be a dedicated address or a form you have assessed for this purpose.

Choose channels your team can monitor. A form linked throughout the venue is misleading if nobody sees submissions until the following morning. Say when each channel is checked, what response people can expect and which route to use during the event for urgent help. Test notifications on the devices the duty team will carry.

Keep a way to ask for help without a working phone. Batteries run out, reception fails and some people won't want to type sensitive details into a public form. A printed sign directing them to a staffed help point gives them another option. The staff member can contact the lead without asking for a public account of what happened.

Don't use a general customer service inbox unless you can restrict access and manage sensitive reports properly. People dealing with ticket changes or marketing enquiries don't all need access to a harassment disclosure. Decide who receives the message before you publish the address.

Make reporting accessible without requiring a companion

An attendee may need to communicate in writing, use an interpreter, move to a quieter location or have more time to explain. Ask what would help rather than assuming every person will be comfortable speaking to a uniformed member of staff in a noisy foyer.

The US Department of Justice's effective communication guidance explains that covered organisations must communicate effectively with people with communication disabilities. The appropriate assistance depends on the situation and the person's needs. For a US event, include your reporting arrangements when reviewing those duties with the people responsible for accessibility.

Choose the help location with privacy and physical access in mind. An upstairs office with no accessible route won't work for everyone. Neither will a supposed private room that requires someone to pass the person they're reporting. Agree alternative locations and who can open them during the event.

A person may want a friend or support person present, but don't make that a condition of receiving help. Be careful about relying on a companion to interpret sensitive information. Plan appropriate assistance with qualified providers where needed. The broader event accessibility checklist can help you review the rest of the attendee journey alongside this specific process.

Explain confidentiality before asking for detail

Don't promise that nobody else will hear about a report. The lead may need to share limited information so another person can provide support, assess risk or carry out a fair procedure. Some situations involve legal reporting requirements. Confirm those requirements locally, including any safeguarding duties where children or adults at risk may attend.

Explain the limits in plain language before inviting a detailed account. Tell the person who normally receives information, why you might need to share it and how you'll discuss the next steps with them where possible. If immediate danger requires urgent action, don't delay that action to finish an explanation.

Distinguish between asking what support someone wants and treating their agreement as the answer to every legal or operational question. Their preferences matter. Your organisation also needs a lawful, documented basis for its decisions, including any decision to act despite a request for no further action. Get qualified advice on those boundaries before the event.

Privacy applies to the setting as well as the paperwork. A conversation next to the queue can expose someone even when the report itself is restricted. Ask whether the person wants to move somewhere quieter and explain who will accompany them. Don't broadcast their name or account over the general radio channel.

Publish instructions people can find quickly

Include the reporting instructions in the event information people receive before arriving. Repeat the essential details at the venue and in any official event space your team moderates. Someone who missed the email should still be able to find help without searching through ticket terms.

Your public wording should answer the practical questions. Who can report? Where can they go? What happens when they do? Which channel works during the event, and how can they raise something afterwards? Explain the alternative contact for complaints involving your team. Keep the full procedure available for readers who want to understand it.

Use the same contact details everywhere. If a lead changes, update the website, signs, staff briefing and any automated replies that mention them. A visible date or version on the internal contact sheet helps staff check they have the current instructions.

Avoid promises such as immediate resolution or guaranteed anonymity unless your arrangements can support them. You can commit to taking concerns seriously, explaining the process and responding within stated monitoring arrangements. You cannot honestly promise the same outcome or completion time for every report. Have the actual duty team read the published wording and confirm they can deliver it.

Teach every staff member the first conversation

Everyone who meets attendees should know how to receive an initial request for help. They don't all need access to the case record or authority to investigate. They do need a calm first response and a reliable way to reach the lead.

RAINN's guidance on talking with survivors of sexual violence emphasises listening and supporting the person's choices without pressure. Use specialist training to prepare staff for disclosures. The first conversation should help the person reach appropriate support, rather than demand a complete account at the ticket desk.

Useful opening questions include whether the person needs urgent assistance and whether they'd like you to contact the reporting lead. Explain what you're doing before stepping away or making a call. If they want to speak somewhere private, arrange that without leaving your assigned post uncovered or asking them to approach the reported person.

Brief staff to avoid questioning someone's clothing, drinking or decision to attend. They shouldn't demand evidence before contacting the lead, propose a confrontation or promise a particular sanction. Your volunteer briefing should include the referral route, the backup contact and what staff do when their normal supervisor is the subject of the complaint.

Separate immediate danger from ongoing support

If someone is in immediate danger or needs urgent medical care, use the venue's emergency arrangements and appropriate local emergency services. Staff shouldn't wait for the reporting lead to approve an emergency call. Their actions must remain within their training and the agreed site procedures.

When the immediate danger has passed, the person may still need practical help. They might want a quiet place, assistance contacting someone they trust or support leaving the event. Ask what they want and explain which options you can provide. Don't assume leaving is their preferred outcome or make them responsible for finding their own replacement arrangements.

A safety response can be necessary before you've completed an investigation. Decide in advance who can authorise proportionate temporary measures and who implements them. Keep the reason for each decision in the restricted record, including what information was available at the time and when the decision will be reviewed.

Connect this process to your event security plan. That plan covers security duties, authority and communication. The reporting procedure explains how a person asks for help, how their information is handled and how their report progresses. Read the two together so they describe a working handover rather than competing instructions.

Ask what the person wants to happen next

Someone might want help moving away from another attendee without making a formal complaint. Someone else may want their account recorded, an investigation or help reaching an outside service. These requests need different conversations. Don't assume that mentioning an incident means agreeing to every next step your organisation could take.

The lead should explain the available options and their limits. Check what contact method is safe, whether a message can identify the event and whether the person wants a support person involved. A shared email account or phone can make an otherwise routine followup unwelcome. Record the contact preference where the response team can find it.

If the person asks you to do nothing further, consider that request against immediate risk, applicable duties and your agreed procedure. Explain any action you must take and why, where it is safe and possible to do so. Don't make a broad promise that a request will always prevent further action.

Offer appropriate specialist support information selected for the event's location. Make clear which services your staff can provide and which require outside expertise. An organiser can help someone find support without presenting an event volunteer as a counsellor, medical professional or independent advocate. Check those referral arrangements before putting them in the briefing.

Accept informal, witness and anonymous reports

Allow someone to describe a concern without filling in a formal statement at the first conversation. Ask enough to understand the immediate situation and agree the next step. The lead can explain whether a further account would help and how the person can provide it later.

Witnesses should have a route to report what they saw or heard. Record their observations separately from what another person told them. A witness may know the location and timing without knowing what support the affected person wants. Contact that person sensitively where appropriate, rather than turning a witness's request into permission to disclose their identity widely.

If you offer anonymous reporting, explain the limitations. Without a way to ask questions, it may be difficult to investigate, confirm details or provide an outcome. You can still assess the information for immediate risk and possible recurring concerns. Avoid promising that every anonymous report will produce an individual sanction.

Check whether the channel is genuinely anonymous. A form may collect account details, technical logs or identifying attachments even when it doesn't ask for a name. Have the responsible privacy specialist review the setup and your description of it. If you can only restrict someone's identity within the response team, explain that accurately instead.

Keep the report focused and restrict access

Create a record that the authorised response team can understand without collecting everything about the person's life. Separate the account received, direct observations, actions taken and decisions still outstanding. If wording is uncertain, record that uncertainty. Don't rewrite an allegation as an established finding.

Useful information may include the report time, incident location, relevant account, immediate support requested, agreed contact method and the person responsible for the next action. Ask for further detail only when it serves the response. A ticket order number or identity document shouldn't become a default requirement just because other customer service processes ask for one.

In the UK, the ICO explains that criminal offence data can include unproven allegations, and information about victims and witnesses also needs particular care. Some reports may contain other specially protected information. Have a qualified adviser check your lawful basis, access rules, sharing and retention arrangements for your jurisdiction. A reporting form's consent box doesn't settle every requirement.

Keep reports out of shared production folders, marketing records and casual staff chats. Limit access to named roles, secure any paper notes and agree how authorised handovers happen. Set a retention and review policy before collecting reports, including how relevant legal preservation requirements change routine deletion.

Handle evidence without turning staff into investigators

A person may offer a screenshot, message or the name of a witness. Explain the approved way to submit it and who can access it. Don't ask them to post it in an event group or send it to a staff member's personal social account.

If venue footage may be relevant, the lead should contact the authorised venue representative about appropriate preservation. Staff shouldn't casually browse recordings or distribute clips around the organising team. Agree the request process with the venue before the event, including who decides what can lawfully be retained or shared.

Keep the original information and record where it came from. Distinguish a screenshot somebody supplied from a message staff directly observed. Don't edit material to make it appear more conclusive, and don't promise that particular evidence will prove what happened. Relevant specialists can advise when police or another formal process becomes involved.

Give the person space to continue their account later without requiring repeated retelling to every manager. A controlled handover can pass the information already supplied to the appropriate person. Check whether further questions are necessary and who is qualified to ask them. The objective is an accurate, fair response with as little avoidable intrusion as possible.

Use a fair process when deciding consequences

Your conduct policy should describe who reviews a report, how conflicts are managed and what decisions the event can take. Apply the procedure consistently across ticket holders and people with commercial influence. Being a major sponsor or a familiar performer shouldn't determine whether someone receives a fair review.

Where a report concerns workers, the employer's obligations and employment procedures need separate attention. In Great Britain, Acas guidance on handling sexual harassment complaints calls for sensitive handling and a fair process led by an impartial, trained person. It also explains that some cases involve police and require care around the criminal process. Don't treat a general event policy as a substitute for the applicable workplace procedure.

For event decisions, document the information considered, the applicable rule and the reason for the action. Explain any review or appeal route your procedure provides. Check contracts and local requirements before promising refunds, exclusions or future bans as automatic responses to every allegation.

Support for the person reporting can continue while the facts are reviewed. You can listen respectfully, arrange practical assistance and explain the next step without announcing a final finding. Keep public communications limited to authorised, necessary information. The event's social media account should never become an improvised channel for arguing a complaint.

Rehearse a report across the whole team

Before opening, walk through a hypothetical report with the venue, reporting lead, deputy, ticketing supervisor and relevant specialists. Use an ordinary moment in your programme. The lead is on a break, the foyer is busy and a volunteer receives a concern about someone wearing a sponsor badge.

Ask the volunteer to show how they contact the deputy. Check where the conversation can move, who covers the desk and who decides whether immediate safety action is needed. Then change one condition. The attendee cannot use stairs, the phone has no signal or the deputy knows the person named in the report.

Follow the example through to the written record and next contact. Who receives the information? Who can read it? What does the attendee hear before leaving? If a report reaches the wrong inbox, how does the recipient transfer it securely? These practical questions reveal gaps that a policy review alone can miss.

Repeat the exercise for a report after the event. The temporary crew may have finished their contracts, but your business still needs an owner for followup. Confirm the address remains monitored and the responsible person can access the relevant records. Fix missing coverage before telling attendees the process is ready.

Follow up without making people chase you

Agree the next contact before ending the conversation whenever possible. Explain who will get in touch, by which method and what that update can reasonably cover. If the review is still underway, say so. Don't disappear because you have no final outcome to share.

Keep promises within the team's control. A report may need specialist advice, additional accounts or coordination with another organisation. Set a realistic update arrangement rather than inventing a universal completion deadline. If that arrangement changes, tell the person through their agreed contact method and explain what happens next.

When closing the report, communicate what you can properly share about the outcome and relevant continuing arrangements. Respect the privacy and procedural rights of everyone involved. Make clear where the person can raise a further concern, including unwanted contact or treatment after reporting. Don't require them to agree that the event handled everything well before you close your internal actions.

Review the operation separately using information people genuinely need. Look at whether the published channel worked, staff reached the right lead and promised updates happened. A low report count alone doesn't establish that the event was safe or that people trusted the process. Investigate gaps in access and response before treating a quiet inbox as success.

Work through a report during a paid conference

Consider a hypothetical conference reception. An attendee tells the help desk that an exhibitor representative keeps approaching them after they've asked to be left alone. They want to stay for the programme, but they're worried the representative will follow them into the next session. They don't want to explain this in front of colleagues.

The desk volunteer contacts the duty reporting lead using the agreed private channel. Another staff member covers the desk while the attendee moves to an accessible quiet space, if that's what they want. The volunteer passes on the request already made, so the lead doesn't begin by demanding the same story again.

The lead checks immediate safety needs, explains information sharing and asks what assistance the attendee wants. Suppose the attendee wants to attend the next session with a friend and avoid further contact. The lead discusses workable options with them, then consults the authorised venue or security contact about any necessary protective arrangements. The exhibitor sales manager doesn't receive the attendee's account merely because the complaint concerns a paying exhibitor.

If the situation requires a conduct review, the responsible person follows the published procedure and manages any commercial conflict. Staff record the account as an allegation, the assistance requested, the actions authorised and the next agreed contact. A temporary safety arrangement has its own stated reason and review point. It doesn't become an undocumented final judgment because the programme is busy.

Before the attendee returns to the session, the lead explains how to reach them if the contact continues. They agree whether and how to follow up afterwards. The next shift receives the limited information needed to maintain any ongoing arrangement, through the restricted handover. The general event briefing doesn't include the attendee's name or a retelling of the complaint.

Change the facts and the response may change. Immediate danger needs the emergency route. A report about an employee may require the employer's procedure. A request for medical support goes to appropriate professionals. The useful preparation is agreeing who makes each decision, so the first staff member can get help without pretending to resolve the entire complaint.

Check the arrangement before you publish it

Bring the final public instructions and internal procedure to the people expected to deliver them. Ask the lead and deputy to confirm coverage, the venue to confirm support locations and the appropriate specialists to check the legal and safeguarding questions that apply to your event.

Test the published contact links yourself. Submit a harmless test message, check who receives it and remove the test according to your agreed process. Walk to the help point using the public directions. Confirm a person can ask for the lead without announcing a sensitive concern to everyone waiting nearby.

Then ask the staff member at the busiest attendee contact point what they would do if someone needed help. They should be able to explain the first step, reach the correct person and use the backup route. If they cannot, revise the briefing and practise again before doors open.