Run the event.
Keep the current sheet.
We designed the event workspace around a run sheet and a responsibility directory.
The production identity keeps the event recognisable, while the working views make the current instructions and their owners easier to find.
Explore the work ↓- PROJECT TYPE
- Interface design & front-end development
- DOMAIN
- Event supplier and crew coordination
- DESIGN FOCUS
- Keeping event crews on the current run sheet
Distribution is different from acknowledgement.
The acknowledgement review shows who has responded to the current version. We kept that separate from simply having a document in the workspace. A changed run sheet needs a visible review trail, especially when suppliers and crew rely on different parts of the schedule.
The pages we designed.
The build brings production overview, crew and supplier responsibilities, versioned run sheet, version acknowledgement review and event contact directory into one workspace.
Crew and supplier responsibilities
View the screen ↓Versioned run sheet
View the screen ↓Version acknowledgement review
View the screen ↓Event contact directory
View the screen ↓Project scope.
We designed and built 5 pages for this self-initiated project, including the layouts, responsive behaviour and front-end interactions. The interface uses sample business records.
The screenshots show authored interface states. Live accounts, operational integrations and production transactions are outside this portfolio build.
The gallery shows our rendered pages with identifying details masked.
A closer look.
Page by page.
Start with the overview, then explore the details. These are screenshots of the original interface, with names, contact details and identifying information blurred for privacy.
5 views Select any view to exploreHave a similar project?
Let’s discuss the work.
Tell us what your customers or team need to do. We can help define the pages, records and interactions around that task.




