Ringers, one race wonders, outsiders, guest drivers… whatever you want to call them, they have been a part of what we do. Is that good or bad? Is it a black and white question? To answer, let’s take a peek at the past.
2017 was the final year that the Majors was “just” the Pacific Majors (hence our web address… really need to update that).
That was the 4th full season of the Majors and the only season in our history where everyone had to pay to race (either season pass or individual race ticket). Why did we make everyone pay that year? Why did we allow free entrants afterwards?
Well, the simplest answer is numbers. By 2017 we had about 120 season pass holders and those combined with the people who would come in and pay to race here and there, we had about 200 drivers score points during the year. For a series that was restricted to just six clubs this was really good and we felt great about having multiple splits every race. We didn’t need to offer free racing to fill the field and it...
The iRacing Endurance special events are particularly challenging to organise for larger teams because they often involved multiple cars for the team,often different types and drivers with different abilities, time constraints etc.
Within BAM and Kinetic, we've been through a number of different ways and processes to organise them and we've finally settled on a process I'm comfortable that works as well as possible.
The process can be broken down into 4 phases
- Planning - this sets up the event, finds out which drivers are available, what cars they want to drive, which timeslot (iRacing's multiple timeslots for races are often a complication) and allows the team manager to decide on a provisional line-up of cars and drivers
- Scheduling and Testing - this prepares for the event, get setups created, tested and finalised, determines race strategies (stint lengths, issues like can tyres be double stinted) etc and allows the car captains to schedule stints for each driver/spotter, who registe...
A vital part of how a team operates and is managed is about communications. The 1st thing to understand is all the different types of communications that need to be done in teams:
- Policy / Organisation / Structure information
- Team Membership (who are the drivers / what do they do)
- Event organisation
- File storage (paints, setups, documents)
- Event organisation - both ad-hoc ones and planned events
- Feedback on setups, tips, race strategies etc
- In-race communications (spotting, driver to driver comms)
- General chatting (both text and audio)
Traditionally, things were fairly simple - teams used a website/forum to do pretty much everything written and Teamspeak to do audio and some kind of server storage (Google drive, Dropbox) for files. But, Discord has clouded it somewhat because it can be used for both text and audio (and to some degree file storage).
There's no perfect solution - you just need to decide what's best for you. As an example, here's what we do at Kinetic: