Calendar Behavior and Attendance Logic
Follow

May 10, 2026 14:49

How Continu workshops connect to Zoom, Microsoft Teams, and Google Meet — how invites, attendance, and recordings flow between the platforms, and how to design live learning that doesn't quietly break around the edges.

Why Calendar Behavior Matters

A workshop only matters if learners actually show up.

Calendar integration is the bridge between learning intent and live attendance. It carries the invite to the learner's calendar. It captures who joined the session and who didn't. It surfaces the recording afterward. Without it, even a well-designed workshop produces no attendance data, no audit trail, and no way to verify that the certification, compliance, or training actually happened.

When calendar integration works, it disappears — invites land, attendance syncs, reports populate, and no one thinks about plumbing. When it breaks, it breaks subtly. The invite goes to the wrong time zone. Attendance shows up an hour late. The recording never appears. A no-show that shouldn't be a no-show shows up as one.

Most workshop debugging is calendar debugging. This guide is about understanding the layer underneath the workshop — what flows where, when, and what can fail along the way.

What Calendar Integration Actually Is

Calendar integration is the connection between Continu workshops and your conferencing platform — most commonly Zoom, Microsoft Teams, or Google Meet.

Three things flow across that connection:

Calendar invites flow out. When a workshop is created and a learner registers, an invite goes to the learner's calendar — including the meeting link, location, agenda, and reminders.
Attendance flows back. When the workshop happens, the conferencing platform records who joined, when they joined, and how long they stayed. That data syncs back to Continu and updates the workshop's state machine.
Recordings sometimes flow back. When a session is recorded and the integration is configured, the recording link or metadata syncs to Continu and becomes available for follow-up content or post-workshop access.

Each conferencing platform handles these three flows slightly differently. The differences matter when you're designing high-stakes programs.

The Calendar Lifecycle

Every workshop with a calendar integration moves through a six-step lifecycle:

Workshop created in Continu. Date, time, capacity, conferencing details configured.
Calendar invite generated. When a learner registers, the platform sends a calendar invite — either via the conferencing platform's native flow or as an ICS file.
Reminders fire on schedule. Pre-workshop reminders go out per the configured cadence (typically 7 days, 24 hours, 1 hour before).
The workshop happens. Learners join the conferencing platform. The platform records attendance.
Attendance syncs back to Continu. After the session ends, the conferencing platform's API delivers attendance data. Continu updates the workshop's state machine — Registered → Attended or No-Show.
Recording syncs (if enabled). A short time later, the recording becomes available, depending on the conferencing platform's processing time.

Each step has its own failure modes. Most workshop debugging starts by walking the lifecycle and finding the broken step.

Conferencing Platform Behavior

The three most common integrations have different operating profiles. Knowing the differences saves debugging time.

Zoom. The most mature integration in most Continu deployments. Attendance is captured via Zoom's API and typically syncs to Continu within minutes of the session ending. Recordings (when cloud recording is enabled in Zoom) sync similarly. Zoom's attendance data includes join time, leave time, and total minutes — useful for "minimum minutes attended" attendance rules.

Microsoft Teams. Similar core capabilities to Zoom, but more sensitive to organization-level policy settings. Some Teams attendance features may be disabled by your IT team for compliance or privacy reasons. Confirm with IT what attendance data is actually exposed to integrations before assuming Continu will see everything.

Google Meet. Unlike Zoom and Teams, Google Meet does not provide attendance tracking through its native integration. To capture attendance for Google Meet workshops, use Continu's Automated Attendance for External Users functionality — which records attendance through Continu rather than relying on Google to pass the data back. For any program where attendance verification matters — certification, compliance, channel kickoffs, partner programs — this is the path you need.

Other platforms. Custom or less common conferencing tools may integrate via webhook, ICS, or API. Behavior varies — confirm what's actually being captured before scaling a program on it.

The strategic question: does the conferencing platform we use give us the attendance fidelity we need for this program's stakes? For a casual office-hours workshop, lower fidelity is fine. For a regulated certification, you need verified attendance — confirm the integration can deliver it before committing.

