Manual / Diversions

The documents you can produce

Everything this tab produces on paper or as a file, what each one is for, and the parts of a document that no setting can remove.

What you are looking at

On a record, under Documents:

Where this deployment cannot make PDFs the third is replaced by PDF unavailable, and hovering it names the missing software. That is the app refusing to offer a button that fails rather than a feature quietly going wrong.

Under them, on anything not yet approved:

Documents are watermarked until this diversion is approved.

In the toolbar, under Export, four downloads covering the whole register: Register (JSON — canonical), Register (xlsx), Service-km lost (CSV) and Service-km lost (xlsx). The two spreadsheet ones are absent where this deployment cannot make spreadsheets.

What is on the printed page

In order down the page:

1. the letterhead, if this depot has set one;
2. the watermark, on anything not currently in force — DRAFT — NOT FOR ISSUE or RETIRED — NOT IN FORCE — and, under the title, a line saying what it means ("This plan has not been approved. Do not issue it to drivers.");
3. the reference and revision, then the title, the state, and the route with its full name and type;
4. the reason and your description;
5. three headline figures — route skipped per trip, stops not served, and the direction with its headsign;
6. the direction's table: last stop served, back on route at, the stops not served by name, the normal route skipped and the drawn path's length;
7. Driver instructions — the bulletin: the last stop served, then the turns one by one, each with the distance to the next turn and a small map of it, then where to rejoin, the stops not served, the kilometres skipped, the timing block, and this depot's standing notice if it has set one;
8. Activations, where any windows have been recorded against the record;
9. the provenance block — who drafted it and when, where it was seeded from if it came from a road incident, who last edited it, who approved it and when, the reference and revision, which timetable version it was resolved against, whether that was the frozen plan or a live resolution, and when this copy was generated and by whom.

The last of those is what lets a page found on a depot noticeboard be traced back to exactly which version of which plan it is.

Bulletin layout

Bulletin layout in the toolbar sets how every bulletin prints. It is one setting for the whole register, not a preference of yours, and the panel says why: "the bulletin a driver is handed must not depend on who pressed print." Changing it needs the ops role; a viewer sees the panel read-only.

Under the form, the list the panel calls What this cannot change — five things every bulletin carries however it is laid out:

• the DRAFT/RETIRED watermark
• the provenance footer
• the ~ marking on estimated figures
• the list of stops not served
• the OBSERVE SCHEDULED TIME block

Each is there for a stated reason. A layout that could omit the watermark would be a way to print an unapproved plan that looks issued; a page on a noticeboard has to be traceable to a revision; the stop list is the part passengers experience; and running early is a punctuality failure exactly as running late is.

What the documents say about their own numbers

Every rendered document carries one sentence about its figures, in one wording, so that a reader is never left guessing which hedge is the real one:

Figures marked ~ are operational estimates for planning and record-keeping. Service-km not operated is estimated from the plan and the timetable, and is frozen when an activation is recorded so a past window keeps the numbers it was recorded with. Counts are exact for the plan as drawn.

What they do not mean

An unwatermarked page is a claim. It says this plan is approved and current. That is exactly why no setting can take the watermark off a draft.

A footer reading "frozen snapshot captured at approval" and one reading "live resolution" are not the same document. The footer says which one you are holding. A page rendered from a live resolution describes a plan nobody has signed off, and it will be watermarked to match.

Two prints of one record can differ. Legitimately: if the record went back to Draft in between, or if somebody changed the register's layout. What cannot differ is what an approved page states about the plan.

The spreadsheet's numbers are numbers. In the workbook the ~ lives in the column heading rather than in the cell, so the column can still be summed. A cell reading ~12.4 would be text, and a spreadsheet whose kilometre column cannot be added up has lost the one thing a spreadsheet is for.

The spreadsheet is not the register. It is a human backup sheet. Spreadsheets get emailed, edited and re-sent; the register stays the authority, and the JSON export is the only format that can put a register back.

A printed document does not update itself. It carries its own maps and its own figures. Re-printing later is what produces a new page, and the provenance block dates every copy.

The maps on the page are pictures, not the map. They are drawn from the plan that was frozen. Where a street map cannot be fetched they fall back to a plain line drawing, which is why the same record can print with pictures one week and line drawings the next without anything being wrong with the plan.

None of it is coloured by any of the app's bands. The state on a document is a lifecycle state, not a delay, a headway or a road severity.

When it looks wrong

A download does nothing, then says it failed. The link reports its own outcome: hovering it after a failure gives the reason. "Sign in again and retry" means the session ended while the page stayed open — nothing is lost.

PDF unavailable. This deployment does not have the software that makes PDFs. The Preview page is the same document in a browser, and printing from there is the fallback; the PDFs chip in the register's header is faded for the same reason.

The bulletin prints "no driver instructions have been written". Nothing has been generated or typed for this record yet — see Driver instructions.