Attendance events, marking, and reporting

Prepare event types, mark attendance consistently, and turn records into useful reports without creating calendar clutter.

9 min readUpdated 8 September 2026

In short

Attendance connects attendees to dated events. Set event types first, use consistent marking rules, and review exceptions before relying on reports.

On this page

Prepare the Attendance module

Attendance requires the Attendees module and works best after a small amount of shared configuration.

Step by step

  1. 1Confirm Attendees and Attendance are enabled.
  2. 2Clean the attendee roster.
  3. 3Create a short list of meaningful event types.
  4. 4Decide who can create events and who only marks them.
  5. 5Agree how cancellations and unknown attendance are handled.

Create useful events

Names, dates, and event types should make an event understandable months later.

  • Use a specific event title and correct date.
  • Choose the event type that matches reporting intent.
  • Avoid duplicate events for the same session.
  • Correct a mistaken event rather than recreating it after marking begins.

Mark attendance consistently

A shared marking routine produces more trustworthy reporting than perfect-looking but inconsistent data.

Step by step

  1. 1Open the event at the start or end of the session.
  2. 2Mark every expected attendee using the agreed status.
  3. 3Resolve unknown entries while the event is still recent.
  4. 4Have one responsible person review the completed event.
  5. 5Correct mistakes promptly instead of compensating in later reports.

Read reports responsibly

Reports reflect the quality and scope of the source events. Interpret them with the same event-type and roster rules used during marking.

  • Filter by a meaningful date range.
  • Compare like event types with like.
  • Investigate missing or duplicate events before drawing conclusions.
  • Treat attendance as operational evidence, not a complete measure of participation or wellbeing.

Put this into practice

Use this browser-only checklist during your next review.

0/5

Common questions

Why can’t Attendance be enabled alone?

Attendance needs attendee records to connect people to events, so Attendees is required.

Who should mark attendance?

Use Editors scoped to Attendance for operational marking, and Admins only when they also need settings or access management.

Continue learning

Attendee records and responsible data handlingBuild useful attendee records, avoid unnecessary sensitive data, and prepare clean attendance and inventory workflows.Roles, module scope, and least-privilege accessAssign responsibility without creating dozens of roles, and keep each person inside the modules they need.Troubleshooting Scoutzy access and workflowsDiagnose missing modules, blocked invitations, Team attachment problems, and confusing operational records.