A corporate transportation RFP checklist helps San Francisco teams turn an informal ride request into a comparable vendor brief. Define the service scope, passenger needs, safety standards, coverage, support, billing, and evaluation criteria before you invite bids, so every response answers the same operational questions.
The strongest RFPs do more than ask, “What does a ride cost?” They explain what success looks like for employees, executives, clients, event guests, or conference attendees. That clarity helps transportation providers design a practical solution and gives your procurement team a fair way to compare service, risk, and total value.
What should a corporate transportation RFP include?
A corporate transportation RFP should include the business objective, service scope, operating schedule, passenger profile, vehicle requirements, safety documentation, service standards, technology, billing terms, and vendor response instructions. Put these requirements in one shared document so each bidder responds to the same baseline.
Start with a short background section. Explain whether the RFP covers recurring employee transportation, executive travel, client movement, conferences, offsites, airport transfers, or a combination of services. If the program has multiple use cases, separate them into clear workstreams rather than asking vendors to interpret a broad phrase such as “corporate transportation.”
For San Francisco and the wider Bay Area, describe the geography precisely. Identify office campuses, hotels, airports, event venues, employee neighborhoods, and any cross-bay or peninsula travel that may affect dispatch planning. A vendor evaluating a recurring employee program needs different information than one quoting a two-day conference shuttle.
1. Define the transportation program and success measures
Begin the RFP with measurable business goals, not a preferred vehicle. The goals may include dependable employee arrivals, a polished client experience, simplified event logistics, lower administrative burden, or a repeatable transportation program for several offices.
- State the primary business problem the transportation program must solve.
- List the rider groups, such as employees, executives, clients, speakers, guests, or students.
- Separate recurring service from one-time events and occasional requests.
- Describe how transportation performance will be reviewed after launch.
- Identify the internal owner for operations, procurement, finance, and rider communication.
- Set the desired launch date and any transition requirements from an existing provider.
- Explain which outcomes matter most, such as punctuality, rider experience, reporting, flexibility, or budget control.
Do not promise a percentage or guarantee that has not been agreed internally. Instead, define the measurement method. For example, you can ask vendors to explain how they record scheduled pickup times, actual arrivals, missed trips, substitutions, customer complaints, and corrective actions.
2. Describe routes, service windows, and demand
Vendors can only build a useful response when the RFP gives enough information to understand demand. You do not need a final route map before issuing the document, but you should provide a planning range and identify what may change.
Include pickup and drop-off zones, approximate passenger counts, expected frequency, peak windows, service days, seasonal changes, and special operating conditions. For an employee program, explain whether demand is concentrated around standard work hours, hybrid schedules, shift changes, or major office days. For a conference or event, include venue access rules, session times, hotel blocks, airport arrival patterns, and the expected movement between locations.
San Francisco programs may also require planning for bridge crossings, downtown loading zones, curb restrictions, steep streets, airport staging, and event congestion. Ask vendors to identify how they handle those conditions without turning the RFP into a day-of itinerary. If your team already has route research, link it to the scope or attach it as a separate schedule.
For recurring employee movement, review the guidance in the commuter shuttle service overview and the employee transportation solutions guide as examples of the information a vendor may need to discuss.
3. Set vehicle, accessibility, and passenger requirements
The RFP should describe the transportation outcome and capacity range before it dictates a single vehicle model. Ask each vendor to recommend vehicle types for the stated passenger counts, luggage needs, comfort expectations, and operating environment.
Request information about seating capacity, luggage space, climate control, passenger entry, accessibility accommodations, and the vehicle age or condition standards the bidder can support. If riders will work during travel, ask vendors to explain available onboard amenities without treating an unverified feature as guaranteed. Use the vendor’s response to compare practical fit rather than choosing from a generic vehicle list.
Epic Limousine’s fleet overview can help a prospective buyer frame vehicle questions around group size and service context. A procurement document should still ask the selected vendor to confirm the exact vehicle mix, substitutions policy, and availability for the requested dates.
Include accessibility requirements early. State whether the program needs lift access, mobility-device accommodation, service-animal accommodation, or additional boarding time. Ask bidders to explain their process for confirming accessible equipment and communicating any limitations before service begins.
4. Request safety, insurance, and chauffeur information
Safety and compliance questions belong in the main RFP, not as an afterthought during final negotiations. Ask every bidder to identify its operating authority, insurance coverage, driver screening practices, training, vehicle inspection process, incident response, and documentation renewal process.
- Current insurance certificates and coverage limits relevant to the proposed service.
- Driver hiring, background screening, licensing, training, and ongoing review practices.
- Vehicle inspection, maintenance, cleaning, and pre-trip readiness procedures.
- Emergency response and escalation procedures for collisions, delays, breakdowns, or medical events.
- Subcontractor disclosure and the standards applied to any partner operator.
- Documentation retention, audit support, and the process for notifying the client of a material change.
- Named operational contacts for urgent dispatch and account-level escalation.
Ask for evidence and an explanation of how the vendor keeps documentation current. Do not award points simply because a bidder attaches a certificate. Your evaluation should consider whether the proposed controls fit the size, frequency, geography, and passenger profile of the program.
For additional context on company background and operating approach, review Epic Limousine’s About Us page. Your RFP should still require each responding vendor to provide its own verifiable information.
5. Define service levels, communication, and backup capacity
A transportation RFP should convert the word “reliable” into service expectations that can be monitored. Ask bidders to propose service levels for on-time performance, advance confirmations, dispatch response, driver communication, vehicle substitutions, and issue resolution.
Specify who receives trip confirmations, when changes must be reported, and how a rider or coordinator reaches dispatch after hours. For an event, ask how the vendor handles changes to a manifest, delayed flights, early program releases, or a venue that changes its loading instructions. For an employee shuttle, ask how the provider reports missed trips, vehicle substitutions, ridership changes, and recurring route issues.
Backup capacity deserves its own section. Ask whether the vendor maintains spare vehicles, a backup driver pool, partner resources, or another contingency plan. Require the response to explain the notification sequence and the decision-maker who authorizes a substitute. This reveals more than a general promise to “provide excellent service.”
For event-specific requirements, compare the service context in the corporate event transportation service and convention shuttle service pages. These are useful reference points for separating event logistics from recurring commuter operations.
6. Ask for technology, reporting, and account management
Technology should support a clear operating process, not replace one. Ask bidders how coordinators request trips, receive confirmations, track changes, access manifests, communicate with dispatch, and review performance reporting.
Useful questions include whether the vendor can provide a single account contact, recurring billing support, trip-level reporting, usage summaries, and a documented escalation path. If your company has data-security or privacy requirements, state the minimum standard and ask the vendor to describe what information it stores, who can access it, and how long it is retained.
For a recurring program, request a sample monthly report or a description of the fields it can include. For executive or client travel, ask how the account team protects privacy, handles last-minute changes, and coordinates with authorized assistants. For an event, ask how the coordinator receives a current manifest and real-time operational updates without depending on scattered text messages.
If airport service is part of the scope, link the RFP to the relevant corporate sedan service guidance and describe the airport coverage and flight-monitoring expectations that bidders should address. Keep those requirements separate from the broader vehicle and route sections.
7. Make pricing responses comparable
Do not ask vendors for a single blended number when the service contains different trip types. A comparable pricing response separates recurring service, event work, airport transfers, additional hours, waiting time, tolls, parking, overtime, cancellations, and approved changes.
Ask each vendor to state what is included, what is excluded, how invoices are supported, and when rate changes may occur. If your organization uses purchase orders, corporate cards, or recurring billing, describe that process. If you expect recurring service, request a pricing model that shows the assumptions behind the proposal without requiring a vendor to guess at final ridership.
- Base hourly, trip, route, or program pricing structure.
- Minimum service time and overtime treatment.
- Waiting, deadhead, parking, toll, airport, and venue charges.
- Cancellation, rescheduling, no-show, and early-release terms.
- Extra vehicle or driver charges when demand changes.
- Invoice detail, billing cadence, payment terms, and dispute process.
- Conditions under which proposed rates can be reviewed or adjusted.
Never evaluate price without comparing the service assumptions behind it. A lower number may omit coverage, backup capacity, reporting, or administrative support that your team needs. The RFP should make those differences visible.
8. Use a vendor scorecard and response format
A scorecard gives stakeholders a consistent way to evaluate each response. Share the response format and major categories in advance so bidders know how the decision will be made.
| Evaluation category | What to compare |
|---|---|
| Operational fit | Coverage, schedule, capacity, vehicle recommendations, and ability to handle the stated use cases. |
| Safety and compliance | Insurance, driver standards, inspections, incident response, and documentation. |
| Service quality | Communication, dispatch, backup capacity, escalation, and proposed performance measures. |
| Technology and reporting | Booking workflow, confirmations, trip records, reporting, privacy, and account access. |
| Commercial terms | Pricing transparency, billing, cancellation terms, contract flexibility, and total value. |
| Experience and references | Relevant corporate programs, local operating knowledge, and references that match the scope. |
Ask for a short executive summary, a completed requirements matrix, supporting documents, pricing assumptions, implementation plan, and references. A consistent response format reduces the chance that a polished proposal wins simply because it is easier to read.
For corporate event and group requirements, the corporate bus rental service and luxury group transportation guide provide useful examples of service questions to keep separate from the procurement scorecard.
9. Set an RFP timeline and next steps
A realistic timeline helps vendors produce accurate responses and gives your internal team time to evaluate them. Include the release date, deadline for clarification questions, answer date, proposal deadline, finalist interviews, selection date, contract target, implementation period, and expected service start.
State the submission format, file naming rules, point of contact, and whether late responses will be accepted. If you plan to conduct a site visit, route review, presentation, or vehicle inspection, include that step in the schedule. Tell bidders what happens after submission so the process is clear and fair.
Before issuing the RFP, complete an internal review. Confirm that finance understands the pricing template, operations can answer route questions, legal has reviewed required terms, and the executive sponsor agrees with the evaluation criteria. A short alignment meeting can prevent conflicting answers after vendors begin asking questions.
For a San Francisco conference, the Moscone Center shuttle planning guide can help your team identify venue-specific questions. Keep event details as an example or attachment unless the RFP is specifically for that conference.
What questions should you ask transportation vendors?
Ask questions that reveal how the provider will operate the requested program, not only what vehicles it owns. The following questions can be placed directly into a corporate transportation RFP or used during finalist interviews.
- Which parts of the proposed service can you operate directly, and which require a disclosed subcontractor?
- How do you confirm vehicles and drivers before each recurring route or event?
- What happens when a vehicle becomes unavailable shortly before pickup?
- How does dispatch communicate with the client during a delay or service disruption?
- What operational and invoice reports will the client receive, and how often?
- How do you support accessibility requests and communicate equipment limitations?
- Which assumptions drive the pricing response, and how are changes approved?
- Can you provide references for a program with similar passenger volume, geography, and service frequency?
Use the answers to test fit against your stated requirements. A vendor that gives a detailed, direct response is easier to evaluate than one that relies on broad marketing language.
How do you compare corporate transportation RFP responses?
Compare responses in the same order as your scorecard, verify assumptions, and document questions before selecting a finalist. Treat service quality, safety, communication, backup capacity, reporting, and commercial terms as connected parts of the decision.
First, mark each requirement as met, partially met, not met, or requiring clarification. Next, normalize pricing so the same service assumptions are being compared. Then review references and confirm that the proposed account team, dispatch model, and local coverage match the response. Finally, record the reason for the selection and the requirements that must carry into the agreement.
Do not let a low headline rate hide an incomplete response. If a bidder leaves a major requirement unanswered, ask for clarification before scoring it. If the answer changes the scope or price, update the comparison record for every finalist.
RFP checklist for San Francisco corporate teams
Before sending the document, confirm that the RFP answers the questions below and gives vendors enough information to respond without guessing.
- Business objective and rider groups are clearly defined.
- San Francisco and Bay Area service geography is described.
- Trip types, routes, schedules, frequency, volumes, and seasonality are included.
- Vehicle capacity, passenger comfort, accessibility, and luggage requirements are stated.
- Insurance, driver screening, training, inspection, and incident-response documentation is requested.
- On-time, communication, dispatch, backup, and escalation expectations are measurable.
- Technology, privacy, reporting, account management, and invoice requirements are explained.
- Pricing assumptions, included items, exclusions, change terms, and cancellation rules are separated.
- Response format, scorecard, questions deadline, proposal deadline, and selection timeline are included.
- Internal stakeholders agree on the scope, evaluation method, and approval path.
This RFP scope is intentionally different from a post-award operational checklist. Once a vendor is selected, a separate implementation plan can cover route details, rider communications, manifests, and day-of procedures. That separation keeps procurement requirements clear and gives the operations team a better handoff.
Ready to issue your transportation RFP?
A well-scoped RFP helps your team compare transportation providers on safety, reliability, local operating fit, service support, and transparent commercial terms. If you are defining a corporate shuttle, executive program, airport transfer, conference movement, or Bay Area event scope, share the requirements and requested dates so the right service model can be evaluated.
For direct assistance, contact Epic Limousine through the Contact Us page or call (415) 799-2744.