Fitness class attendance data dictionary

Fitness class attendance data dictionary

The CDC’s 150-minute adult activity guidance describes a population-level recommendation. It is not a definition of attendance, a minimum for a member, or a performance target for a studio. A data dictionary should instead describe the local event: a booking, check-in, late arrival, cancellation, or no-show. Clear definitions keep a report from answering a different question than the one an owner intended.

Name every state

Use separate fields for booking status, check-in status, and class status. A cancelled booking is not a no-show, and a studio-cancelled class is not a member absence. Include event time, source system, location, class identifier, and correction owner. If attendance is entered manually, retain the entry time and editor. “Unknown” is a valid state when the system cannot establish what happened.

Evidence table

Keep the guideline citation beside the public statistic and keep member data under its own access rules. Neither should be used to imply that a person met a health recommendation.

Reconcile sources

Compare the booking platform, door system, and instructor roster using a stable class and member identifier. Choose a source of truth for each field. Record the time zone and late-entry rule. Reconcile a sample after every integration change. When two systems disagree, flag the event for review rather than selecting the value that makes a report look better.

Treat exceptions as information

Accessibility needs, equipment failures, guest passes, and staff test entries can affect counts. Define exception codes and require a brief operational note. Do not put unnecessary medical detail into the attendance record. An assistant can check for missing codes and route questions; the manager decides whether a record is corrected and the qualified person handles health or safety judgment.

Use useful measures

Show bookings, check-ins, cancellations, no-shows, and eligible events separately. A rate needs a named denominator and date range. Compare formats only when rules, capacity, and collection methods are compatible. Process metrics such as reconciliation time and unresolved exceptions are safer than claims that attendance caused a result. Mark policy and system changes on the timeline.

Secure the dictionary

Publish the field definitions where staff can find them. Limit editing rights, log changes, and review stale fields. FTC materials support protection of personal information; HHS privacy resources are relevant to sensitive records. The studio should determine its own retention and access requirements. Delete or archive according to policy, not because a dashboard needs fewer rows.

Questions to review

Is a check-in proof of a workout?

No. It is evidence of an operational event under the studio’s definition. It does not establish what a person did or how they benefited.

Can a no-show be inferred from a blank?

Only if the business has verified the source and defined the blank state. Otherwise record unknown and investigate.

Who changes a field definition?

The owner of the reporting process should approve changes, document the effective date, and preserve the prior version for historical interpretation.

Source notes

CDC, HHS, WHO, and Healthy People links support public activity context only. FTC and HHS sources inform privacy controls. BLS, NIDDK, and NHLBI provide related background. None supports a claim about this studio’s attendance, member health, or business results.

1. CDC adults
2. HHS
3. WHO
4. FTC
5. HHS privacy
6. BLS
7. CDC overview
8. Healthy People
9. NIDDK
10. NHLBI

Discuss the workflow

Book a free call to discuss attendance definitions, source reconciliation, and exception queues. The call is for workflow fit and delegation boundaries, not health advice.

Maintain the definitions

Put the dictionary beside the report rather than in a private note. When a new check-in device or booking provider is added, test the identifiers, time zones, late-arrival rules, and deletion behavior before relying on the combined data. Ask an instructor and coordinator to read the same sample and explain each status. Differences in interpretation are a training issue, not a reason to average the values. Keep a version number, an owner, and an effective date. If a historical definition changes, annotate the report and preserve the earlier logic for comparison. The maintenance routine can be monthly for a stable studio and more frequent during system changes. Its purpose is not to create more administration; it is to ensure that a count remains understandable when a member, manager, or auditor asks where it came from.