Case study / Admin App
Less organising. More bringing people together.
A shared workspace for chapter hosts to manage gatherings, review RSVPs, and keep the small details from falling between conversations.
- Role
- Workflow mapping, UX & UI
- Timeline
- 8 weeks · example scope
- Scope
- Admin workspace · Event management · Member directory
Illustrative draft Sample story, scope, and concept screens. These are placeholders, not verified project results.
01 / The challenge
The work behind a good gathering.
This draft imagines a growing network of chapter hosts coordinating through chat and spreadsheets. An RSVP lives in one place, a venue update in another, and the person welcoming guests has to piece everything together.
The challenge was to give organisers a shared operational view without turning community hosting into an administrative job. The interface had to make the next action clear while keeping each chapter’s information easy to find.
02 / The approach
Design around the day of the event.
Instead of starting with charts, the proposed workspace starts with what a host needs to prepare, check, and follow up on.
Attention before analytics
A compact attention list surfaces an unconfirmed venue, a full event, or a draft waiting to be published. Each item points directly to the relevant gathering.
One record for every gathering
Event details, capacity, guest lists, and check-in live together. Clear status labels separate drafts, published events, and completed gatherings.
Chapter context stays visible
A persistent chapter selector keeps hosts oriented. The proposed permissions model gives local hosts access to their chapter and community leads a cross-chapter view.
03 / A closer look
04 / The reflection
A calmer routine for community hosts.
The concept connects event creation, guest management, and check-in in one workspace. Before implementation, I would validate the workflow with chapter hosts and test permissions, empty states, and accidental edits. No operational improvements are claimed in this draft.