Rail Editing and Proofreading Services
A train loses eleven minutes. The delay is logged against a signalling fault at a junction. Six weeks later it emerges that the signalling fault lasted ninety seconds and the remaining nine and a half minutes were a crew change that could not happen because the relief was on the delayed service behind. The attribution is wrong, the money moves in the wrong direction, and the actual problem — a rostering pattern with no resilience — is invisible because nothing ever recorded it.
We edit what railway operators, infrastructure managers and suppliers produce — delay attribution records and disputes, incident reports and investigation findings, performance reports and periodic reviews, operating instructions and rule book amendments, possession and engineering access planning documents, safety notices and briefing material for train crew, and the passenger-facing explanations that follow a bad day. Our editors work on records where a cause is assigned in minutes and argued about for months.
The delay attribution record is where railway performance is either understood or merely accounted for, and its failure is a code applied to a whole delay. A single cause almost never explains eleven minutes. We work through these so the delay is broken into its intervals with a time against each, since the first minute and the last nine usually have nothing to do with each other; so the primary incident is separated from the reactionary delay it caused, because a fault that lasted ninety seconds and a consequence that lasted nine minutes are different problems with different owners; so what was decided and by whom is recorded alongside what failed, given that many delays are extended by a reasonable decision taken with poor information; so the record says what would have had to be true for the delay not to happen, as this is the sentence that turns attribution into learning; so the account is written so the party being charged can follow it, since an attribution that cannot be explained will be disputed regardless of merit; so the passenger explanation is derived from the same record rather than composed separately, because "a fault with the signalling" describes ninety seconds of an eleven-minute delay; and so recurring patterns are described rather than counted. Records written this way fix things instead of allocating them.
Everything you send is treated in confidence, including performance data, incident records and internal correspondence. We are editors rather than railway operators, engineers or safety specialists, and we offer no view on attribution, causation or operational decisions. What we can do is make the record explain the whole delay.
Key Rail vocabulary
- Code applied to a whole delay
- One cause for eleven minutes
- Delay broken into intervals
- Time against each interval
- First minute and last nine
- Primary incident
- Reactionary delay
- Ninety seconds versus nine minutes
- Different problems different owners
- What was decided and by whom
- Reasonable decision poor information
- Decision recorded alongside the failure
- What would have had to be true
- Attribution turned into learning
- Written for the party being charged
- Disputed regardless of merit
- Passenger explanation from the same record
- A fault with the signalling
- Composed separately from the facts
- Recurring pattern described
- Counting incidents
- Rostering with no resilience
- Crew relief on a delayed service
- Junction margin lost
- Platform reoccupation
- Turnaround time absorbed
- Recovery time in the schedule
- Incident investigation finding
- Performance period review
- Possession and engineering access
- Rule book amendment
- Train crew briefing
Rail Word Challenge
Even seasoned pros miss these — give it a shot.
« More Transportation and Logistics editing | All editing services