Home > Attendance

Recording Headcount Without Double-Counting Visitors

Learn how headcount recording got faster and stopped tallying visitors more than once.

What changed

Recording headcount is now faster, and it no longer double-counts visitors, a previous issue where a visitor's headcount could be tallied more than once has been fixed.

Why double-counting was a problem

A visitor being counted twice inflated attendance numbers in a way that wasn't obvious just from looking at the total, it only showed up when you compared headcount figures against other attendance data and the numbers didn't line up.

What to expect now

Headcount totals should now match what you'd expect from a straightforward count of who was actually present, and the recording process itself moves faster, so it's less of a bottleneck when you're trying to get a count in during or right after a busy service.

Best practice

If you have historical headcount figures from before this fix, treat them as slightly inflated where visitors were involved, and use recent counts as the more reliable baseline going forward.