Railway guide

How to use every page of HRTS Manage. Times everywhere are your railway's local times.

Start here

Log in, then choose your railway. If you belong to one railway you go straight to its dashboard. Your profile shows your railways and lets you change your name, email and password.

Dashboard

What is happening today: the active timetable, scheduled service count, next departures, today's specials, cancelled services, warnings that need attention, and recent changes. Next departures refresh from live timetable data every minute. Buttons jump to today's running, adding a special train, or a new timetable.

Today's running

Every service for the chosen date in departure order, with origin, destination and badges for cancelled, amended and special services. Filter by date and service type. Select a headcode to open the service, where amendments and cancellations happen.

Timetables

A timetable is one version of your service pattern with validity dates, for example September Standard running 1 to 30 September. Old versions stay available as history. The list shows validity, state and service count, with search and active or archived filters.

New timetable asks for code, name, validity dates and whether it is active. The detail page lists every service with first departure and route, filterable by type. Edit changes dates and details. Copy duplicates the whole timetable with all services for a new date range; copies start inactive so review before publishing. Export downloads one timetable as JSON; the list page exports the whole railway. Import uploads an export file, previews counts, then applies it on confirm: matching codes update, new codes create, and each imported service replaces its movements and exceptions. Only import files made for your railway. Archive hides a timetable from departures without deleting history; reactivate any time.

Trip editor

Open a service from its timetable, then Edit service. One page holds everything: headcode, service type, name, description, direction and whether it is active.

Running days is a seven button grid from Monday to Sunday. Green means the service runs that day. One off dates do not belong here; use date exceptions below instead.

Movements are the station by station schedule in order. Each stop needs an order number, station and type: Origin carries a departure, Destination carries an arrival, Stop carries arrival and departure, Pass carries a pass time. Only the times fitting the type are shown. Day offset stays 0 unless that time is after midnight, then 1. Tick Remove this stop to drop a row, and save once for the whole service. Leaving with unsaved changes warns first.

Date exceptions sit below movements: add dates the service runs additionally or does not run, with a reason. Give an end date to cover a range, for example engineering works from the 19th to the 20th. Duplicate copies a service with all its movements under a new headcode; set the new first departure and every other time shifts with it. Delete permanently removes the service and its history after confirmation.

Special trains

Add special train creates a one off service for a single date. Specials do not belong to a standard timetable; they live in the One off specials holder automatically. Give the date, headcode, type and description, add movements, save, and it appears in departures at once.

Day operations: amend, cancel, notes

Open a service from today's running and pick the day. These changes apply to that date only; the planned timetable is never altered. Every service row carries its own buttons: Confirm, Delay, Amend and Cancel.

Amend on any movement retimes it or removes the stop for the day, with a note. Delay records minutes late and shifts every time that day. Cancel for the day removes the service from departures and marks it cancelled everywhere; reinstate to undo. Services flagged as required stay hidden until confirmed: Confirm puts them in departures, Withdraw takes them out. Required services are listed every day so they can be confirmed for any date, even outside their normal pattern. Not running records a firm decision it will not run, keeping it out of departures entirely; confirming afterwards reverses that. Add a note attaches free text to the date, removable later.

Stations

Stations listed in railway order. Add station needs a code, name and display order; edit changes details, codes and order; disable keeps history while hiding; delete is refused while movements still use the station.

Units

Units are your reusable roster of locomotives and sets, each with a number and a name. Add each unit once; it can then be allocated to any service. Open a service from today's running, pick the day, and add one or more units for that date only; the planned timetable is never altered. Today's running shows each service's units. Deactivate a unit to stop new allocations while keeping history; delete is refused while allocations still use it.

Service types

Passenger, Express, Freight, Special and anything you add. Types are shared across all railways, so codes cannot change after creation. Found from the timetables page.

Users and invitations

Railway administrators manage their own users. Invite user sends an email invitation with a role; existing account holders accept without a second account, others sign up with the invited address. Pending invitations can be resent or cancelled.

Permissions on a member sets the role and seven flags: view and edit timetables, stations, day running, specials, users and settings. Changing role resets flags to that role's defaults. Disable suspends access reversibly; Remove takes it away entirely. You cannot disable or remove yourself, nor remove the last administrator. Every change is audited.

Activity

Who changed what and when, with before and after detail. Filter by action or search the summaries.

Settings

Railway name, short name, code, description, website, timezone, contact details and active state. Railway administrators only.

Search

One search across services, specials, timetables, stations and users. Enter a headcode such as 2M03 to jump straight to the service.

Platform administration

Platform administrators see Requests, Railways, Users and Activity in the platform area. Railway requests arrive from the public request form; approve to create the railway and prepare the administrator invitation, or reject with recorded reasons. No user account is ever created silently.

Public boards

Passengers see departure boards from the site home page: pick a railway and station for the classic board with destinations, calling points, platforms and expected status, refreshing every minute. Select a destination for the full calling pattern. The same data feeds the public JSON API documented at /api/docs/.