Attendance Marking and Verification - Article
Summary
Attendance records whether a participant attended a live session. Use it when delivery teams need reliable participation information for follow-up, reporting, or a configured learning requirement. Attendance can be recorded manually or through supported conferencing automation, but the result must still be interpreted in the context of the event and the organization's evidence policy.
Use this article to:
- Enable attendance and understand when marking is available.
- Record attendance individually or in bulk.
- Use configured Microsoft Teams automation without generalizing its behavior to every provider.
- Handle cancellations, rescheduling, corrections, and optional operational handoff.
Understand what attendance represents
| Record or action | What it establishes | What it does not establish by itself |
|---|---|---|
| Activity registration | The person has a signup in the Training Activity. | That they attended a specific event. |
| Calendar invitation or RSVP | The meeting is represented in an external calendar or the recipient responded there. | That the Eurekos participation record changed or the person attended. |
| Attended | Attendance has been recorded manually or by a configured integration. | That every other module, assessment, feedback, or certification requirement is complete. |
| Not attended | Absence has been recorded. | The reason for absence or the appropriate remedial action. |
| Not marked | No final attendance result has been recorded in that state. | Confirmed absence. |
| Recording engagement | The person accessed or watched recorded material according to the relevant evidence. | Live participation, unless a specific approved learning design treats it as an alternative. |
If attendance contributes to a certificate or activity completion, configure the relevant formal learning criteria described in Certificates and test the complete result. A supporting meeting created through Calendar Events for Activities and Communities does not become an Event module merely because attendance is recorded.
Enable attendance and identify the responsible person
Enable Enable attendance marking when creating or editing the relevant event. For an Event module, use the corresponding module configuration in the Training Activity.
Authorized administrators and relevant responsible instructors can mark attendance for activity-related events within their permissions and scope. Community events also depend on Community ownership, event ownership, and the configured roles allowed to manage Community events. Ordinary Community membership alone should not be presented as authority to mark everyone's attendance.
If Calendar is disabled on the platform, authorized staff can use the activity’s Statistics attendance view where available. A missing Calendar menu does not by itself mean attendance cannot be recorded.
Assign an operational owner before the session. This should be the person who can verify attendance or review the integration evidence, not simply whoever happened to create the calendar invitation.
When marking becomes available
| Platform configuration | When the action is available | Appropriate interpretation |
|---|---|---|
| After event ends — the default | After the scheduled end. | Supports recording attendance once the session has concluded. |
| After event starts | Once the session is in progress. | Allows an approved live check-in process. |
| Always, including before the event | Before, during, or after the session. | A special operational choice; early entry must not be mistaken for proof that the person later attended. |
Eurekos Support can help confirm or configure this behavior. Do not assume the action is faulty because it is unavailable before the event ends on a normally configured platform.
Mark attendance manually
- Open the event's details and select Mark attendance when available. Attendance can also be reached through the applicable statistics/reporting route.
- Confirm that this is the correct event and schedule.
- Review the attendee population and distinguish cancellations from unmarked participants.
- Set Attended or Not attended for individual participants, or use the available bulk action for a verified group.
- Complete the interface's update action and verify the saved statuses.
- Follow the agreed process for absentees, disputed records, and any related learning requirements.
Use bulk marking only after confirming that every selected person has the same result. Do not mark an entire list as attended merely because it is easier than resolving a few uncertain cases.
Keep Not marked as an unresolved state until the evidence is sufficient. Attendance correction should follow the organization's evidence policy; the ability to edit a value is not permission to invent attendance.
Microsoft Teams automatic attendance
When the Microsoft integration's Enable automatic attendance marking setting is enabled, supported Microsoft Teams sessions can synchronize attendance after the meeting. This applies to Event modules, direct Calendar events, and Community events using the configured Teams integration.
The event's Required attendance time determines the qualifying attendance duration. The platform-wide default is 70%, managed by Eurekos rather than through an ordinary administrator setting. An authorized Event editor can set the requirement for an individual Event to a whole percentage from 1 to 100 without changing that platform-wide default. Contact Eurekos Support only if the platform-wide default needs to change.
| Behavior | Operational meaning |
|---|---|
| A participant meets the required attendance percentage | The integration can mark the participant present automatically. A universal manual-approval step should not be assumed. |
| The percentage is left blank | The field is required when automatic attendance is enabled. Enter a whole percentage from 1 to 100; leaving it blank produces a validation error. |
| Attendance is not immediately visible after the meeting | Teams must generate its attendance report. Updates typically take 10–15 minutes and can take longer. |
| A person joins early or remains after the scheduled end | Only time within the scheduled event interval counts toward the requirement. |
| Breakout rooms are used | The calculation does not count time in breakout rooms. Review whether automatic marking is suitable for that session design. |
| The participant is already marked present | Later synchronization does not change that present status. A missing later record is not automatically evidence of absence. |
For a 60-minute scheduled meeting, a 70% threshold requires 42 minutes of qualifying attendance within the scheduled time. Time in breakout rooms does not count toward the synchronized attendance calculation. If the session relies heavily on breakout work, define how the instructor will verify participation before using an automated threshold as certification evidence.
Automatic attendance and automatic Teams co-host assignment are separate capabilities. The activity-responsibility mechanism for co-hosts should not be assumed to apply to direct Calendar or Community events. See Microsoft.
Other conferencing services
Providers differ in what they report, when they report it, how identities are matched, and whether live or recording activity affects the result. Use the dedicated integration guidance and the configured platform behavior for the selected service.
A generic video-conference URL is a joining link, not an attendance data connection. Do not promise automatic attendance merely because the meeting is online.
Avoid the opposite blanket claim as well: not every integration supplies only a suggestion that an instructor must approve. Confirm the actual workflow for the service and configuration in use.
Cancellations and changing attendee lists
For direct Calendar and Community events, participants may be able to cancel participation when the event allows it. The attendee view can show cancellation information separately from attendance.
Activity signup cancellations, expirations, and reactivations can also affect the attendance view, with different handling depending on whether the event is future, in progress, or past. Do not treat all signup-state changes as the same event-attendance operation.
| Change | What to review |
|---|---|
| Activity added to or removed from a direct Calendar event | The attendee population can change with the connected activity population. |
| Community membership or selected event participants changed | Review the event's audience, especially future events intended for all members. |
| A cancelled or expired signup reactivated | Attendance can return to Not marked; verify the correct result rather than assuming the earlier status is retained. |
| The entire Training Activity cancelled | Its events can disappear from Calendar. Use the appropriate record and reporting context when investigating history. |
Keep event participation and Training Activity enrollment separate in both instructions and support investigations. Review the event’s cancellation and reactivation settings alongside the activity signup.
Rescheduling can reset attendance
When an event's start date is changed to a future date, recorded attendance can reset to Not marked. This applies to Event modules, direct Calendar events, and Community events, with special handling of cancellation records.
Before moving an already attended event, decide whether you are correcting the same session or scheduling another one. A new delivery normally needs its own event record. Reusing the old event can make its existing attendance evidence misleading or remove the statuses you expected to retain.
After any correction, recheck the attendee list, saved statuses, reporting, and relevant completion or certificate consequences.
Instructor reminders
After an attendance-enabled event ends, a responsible instructor can receive a My overview notification leading to attendance marking. The dashboard shows a limited set of these notifications and they can disappear when all attendance is marked, when dismissed, or through age-related cleanup.
Use the dashboard as a prompt, not as the complete attendance audit. If a notification is no longer visible, find the event or the relevant statistics/reporting view and inspect the actual attendance record.
Optional ready-for-invoicing handoff
Some platforms enable an Invoice / Ready for invoicing action as an operational handoff after attendance review. This is not a universal feature and should not be presented as automatically creating or sending a financial invoice.
When enabled, marking an event ready for invoicing can make attendance editing unavailable until an appropriately authorized administrator reopens that state. Configuration can also determine whether newly enrolled participants are added to the attendee list after the handoff.
Use this only with a defined Finance or operations process. Confirm the roster, attendance evidence, downstream handoff, and correction owner before marking the event ready. Detailed financial processing remains outside the act of recording attendance.
Practical attendance patterns
| Scenario and requirement | Recommended approach | Why and what to check |
|---|---|---|
| Classroom workshop with a facilitator-verified roster | Enable manual attendance and record the verified result after the session. | The record reflects actual presence rather than registration. Resolve uncertain cases before bulk completion. |
| Teams webinar with an approved minimum duration | Enable the integration, set an explicit percentage, and review the synchronized results after processing. | Reduces manual work while keeping the threshold understandable. Check schedule and identity assumptions. |
| Interactive workshop using breakout rooms | Establish an instructor verification process in addition to any available meeting data. | The Teams duration calculation does not include breakout-room time. |
| Attendance-based external billing process | Use the optional ready-for-invoicing handoff only where configured and approved. | Attendance and financial processing remain distinct, with an explicit handover. |
Verify the evidence
| Verify | Expected outcome |
|---|---|
| Event identity and schedule | The record represents the session that actually took place. |
| Attendee population | Intended participants, cancellations, and later membership changes are understood. |
| Marking method | Manual evidence or the configured integration supports the recorded result. |
| Learning consequences | Any completion or certification requirement uses the intended attendance evidence. |
| Corrections | There is an authorized route to investigate and correct errors without rewriting unrelated historical sessions. |
Troubleshooting
| Problem | What to check |
|---|---|
| “Mark attendance” is missing | Confirm attendance is enabled, the configured marking time has been reached, and the user has appropriate event responsibility or permission. Also check any ready-for-invoicing state. |
| An expected person is absent from the list | Check the exact activity or Community audience, signup/membership state, event timing, and any post-invoicing roster configuration. |
| Teams attendance has not appeared | Allow for report generation, then verify the integration toggle, event's Teams configuration, participant identity, and meeting schedule. |
| A brief Teams visit counted as attendance | Check the Event’s Required attendance time and scheduled period, then review the synchronized report and any manual attendance entry. The default requirement is 70%; a blank required field is rejected. |
| Breakout participants were marked absent | The Teams percentage does not count breakout-room time. Review instructor evidence and the approved correction process. |
| Attendance returned to “Not marked” | Check whether the start date was moved into the future or a signup was reactivated. |
| Attendance is correct but the certificate is missing | Review the complete certificate and completion criteria, other modules, feedback requirements, and the distinction between a supporting event and a formal Event module. |
| The dashboard reminder disappeared | Inspect the actual event record; notification dismissal or age does not prove that attendance was completed. |
| Attendance cannot be edited after operational handoff | Check Ready for invoicing and ask an appropriately authorized administrator to review whether reopening is permitted. |
FAQ
-
Is attendance marking available only after an event ends?
That is the default. The platform can instead allow marking after the event starts or at any time. Ask the platform administrator or Eurekos Support to confirm the configured behavior.
-
Is Not marked the same as Not attended?
No. Not marked is unresolved attendance. Not attended is a recorded absence. Do not treat missing evidence as a confirmed absence without review.
-
Does every integration require an instructor to approve attendance manually?
No. Configured Microsoft Teams attendance can mark results automatically using the event's required attendance percentage. Other services have their own behavior and should be checked separately.
-
Can the Teams Required attendance time be left blank?
No. When automatic attendance is enabled, Required attendance time is required. Enter a whole percentage from 1 to 100; a blank value produces a validation error. The platform-wide default is 70%. An authorized Event editor can change the requirement for that Event, while a change to the platform-wide default requires Eurekos Support.
-
Why is Teams attendance not available immediately?
Microsoft must generate the meeting attendance report. Synchronization typically takes 10–15 minutes after the meeting and can take longer.
-
Does Teams breakout-room time count toward the required attendance percentage?
The calculation excludes breakout-room time. Use an appropriate instructor-verification process when breakout work is important to the session.
-
Can rescheduling reset attendance?
Yes. Moving an event's start date into the future can reset attendance to Not marked. Do not reuse a historical session as a new delivery without reviewing its evidence.
-
Does Ready for invoicing send an invoice?
Do not assume so. Where enabled, this is an operational handoff state that can restrict attendance editing and support an external financial process. Confirm the platform's approved invoicing workflow separately.