From first lap to final result
Create competitions, connect drivers, manage sessions and publish professional leaderboards from one platform.
Pitwall OS Timing is being designed for simulator venues, esports competitions, motorsport experiences, corporate events and public activations.
Register drivers, define the competition format, collect lap times and results, then present the information through live race control views and branded public leaderboards.
Timing data remains connected to the event, driver, track, vehicle and workspace that created it.
Timing sources, integrations and interface designs may continue to change as the platform is tested with different simulators and competition formats.
Suggested screenshot: Timing overview showing an active competition, registered drivers, latest laps and leaderboard positions.
- Active competitions
- Current session
- Connected rigs
- Drivers registered
- Latest lap times
- Current leaderboard
- Timing connection status
- Results awaiting review
More Than A List Of Lap Times
A useful competition platform needs to understand more than the fastest recorded lap.
It needs to know who was driving, which simulator produced the result, which vehicle and track were used, whether the lap was valid, which class the driver entered and whether the result has been approved for publication.
Pitwall OS Timing is designed to preserve this context while making competitions easier to operate and results easier to understand.
The primary timing relationships
- EventAvailable in preview
- CompetitionAvailable in preview
- DriverAvailable in preview
- TeamIn development
- SessionAvailable in preview
- SimulatorIn development
- TrackAvailable in preview
- VehicleAvailable in preview
- Timing sourceIn development
- LapAvailable in preview
- ResultAvailable in preview
- LeaderboardAvailable in preview
Text alternative: an event contains competitions. Each competition holds sessions, registered drivers and teams, runs on a chosen simulator, track and vehicle, receives laps from a timing source, and produces results that feed a leaderboard.
Build, Run, Review And Publish
- Stage 01
Create the competition
Choose the event, competition type and rules.
- Stage 02
Configure the combination
Select the simulator platform, track, vehicle and permitted assists.
- Stage 03
Register drivers
Add drivers individually, import them or connect registration with an event.
- Stage 04
Connect the timing source
Choose manual entry, approved import or a supported simulator connection.
- Stage 05
Run the sessions
Operate practice, qualifying, races or fastest-lap attempts.
- Stage 06
Review the results
Validate laps, apply penalties and approve official results.
- Stage 07
Publish the leaderboard
Show approved results through public displays, exports and sharing tools.
What The Timing Module Does
Competition builder
Create fastest-lap challenges, practice and qualifying sessions, races, team competitions and championship formats.
Driver registration
Register drivers, assign display names and connect participants with events, teams, groups and competition classes.
Track and vehicle configuration
Define the simulator platform, circuit, layout, vehicle, class, weather, assists and competition conditions.
Timing source management
Collect results through manual entry, approved imports and supported simulator or telemetry connections.
Live race control
Monitor current sessions, connected simulators, driver activity, lap validity and timing status.
Leaderboards
Rank drivers by fastest lap, race result, points, class, team or another configured scoring method.
Result review
Review suspicious, incomplete or invalid results before approving them for public display.
Penalties and adjustments
Record invalidated laps, time penalties, position changes and administrative corrections with a reason.
Public displays
Present branded leaderboards on venue screens, event displays, websites and shared links.
Multiple boards
Create separate leaderboards for different events, tracks, vehicles, classes, venues or competition periods.
Championships and points
Combine results from multiple rounds into driver, team or class standings.
Exports and sharing
Export approved results, generate branded images and share leaderboard updates through supported channels.
Create The Competition Around The Experience
Pitwall OS Timing supports different competition formats rather than forcing every event into a single fastest-lap table.
The competition builder guides the organiser through the format, vehicle and track combination, driver eligibility, timing rules, scoring and publication settings.
Competition types may include
- Fastest-lap challenge
- Rolling fastest lap
- Practice session
- Qualifying session
- Sprint race
- Feature race
- Multi-race event
- Knockout competition
- Team challenge
- Relay event
- Endurance competition
- Time-limited public activation
- Venue championship
- Multi-round championship
- Custom format
Competition settings may include
- Competition name
- Connected event
- Venue
- Start and end dates
- Simulator title
- Track
- Track layout
- Vehicle
- Vehicle class
- Weather
- Time of day
- Assists
- Setup restrictions
- Number of attempts
- Session duration
- Minimum valid laps
- Driver classes
- Scoring system
- Tie-break rules
- Publication status
- Prize information
Suggested screenshot: competition type, event connection, track and vehicle, session format, driver classes, scoring and publication settings.
- Competition type
- Event connection
- Track and vehicle
- Session format
- Driver classes
- Scoring settings
- Publication settings
- Save draft
Connect Every Result To The Correct Driver
Suggested screenshot: registered driver list with display name, driver code, team, class, assigned simulator, check-in status and QR action.
- Registered driver list
- Display name
- Driver code
- Team
- Class
- Assigned simulator
- Check-in status
- QR action
A lap time becomes more useful when it is attached to a verified competition entry.
Register drivers before the session, import participants from Pitwall OS Events or use a quick event-day registration interface.
Driver identification can be connected to a simulator manually or through a supported QR workflow.
Driver records may include
- Full name
- Public display name
- Driver code
- Team
- Company
- Competition class
- Experience level
- Connected event
- Assigned simulator
- Registration status
- Check-in status
- Consent and display preferences
- Notes visible to authorised organisers
Public leaderboards must use the approved display name rather than exposing private contact information.
QR driver connection
In development- Step 01
Register the driver
- Step 02
Generate or display the driver's QR code
- Step 03
Scan the QR code at the simulator
- Step 04
Attach the driver to the selected rig
- Step 05
Confirm the active driver
- Step 06
Record incoming laps against the correct entry
- Step 07
Release the simulator when the session ends
Preserve The Conditions Behind Every Result
Lap times are only comparable when the competition conditions are understood.
Pitwall OS connects each competition with the relevant simulator title, track layout, vehicle, class and configuration.
Competition conditions may include
- Simulator or game
- Game version
- Track
- Track layout
- Historic layout
- Vehicle
- Vehicle class
- Vehicle version
- Balance of performance
- Fixed or open setup
- Fuel level
- Tyre compound
- Damage
- Weather
- Track conditions
- Time of day
- Driving assists
- Session restrictions
- Server information
Where catalogue information is shared globally, organisations should be able to select the recognised track and vehicle record. Workspace-specific competition settings and results remain private unless deliberately published.
Suggested screenshot: simulator platform, track and layout, vehicle and class, competition conditions, assists, weather and fixed-setup status.
- Simulator platform
- Track and layout
- Vehicle and class
- Competition conditions
- Assists
- Weather
- Fixed setup status
Bring Timing Data Into One Controlled Workflow
Suggested screenshot: timing sources, connected rigs, SimHub bridge status, last heartbeat, latest result, test connection, error status and integration type.
- Timing sources
- Connected rigs
- SimHub bridge status
- Last heartbeat
- Latest result
- Test connection
- Error status
- Integration type
Different venues and simulator platforms produce timing data in different ways.
Pitwall OS is being designed to accept timing information through several controlled methods while preserving the source of every result.
Potential timing sources
- Manual result entryAvailable in preview
- CSV importAvailable in preview
- Approved spreadsheet importIn development
- Google Sheets connectionIn development
- SimHub bridgeIn development
- Simulator telemetryPlanned
- Local Pitwall OS bridgeIn development
- Venue timing serverPlanned
- Future API integrationPlanned
Every timing source should show
- Source name
- Source type
- Connected workspace
- Connected event
- Connected competition
- Connected rig
- Connection status
- Last heartbeat
- Last result received
- Software version
- Data validation status
- Error messages
- Test connection action
Visible integration status labels
- Connected
- Testing
- Disconnected
- Error
- Not configured
- Planned
Status is always shown as a written label as well as a colour, so connection state never depends on colour alone. Planned integrations are not presented as completed.
Operate The Competition From One Race Control View
The race control interface brings together the current session, active drivers, simulator status and incoming timing information.
Operators should be able to understand what is happening without moving between several screens.
Confirmation steps are used for actions that could affect official results, and touch targets are sized for tablet use in a live environment.
The race control interface may show
- Event
- Competition
- Current session
- Session clock
- Track and vehicle
- Active drivers
- Assigned simulators
- Rig connection status
- Latest laps
- Personal bests
- Session best
- Position changes
- Lap validity
- Flags or session status
- Pending reviews
- Technical warnings
- Start, pause and close session controls
Suggested screenshot: current session, session clock, active drivers, connected rigs, latest laps, best lap, validity, position changes and session controls.
- Current session
- Session clock
- Active drivers
- Connected rigs
- Latest laps
- Best lap
- Validity
- Position changes
See Every Incoming Result
Suggested screenshot: chronological lap feed with driver, simulator, lap time, sectors, personal best, validity and review action.
- Chronological lap feed
- Driver
- Simulator
- Lap time
- Sectors
- Personal best
- Validity
- Review action
The live lap feed provides a chronological view of timing activity.
Each result should retain enough context for an organiser to understand where it came from and whether it should contribute to the competition.
Each timing entry may show
- Timestamp
- Driver
- Simulator
- Session
- Lap number
- Lap time
- Sector times where available
- Personal-best indicator
- Session-best indicator
- Position
- Validity
- Timing source
- Review status
- Notes or warning
Race control users can
- Filter by driver
- Filter by simulator
- Filter by session
- Show valid laps only
- Open the full result
- Flag a result for review
- Invalidate a lap
- Restore an invalidated lap
- Add an official note
Build Leaderboards Around The Competition
Pitwall OS can create separate boards for different events, venues, tracks, vehicles, driver classes and competition periods.
Organisers can control which results are included and when a leaderboard becomes public.
Ranking methods may include
- Fastest valid lap
- Best combined sectors
- Qualifying result
- Race finishing position
- Total race time
- Number of completed laps
- Championship points
- Team points
- Average result
- Custom scoring
Leaderboard controls may include
- Driver class
- Team
- Venue
- Event
- Track
- Vehicle
- Date range
- Competition round
- Approved results only
- Maximum attempts
- Reset schedule
- Tie-break rules
- Public or private status
- Archived status
Suggested screenshot: leaderboard positions, driver, team or class, best lap, gap, attempts, date, approval, filters and publish controls.
- Leaderboard positions
- Driver
- Team or class
- Best lap
- Gap
- Attempts
- Date
- Approval
Manage More Than One Competition At A Time
Suggested screenshot: multiple leaderboard cards with board status, track and vehicle, result count, display theme, reset date and public display link.
- Multiple leaderboard cards
- Board status
- Track and vehicle
- Result count
- Display theme
- Reset date
- Public display link
A venue may operate several leaderboards simultaneously.
One board could cover a monthly GT3 challenge while another shows a corporate event, junior competition, team championship or historic vehicle category.
Pitwall OS is being designed to manage multiple boards from one workspace.
Each board may include
- Board name
- Event
- Track
- Vehicle
- Driver class
- Competition period
- Number of results displayed
- Public display theme
- Sponsor branding
- Reset date
- Archive date
- Publication status
- Display rotation order
Selected public boards can rotate automatically on a display screen.
Turn Results Into Part Of The Experience
A leaderboard should be easy to read from across a venue and flexible enough to reflect the event or customer brand.
Pitwall OS public displays are being designed for venue screens, event displays, race rooms, websites and shared links, and tested at common 1080p and 4K resolutions.
Display customisation may include
- Event logo
- Customer logo
- Sponsor logos
- Background image
- Brand colours
- Light theme
- Dark theme
- Transparent background
- Number of positions
- Position movement
- Driver class
- Track and vehicle
- Competition status
- Session clock
- Fastest lap
- Latest result
- QR code
- Prize information
- Full-screen mode
- Automatic refresh
- Board rotation
Public displays must never expose
- Email addresses
- Telephone numbers
- Private notes
- Full legal names when a display name is required
- Private CRM information
- Internal review notes
- Unapproved results
Suggested screenshot (16:9): branded full-screen leaderboard with positions, driver display names, best laps, gaps, track and vehicle, event branding, latest result and QR code where enabled.
- Branded full-screen leaderboard
- Positions
- Driver display names
- Best laps
- Gaps
- Track and vehicle
- Event branding
- Latest result
Keep Control Of The Official Result
Suggested screenshot: result details, driver, timing source, lap time, validity, review reason, original result, adjustment, approve and reject actions and audit history.
- Result details
- Driver
- Timing source
- Lap time
- Validity
- Review reason
- Original result
- Adjustment
Automated data collection does not remove the need for human review.
Organisers can inspect a result, verify its source, record a decision and preserve the reason for any adjustment.
Review reasons may include
- Invalid lap
- Track limits
- Incorrect driver
- Wrong simulator
- Incorrect vehicle
- Incorrect track
- Disallowed assist
- Duplicate result
- Connection error
- Timing source error
- Manual correction
- Competition rule breach
- Administrative adjustment
Available actions may include
- Approve result
- Reject result
- Invalidate lap
- Restore lap
- Add time penalty
- Apply position penalty
- Reassign driver
- Move to correct class
- Add official note
- Request further review
Every result adjustment records
- Original value
- Updated value
- Reason
- Authorised user
- Date and time
- Connected competition
- Supporting notes
Combine Individual Events Into A Championship
Create a series of rounds and calculate standings across multiple events.
Championships can be organised by driver, team, class, venue or another approved category.
Championship settings may include
- Championship name
- Season
- Rounds
- Events
- Driver classes
- Teams
- Points system
- Bonus points
- Fastest-lap points
- Dropped scores
- Tie-break rules
- Penalties
- Final-round multipliers
- Publication status
Example scoring systems
- Finishing-position points
- Qualifying points
- Fastest-lap bonus
- Participation points
- Team totals
- Custom points table
All custom scoring rules remain visible and reviewable.
Suggested screenshot: championship standings with rounds, driver points, team, class, dropped score, bonus points, gap and next round.
- Championship standings
- Rounds
- Driver points
- Team
- Class
- Dropped score
- Bonus points
- Gap
Publish Results In The Right Format
Suggested screenshot: export format, theme selection, background choice, image preview, result approval status, download button, copy display link and Discord sharing option where available.
- Export format
- Theme selection
- Background choice
- Image preview
- Result approval status
- Download button
- Copy display link
- Discord sharing where available
Approved timing information can be prepared for public displays, reports, websites and social channels.
Export controls must respect workspace permissions and result approval status.
Potential outputs
- CSV results exportAvailable in preview
- Printable result tableAvailable in preview
- PDF reportIn development
- PNG leaderboard imageIn development
- White-background imageIn development
- Black-background imageIn development
- Transparent-background imagePlanned
- Public display linkAvailable in preview
- Embeddable leaderboardPlanned
- Discord updatePlanned
- Website result cardPlanned
- Event report connectionPlanned
Timing Connected To The Wider Event
Pitwall OS Timing is designed as part of a connected motorsport operating platform.
Driver, event and competition information can move between modules without requiring organisers to repeatedly enter the same records.
Timing and Events
Build competitions within an event and connect schedules, participants, sessions and final reports.
Timing and CRM
Connect registered drivers and customer records while protecting private contact information from public displays.
Timing and Assets
Identify which simulator or timing source produced a result and review the operational status of connected equipment.
Timing and Driver
Develop future driver histories showing participation, personal bests, results, classes and progress.
Shared Catalogue Information, Private Competition Data
Pitwall OS can use shared catalogue records for simulator titles, tracks, layouts, vehicles and classes.
Individual workspaces can then create their own events, competitions, timing results and private records using that structured information.
Shared catalogue data
- Simulator title
- Track
- Track layout
- Vehicle
- Vehicle class
- Manufacturer
- General specifications
- Recognised identifiers
Private workspace data
- Events
- Competitions
- Registered drivers
- Lap times
- Results
- Penalties
- Internal notes
- Timing sources
- Simulator assignments
- Private leaderboards
- Unpublished results
Private competition information must never become public without an authorised publication action.
The Right Timing View For Every Role
Competition organisers, race control, simulator operators, drivers and spectators need different information.
Pitwall OS is web-based and is being designed with role-specific interfaces.
Competition management
Competition configuration, rules, classes, scoring and publication.
Race control
Current sessions, drivers, rigs, incoming laps and result review.
Simulator operator
Active driver, rig connection, session and quick support actions.
Registration
Driver check-in, class, team and simulator assignment.
Public display
Approved positions, lap times and competition branding.
Driver view
Personal results, position and competition information where enabled.
Suggested screenshot: race control on desktop, operator view on tablet and driver or registration view on mobile (mobile retains its original aspect ratio).
- Race control on desktop
- Operator view on tablet
- Driver or registration view on mobile
AI Where It Can Improve Understanding
Future AI-assisted features will focus on data quality, competition reporting and useful analysis.
AI must not automatically approve official results, apply penalties or change competition standings without an authorised human decision.
- Identifying possible duplicate results
- Flagging unusual timing data
- Summarising competition activity
- Producing draft result reports
- Creating commentary summaries
- Suggesting driver classes
- Identifying missing competition settings
- Explaining position changes
- Comparing previous events
- Creating social result summaries
- Helping users search results using everyday language
- Identifying improving drivers
Planned development — not currently available
Developed Through Real Competition Workflows
Pitwall OS is developed using a fast, feedback-led and AI-assisted approach. This allows us to build working features, test competition formats, investigate bugs and adapt functionality around genuine requests.
The Timing module is being shaped by experience with simulator venues, fastest-lap competitions, corporate events, public activations and connected simulator systems.
Timing reliability and result integrity require structured testing. New integrations will be introduced carefully and labelled according to their development status.
What does your timing workflow need?
Tell us which simulator platforms you use, how you currently capture results and what makes your competitions difficult to manage.
From Functional Preview To Controlled Beta
The current Timing preview demonstrates competition management, result structures, leaderboard interfaces and planned data connections.
The next major stage is strengthening the backend, validating timing sources and testing result integrity before controlled beta use.
Development priorities
- Secure authentication
- Role-based permissions
- Workspace data separation
- Driver data protection
- Public display privacy
- Timing source authentication
- Input validation
- Duplicate result protection
- Result integrity testing
- Penalty and adjustment audit history
- Session recovery
- Connection loss handling
- Timing bridge testing
- SimHub integration testing
- Import validation
- Leaderboard calculation testing
- Championship points testing
- Tie-break testing
- Cross-browser testing
- Display resolution testing
- Desktop, tablet and mobile testing
- Load and performance testing
- Controlled beta onboarding
- Documentation and support processes
Pitwall OS Timing is currently preview software. Interfaces, integrations and calculation methods may change. Official competition results should be reviewed and approved by an authorised organiser before publication or prize allocation. Pitwall OS Timing is focused on simulator competitions, esports, venue leaderboards, corporate events and motorsport experiences, and is not an FIA-approved, Motorsport UK-approved or certified professional circuit timing system.
Make Every Lap Part Of The Experience
We are inviting simulator centres, esports organisers, motorsport experience providers and event companies to review the Pitwall OS Timing preview.
Request a demonstration, join the future beta programme or tell us about the competition formats and timing systems you need Pitwall OS to support.
Drivers, sessions, lap times and leaderboards connected from registration to final result.
Timing Preview — Frequently Asked Questions
How does driver registration work in the preview?
Drivers can be added individually, imported in bulk, or linked through an event registration flow. Each entry captures the display name, contact details, class, team and any eligibility or entry information the competition requires. In the preview you can also register drivers on the day using the quick event-day registration interface, so results always attach to the correct competitor.
How are results approved before they become official?
Every result enters a review queue before it is published. Organisers can validate lap times, flag suspicious or incomplete entries, identify possible duplicates and apply penalties or adjustments. A result only becomes official once it is explicitly approved, and the approval, reviewer and any changes are recorded in an audit history.
How does leaderboard publication work?
Only approved results appear on published leaderboards. You choose which leaderboard a result belongs to, the ranking method (fastest lap, race result, points, class, team or another scoring system) and the publication status. Leaderboards can be shown on venue displays, event screens, shared links and public pages, with private unpublished results never exposed publicly.
Can I export results and leaderboards?
Yes. The preview supports CSV results export and printable result tables. Branded PNG leaderboard images, embeddable leaderboard widgets and website result cards are in development. Exports contain only approved, published results, so the data you share always matches what is shown on the live leaderboard.