Skip to content

Mobility guides

Working documents for authorities and operators preparing a demand-responsive service. Pick what you need and download it as a PDF — no newsletter, and no sales call unless you ask for one.

I'm writing a tender

A ready-to-edit specification and an evaluation guide.

Most teams tender an on-demand system only once, and the wording decides whether you get real competition. A vendor-neutral specification to adapt as your own, and a guide to reading bidders' answers.

  • Model DRT specification

    Worked example

    A starting draft for a demand-responsive service, written to be vendor-neutral. Delete what does not apply to your area and adapt the rest.

    For the officer drafting the document.

    What's inside
    • Requirement clauses across architecture, passenger, driver, operations, configuration, security and integrations
    • The operational parameters to fix in the tender, and sensible ranges for each
    • Suggested evaluation criteria with indicative weightings
    • Wording for data ownership, export and exit

  • Reading the answers: a DRT evaluation guide

    Guide

    What bidder responses usually mean, where the ambiguity is deliberate, and the follow-up questions that resolve it before award rather than after.

    For anyone scoring bids for the first time.

    What's inside
    • Claims that need a demonstration, not a statement
    • How to test an accessibility, availability or response-time claim
    • The integration questions to ask before signing
    • Pilot design: what a first season should prove

  • Before you tender

    E-book

    The short opener to the two documents above: things worth considering, where each document fits, and why we share these at all.

    For whoever owns the procurement end to end.

    What's inside
    • A few patterns worth watching for in DRT tenders
    • Where each document fits, from drafting to scoring
    • Why we share these at all

I'm designing a service

Handbooks built from real deployments — service shapes, costs and design decisions.

Every place asks a different question. These handbooks answer from deployments that already faced yours: the service shapes that worked, the numbers behind them, and the decisions that kept vehicles full.

  • The rural mobility handbook

    Handbook

    How towns of 5,000–25,000 got public transport that works: five service shapes traced through five real deployments, the honest cost levers, and the decisions that make or break a rural service.

    For mayors, county planners and small-town mobility officers.

    What's inside
    • Why timetables lose in low density — and what replaces them
    • Five service shapes, five real towns: Vallirana, Cártama, Can Sunyer, Sant Vicenç, Viladecavalls
    • What it costs, honestly: the levers behind −15% mileage
    • The listening step every failed service skipped
    • The six make-or-break design decisions

  • Planning recurring transport

    Handbook

    School runs, shift changes and every journey that repeats: how the cut-off model plans routes once for the whole operation — exact pickup times, no cascading changes — told through a rural school run.

    For employers, schools and the operators who serve them.

    What's inside
    • On-demand vs planned: when each optimisation wins
    • A rural school run: 130 students across 195 km²
    • The cut-off model mechanics, parameter by parameter
    • Getting the promise right: the three rules recurring riders judge you on

I'm making the case

Real operating numbers, cost comparisons and ready-made arguments.

A mayor, a board or a budget committee will ask what it costs, what it replaces and how you'll know it worked. Real numbers from live deployments, ready to lift into a board paper.

  • The DRT business case

    Whitepaper

    The economics of demand-responsive transport, outcome by outcome — mileage cut, waits held, ridership multiplied — each with the mechanism behind it and the conditions it depends on, so your board paper survives hard questions.

    For whoever has to convince the board, the mayor or the budget committee.

    What's inside
    • Where the money actually goes: kilometres as the currency of a bus service
    • The cost side and the service side: observed outcomes, mechanisms and caveats
    • Does it scale — and the costs people forget to count, including where DRT loses
    • How to build your own case: price your empty kilometres, simulate, set thresholds in the contract

Looking for the underlying detail rather than a template? The requirement library and platform facts are open on the site, no form involved.

Rather see it running than read about it?

Thirty minutes, your area on screen, and the operational questions answered by someone who has launched services in towns like yours.

Book a demoSee all case studies