Plan every stage. Deliver with confidence.
Connect customers, venues, schedules, crew, equipment, drivers and results through one motorsport event platform.
Pitwall OS Events is being designed for organisations that deliver simulator experiences, motorsport competitions, corporate events, exhibitions, driver coaching and mobile activations.
Build the event from the original enquiry, organise the operational detail, assign the right people and equipment, then give the delivery team a clear view of what needs to happen on the day.
Information remains connected before, during and after the event, helping teams reduce duplicated work, missed actions and last-minute surprises.
Features and interface designs may continue to change as event workflows are tested with simulator, motorsport and live experience providers.
Suggested screenshot: Events overview showing upcoming work, preparation status, tasks, crew and equipment alerts.
- Event calendar or list
- Upcoming events
- Event status
- Preparation progress
- Task alerts
- Crew warnings
- Equipment warnings
- Create event button and filters
More Than Dates On A Calendar
A motorsport simulator event involves much more than choosing a date and venue.
Teams may need to confirm customer requirements, arrange venue access, assign crew, prepare simulators, allocate computers and displays, organise transport, register drivers, configure competitions, publish leaderboards and complete post-event reporting.
Generic calendars cannot manage these relationships. Pitwall OS Events is designed to connect them.
The event record and its connections
- Event record (centre)Available in preview
- CustomerAvailable in preview
- VenueAvailable in preview
- ContactsAvailable in preview
- CrewIn development
- SuppliersIn development
- SimulatorsIn development
- EquipmentIn development
- ScheduleIn development
- DriversIn development
- CompetitionPlanned
- Timing resultsPlanned
- Post-event reportPlanned
Text alternative: the event sits at the centre. Every item beneath it is a connected record that can be opened on its own without losing its relationship with the event.
One Platform For Different Event Formats
Pitwall OS Events is being developed to support permanent venues, mobile operations and temporary installations.
Event records and workflows should adapt to the type of experience being delivered rather than forcing every event into the same rigid template.
Corporate simulator events
Team experiences, hospitality activations, staff competitions and client entertainment.
Public activations
Shopping centres, exhibitions, festivals, race meetings and promotional experiences.
Esports competitions
Practice, qualifying, races, hot-lap challenges, championships and leaderboard events.
Driver development
Coaching sessions, circuit preparation, vehicle familiarisation and structured training.
Commercial demonstrations
Simulator demonstrations, product launches, customer trials and technical showcases.
Permanent venue events
Weekly competitions, monthly challenges, championships and scheduled group experiences.
Charity and community events
Fundraising activities, accessible motorsport experiences and community programmes.
Multi-day installations
Events requiring staged delivery, setup, operation, pack-down and collection across several days.
From First Enquiry To Final Report
- Stage 01
Enquiry
Capture the customer, initial requirements, proposed date, location and expected attendance.
- Stage 02
Qualification
Confirm suitability, availability, budget expectations and required event format.
- Stage 03
Proposal
Prepare the recommended experience, equipment, staffing and delivery approach.
- Stage 04
Provisional
Reserve potential crew, equipment and dates while details are being finalised.
- Stage 05
Confirmed
Lock the event into the operational schedule and begin detailed preparation.
- Stage 06
Planning
Build the run sheet, assign tasks, allocate equipment and collect documentation.
- Stage 07
Ready
Complete final checks for crew, equipment, venue, transport and competition setup.
- Stage 08
Live
Give the operating team access to schedules, contacts, tasks, incidents and event updates.
- Stage 09
Pack-down
Track equipment, outstanding actions, venue handover and return logistics.
- Stage 10
Review
Record results, feedback, issues, costs, photographs and lessons learned.
- Stage 11
Follow-up
Create customer actions, reports, future opportunities and internal improvements.
Workspace administrators will be able to customise event stages in future versions.
What The Events Module Does
Event dashboard
See upcoming events, planning progress, outstanding actions and operational warnings in one view.
Event creation wizard
Create a structured event by collecting customer, venue, schedule, crew, equipment and competition requirements.
Multi-day planning
Manage setup, operation, overnight requirements, pack-down and collection across multiple dates.
Schedules and run sheets
Build a chronological operational plan with times, responsibilities, locations and dependencies.
Crew assignments
Assign team members to roles, shifts, activities and event responsibilities.
Venue and logistics
Record access times, parking, loading instructions, power, internet, space and venue contacts.
Equipment allocation
Reserve simulators, computers, displays, cases, networking equipment, spares and supporting assets.
Tasks and checklists
Create preparation, delivery and follow-up actions connected to the correct event.
Driver registration
Collect participant details and connect drivers with competitions, sessions and results.
Timing and leaderboards
Connect an event with competition formats, timing activity and public leaderboard displays.
Client collaboration
Present approved event information through a controlled customer-facing page.
Post-event reporting
Record outcomes, incidents, feedback, results, photographs and improvement actions.
See What Is Happening And What Needs Attention
The Events dashboard provides an operational overview of upcoming and active work.
Instead of opening every event individually, authorised users can see preparation progress, task deadlines, crew availability, equipment conflicts and readiness warnings from one screen.
Events should be available in calendar, timeline, list and status-board views.
Dashboard information
- Events today
- Events this week
- Events this month
- Provisional bookings
- Confirmed events
- Events requiring attention
- Tasks due
- Crew conflicts
- Equipment conflicts
- Missing customer information
- Missing venue information
- Readiness percentage
- Recently updated events
Suggested screenshot: Events overview showing upcoming work, preparation status, tasks, crew and equipment alerts.
- Event calendar or list
- Upcoming events
- Event status
- Preparation progress
- Task alerts
- Crew warnings
- Equipment warnings
- Create event button and filters
Build A Complete Event From The Beginning
Suggested screenshot: wizard progress, event type, customer, date and venue fields, save draft, missing-information warning and previous/next controls.
- Wizard progress
- Event type
- Customer
- Date and venue fields
- Save draft
- Missing information warning
- Previous and next controls
The event creation wizard guides users through the essential information required to create a useful operational record.
A quick-create option should allow an event to be added with basic information when time is limited. The complete wizard can then collect detailed requirements before the event progresses to confirmation.
Event basics
- Event name
- Event type
- Customer
- Status
- Priority
- Owner
- Proposed dates
- Expected attendance
Venue and location
- Venue
- Address
- Venue contacts
- Access times
- Setup area
- Parking
- Loading access
- Restrictions
Event format
- Experience type
- Competition format
- Session duration
- Driver capacity
- Public or private event
- Branding requirements
Equipment
- Number of simulators
- Simulator type
- Displays
- Motion requirements
- VR requirements
- Networking
- Race control
- Spare equipment
Crew
- Event manager
- Technical lead
- Operators
- Registration staff
- Hosts
- Media staff
- External suppliers
Logistics
- Transport
- Collection
- Delivery
- Accommodation
- Catering
- Power
- Internet
- Security
Documents
- Customer brief
- Venue information
- Insurance documents
- Risk assessments
- Method statements
- Floor plans
- Supplier documents
Review
- Missing information
- Conflicts
- Required approvals
- Next actions
- Readiness summary
One Operational Record For The Entire Event
The event record brings together the information required by sales, planning, technical and delivery teams.
Each area of the event should be available through clear tabs or panels, while the main overview shows progress, responsibilities and outstanding actions.
Suggested event tabs
- Overview
- Customer
- Venue
- Schedule
- Tasks
- Crew
- Assets
- Logistics
- Drivers
- Competition
- Documents
- Communications
- Costs
- Incidents
- Media
- Post-event report
- Activity
Event overview
- Event name
- Status
- Customer
- Venue
- Dates
- Event owner
- Key contacts
- Event type
- Expected attendance
- Readiness
- Current risks or blockers
- Next action
- Recent activity
Suggested screenshot: event header with status, customer, venue, dates, preparation progress, crew, equipment, tasks, navigation tabs and warnings.
- Event header
- Status
- Customer and venue
- Dates
- Preparation progress
- Crew and equipment
- Tasks
- Event navigation tabs and warnings
Plan Every Phase Of A Multi-Day Event
Large events rarely begin when the public arrives.
Equipment may be collected several days earlier, vehicles loaded the evening before, crew accommodated overnight and systems removed after the event has closed.
Pitwall OS should allow each event to contain multiple operational days and phases.
Example phases
- Workshop preparation
- Equipment collection
- Vehicle loading
- Travel
- Venue access
- Installation
- Technical testing
- Staff briefing
- Guest registration
- Live operation
- Competition final
- Awards or podium
- Pack-down
- Venue handover
- Return travel
- Equipment check-in
- Post-event review
Each phase supports
- Date
- Start and finish time
- Location
- Responsible person
- Assigned crew
- Required equipment
- Dependencies
- Notes
- Completion status
Give Every Team Member A Clear Run Sheet
Suggested screenshot: multi-day schedule with time, activity, assigned person, location, status, dependencies, delay warning and add schedule item control.
- Multi-day schedule
- Time
- Activity
- Assigned person
- Location
- Status
- Dependencies
- Delay warning
Build the event schedule as an operational run sheet rather than a simple calendar entry.
Each item should explain what is happening, when it starts, where it takes place, who is responsible and what must be completed first.
Changes should be visible to authorised users without creating several conflicting document versions.
Example schedule items
- Venue access
- Equipment delivery
- Setup
- System testing
- Staff arrival
- Crew briefing
- Customer arrival
- Driver registration
- Practice
- Qualifying
- Competition
- Finals
- Podium
- Media activity
- Breaks
- Pack-down
- Collection
- Venue departure
Scheduling tools
- Drag-and-drop scheduling
- Day and timeline views
- Dependencies
- Role assignments
- Location
- Status
- Notes
- Conflict warnings
- Print view
- Mobile crew view
- PDF export where available
Put The Right People In The Right Roles
Assign internal crew, contractors, suppliers and customer contacts to the event.
Each person should be able to see their role, working times, responsibilities and relevant event information.
Availability and scheduling warnings can help event managers identify conflicts before the event.
Example roles
- Event director
- Project lead
- Customer contact
- Venue contact
- Technical lead
- Simulator technician
- Race director
- Registration operator
- Simulator operator
- Driver coach
- Host
- Commentator
- Photographer
- Videographer
- Transport driver
- Health and safety lead
- Catering contact
- Security contact
Crew records
- Role
- Shift
- Arrival time
- Finish time
- Contact information
- Assigned tasks
- Assigned schedule items
- Travel arrangements
- Accommodation
- Notes
- Briefing confirmation
- Availability status
Private crew contact information must not be exposed to users without appropriate permission.
Suggested screenshot: crew list with roles, shift times, confirmation status, assigned activities, contact action, availability warning and scheduling conflict.
- Crew list
- Roles
- Shift times
- Confirmation
- Assigned activities
- Contact action
- Availability warning
- Scheduling conflict
Keep Venue And Access Information Together
Suggested screenshot: venue details, access notes, loading information, power, internet, floor plan, venue contact, event-specific instructions and missing-information warning.
- Venue details
- Access notes
- Loading information
- Power
- Internet
- Floor plan
- Venue contact
- Event-specific instructions
Venue details often arrive through several emails, documents and telephone conversations.
Pitwall OS should bring the practical information required for delivery into one structured area that can be accessed by authorised event crew.
Venue information
- Venue name
- Full address
- What3Words or location reference
- Main venue contact
- Out-of-hours contact
- Access date and time
- Loading entrance
- Parking
- Vehicle restrictions
- Lift dimensions
- Door dimensions
- Stairs
- Floor level
- Setup area
- Floor plan
- Power availability
- Network availability
- Mobile signal
- Lighting
- Sound restrictions
- Security procedures
- Storage
- Waste arrangements
- Pack-down deadline
Logistics planning
- Vehicles
- Drivers
- Route
- Mileage
- Fuel or charging
- Tolls
- Parking
- Delivery windows
- Collection windows
- Accommodation
- Equipment collection
- Supplier deliveries
Connect Event Planning With The Equipment Fleet
Reserve the simulators, computers, displays, controls, cases, cables, networking equipment and spares required for the event.
Pitwall OS Events connects with the Assets module so equipment can be checked for availability, condition and readiness before it is allocated.
Conflicts and maintenance warnings should be visible while the event is still being planned.
Equipment planning supports
- Requested equipment
- Proposed equipment
- Confirmed allocation
- Alternatives
- Equipment conflicts
- Current location
- Preparation requirements
- Maintenance status
- Assigned transport case
- Load-out status
- Delivery status
- Return status
- Post-event inspection
Suggested screenshot: event equipment requirements, reserved assets, availability, current location, readiness, conflict warnings, preparation progress and load-out status.
- Equipment requirements
- Reserved assets
- Availability
- Current location
- Readiness
- Conflict warnings
- Preparation progress
- Load-out status
Make Preparation Visible
Suggested screenshot: task groups, completion progress, assigned person, due date, priority, documents, approval status and missing-document warning.
- Task groups
- Completion progress
- Assigned person
- Due date
- Priority
- Documents
- Approval status
- Missing document warning
Every event generates actions across sales, operations, technical preparation, logistics and customer communication.
Tasks and checklists should remain connected to the event that created them. Users can see what must be done, who is responsible and whether any delay is affecting overall readiness.
Commercial
- Confirm customer requirements
- Approve quotation
- Receive purchase order
- Confirm invoicing details
Venue
- Confirm access
- Review floor plan
- Confirm power
- Confirm internet
- Approve branding
Technical
- Test simulators
- Update software
- Check controls
- Configure competition
- Prepare spare equipment
Logistics
- Allocate vehicle
- Prepare cases
- Complete load-out
- Confirm accommodation
- Confirm supplier delivery
Event delivery
- Brief crew
- Open registration
- Start competition
- Publish results
- Complete pack-down
Follow-up
- Send results
- Request feedback
- Record issues
- Create final report
- Schedule next contact
Document categories
- Customer brief
- Proposal
- Purchase order
- Venue plan
- Risk assessment
- Method statement
- Insurance evidence
- Supplier document
- Competition rules
- Driver briefing
- Run sheet
- Results
- Photographs
- Post-event report
Pitwall OS can organise safety and event documents, but it does not replace competent risk assessment, professional advice or venue approval.
Connect Participants With The Event Experience
Register drivers, guests and participants against the correct event.
Collect the information required for the experience, assign participants to sessions or competitions and preserve their connection with results where appropriate.
Potential registration fields
- Name
- Driver name
- Contact information
- Company
- Team
- Age category
- Experience level
- Accessibility requirements
- Emergency contact
- Session
- Competition class
- Simulator assignment
- Registration status
- Briefing status
- Consent or waiver status
Sensitive and special-category information must only be collected where there is a legitimate requirement and appropriate protection.
Registration support
- Internal registration
- Customer-provided guest list
- Shareable registration link
- QR check-in
- On-site quick registration
- Duplicate detection
- Driver number
- Session assignment
- Export where authorised
Suggested screenshot: participant list, registration status, team or group, session, check-in, information warning, search and filters, add participant action.
- Participant list
- Registration status
- Team or group
- Session
- Check-in
- Information warning
- Search and filters
- Add participant action
Connect Event Delivery With Competition Results
Suggested screenshot: competition format, registered drivers, sessions, track and vehicle, current leaderboard, timing status, public display link and results approval.
- Competition format
- Registered drivers
- Sessions
- Track and vehicle
- Current leaderboard
- Timing status
- Public display link
- Results approval
For simulator competitions and motorsport experiences, the event does not stop when the equipment is running.
Pitwall OS Events can connect with the Timing module to organise competition formats, driver sessions, results and leaderboard displays.
This connection helps preserve the relationship between the customer, event, participant and competition result.
Potential competition formats
- Fastest lap
- Practice and qualifying
- Individual race
- Multiple heats
- Knockout competition
- Team endurance
- Championship round
- Rolling public leaderboard
- Hourly or session-based reset
- Final and podium
Competition information
- Simulation platform
- Track
- Vehicle
- Vehicle class
- Session length
- Assists
- Conditions
- Server
- Simulator assignments
- Scoring
- Penalties
- Prizes
- Leaderboard display
- Results approval
Give The Customer A Controlled View
Customers often need access to event information without requiring access to the complete internal workspace.
A controlled client-facing event page can present approved information, collect decisions and keep customer comments connected to the correct event.
The client-facing page may show
- Event summary
- Dates and venue
- Agreed event format
- Key contacts
- Milestones
- Approval requests
- Selected tasks
- Documents
- Customer comments
- Questions
- Change requests
- Guest registration link
- Final schedule
- Results and post-event report
Internal notes, costs, private staff details and sensitive operational records must remain hidden unless explicitly shared.
Permission states
- Internal only
- Client can view
- Client can comment
- Client approval required
- Public
Suggested screenshot: branded event summary, customer actions, documents, questions, comments, approval request and last-updated information.
- Branded event summary
- Customer actions
- Documents
- Questions
- Comments
- Approval request
- Last updated information
A Focused Interface For The Live Event
During the event, operators need fast access to current information rather than the complete planning workspace.
Pitwall OS is being designed with a simplified live event interface for authorised crew. It should show the current schedule, important contacts, active tasks, participant status, equipment issues and operational announcements.
The live interface may include
- Current activity
- Next activity
- Countdown
- Event status
- Crew on duty
- Participant queue
- Simulator status
- Equipment fault reporting
- Active competition
- Latest leaderboard
- Urgent contacts
- Incident recording
- Announcements
- Quick notes
- Escalation controls
Clear, large controls suitable for tablets and touchscreens.
Suggested screenshot (keep the original mobile aspect ratio where the layout is a phone view): current schedule item, next activity, live clock, event status, crew, equipment warnings, participant count and quick actions.
- Current schedule item
- Next activity
- Live clock
- Event status
- Crew
- Equipment warnings
- Participant count
- Quick actions
Turn Every Event Into Useful Experience
Suggested screenshot: event summary, attendance, results, equipment issues, feedback, lessons learned, follow-up actions and generate report button.
- Event summary
- Attendance
- Results
- Equipment issues
- Feedback
- Lessons learned
- Follow-up actions
- Generate report button
When an event finishes, important knowledge is often lost as equipment is packed away and the team moves to the next job.
Pitwall OS can guide the team through a structured review, preserving what worked, what failed and what should change next time.
The post-event report may include
- Attendance
- Registered drivers
- Sessions completed
- Competition results
- Customer feedback
- Crew feedback
- Equipment issues
- Incidents
- Schedule performance
- Venue observations
- Supplier performance
- Photographs and media
- Additional costs
- Missing or damaged equipment
- Lessons learned
- Improvement actions
- Customer follow-up
- Future opportunity
- Overall event rating
Improvement actions can become assigned tasks, and approved information can be included in a customer-facing report.
Events At The Centre Of The Operation
Pitwall OS Events is designed to connect the commercial, operational and competition sides of an organisation.
Information created elsewhere in the platform can be reused by the event rather than entered repeatedly.
Events and CRM
Connect the event with the customer, company, venue contacts, suppliers and future sales opportunities.
Events and Assets
Reserve simulators and supporting equipment while checking availability, condition and readiness.
Events and Timing
Connect participants, competition formats, sessions, results and public leaderboards.
Events and Projects
Manage larger event programmes with milestones, dependencies, budgets and customer collaboration.
Connections are labelled individually above — not every connection is operational yet.
The Right Event View For Every User
Event information is used by managers, technicians, crew, customers and participants.
Pitwall OS is web-based and is being designed with interfaces that present the right information for each role.
Management workspace
Commercial overview, event pipeline, readiness, resources and reporting.
Event planner
Detailed schedules, tasks, crew, logistics and equipment.
Live control view
Current activity, participant flow, simulator status and operational issues.
Mobile crew view
Personal schedule, tasks, contacts and event updates.
Client event page
Approved milestones, documents, comments and decisions.
Participant registration
Registration, check-in, session assignment and competition information.
Suggested screenshot: desktop, tablet and mobile event views shown together with fictional demonstration data only.
- Management workspace
- Race control tablet view
- Mobile crew view
AI Where It Improves Preparation
Future AI-assisted features will focus on reducing administration, identifying missing information and helping teams prepare more consistently.
AI will assist users rather than make unreviewed operational or safety-critical decisions.
- Turning a customer brief into a draft event
- Extracting requirements from documents
- Suggesting event tasks and checklists
- Identifying missing venue information
- Suggesting crew roles
- Recommending equipment requirements
- Detecting scheduling conflicts
- Creating a first run-sheet draft
- Summarising event changes
- Producing crew briefing summaries
- Drafting post-event reports
- Identifying repeated operational issues
- Suggesting follow-up actions
Planned development — not currently available
Developed Around Real Event Delivery
Pitwall OS is developed using a fast, feedback-led and AI-assisted approach. This allows us to build working features, test practical workflows, investigate bugs and adapt functionality around genuine user requests.
The Events module is being shaped by experience with simulator competitions, corporate events, mobile installations, public activations, driver experiences and multi-day event delivery.
Preview features may be changed, extended or simplified as we test the platform with real organisations.
What makes your events difficult to manage?
Tell us where information becomes disconnected, which event tasks are repeatedly missed and what your current systems cannot handle.
From Functional Preview To Controlled Beta
The current Events preview demonstrates the intended interface, data structure and event workflows.
The next major stage is strengthening the backend and preparing the platform for controlled testing. Event records may contain private customer, venue, crew, participant and commercial information, so permission and data separation must be thoroughly tested before production use.
Development priorities
- Secure authentication
- Role-based access controls
- Workspace data separation
- Client portal permissions
- Participant data protection
- Private and shared record separation
- Secure document handling
- Database security rules
- Input validation
- Activity and audit logging
- Backup and recovery
- Error monitoring
- Automated application testing
- Manual workflow testing
- Multi-day event testing
- Crew and equipment conflict testing
- Cross-browser testing
- Desktop, tablet and mobile testing
- Controlled beta onboarding
- Documentation and support processes
Pitwall OS Events is currently preview software. Features, interfaces and workflows may change. Organisations should not use the preview as their only source of safety-critical, legal or operational event information.
Build Better Events From The First Enquiry
We are inviting simulator centres, motorsport organisations, event providers, equipment specialists and driver development businesses to review the Pitwall OS Events preview.
Request a demonstration, join the future beta programme or tell us about the specialist event workflows your current software fails to support.
Customers, venues, crew, equipment and competition activity connected through one event workspace.