Sector pursuit field 55 · Transport, logistics and industry
Our basic working position: This is the first position we would test—not the final bid position. It changes with every buyer organisation, procurement or commercial team, evaluator group, operational user, budget owner and other stakeholder. The live opportunity, people, documents, conversations and clarifications determine the final pursuit.
Match the support to the pursuit
Start with the work the opportunity actually needs.
These are three useful routes—not a fixed package. The live documents, bidder position, deadline and buyer decision determine the final support.
Bid & Tender Writing
Turn approved network, user, operation, asset and mobilisation evidence into clear transport answers.
See when to use this serviceEnd-to-End Bid Management
Integrate network, users, operations, assets and mobilisation across transport pursuits.
See when to use this serviceSocial Value & Carbon
Make accessibility, carbon, employment and community commitments part of transport delivery.
See when to use this servicePublic and private contract pursuit
Same capability. Different buying system.
A transport and mobility pitch cannot be carried unchanged from a published public competition into a private sourcing decision. The solution may be similar, but authority, visibility, negotiation, risk appetite and the people shaping the decision can be very different.
Follow the declared route—and the decision behind it.
Buyer settings evidenced in the sector dossier: South Yorkshire Mayoral Combined Authority; Cumberland Council; Nexus.
Start with the live notice, conditions, evaluation model, timetable, clarification rules and contract.
- Define mode, passengers, geography, timetable or demand model, booking channels, vehicle, driver, assistance, fares and authority interface. Select evidence matching that service. A conventional route does not prove accessible DRT technology, and a pilot does not prove large-framework coverage.
- Verify buyer, regime, lot, award method, operator role, required registrations, contract duration, route information, participation conditions and latest amendments. Model call-off and utilisation uncertainty. Treat every licence or insurance assertion as a dated evidence item.
Find the real buying group and approval path.
Operators, employers, developers and investors buy mobility platforms, shuttle services, concessions and integrated transport partnerships.
- Establish who initiated the purchase, who owns the budget, who can veto it and how procurement, legal and finance will shape the agreement.
- Test incumbent relationships, negotiation room, approval gates, commercial risk and the evidence each decision-maker needs.
- Use conversations lawfully available in the process to refine the proposition; do not assume a private RFP reveals every deciding factor.
The “buyer” is rarely one person.
Align passengers, operations, local authorities, property, digital, finance, accessibility and safety owners.
Sector roles to test: South Yorkshire Mayoral Combined Authority; Cumberland Council; Nexus; Surrey County Council; client technical, commercial, legal and governance owners.
The bidder is ready; the response needs precision.
Use focused writing when the transport and mobility offer, price, delivery model, responsibilities and approved evidence already withstand challenge. We then align them to the question, stakeholder, evaluation logic and response architecture without pretending prose can repair the underlying business.
Strengthen the bidder, then build the bid.
Use end-to-end management when qualification, solution design, process, team, partners, evidence, commercial logic or mobilisation still needs work. The pursuit becomes a project: gaps are exposed, capability is implemented, owners decide and the written answer grows from a stronger operating position.
Candidate lifecycle movements: Shape → Prove → Decide → Deliver. Useful operating lenses to test include Zanshin, independent review and handover readiness. They are selected proportionately; they are not certification claims or a substitute for the live contract.
Explore Achmed Esser's Assurance & Delivery Lattice →Relevant practice here can include capture planning, teaming, compliance, technical-commercial alignment, reviews and post-award transition. We apply the parts that fit the pursuit rather than forcing every competition through one template.
See APMP's winning-business lifecycle →Mobility contracts combine services, users, vehicles and platforms
Evidence-linked insight · What this changes The current sample includes secured routes, two demand-responsive models and assisted passenger transport. Some contracts combine booking software, drivers and vehicles; others allocate routes or care-related capability across many suppliers. These are different operating systems, not interchangeable bus references. [ 011, 012, 013, 014 ]
Where we would start first Define mode, passengers, geography, timetable or demand model, booking channels, vehicle, driver, assistance, fares and authority interface. Select evidence matching that service. A conventional route does not prove accessible DRT technology, and a pilot does not prove large-framework coverage. [ 011, 012, 013, 014 ]
Public transport procedure and operating authority both matter
Evidence-linked insight · What this changes Notices range from single tenders to multi-lot and open-framework arrangements. Procurement compliance does not replace operator licensing, route registration or service-specific approvals. Framework value and extension options are not committed mileage or revenue. [ 001, 002, 003, 004, 011, 012, 013, 014 ]
Where we would start first Verify buyer, regime, lot, award method, operator role, required registrations, contract duration, route information, participation conditions and latest amendments. Model call-off and utilisation uncertainty. Treat every licence or insurance assertion as a dated evidence item. [ 001, 002, 003, 004, 011, 012, 013, 014 ]
Transport powers and operating rules need territorial precision
Evidence-linked insight · What this changes The legislative sources cover public passenger vehicles and local transport functions but exact application changes with country, authority, mode and service. A rural English bus pilot, a metropolitan secured route and assisted transport cannot be governed through one unchecked summary. [ 003, 004, 005, 006, 007, 011, 012, 013, 014 ]
Where we would start first Build an applicability schedule naming operator, transport authority, Traffic Commissioner or other decision-maker, vehicle category, registration, route and passenger group. Obtain transport and legal review for exemptions, cross-boundary services or mixed operating models. [ 003, 004, 005, 006, 007 ]
The network proposition must connect need to a deliverable service
Evidence-linked insight · What this changes Fixed routes optimise known corridors and timetables; DRT uses dynamic requests and coverage rules; assisted transport may allocate individual journeys. Demand, interchange and passenger constraints determine whether each design is viable. [ 011, 012, 013, 014 ]
Where we would start first Show zones or routes, hours, stops, booking window, eligibility, vehicle types, capacity, dead mileage, layover, interchange and fallback. Use buyer data with caveats and test peaks, dispersed trips, no-shows, disruption and accessibility before promising coverage. [ 011, 012, 013, 014 ]
Registered service and contract timetable must stay aligned
Evidence-linked insight · What this changes Cumberland explicitly requires legally necessary registrations and approvals. Timetable or zone change can affect public information, operating authority, vehicles, staff and subsidy. A contract instruction may not by itself complete a regulatory change. [ 003, 004, 012, 013 ]
Where we would start first Create a route-change gate linking client approval, registration, notice periods, scheduling, driver duties, passenger communications, ticketing and commencement. Record the controlling version. Reserve statutory decisions to the competent body and price additional change cycles. [ 003, 004, 012, 013 ]
Accessibility must work across vehicle, information and assistance
Evidence-linked insight · What this changes Equality, vehicle-accessibility and accessible-information sources address related but separate duties. Passenger needs also extend to booking, stops, transfers, communication and staff behaviour. A compliant vehicle does not guarantee an accessible journey. [ 008, 009, 010, 012, 014 ]
Where we would start first Map passenger journeys with wheelchair, sensory, cognitive, communication and digital-exclusion scenarios. Evidence vehicle features, audible and visible information, reasonable adjustments, alternative booking and staff competence. Involve users without treating consultation as formal legal approval. [ 008, 009, 010, 012, 014 ]
Assisted passengers require individual and service-level controls
Evidence-linked insight · What this changes Surrey's notice includes journeys for students and people with health or complex needs, potentially requiring care plans, additional training or regulated activity. Transport performance cannot be separated from safeguarding, handover and authorised assistance. [ 008, 014 ]
Where we would start first Define eligibility input, passenger profile, consent, pickup and handover, escort, medication boundary, missed collection, distress, incident and confidentiality. Verify regulated roles where specified. Never infer a care capability from a driver licence or general passenger experience. [ 008, 014 ]
Safeguarding must shape allocation and daily dispatch
Evidence-linked insight · What this changes Passenger transport can involve children and vulnerable adults in one-to-one or shared journeys. Risk depends on driver vetting, escort arrangements, route changes, communication and incident escalation. A recruitment check is one control, not the whole system. [ 008, 014 ]
Where we would start first Provide role-based safer recruitment, training, identity, allocation rules, lone-working controls, contact restrictions, concern reporting and referral. Link dispatch changes to safeguarding review. Obtain specialist advice and align with the buyer's policy and contractual authority. [ 008, 014 ]
Digital booking is part of the operating control loop
Evidence-linked insight · What this changes The South Yorkshire and Cumberland models rely on software alongside vehicles and drivers. Booking, scheduling, eligibility, mapping, payment and passenger messages influence dispatch. Platform uptime alone does not demonstrate transport reliability. [ 011, 012 ]
Where we would start first Describe channels, user accounts, accessibility, rules engine, optimisation constraints, manual override, API or timetable data, monitoring, incident recovery and support. Test loss of mobile data, duplicate requests, cancellations and service saturation with an operable manual fallback. [ 008, 010, 011, 012 ]
Schedules need legal, human and passenger feasibility
Evidence-linked insight · What this changes Running time, traffic, boarding assistance, breaks, depot moves and charging or fuelling affect feasible duties. Optimisation that ignores these constraints produces missed pickups or unsafe pressure. Rural DRT adds sparse demand and repositioning uncertainty. [ 003, 011, 012, 013, 014 ]
Where we would start first Show assumptions for travel time, dwell, recovery, driver duty, vehicle availability and assistance. Simulate peaks and disruptions. Give dispatchers escalation and override authority, then measure planned versus actual performance to improve parameters. [ 003, 011, 012, 013, 014 ]
Vehicle allocation should follow passengers and duty cycles
Evidence-linked insight · What this changes Current notices require vehicles from cars to coaches and different minibus or bus models. Seats, wheelchair spaces, access, luggage, range and depot compatibility affect service. Nominal fleet count does not equal available compliant capacity. [ 009, 011, 012, 013, 014 ]
Where we would start first Create a vehicle-to-duty matrix with approval, capacity, accessibility, condition, range, inspection, backup and restriction. Evidence committed vehicles and delivery dates. Separate owned, leased and subcontracted availability, and prohibit unapproved substitution. [ 003, 009, 011, 012, 013, 014 ]
Driver plans need competence, resilience and realistic duties
Evidence-linked insight · What this changes Mobility contracts depend on licensed, trained and available drivers across early, late, weekend and emergency work. Assisted transport and DRT add passenger-support and technology tasks. Headcount without roster coverage or attrition allowance is weak evidence. [ 003, 008, 011, 012, 013, 014 ]
Where we would start first Map shifts, licence category, checks, training, local knowledge, assistance competence, absence and standby. Reconcile duties with schedule assumptions. State whether people are employed, agency or subcontracted and verify commitments rather than naming speculative capacity. [ 003, 008, 011, 012, 013, 014 ]
The control room must join passenger, driver and client decisions
Evidence-linked insight · What this changes Real-time operation handles late running, breakdowns, missed passengers, no-shows, road closures, safeguarding concerns and booking faults. Fragmented channels can leave no person authorised to reprioritise journeys or notify affected users. [ 011, 012, 013, 014 ]
Where we would start first Define operating hours, event triage, dispatch authority, passenger contact, escalation, client notification and evidence capture. Run scenarios for vulnerable passenger no-show, vehicle failure and widespread disruption. Preserve decisions and recovery time for review. [ 011, 012, 013, 014 ]
Safety assurance needs journey and operating evidence
Evidence-linked insight · What this changes Passenger comfort and safety are explicit in the Cumberland notice. Safe delivery depends on roadworthy vehicles, competent drivers, boarding, securement, route choice, fatigue, incidents and learning. Absence of reported harm is not proof that every control worked. [ 003, 012, 014 ]
Where we would start first Set inspection, defect, driver fitness, wheelchair securement, boarding, collision, near-miss and emergency processes with accountable roles. Use leading and lagging measures. Reserve statutory investigation and enforcement conclusions to the relevant authority. [ 003, 008, 009, 012, 014 ]
Passengers need accurate information before and during travel
Evidence-linked insight · What this changes Accessible information regulations, booking messages and route communications interact. Delay or cancellation is especially consequential where passengers depend on connections, carers or school handover. Conflicting app, stop and call-centre messages damage trust. [ 008, 010, 011, 012, 013, 014 ]
Where we would start first Establish one source for service status, timetable, accessibility and disruption messages with approval and update clocks. Provide digital and non-digital channels. Measure successful receipt and resolution, not simply messages sent. [ 008, 010, 011, 012, 013, 014 ]
Mobility services must complement surrounding networks
Evidence-linked insight · What this changes Cumberland states its hybrid service should complement fixed bus and rail. Transfers depend on schedules, stop locations, ticket or eligibility rules and disruption information controlled by different parties. Claimed integration can fail at everyday interfaces. [ 005, 006, 007, 012 ]
Where we would start first Map interchange points, minimum connection, data exchange, through information, payment boundaries and missed-connection responsibility. Test the service against live network constraints. Describe collaboration without implying control over another operator's timetable. [ 005, 006, 007, 012 ]
Mobility data needs passenger protection and operational lineage
Evidence-linked insight · What this changes Bookings, locations, eligibility, care notes, payments and performance records can be personal and sensitive. Aggregated demand helps improve services, but incorrect stops or passenger profiles can also create safety and equality consequences. [ 008, 011, 012, 014 ]
Where we would start first Define minimum data, lawful client instruction, access, validation, retention, incident, anonymisation and export. Separate live dispatch information from analytical datasets. Test that the buyer can retrieve a journey audit without exposing unnecessary passenger detail. [ 008, 011, 012, 014 ]
Service measures should reflect complete passenger journeys
Evidence-linked insight · What this changes Departure punctuality alone can mask failed pickups, long waits, denied boarding, missed assistance or poor connections. DRT also needs booking acceptance, ride time and coverage measures. Targets can conflict when dispatch optimises one passenger at another's expense. [ 011, 012, 013, 014 ]
Where we would start first Create metric definitions with clock, denominator, exclusions, data source and remedy. Balance reliability, accessibility, safety, complaints and efficiency. Segment results by service and user group where lawful, and audit overrides rather than gaming closure codes. [ 011, 012, 013, 014 ]
Continuity plans must cover fleet, people, systems and roads
Evidence-linked insight · What this changes One contingency coach cannot address simultaneous severe weather, driver shortage, booking-platform failure or road closure. Assisted passengers and rural areas may have few alternatives. Recovery priorities require client-agreed service and safeguarding logic. [ 011, 012, 013, 014 ]
Where we would start first Quantify spare vehicles, standby people, alternative communications, depot or fuel dependencies and subcontractor response. Set priority rules and maximum tolerable interruption. Exercise scenarios and record what the buyer must decide during constrained service. [ 011, 012, 013, 014 ]
Mobility economics must expose mileage and demand uncertainty
Evidence-linked insight · What this changes Pricing can use route payments, vehicle or driver hours, mileage, journey bands and technology fees. Dead running, assistance dwell, cancellations, fuel, wage movement and low utilisation matter. A pilot value or framework ceiling cannot establish unit viability. [ 011, 012, 013, 014 ]
Where we would start first Build an auditable model from service hours, peak vehicle requirement, duties, mileage, software, depot, supervision and contingency. State volume, indexation, cancellation, change and extension assumptions. Stress-test demand shape and zero-volume call-offs. [ 011, 012, 013, 014 ]
Mobilisation should prove a safe first passenger journey
Evidence-linked insight · What this changes Vehicles, drivers, routes, registrations, platform configuration, passenger data, safeguarding and communication must converge before launch. Pilot dates do not remove approval or testing dependencies. Late user data can invalidate allocation and training. [ 003, 009, 010, 011, 012, 013, 014 ]
Where we would start first Gate mobilisation through licences, service records, rosters, vehicle acceptance, data migration, accessibility tests, route rehearsal, passenger communication, incident drills and client sign-off. Run a controlled shadow service and keep unresolved risks explicit. [ 003, 009, 010, 011, 012, 013, 014 ]
Winning evidence should show an operable passenger service
Evidence-linked insight · What this changes The four procurements differ in geography, users and commercial shape. Evaluators need to see how the proposed people, vehicles, technology and controls operate together under realistic demand—not a brochure of fleet and software features. [ 011, 012, 013, 014 ]
Where we would start first Trace each tender requirement to a scenario, owner, process, artefact, measure, proof and price. Reconcile the roster, fleet table, implementation plan and cost model. Use transport, accessibility, safeguarding, digital and commercial challenge before submission. [ 001, 002, 011, 012, 013, 014 ]
Connectivity outcomes require honest attribution
Evidence-linked insight · What this changes Journeys delivered, bookings accepted and routes operated are supplier outputs. Access to education, employment or health, reduced isolation and mode shift depend on network design, funding, user behaviour and external services. A short pilot cannot prove every long-term benefit. [ 011, 012, 013, 014 ]
Where we would start first Report service and passenger-experience measures first, then evaluate broader outcomes with baseline, comparison and limitations. State the supplier's contribution. Avoid inventing modal shift, attendance, wellbeing or emissions percentages. [ 011, 012, 013, 014 ]
Mobility bids weaken when operating interfaces stay implicit
Evidence-linked insight · What this changes Typical gaps include assuming licensing, describing accessibility as a ramp, ignoring assisted-passenger handover, separating software from dispatch, underestimating dead mileage, offering uncommitted vehicles or drivers and promising social outcomes from service activity alone. [ 003, 008, 009, 010, 011, 012, 013, 014 ]
Where we would start first Challenge a full journey from booking to safe destination in normal and disrupted conditions. Record every missing authority, resource, data item and cost assumption. Qualify unresolved items rather than inventing registrations, capacity or results. [ 003, 008, 009, 010, 011, 012, 013, 014 ]
The Bid Strengthening Plan should rehearse critical journeys
Evidence-linked insight · What this changes High-value actions include validating operator authority, vehicle and driver commitments, accessibility, safeguarding, route data, scheduling constraints, platform fallback, control-room decisions, passenger communications and the cost base. Each closes a specific delivery or evaluation risk. [ 003, 008, 009, 010, 011, 012, 013, 014 ]
Where we would start first Give actions acceptance tests and deadlines tied to questions. Use tabletop and live rehearsals where proportionate. Preserve journey maps, resource models and incident playbooks so bid work becomes mobilisation evidence rather than disposable prose. [ 011, 012, 013, 014 ]
Transport proof must identify service and passenger boundary
Evidence-linked insight · What this changes A procurement notice verifies the buyer's activity, not delivered reliability. Comparable proof states route or zone, users, demand, supplier role, vehicles, platform, measured period and authorised result. An award does not show successful mobilisation or safe journeys. [ 011, 012, 013, 014 ]
Where we would start first Link each claim to a permissioned contract record, KPI definition, service report or reference. Mark limitations and shared attribution. Until evidence is approved, use bounded operating methods rather than fabricated clients, punctuality, savings or satisfaction. [ 011, 012, 013, 014 ]
Authorities retain network, eligibility and funding choices
Evidence-linked insight · What this changes The buyer retains service design, eligible users, subsidy, performance regime and change instructions; regulators retain licensing and enforcement decisions. The provider controls only its contracted operation and cannot guarantee passenger demand or wider network outcomes. [ 003, 004, 005, 006, 007, 011, 012, 013, 014 ]
Where we would start first Maintain a decision calendar for zones, routes, timetables, eligibility, fares, adjustments, priorities and claims. Present evidence and consequences. Escalate late decisions before they compromise registration, communications, roster or vehicle commitments. [ 003, 004, 005, 006, 007 ]
Relevant award story
Securing a multi-million-pound public-sector award for concessionary travel and mobility managed services
An anonymised Bid Champions client was selected by London local-government body to provide concessionary travel and mobility managed services. The public award record places the opportunity in the £5m–£9.9m band.
- Buyer
- London local-government body
- Published value band
- £5m–£9.9m
- Outcome
- Contract award recorded
The precise tender-support workstream is confidential. The full case separates Bid Champions’ recorded support, the client’s solution and commitments, and the buyer’s award decision.
Read the complete case studyLive-pursuit check
What we would verify before fixing the strategy.
For a live opportunity, we would recheck the applicable law and standards, the buyer's latest notice and documents, qualification route, amendments, commercial assumptions and delivery conditions. This keeps the analysis useful without treating a general market position as a substitute for the actual competition.
Priority public records to recheck: Demand Responsive Transport Pilot; Rural Mobility Fund Pilot Bus Operator; Secured Bus Services - July 2026; Provision of Client Assisted Passenger Transport Services.
Independent verification checks
The public references supporting the evidence points above remain available so a bidder, specialist or decision-maker can test the position against the original authority.
Open 14 public references used to test this sector position
- Procurement Act 2023 — UK Parliament / legislation.gov.uk
- Procurement Regulations 2024 — UK Parliament / legislation.gov.uk
- Public Passenger Vehicles Act 1981 — UK Parliament / legislation.gov.uk
- Transport Act 1985 — UK Parliament / legislation.gov.uk
- Transport Act 2000 — UK Parliament / legislation.gov.uk
- Local Transport Act 2008 — UK Parliament / legislation.gov.uk
- Bus Services Act 2017 — UK Parliament / legislation.gov.uk
- Equality Act 2010 — UK Parliament / legislation.gov.uk
- Public Service Vehicles Accessibility Regulations 2000 — UK Parliament / legislation.gov.uk
- Public Service Vehicles (Accessible Information) Regulations 2023 — UK Parliament / legislation.gov.uk
- Demand Responsive Transport Pilot — South Yorkshire Mayoral Combined Authority / Find a Tender
- Rural Mobility Fund Pilot Bus Operator — Cumberland Council / Find a Tender
- Secured Bus Services - July 2026 — Nexus / Find a Tender
- Provision of Client Assisted Passenger Transport Services — Surrey County Council / Find a Tender