Flagship study

Route Profitability Review

A written reading of one corridor: who books it, what they pay, and which departures quietly lose money.

A long-distance train approaching a rural platform in low light

Who it is for

Scheduled coach, rail, ferry, and small airline teams who keep a named origin–destination pair on the timetable and need a frank view of whether that pair earns its keep.

What you leave with

A bound set of figures and a ninety-minute briefing that names weak departure days, fare-mix leaks, and the booking windows that actually fill the vehicle — not a live screen you must staff.

Scope

One named corridor, or a tightly related pair of directions, using twelve to twenty-four months of booking records you already hold.

Included

  • A data request list written in the language of your extract (PNR, ticket, or reservation dump — not a new system)
  • Cleaning notes: duplicate tickets, staff travel, and complimentary seats called out so they stop inflating load
  • Load, yield, and contribution by departure weekday and by booking week
  • A calendar of thin days with the weather and event caveats we can reasonably see in the file
  • A written briefing pack (PDF) and one live walkthrough for up to six people
  • One revision of figures if a fare-class mapping was incomplete on first pass

Not included

  • A staffed revenue desk, GDS changes, or a screen that refreshes overnight
  • Network-wide fleet planning for more than two corridors in a single review
  • Mystery shopping, passenger interviews, or survey design
  • Legal advice on franchise, PSO, or slot obligations

Who does the work

Read in Tillypronie by Systemcraftpoint. Briefings are held by video or, by arrangement, at your operations office in the United Kingdom.

How the study runs

  1. You send a sample week of the extract so we can see column names before we quote a finish date.
  2. We issue a full data request and a list of questions for the person who knows how complimentary and disrupted journeys are coded.
  3. We rebuild the corridor file, mark exclusions, and draft the first figures.
  4. You receive the pack three working days before the briefing so the commercial lead can annotate it.
  5. We walk the pack, then freeze a final version after one round of factual corrections.

What to prepare

Nominate one operations contact and one commercial contact. Export bookings with departure date, booked date, fare paid, party size, origin, destination, and cancellation flag. If you sell through more than one channel, say so before we start.

Limits we will not paper over

We do not invent missing fares. If a channel reports only passengers, we can read load but not contribution. Peak holiday fortnights with heavy disruption coding need extra time.

Next step

Write to us with the corridor name, months you can export, and whether staff travel is flagged. We reply with a sample-week checklist.