A rollout for 500 employees is not just a matter of sending 500 invitations. Before access is opened, the organisation needs to decide who is eligible, what employees are expected to do, how they will get help and how the rollout will be checked.
The exact steps depend on the platform and the organisation’s policies. Treat this as a planning framework, then confirm the available account, access, booking and reporting processes with the provider.
First, distinguish employee onboarding from driver onboarding
In this guide, employee onboarding means helping staff access and use a corporate taxi booking arrangement. It can include explaining who may book, what information to provide, which rules apply and where to ask for help.
That is different from onboarding taxi drivers to a driver app. Drivers may need a separate workflow, instructions and checks, depending on the provider and operator. Do not assume that an employee invitation process also covers drivers, or vice versa. See our guide to taxi driver app onboarding for the separate driver-side process.
1. Name an owner and agree the rules
Choose one person to coordinate the rollout and make clear who can approve decisions. The owner may need input from teams responsible for travel or operations, procurement, IT, finance, employee communications and support. The right participants depend on how the organisation manages travel and purchasing.
Before inviting anyone, settle the rules employees need to know. For example: who is eligible, what kinds of journeys may be booked, how bookings should be made or changed, what information is required, how cancellations are handled, and where employees should direct questions. Confirm any policy or approval requirements internally rather than expecting the platform to define them for you.
Write these decisions in plain language. If a rule is unresolved, identify who will decide it and when; do not leave employees to interpret competing guidance.
2. Decide who gets access and what the process requires
List the intended users and decide how they will be identified, invited or otherwise given access. Ask the provider what employee information is needed, who can create or change accounts, what happens when someone changes role or leaves, and what access controls are available. Do not assume that invitations, bulk uploads, single sign-on or automated account changes are supported; confirm each requirement directly.
Also agree how the organisation will handle employees who cannot complete the standard access process. Provide a named support route or an alternative process if one is appropriate to your organisation. Keep access instructions separate from sensitive account information, and follow your internal data-handling requirements.
3. Prepare the employee instructions before launch
Create a short set of instructions employees can use at the point they need to book. Cover:
- who may use the arrangement and for what purposes;
- how to obtain access and where to go if access does not work;
- what journey details to provide;
- how to make, amend or cancel a booking under your process;
- what employees should do if a journey or booking needs attention; and
- where to find the relevant travel policy and support contact.
Use the actual workflow agreed with the provider. If the platform’s labels or steps differ from the guidance, update the instructions before rollout. Avoid promising response times or outcomes unless the organisation and provider have agreed them.
4. Test the whole journey with a representative group
Before opening access to all 500 employees, test the process with a small group that reflects the people and situations the programme is intended to serve. The purpose is to find unclear instructions, access problems and policy gaps—not to claim that a small test proves every case will work.
Ask testers to follow the written instructions from start to finish. Include the ordinary booking path and relevant exception cases identified by your organisation, such as a change or cancellation. Check that employees know where to get help and that the people assigned to support them understand how to handle questions. Confirm which parts of the workflow are managed by your organisation and which depend on the provider.
Record issues, assign an owner to resolve each one and update the instructions or process. If an important policy decision or access issue remains unresolved, pause expansion until the responsible owner has decided how to handle it.
5. Choose a rollout pattern that fits your readiness
There is no universally correct way to release access to 500 employees. A single launch may be appropriate if the rules, access process, communications and support arrangements are ready and can be managed together. A staged rollout may be preferable if the organisation wants to learn from an initial group, has distinct employee groups, or needs to confirm support arrangements before expanding.
If you use stages, decide in advance how groups will be selected, what must be checked before the next group is invited, and who can approve the expansion. The group size and pace should reflect your internal capacity and the provider’s confirmed process; they cannot be inferred from the headcount alone.
Whichever approach you choose, give employees a clear launch message with the effective date, eligibility rules, access instructions, booking guidance and help route. Make sure managers or other internal contacts know where to direct questions rather than creating conflicting instructions.
6. Monitor issues and review the rollout
During rollout, keep a simple record of access problems, repeated questions, booking-process issues and unresolved policy decisions. Assign each issue to an owner and communicate any changes to the people affected. Agree beforehand who will review this information and when a decision about the next step will be made.
After launch, review the rollout against the organisation’s own aims. You might examine whether intended employees received usable instructions, whether access problems were resolved through the planned route and which parts of the process caused confusion. Select measures that can be collected appropriately and that are relevant to the programme; do not treat a high invitation count alone as proof that employees can use the service successfully.
Use the review to update guidance, access procedures or support arrangements. Confirm any platform-specific changes with the provider before telling employees that a capability or process has changed.
A practical checklist before inviting employees
- Is there one accountable rollout owner and a clear decision-making route?
- Are eligibility, journey rules and internal approvals agreed?
- Has the provider confirmed the supported access and account-management process?
- Are employee instructions based on the actual booking workflow?
- Has a representative group tested the process and reported issues?
- Are support ownership and escalation routes clear?
- Is the organisation ready to launch everyone at once, or should it expand in stages?
- Is there a review plan for resolving issues and improving the guidance?
A 500-person rollout is easier to manage when access, guidance, ownership and support are planned together. Confirm the platform’s actual capabilities with its provider, and keep employee access planning distinct from the separate process of onboarding taxi drivers.