# Plan event attendance with a checked joining route, calendar and visibility

Original constructed teaching cases. No real accounts, participants, interviews or customers. Read the complete matching guide and do not substitute these examples for missing evidence.

T1 — Constructed calendar: a session is planned for 12 November 2026, 18:00–18:30 Europe/Berlin, equivalent here to 17:00–17:30 UTC. The imported calendar says 18:00 UTC. Decision: fix the local calendar copy against the actual event instant and inspect the joining link. Outcome: a checked reminder, not evidence of a booked seat or attendance.

T2 — Constructed visibility goal: an attendee disables the organization/interests preference but comments publicly on the event post. Decision: keep the setting and visible comment as different observations. Outcome: no promise of secret attendance, erased Activity or hidden speaker participation.

T3 — Constructed withdrawal: the member leaves the LinkedIn event, while a separate external booking and .ics entry remain. Decision: inspect the native removed-attendee state, then handle the external booking and calendar through their own intended controls. Outcome: three separate states; no inferred refund, host message or automatic cancellation.