[E12] Events List (browse / find)

Summary

The exhaustive event list for the organisation — tenant scope, Events group. Where E05 is "my desk this morning", E12 is the filing cabinet: you come here knowing what you are looking for, or to slice the whole portfolio.

ID allocated 2026-08-14; not yet designed. This page exists so the use-case ID is reserved and the Claude Design directory, this page and any ADO item share one key.

The design directory was previously named E10-events-list, which collided with E10 Export Participants; its README still carried a third, older code (E06) internally. Renamed to E12 during the 2026-08-14 navigation-module refactor.

Actor & Context

Actor: event organiser, tenant admin.

Frequency: regular — whenever the operator needs an event that is not in E05’s curated "right now" view.

Entry point: Events row in the tenant sidebar (C01 EVENTS group); also E05’s Recent panel "View all" footer link.

Intent (from the design placeholder)

  • All events visible — Active, Recent, Draft, Archived, Cancelled. Status as a filter chip, not a section divider.

  • Filter and sort — status, date range, distance, course, organiser, open follow-ups. Saved views.

  • View modes via a tab-style switcher: a dense sortable table, and a timeline / planning view.

  • Bulk operations — tag, archive, duplicate, export.

  • Create event as the primary header action.

  • Search across the whole portfolio, including past events, which E05 deliberately hides behind "View all".

  • Pagination / virtualisation — a five-year-old organisation could hold 200+ events.

Open Questions

  1. Calendar vs weekend-density timeline. A month grid is a poor fit: events run on weekends and public holidays, so Mon–Fri is mostly empty, and organisers think in "is the second weekend of October free?" rather than "what is on Wednesday". The design placeholder proposes a horizontal weekend-density timeline that works as a gap-finder. Undecided.

  2. Cross-organisation event awareness. For the timeline to work as a planning tool it needs regional events from other providers, not just events in this platform. Options include aggregator sync, an organisation-curated "external events of note" list, cross-organisation visibility subject to platform config, and public/school holiday calendars. This is a product-capability decision, not a UI one — defer until data sources are agreed.

Design Anchors

  • C01 — tenant sidebar, EVENTS group

  • E05 — hands off to this page via "View all"

  • ADR-0008

Change History

Date Change

2026-08-14

ID allocated. Placeholder created so the shared use-case key holds across the design project, docs-event and ADO. Content carried over from the design directory’s README; renamed from the colliding E10-events-list.