Racing Team Coordinator: Difference between revisions
No edit summary |
Beefed up this 'use case' with material from my Racing 88 case study. Fair cherry picky right now but its a start and at least some substance |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
EventR was designed | EventR was designed initially for Formula 1, based on the gruelling demands of getting 120+ people to 24 races around the world week in week out. This use case requires: | ||
[[EventR Team Guide]] | [[EventR Team Guide]] | ||
| Line 7: | Line 7: | ||
[[EventR Expense Guide]] | [[EventR Expense Guide]] | ||
We recommend [[How to add users to EventR via a spreadsheet|users are added via Excel SpreadSheet]]. Once added, the coordinator has many features to | <big>'''Adding Users'''</big> | ||
We recommend [[How to add users to EventR via a spreadsheet|users are added via Excel SpreadSheet]]. Once added, the coordinator has many features available to enable full logistic support for the team, from pick up to drop off. | |||
<big>'''Control Approach'''</big> | |||
Depending on the scale of the race team, there are many options to configure. Some teams prefer a [[Locking down EventR updates|locked down coordinator environment]], others prefer the [[Using EventR in a fully collaborative way.|ad-hoc "Guerrilla" approach]] that can work for a small team to collaboratively work together to ensure nothing is missed. EventR Enterprise also supports a hybrid of these - so you can easily find the pattern that works for you. | |||
'''<big>Itinerary Timetabling</big>''' | |||
Separate itineraries can be created for each race event, and within the itinerary a timetabled list of activities with locations attached can be created. EventR supports [[Calendar Syncing|device calendar sync]] as well to integrate with existing workflows, and the complex race season can be simplified into mangeable chunks with EventR's powerful features. | |||
<big>'''Accommodation Approaches'''</big> | |||
The [[Rooming Lists|rooming lists]] feature can be utilised in this context to accommodate the entire travelling race team in an efficient manner. | |||
'''<big>User Tags</big>''' | |||
By tagging team members by department, bulk addition can be used to add subteams and specific departments to their respective transports, accommodations or activities. | |||
Latest revision as of 14:24, 3 July 2026
EventR was designed initially for Formula 1, based on the gruelling demands of getting 120+ people to 24 races around the world week in week out. This use case requires:
EventR Enterprise Coordinator Hub Features
Adding Users
We recommend users are added via Excel SpreadSheet. Once added, the coordinator has many features available to enable full logistic support for the team, from pick up to drop off.
Control Approach
Depending on the scale of the race team, there are many options to configure. Some teams prefer a locked down coordinator environment, others prefer the ad-hoc "Guerrilla" approach that can work for a small team to collaboratively work together to ensure nothing is missed. EventR Enterprise also supports a hybrid of these - so you can easily find the pattern that works for you.
Itinerary Timetabling
Separate itineraries can be created for each race event, and within the itinerary a timetabled list of activities with locations attached can be created. EventR supports device calendar sync as well to integrate with existing workflows, and the complex race season can be simplified into mangeable chunks with EventR's powerful features.
Accommodation Approaches
The rooming lists feature can be utilised in this context to accommodate the entire travelling race team in an efficient manner.
User Tags
By tagging team members by department, bulk addition can be used to add subteams and specific departments to their respective transports, accommodations or activities.