Rally Tally for Journalists

When you cover a public event, getting the crowd size right matters. Too high and you are amplifying organisers' claims uncritically. Too low and you may be dismissing a significant gathering. Get it wrong and you undermine your credibility.

The problem is that traditional crowd counting makes this hard. Organisers report one figure, authorities another, and neither is transparent about how they reached it.

Rally Tally offers journalists a third signal: what participants themselves reported about their presence.

As a journalist covering a protest, rally, or public gathering, you typically hear:

1. Organiser estimates, which may be optimistic
2. Police or authority estimates, which may be conservative
3. Your own observation, which may be incomplete

Each source has incentives to bias the figure in their direction. And your own observation is limited by where you can physically be and for how long.

The result is often one of three unhappy scenarios:

• You pick the most credible-sounding figure and report it as fact, knowing full well it may be wrong
• You report a range ("organisers claim X, police estimate Y") and leave readers confused
• You invest significant time in your own observation and still end up with an estimate, not a count

Rally Tally breaks this impasse by providing a fourth signal: direct participant check-ins.

When an event is tracked in Rally Tally:

• You can see how many people actually checked in
• You can compare participant check-ins with other attendance evidence
• You can see the locations, showing whether the event stayed in one place or moved
• You can see how the check-in total compares to other reported figures

This does not guarantee accuracy, but it provides leverage for better reporting.

If organisers claimed 100,000 and authorities said 20,000, and check-ins show 15,000, you now have useful information:

• Either the organiser figure is significantly inflated
• Or the check-in tool did not reach most participants
• Or participants were not aware of the check-in option

Each possibility is reportable and more honest than simply picking one claim over another.

When crowd figures are contentious, your job is not to pick a winner. It is to help readers understand why the figures differ.

A more honest approach looks like:

Weak reporting: "Organisers said 50,000 attended the rally."

Better reporting: "Organisers claimed approximately 50,000 attended; police estimated 15,000; independent observation suggested the crowd peaked at around 30,000; and 8,000 participants checked in via Rally Tally, an anonymous attendance app."

The second version gives readers the information they need to form their own judgment, and it signals that you did diligent reporting rather than uncritically repeating one claim.

If your assignment is to cover a public event and attendance is disputed:

1. Check Rally Tally before you go. See if the event is registered and what check-in data is available.
2. Do your own observation. Walk the event, check different areas, note when you observe peak attendance.
3. Interview organisers about their estimate. Ask how they reached their figure, what method they used, what it includes and excludes.
4. Compare all signals. If you have observation, organiser claims, authority claims, and check-in data, you can see where they align and where they diverge.
5. Report the variance as the story. "Estimates of attendance ranged from X to Y, with most independent observers near Z" is more valuable reporting than picking one figure.

Rally Tally data is most useful in situations where:

• Attendance is politically sensitive or disputed
• Organisers and authorities are known to have incentives to exaggerate or downplay numbers
• Multiple locations or time periods make a single estimate meaningless
• You want to track whether momentum is building across successive events

In these cases, check-in data from multiple events or time periods can reveal trends that any single crowd estimate cannot.

One advantage of Rally Tally for journalists is that it creates a documented record that future journalists can reference.

Instead of relying only on historical news archives (which may have picked poor estimates), future coverage can reference:

• What participants themselves reported
• When they reported it
• Where they were located

This is particularly valuable for tracking sustained movements, series of events, or comparing how different protests grew over time.

One concern journalists might have about using check-in data: Is this data collection ethical?

Rally Tally is designed specifically to be privacy-first:

• Check-ins are anonymous (no personal identification)
• Data is stored securely
• Participants choose to check in

From a journalism ethics standpoint, using published, anonymized check-in data is no different from using published polling data or survey results. You are reporting on available evidence, not creating it.

Rally Tally also enables a new interview angle for journalists.

Instead of asking organisers or police for attendance estimates, you can:

• Interview participants about why they came
• Ask whether they checked in through Rally Tally
• Ask what barriers prevented them from checking in
• Compare personal testimony against aggregate check-in data

This gives you richer, more human-centered reporting about what actually happened at an event.

By consistently reporting crowd figures with their methods attached, you teach readers to be skeptical of claims made without evidence.

If a press release says "15,000 attended" with no method, you can note that. If another source provides clear methodology and check-in data, you can highlight that too.

Over time, this signals to readers that crowd size claims are only as good as their underlying evidence.

If you are investigating whether particular groups or causes are growing, check-in data across multiple events is more reliable than individual crowd estimates.

Rally Tally records allow you to:

• Compare attendance at successive events by the same organiser
• See whether a cause is gaining or losing momentum over time
• Identify geographic patterns (where support is strongest)
• Compare participation across different movements

This kind of structured data is ideal for investigative reporting about social movements.

If you want to use Rally Tally data in your coverage:

1. Visit rally-tally.com and browse upcoming events in your coverage area.
2. Look for events relevant to your beat. Is there a scheduled protest, rally, or gathering?
3. Check back after the event to see check-in data and compare it to reported figures.
4. Interview organisers about check-in reach. Did they publicize the tool? How many participants did they expect to be aware of it?
5. Use check-in data as one signal among several, not as the final word on attendance.

Rally Tally is most useful not as a replacement for your reporting, but as one additional data source that helps you report more accurately and honestly.

For journalists, the goal is not to pick between conflicting claims. It is to give readers enough information to understand what actually happened.

When crowd attendance is disputed, Rally Tally provides check-in data that can help fill that gap. Combined with your observation and careful interviewing, it makes your reporting stronger and more credible.

When newsroom deadlines are tight, it helps to use a repeatable verification model. A simple four-signal framework works well:

• organiser estimate
• authority estimate
• reporter observation
• participant check-in signal

No single signal should dominate by default. The reporting value comes from comparing all four and explaining discrepancies.

Example structure:

"Organisers estimated 40,000 attendees, while city officials put attendance at 12,000. On-site reporting observed high-density sections near the main square between 2pm and 3pm, and Rally Tally recorded 9,800 anonymous check-ins during the event window."

That phrasing is transparent, method-aware, and easy for readers to interpret.

Crowd stories often present exact numbers where only estimates exist. False precision makes coverage look authoritative while hiding uncertainty.

Better practice:

• report ranges when methodology is uncertain
• identify what each number includes or excludes
• separate peak crowd from total participation
• avoid writing a single number as settled fact when major sources conflict

When check-ins are available, report them as check-ins, not as automatic total attendance.

Before assignment

• check whether the event exists on Rally Tally
• review prior attendance patterns for similar events
• prepare source questions about methodology

During live coverage

• record time-stamped observations from at least two locations
• note route changes or split locations
• confirm whether organisers actively promoted check-ins

Before filing

• compare organiser, authority, observational, and check-in figures
• flag any large divergence and explain why it may exist
• include method notes in one concise line

For post-publication updates

• revise attendance context if better data appears later
• document updates clearly for reader trust

When interviewing organisers:

• What method produced your estimate?
• What time window does your figure cover?
• Does your total include supporters not physically present?
• How was the check-in process communicated to participants?

When interviewing authorities:

• What counting model was used?
• Which locations were included and excluded?
• Was your figure peak presence or total attendance?

When interviewing participants:

• Did you check in?
• If not, what prevented you?
• Did you move between locations during the event?

For distributed actions, avoid collapsing all attendance into one opaque figure. Instead:

• report city-by-city or location-by-location counts where available
• provide a combined total only after explaining what is included
• make clear whether participants might have moved between locations

Should we treat check-ins as definitive turnout?

No. Check-ins are a direct participation signal, not a guaranteed full census. They are most useful when reported alongside other methods.

Can we cite check-ins if we do not know adoption rate?

Yes, if language is precise. Report what was observed (for example, "X anonymous check-ins were recorded") and avoid converting that to total attendance without supporting evidence.

What if organiser and check-in numbers differ dramatically?

That discrepancy is newsworthy. Report the gap and explain possible causes: awareness levels, connectivity limitations, participation behavior, or estimation bias.

Is it ethical to use anonymous attendance data?

When data is anonymized and publicly reported, citing it is comparable to citing survey data: useful evidence with known limits.

How should headlines handle disputed numbers?

Prefer phrasing that signals uncertainty and context rather than claiming one definitive figure from a contested event.

• Rally Tally home: https://www.rally-tally.com
• Rally Tally guides: https://www.rally-tally.com/guides
• Rally Tally downloads: https://www.rally-tally.com/download
• Universal Declaration of Human Rights (Article 20, peaceful assembly): https://www.un.org/en/about-us/universal-declaration-of-human-rights
• Amnesty International background on protest and expression rights: https://www.amnesty.org/en/what-we-do/freedom-of-expression/
• Background on crowd estimation practice: https://en.wikipedia.org/wiki/Herbert_Jacobs

• Methodology overview: Crowd Counter
• Protest-specific attendance context: Protest Attendance Tracker
• Mapping and route documentation: Protest Mapping Guide
• Event browsing for assignments: All Events
• App download page: Download

For your next public event assignment, explore Rally Tally's resources for journalists and media and consider how check-in data could improve your coverage.

Better reporting on public gatherings starts with better data. Rally Tally helps provide it.