Organise a Community Event (50+ Attendees)

Proof required

Submit: (1) a half-page event brief covering the event name, target audience, date, venue or platform, and the reason someone would choose to attend, (2) venue confirmation (booking confirmation, email, or screenshot showing the date is secured), and (3) a list of co-organisers with each person's name and their specific confirmed responsibility.

What gets checked

• Venue is confirmed with a date — 'we are thinking about using the community hall' does not pass; a booking confirmation email, a signed agreement, or a written confirmation from the venue contact is required
• Co-organiser list names at least one person with a specific task — 'my friend is helping' does not pass; 'Priya is responsible for catering coordination' does; the task must be specific enough that if Priya dropped out, you would know exactly what needs to be covered
• Event brief explains why someone would choose to attend — 'it will be a nice community event' does not pass; the brief must articulate the specific value or experience the attendee gets that they could not get elsewhere; this is the pull factor that makes 50+ voluntary attendance achievable

Common mistakes

• Booking a venue before defining who the event is for — a venue with a date but no clear audience or pull factor is a common first-organiser mistake; the event brief must be drafted before the venue is booked so the venue choice (capacity, location, accessibility) follows from the audience, not the other way around
• Listing co-organisers who have not actually agreed — a co-organiser list built from 'people who said they might help' is aspirational, not confirmed; each person on the list must have explicitly agreed to a specific task; follow up by email or message and keep the confirmation
• Planning an event where attendance is mandatory or strongly expected — a departmental all-hands, a school assembly, or a work meeting where people attend because they are required to does not meet the GOVERNANCE standard; 50+ voluntary attendees means 50+ people who showed up because they chose to

Resources

What a verifier looks for

• Check the venue confirmation is for a specific date — a venue enquiry email without a confirmed booking does not pass; the date must be agreed and the venue must be expecting the organiser
• Review the co-organiser list and verify each person has a specific named task — 'general help' does not pass; probe one co-organiser from the list: 'What is Priya responsible for?' If the answer is vague, the tasks have not actually been assigned
• The event brief must explain the pull factor — why would someone choose to attend? If the brief cannot answer this question clearly, the event is unlikely to reach 50 voluntary attendees; flag this before milestone 2, not after

You'll sign in first, then come straight back here.

Proof required

Submit: (1) a screenshot or export from your RSVP or ticketing system showing 50+ confirmed sign-ups (names or email addresses visible to confirm they are distinct individuals), and (2) a one-page logistics summary covering catering/refreshments, programme or run-of-show, volunteer briefings, and any contingency plans.

What gets checked

• RSVP list shows 50+ distinct individuals — a list with fewer than 50, or with duplicates, or with obvious placeholder names does not pass; the RSVP system screenshot must show actual sign-up data, not a summary count
• RSVP list excludes co-organisers — the co-organisers from milestone 1 are not attendees; if the list includes them, subtract them from the count; the 50+ must be people coming as audience, participants, or guests
• Logistics summary covers all four elements: catering/refreshments (or explicit note that none are provided), programme or run-of-show, volunteer briefings, contingency plans — a summary missing any of the four does not pass milestone 2

Common mistakes

• Relying on word-of-mouth RSVPs without a system — 'I told people to come and I think 50 will show up' is not verifiable; an RSVP system that captures names or emails is required; without it, milestone 3's attendance count has no baseline to compare against
• Counting co-organisers, speakers, performers, or event staff as attendees — the 50+ must be people coming to experience the event, not people producing it; if the event roster includes 10 speakers, 5 volunteers, and 3 organisers, those 18 do not count toward the 50
• Locking logistics too late — a logistics summary written after the event cannot be milestone 2 proof; the logistics must be confirmed before the event happens; if the submission date of the logistics summary is after the event date, the milestone order was reversed

Resources

What a verifier looks for

• Open the RSVP screenshot and count distinct entries — confirm the count is 50 or above; check for obvious duplicates (same name/email appearing twice) and subtract co-organisers, volunteers, and speakers from the count
• The logistics summary must be dated before the event — if the document was created after the event date, the milestone order was reversed; check the document creation date or ask when the summary was written
• Check that the run-of-show or programme is realistic — an event that plans 30-minute speeches from 10 speakers in a 2-hour slot has a logistics problem; flag implausible schedules before the event happens, not after

You'll sign in first, then come straight back here.

Proof required

Submit: (1) at least two photos showing the event in progress with attendees visible, (2) verified attendance count (sign-in sheet, ticket scan export, or counter screenshot showing 50+), and (3) a 200+ word post-event brief covering what was achieved, what deviated from plan, what went wrong, and what you would change.

What gets checked

• Photos show an active event with people present — a photo of an empty venue before attendees arrived, or a photo of the organising team without any event participants visible, does not confirm 50+ attendance; the photos must show people engaging with the event
• Attendance count reaches 50 and is verified by a method other than the organiser's self-report — sign-in sheet (photographed), ticket scan log from an app, or a head count confirmed by a named co-organiser; 'I counted and there were 50' without any supporting evidence does not pass
• Post-event brief includes something that went wrong — an event of this size always has at least one thing that did not go to plan; a brief that reports only success is almost certainly incomplete; probe for the specific moment when something went differently than planned

Common mistakes

• Reporting 50 attendees without a verification method — this is the most common failure mode for this outcome; the attendance count must have a source; if no sign-in sheet was used and no ticket scanning was set up, the count cannot be verified; plan the verification method before the event
• Submitting photos where no attendees are clearly visible — a photo of a decorated room, a photo of the organising team at the end of the night, or a wide-angle photo where all faces are too small to confirm people are present does not prove attendance; at least one photo must show a crowd or audience clearly
• Writing a post-event brief that describes only logistics rather than outcomes — 'we had food, a speaker, and a raffle' is a description of programme elements, not of what the event achieved; the brief must address what the attendees experienced or gained, not just what the organisers provided

Resources

What a verifier looks for

• Check at least two photos show people engaging with the event — not the venue pre-event, not the organising team alone; the photos must confirm the presence of an audience or participants; if all photos show the organising team, ask for at least one photo showing the crowd
• Verify the attendance count source — ask how the 50+ count was recorded; a sign-in sheet, ticket scan log, or platform report all pass; 'I counted heads' without any corroborating record does not pass; ask whether a co-organiser witnessed and can confirm the count
• GOVERNANCE final check — ask whether any co-organiser had to step in during the event to cover a gap the organiser could not handle; genuine events at 50+ scale always have at least one moment where someone else's decision or action was critical; if the organiser claims they handled everything personally with no delegation, probe further

You'll sign in first, then come straight back here.