Practical guide

Reconcile attendance counts without hiding unresolved cases

Last materially reviewed 2026-09-28

Quick answerUse one unit, one scope and mutually exclusive categories; a balanced sum does not prove the records are correct.
What to know

Freeze the scope of the question

Choose one event occurrence and define the unit you are reconciling. For a ticket-based exercise, do not mix an order count into the same sum. Identify the reporting time and whether all intended devices have shared their data. A changing scope can make yesterday’s correct arithmetic look wrong today. Save the original scope and add an explanation when it changes rather than overwriting the basis of the calculation.

What to know

Keep uncertainty as a category

Separate tickets with an observed admission, tickets not recorded as admitted and cases that remain unresolved. Use one current category per item so the counts do not overlap. An unresolved item is not automatically a no-show or an error by a volunteer. The organization may need to inspect its private operational records to resolve it. Our worksheet accepts anonymous totals and cannot perform that investigation.

What to know

Use the local worksheet carefully

The tool compares the entered scope with the sum of the entered categories. Blank means unknown, not zero. Negative, fractional and unreasonable counts are rejected. A zero difference means the arithmetic balances under your inputs; it does not verify attendee identity, ticket validity or data completeness. A nonzero difference is a prompt to check the inputs and categories, not a diagnosis of fraud or lost admissions.

What to know

A fictional balanced result

A scope of 100 tickets is divided into 82 with admission evidence, 15 without a recorded admission and three unresolved. The sum balances, while three cases still need attention. That is more honest than moving them into another category merely to produce an all-clear report. Save the meaning of the categories with the result, then use the appropriate private records to investigate outstanding cases. No ticket codes belong in this public tool.

Continue when useful

Next: Check-in export

A downloaded file needs definitions, a date and access controls before it becomes a useful handover record.

Open Check-in export →

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. Ticket Tailor: check-in reporting and its limitations — Merchant documentation · help.tickettailor.com · Merchant-controlled · checked 2026-09-28
  2. Ticket Tailor: printing a doorlist — Merchant documentation · help.tickettailor.com · Merchant-controlled · checked 2026-09-28
WORKSHEET 02 / RECORDS

Keep uncertainty in the count.

Use one unit throughout: tickets or people, not orders mixed with tickets. Categories must not overlap. Arithmetic cannot verify attendance.

Read the evidence boundaries →
Anonymous totals only. Inputs are not saved or sent.