Wireframes

Event workflow, one desk at a time

The path an event takes from a client's request to a published registration page, laid out as the screens each role actually works in. Layout and flow only — the data is seeded and the buttons don't write anything yet.

The gate to watch: approval is not confirmation. Approving says the request holds enough information to plan against; confirming says the arrangements are actually in place. Registration only opens after confirmation.

  1. 01Event OrganiserSteps 1-2

    Drafts an event request and submits it. Sees only their own drafts and submissions.

    Acting as Alice

  2. 02Event Coordinator LeadStep 3

    Sees every submitted request and assigns an Event Coordinator to each one.

    Acting as Daniel Okonkwo

  3. 03Event CoordinatorSteps 4-11

    Reviews and approves, raises the venue booking, records equipment, tracks readiness, confirms the event, then opens registration.

    Acting as Nadia

  4. 04Venue StaffStep 7

    Approves or rejects booking requests, with enough event detail to decide.

    Acting as Mei Chen

  5. 05Technical Support StaffStep 8

    Reviews equipment lines and reserves what is available, line by line.

    Acting as Ravi Kulkarni

  6. 06Safety OfficerStep 9

    Reviews events whose venue and equipment are in place, then approves them or rejects them with what must change.

    Acting as Sam Lim

AttendeeStep 11

The public registration pages, already built. Where a confirmed event with registration enabled ends up.