Calendar Invite Generation

Continu's calendar integration uses Google Calendar as the underlying technology — and it works with both Google Calendar clients and Outlook. The integration is two-way: workshop changes in Continu propagate out to learners' calendars, and learner-side actions (accept, decline, remove) sync back to Continu's records.

What's typically included in the invite:

The workshop title and description
The conferencing link (Zoom, Teams, Meet URL)
Date, time, and time zone
Reminders configured at the calendar level
The facilitator's name (sometimes)

What's typically not included:

Pre-workshop materials or prerequisites (those usually go through Continu's notification system, not the calendar invite)
Post-workshop content
Cohort coordination details

A note for Outlook users. Outlook users may occasionally see workshop updates or removals that don't propagate cleanly. If a registered learner reports that a reschedule didn't reach their Outlook calendar — or that a canceled workshop is still showing — the issue is typically at the organization's Outlook bridge configuration. Have them check with their IT team before assuming the Continu integration is broken.

Confirm what your integration is sending before launching a high-visibility workshop. The first time a partner gets an invite that's missing the join link is the last time they trust your invites.

Attendance Sync

Attendance is where most calendar integration debates live. Get this wrong and every downstream report misleads.

When attendance syncs. Typically after the session ends. There can be a short delay — usually minutes, sometimes longer for Teams or Meet — before the data appears in Continu. Don't pull a "who attended this workshop" report seconds after the session ends.

What counts as Attended. This is configurable, and it matters more than most admins realize. Common attendance threshold options:

Joined the meeting at all (lowest bar, captures anyone who clicked the link).
Joined and stayed for a minimum duration (e.g., 30 minutes of a 60-minute session).
Joined and met an engagement threshold (camera on, polls answered, etc., where the platform supports it).

For high-stakes programs (certification, compliance), pick a stricter threshold. For office hours and informal sessions, the lowest bar is fine. Decide deliberately — the default may not match your program's needs.

Manual override. Facilitators can typically mark attendance manually for in-person workshops, edge cases (the integration didn't capture someone who clearly attended), or when a learner had connection issues. Document who has permission to override and how the override is logged.

No-Show vs. Cancelled. A learner who registered but didn't attend is a No-Show. A learner who cancelled in advance is Cancelled. The two are different states with different reporting implications. Confirm your platform distinguishes them and your reports respect the distinction.

Recording Sync

When recordings are enabled, the link or metadata syncs to Continu after the conferencing platform finishes processing.

Timing. Zoom cloud recordings typically appear within an hour of the session ending; longer for high-resolution or multi-hour sessions. Teams and Meet recordings depend on org-level retention and processing settings.

Where the recording lives. The recording itself stays on the conferencing platform's storage. Continu typically stores or links to a reference, not the file. This matters for retention and access — if your IT team retires the cloud recording after 30 days, the link in Continu becomes a dead link.

Access controls. Recording access is typically gated by the conferencing platform's access rules first, and Continu's content visibility rules second. A learner who can see the workshop in Continu may still hit a Zoom permissions wall on the recording. Test this before promising recordings to an external audience.

Retention. Decide your recording retention policy deliberately. Some recordings should live forever (certification evidence, compliance audit trail). Some should be ephemeral (customer-specific roadmap discussions, partner-confidential pricing). Configure your conferencing platform's retention to match the workshop's purpose.

Reschedule and Cancellation Behavior

Workshops change. The integration's behavior during change is where surprise emails come from.

Reschedule. When you reschedule a workshop in Continu, the integration should propagate the change to the learner's calendar — typically via an updated invite. Confirm this is happening. A reschedule that doesn't update the calendar produces a workshop where everyone shows up at the original time.

Cancellation. When you cancel a workshop, the integration should send a cancellation notice to registered learners. Confirm this fires. A cancelled workshop where no one was notified is a credibility hit you don't want to take with external audiences.

Time changes within the same day. A small reschedule (moving from 10am to 11am the same day) often doesn't propagate as cleanly as a date change. The calendar invite may update but reminders may not. Re-send a notification manually for any same-day reschedule.

Recurring workshop changes. Editing a single instance of a recurring workshop (a series) doesn't always behave the way admins expect. Test deliberately. The platform may update only the instance, only future occurrences, or all occurrences, depending on configuration.

Time Zone Handling

Time zone bugs are the most common silent failure in workshop integrations. Get them wrong and partners on the wrong continent show up at 3am.

The workshop has a time zone. When you create a workshop, you set its time zone. Every learner sees the workshop converted to their local time zone (in most properly configured integrations).

The invite carries the time zone. Calendar invites typically include the workshop's source time zone. The learner's calendar app handles the conversion to local time.

Reports may interpret time differently. A "workshops in the last 30 days" report may use UTC, the admin's time zone, or the workshop's source time zone — depending on configuration. For high-stakes reports, confirm the time zone interpretation before drawing conclusions.

Daylight saving transitions. Workshops scheduled across daylight saving boundaries can drift by an hour. Test recurring workshops that span the transition. Two months out of every year, this bites someone.

The strategic question: for a global program with partners in multiple time zones, what's the right anchor time zone? Pick one deliberately and document it in the workshop description. "10am Eastern" is unambiguous. "10am" is not.

Best Practices

Habits worth internalizing for every workshop with a calendar integration:

Test the integration end-to-end before going live. Schedule a test workshop. Register a test user. Run the session. Confirm the invite arrived, the join link worked, attendance synced, and (if applicable) the recording appeared. Only then launch the program.

Confirm the attendance threshold matches the program's stakes. Default attendance thresholds may not match what your certification or compliance program requires. Set the threshold deliberately.

Plan for the sync delay. Don't pull attendance reports immediately after a session. Give the integration 10-30 minutes for high-volume sessions, longer for Teams or Meet. Build the delay into your post-workshop workflow.

Time zone the workshop deliberately. For internal audiences, use the company's primary time zone. For external audiences spanning continents, document the time zone clearly in the workshop description and consider running parallel sessions in different anchor time zones.

Audit a sample workshop quarterly. Pick one live-virtual workshop per quarter and verify end-to-end: invite quality, attendance accuracy, recording availability, time zone correctness. Catch drift before a critical program does.

Document the recording retention policy. Where do recordings live? How long? Who has access? When are they purged? Document the answers and confirm with your IT team that the conferencing platform's settings match.

Configure manual override permissions deliberately. Decide who can manually mark attendance and document it. For compliance-critical workshops, log every override.

Coordinate with the conferencing platform admin. Most calendar integration issues are configuration issues at the conferencing platform layer (org-level Teams policies, Zoom account settings, Google Meet recording permissions). Build a relationship with the team that owns those settings.

Anti-Patterns to Avoid

The calendar integration mistakes we see most often:

Trusting attendance numbers without verification. Attendance data is downstream of integration configuration. If the threshold is wrong, the numbers are wrong. Spot-check before believing.
Ignoring recording sync delays. Promising a learner the recording "will be available immediately after the session" sets up a credibility loss when the actual delay is 30+ minutes.
Letting time zone defaults bite. A workshop scheduled in the admin's time zone, attended by learners in three other time zones, with no time zone documentation in the description — that's a recipe for missed sessions.
Treating reschedule as low-stakes. Every reschedule is a chance to lose attendees who don't see the update. Confirm the integration propagated the change.
Forgetting daylight saving. Workshops scheduled across DST transitions need explicit verification.
Relying on the integration without a manual fallback. When the integration breaks (and occasionally it will), have a manual attendance-marking process ready. For compliance workshops, the audit doesn't care that "the integration was down."
Not testing the join link. A calendar invite with a broken join link is a workshop with zero attendance. Click the link in your test invite. Don't assume it works.

Calendar Behavior in the Continu Architecture

Calendar integration sits at the intersection of several other Continu objects.

Workshops are the primary object. The calendar integration extends the workshop's state machine into real-world attendance data.

Smart Segmentation defines who gets the invite. Registration eligibility is scoped by Smart Segmentation. The calendar invite goes only to learners who match the segment and have registered.

Notifications coordinate with calendar invites. Continu's notification system sends pre-workshop reminders that complement (not replace) the calendar invite. Coordinate the cadence — duplicate reminders feel spammy, sparse reminders lose learners.

Reporting reads attendance from the integration. Workshop attendance reports are downstream of the integration. Bad integration = bad report.

Provisioning underlies user identity. Attendance gets matched to user records by email or unique identifier. If the user's email in Continu doesn't match the email they joined the conferencing session with, attendance won't link cleanly.

A well-designed calendar integration is configured deliberately, tested end-to-end, monitored on a cadence, and paired with a manual override process for edge cases. The platforms handle the mechanics. Your job is to make sure the mechanics produce the program you designed.

External Audience Patterns

External audiences make calendar integration stakes higher because the audience has less patience for failures.

Partner certification sessions. Highest stakes — attendance is the certification evidence. Configure strict attendance thresholds. Test every session beforehand. Have a manual override process documented for the inevitable edge case (partner had connectivity issues, etc.). Confirm the recording is accessible to the partner for post-session review where appropriate.

Customer office hours. Lower stakes, but high reputational impact. A customer who shows up at the wrong time or to a broken link won't come back. Document the time zone in the title. Test the recurring instance before each new month or quarter.

Channel kickoffs. Often large, often multi-region, often time-zone-sensitive. Consider parallel sessions for major regions rather than asking everyone to join at the same wall-clock time. Use the post-workshop recording aggressively for those who couldn't attend live.

Franchisee training. Often in-person or hybrid. Plan for manual attendance marking by the facilitator for the in-person component. Confirm the hybrid integration captures both groups deliberately.

A note on external invites. Partners and customers may use email domains that conflict with their conferencing platform's authentication (a Gmail user trying to join a Teams meeting that requires Microsoft authentication). Test the join experience from the audience's perspective before scaling.

Internal Audience Patterns

Internal audiences are easier because the conferencing platform is typically standardized across the organization.

New hire onboarding sessions. Schedule in the company's primary time zone. Use the standard conferencing tool. Reminders coordinate naturally with the rest of onboarding.
Compliance training cohorts. Strict attendance thresholds. Document override processes for compliance audit purposes.
Manager training. Cohort-based, recurring. Test the recurrence before launching.
Town halls and all-hands. Often large; confirm capacity at the conferencing platform level matches your audience size.

Internal calendar integrations typically just work — but the test step still matters. The first time you scale a new program, run a test session.

Known Behaviors and Limits

A few things worth knowing in advance:

Attendance sync timing depends on the platform. Zoom is fastest. Teams varies. Meet is the slowest and may require longer to finalize.
Some attendance details are configuration-dependent. The exact data exposed by the conferencing platform depends on org-level settings. What works for one customer's Teams instance may not work for another's.
Recording availability depends on cloud recording being enabled. If cloud recording is disabled at the conferencing platform level, no amount of Continu configuration will produce recording syncs.
Calendar invites may render differently in different calendar clients. Outlook, Google Calendar, Apple Calendar, and others handle ICS files slightly differently. Test in the audience's primary calendar client.
Time zone interpretation varies across reports. Confirm time zone treatment before drawing conclusions from any cross-time-zone report.
Cancelled workshops may not unsubscribe everyone everywhere. Confirm the cancellation actually removed the calendar invite from learners' calendars; some integrations only mark the workshop as cancelled in Continu without propagating outward.
Bulk workshop creation has rate limits. Creating fifty workshops simultaneously may stagger across the conferencing platform's API rate limits. Plan rollouts accordingly.
Daylight saving transitions create silent drift. A weekly recurring workshop scheduled before a DST transition may shift by an hour after. Audit recurring workshops around DST boundaries.

Calendar Behavior and Attendance Logic Follow