PCA Club Racing: An Incident Management Workflow Built on Hyperlogs
Project overview: race incident management for PCA Club Racing
As a Hyperlogs partner, we built the race incident management workflow for Porsche Club of America (PCA) Club Racing, then onboarded and trained the club. Stewards, drivers and scrutineers now file every incident report in one connected system on web, iOS and Android instead of paper forms and email.
About PCA Club Racing
The Porsche Club of America (PCA) runs Club Racing events for its members. A season has about 24 race weekends, each with 10 to 30 incidents, and several hundred drivers on the roster. Every incident has to be logged, heard from both sides, checked against the cars and closed by the Steward.
The challenge: paper forms and scattered email
Before the project, incident reporting ran on paper PDF forms and email threads. Driver statements, damage notes and photos arrived in different places, and the Steward had to piece each incident together by hand. Across 700+ incidents a season, that added up to a lot of chasing and slow decisions.
Our role: Hyperlogs partner services
We built Hyperlogs, and we deliver implementation services under the Hyperlogs partner program. For PCA Club Racing we did three things:
- Built the incident management workflow. We turned PCA's requirements into 6 forms, 3 automated workflows and a dashboard on Hyperlogs.
- Onboarded the club. We set up trial users, wrote an onboarding document, recorded an onboarding video and set up PCA's admin accounts.
- Trained the officials. We wrote a user guide for web and Android (v1.0, June 16, 2026) and supported PCA through user testing.
How the incident workflow works
- Event setup. The Steward sets up the event and the driver roster.
- Incident logging. The Steward logs each incident: session, corner, flag, track condition, a video link, the cars involved, and checkboxes such as at-fault and metal-to-metal contact.
- Driver statements with no login. Each driver involved gets an emailed link to file a statement, with a diagram and a signature.
- Damage reports. Scrutineers log damage zones and photos for each car.
- PDF reports and closing. Each submission becomes a PDF report sent to the Steward, who reviews it and closes the incident.
- Dashboards. Dashboards sit on top of the incident data.
It runs on the web, iOS and Android.
What changed for PCA Club Racing
- Incident review time cut by 70% or more (our estimate).
- No more paper forms or email chains.
- Every report in one place for the Steward.
- Incidents close in days instead of weeks.
- Built for a full season: 700+ incidents across about 24 race weekends and several hundred drivers.
Timeline
- September 2025: first Hyperlogs demo for PCA Club Racing.
- March 2026: refresher call on March 5 and a custom demo on March 31.
- April 29, 2026: PCA shares its requirements spreadsheet.
- May 28, 2026: near-production demo.
- June 16, 2026: user testing, with a PCA official playing a full race weekend as the scrutineer, and the v1.0 user guide.
- June 2026: live.
Why a workflow platform instead of custom software
Building on a workflow platform meant no long custom build: we went from PCA's requirements spreadsheet on April 29 to a near-production demo on May 28. When a team does need custom work, we offer software development, dashboard development and QA and testing.
Read the Hyperlogs case study on PCA Club Racing for how the club uses the platform day to day.
Still running incident reports on paper and email?
Tell us who files reports, who reviews them and where things get stuck. On a 30-minute call we will show you how we would set it up.
Related
Project inquiry
Tell us what you are trying to ship
Response within 1 business day
The Challenge
Our Solution
Technologies Used
Results & Impact
Impact
Client Testimonial
Excellent test drive today. Appreciate the work on this system.
Services Provided
Why Maxiom?
- Software since 2002
- $100M+ in contract value
- 221+ clients
- Top-rated on Clutch
Frequently asked questions
What did Maxiom do for PCA Club Racing?
Under the Hyperlogs partner program, we built the incident management workflow on Hyperlogs (6 forms, 3 automated workflows and a dashboard), then onboarded and trained PCA's officials.
How much time does the workflow save?
We estimate it cuts incident review time by 70% or more, because statements, damage reports and photos arrive as complete PDF reports in one place instead of across paper forms and email threads.
How does a driver file a statement?
Each driver involved gets an emailed link to file a statement with a diagram and a signature. No login is needed.
What does the Steward record for each incident?
The session, corner, flag, track condition, a video link, the cars involved, and checkboxes such as at-fault and metal-to-metal contact.
What devices does it run on?
The web, iOS and Android.
How was PCA onboarded and trained?
We set up trial users and admin accounts, wrote an onboarding document, recorded an onboarding video and wrote a user guide for web and Android. A PCA official then tested a full race weekend as the scrutineer before go-live in June 2026.
What is the relationship between Maxiom and Hyperlogs?
We built Hyperlogs, and we deliver implementation, onboarding and training services to Hyperlogs customers through the Hyperlogs partner program.
Can Maxiom build a workflow like this for our organization?
Yes. If your team collects reports from several people and one person has to review and close them, we can set it up. Tell us how it works today and we will show you how we would build it.