Do we need our own domain?

No. Your pages work immediately at our address, and move to your own domain whenever you have one — the certificate is issued for you and the timetables carry on unchanged.

Can we keep the website we already have?

Yes. Many operators keep a county or society site and use ours only for timetables, notices and booking. There is an embeddable departure board for the site you already have.

Who writes the pages?

You do. There is writing help that drafts in your own voice, but it hands you a suggestion beside the page and nothing it writes is published without somebody pressing a button.

What do you put on our site?

One line in the footer saying it runs on Transit OS. No adverts, no trackers of ours, and nothing that follows your riders anywhere.

Features

What riders see.

The same schedule the dispatcher works from, on your own domain, in your own words. About 64 KB on a phone, with no JavaScript at all.

Rider pages

Your timetables on your own domain, reading the schedule the dispatch board reads. They cannot disagree.

Your domain with automatic SSL, or ours until you have one.
64 KB and four requests on a phone, with no JavaScript — it opens on one bar of signal at a rural stop.
Five palettes and four typefaces, each contrast-checked. A colour of your own is refused if a rider could not read it.
GTFS, GTFS-Realtime, robots.txt, sitemap and llms.txt, served without anybody configuring anything.

prairielinetransit.orgYour domain

Prairie Line 1 · Eastbound · weekdays

Millbrook	Sarno	Hallett Jct	Depot
05:52	06:11	06:36	06:58
09:15	09:34	09:59	10:21
14:40	14:59	15:24	15:46
17:25	17:44	18:09	18:31

Same schedule as the dispatch board. There is only one.

Your own pages

Fares, how to ride, who to call — the questions your office answers on the telephone every week.

Blocks of plain text. No rich-text field and no embed box, so nothing on your site can become a script.
Timetable and notice blocks read live data, so a page cannot drift from what you are running.
A health meter on every page: reading level, undescribed pictures, untappable telephone numbers, download weight.
Writing help drafts in the words you chose in Brand Studio, as a suggestion beside the page. It refuses to invent a fare.

Pages · How to rideDraft

92Reads well

7.1Grade level

64 KBOn a phone

Text

Ring the office by four o'clock the day before…

Questions and answers

3 questions riders actually ask

Telephone bar

(555) 010-0142 · sticky on a phone

Service notices

Whatever is in force today

Plain text only. Nothing here can become a script tag.

Service notices

One notice reaches the rider pages, the realtime feed and your list at the same moment.

Drafted from the incident note so nobody retypes it, stored as a draft and marked as one.
Nothing is ever published automatically. Not ever.
Expired notices come down by themselves rather than frightening people six weeks later.

Alerts · New noticeNot published

From incident #204 · crossing obstruction

Draft — nothing is sent until you send it

Prairie Line service between Millbrook and Hallett Junction is stopped while a blocked crossing at County Road 12 is cleared. Riders should expect delays of up to an hour. We will post an update by 09:30.

Publish noticeEdit

Your list, and letters to it

Riders, supporters and volunteers, each with their own list — and each of them asked to be on it.

Double opt-in on every path onto the list, including addresses your staff type in.
One-click unsubscribe with no login and no survey. It works on the first press or it does not work.
A season ending or a notice published raises a draft. It is never sent for you.
A send that fails halfway resumes where it stopped. Nobody receives the same letter twice.

Letters248 on the list

Drafted by a moment · not sent

Last chance to ride the Autumn Excursion

The EXC runs until 26 October. [Say what makes it worth a trip.]

Riders	186	confirmed
Supporters	51	confirmed
Volunteers	11	confirmed
Waiting to confirm	4	pending

Nobody is written to who did not ask twice.

Being found, and being answered correctly

We fetched seven small agency and heritage sites in August 2026. Not one carried a line of structured data, so an assistant asked how to book a dial-a-ride has nothing to read and guesses.

Structured data as standard

Your organisation, your pages and your questions, in the format search engines and assistants read.

An llms.txt of your own

What your service is, how to book it, and where the machine-readable feeds are — in plain sentences.

A review that names the fix

Graded across being found, machine readability, what riders read, accuracy and speed. Every finding says what a rider experiences because of it.

A board for somebody else's site

One iframe gives the county or the hotel your next departures. Under 2 KB, no script, always current.

Printable from live data

The handout on the noticeboard prints from today's schedule, not from a PDF made once in 2016.

Counting visits, by ID only

Paste an identifier, never a block of code. Whatever you switch on is named in your footer automatically.

What we measured, and the five fixes →

Close view of weathered working hands holding a creased paper timetable annotated in pencil, resting on a denim-clad knee.

See it with a real timetable in it.

The demo agency's rider pages are live, on our address, built from the same schedule as its dispatch board.

Open the rider pages Booking and tickets