Your account
HOL-D078Story implementation: Planned

Prepare events and manage approved appearances

events · Proposed launch phase 4

Start from Home

Review as Commercial manager · Full workflow planned

User story

As a commercial manager, I want to coordinate an event within an assigned operating responsibility so its details eligibility and approved people stay accurate for participants.

Draft requirements for review · Updated 2026-10-19

What the app should do

  • Publish existing public event catalog metadata, timing/timezone, eligibility and approved person/organization appearance links through the shared public projection. Event preparation, approvals and attendee-management tools stay separate.
  • Prepare event title, date/timezone, place, capacity, public/member eligibility, preparation information and approved Guide/Athlete/partner associations.
  • Preview and submit the event for the agreed approval before publishing; keep attendee reservation D005 and waitlist/cancellation D034 separate from operator editing.
  • Record an approved person’s appearance/clinic association without granting that person event-editing, private attendee-list or paid-member rights.
  • Manage capacity/date/cancellation changes through explicit participant outcomes and next steps; do not promise that an unsent notice reached participants.
  • Event ownership, approval and participant communications remain HOL decisions. Commercial manager is a proposed review perspective; there is no partner/host self-service grant.
  • Associate events with approved public organization hosts, tour companies or disclosed partners separately from approved individual Guide/Athlete appearances; use stable reciprocal links and explicit labels.
  • Public host information does not create self-service organization event management, guarantee a booking or override event eligibility/fees; operating ownership still requires confirmation.

What to check in the demo

Follow these steps from the role’s landing page through navigation and feature checks.

Review as

Commercial manager

Start here: Home

Choose the Avery Chen dummy account and open its assigned Commercial manager Home without a password or authenticator prompt. This dev-only Home review does not verify MFA or unlock protected staff actions. Use your own provisioned staff account and authenticator when reviewing those actions.

Navigation from sign-in

  1. 01Open the fictional Commercial manager account through the connected sign-in service. Seeded Home review opens directly. Real HOL staff access and protected actions require an authenticator check.
  2. 02Start on Commercial manager Home and open Features + permissions. A full event-operations workspace does not exist; Events and professional appearance collections are separate previews.

Feature checks start here

Prepare events and manage approved appearances · Full workflow planned

Public-content reads are available for dev review; full story acceptance and stakeholder approval remain separate. Planned full workflow. Existing workspace samples, where present, demonstrate only isolated controls. Backend implementation is on hold; no completed end-to-end outcome or stakeholder approval is claimed. Public people and organization pages are available; this operator handoff remains incomplete. Backend implementation is on hold.

  1. 03Current UI review: follow the navigation as far as the explicitly available screen; the complete feature below is not built. Stop when the named control is absent.
  2. 04Planned acceptance — Inspect the proposed operating scope; distinguish event authoring from buying/reserving a member seat.
  3. 05Planned acceptance — prepare a fictional eligible event and submit its details and associations for approval.
  4. 06Planned acceptance — After authorized publication, compare the same event’s public details with Guide/Athlete approved-appearance collections.
  5. 07Planned acceptance — Change capacity/date or cancel a sample event; inspect reservation/waitlist consequences and the unsent-versus-delivered communication state.
  6. 08Planned acceptance — Once built and operating ownership confirmed, open an event’s organization host and approved Guide appearance, then return via related events; inspect withdrawn host/appearance and cancellation states.

Backend work for this feature

Backend development authorized · Dev only

What needs to be supported

  • Selected authorization is the public read/content-seeding slice only. Existing write, participation, editorial management, event operations, gift redemption, payment and delivery requirements below are separate later work unless already authorized elsewhere.
  • Publish existing public event catalog metadata, timing/timezone, eligibility and approved person/organization appearance links through the shared public projection. Event preparation, approvals and attendee-management tools stay separate.
  • Store event versions, timezone/place, eligibility, capacity, operating assignment, approval state and approved person/partner associations using one canonical event ID.
  • Enforce assigned operator editing and separate approval; public attendees and associated Guides/Athletes cannot read private lists or self-publish event changes.
  • Maintain reservation/capacity/waitlist consistency under concurrent requests and changes; preserve user eligibility and a clear cancellation/history record.
  • Link D005/D034 participant status to approved event changes. Prepare an idempotent communication queue/status contract without sending email, push or external notices now.
  • Record actor/time/reason and handle failed publication, stale edits, declined appearances and conflicting dates without silently moving an attendee or granting paid access.
  • Store organization-host/partner and person-appearance associations as distinct approved event relations; revalidate target publication and operating assignment, and keep attendee/contact data private.

How to verify in dev

  1. Verify published-only anonymous projection, no private/protected payload, stable IDs and links, missing/unpublished records, empty/loading/error UI, and no silent static fallback. Idempotent seed rerun preserves edited records; authenticated/dummy Home entry remains unchanged.
  2. Inspect public event/appearance links and current published details; this does not accept the later staff event-preparation workflow.
  3. Test assigned operator, approver, associated Guide/Athlete and attendee access; deny event editing or private participant reads outside scope.
  4. Race reservation/waitlist activity with a capacity/date change; verify one consistent event and participant status.
  5. Cancel or decline a sample appearance, reload all affected views and verify audit/communication state without a real message or financial action.
  6. Change or withdraw an event’s organization relation, cancel the event and compare reverse public pages; verify no stale approval, attendee leakage or automatic organization login permission.

Before this can work

  • Choose the Avery Chen dummy account and open its assigned Commercial manager Home without a password or authenticator prompt. This dev-only Home review does not verify MFA or unlock protected staff actions. Use your own provisioned staff account and authenticator when reviewing those actions.
  • HOL must select event operating owner, approver, appearance-assignment rules, cancellation policy and permitted participant communications before a connected build.
  • Use fictional role-preview records. Frontend prototypes may simulate the workflow; no backend implementation or real service operation is authorized.

Connected stories