Transportation Engineering Editing and Proofreading Services

Every road safety audit ends the same way: a list of problems written by one engineer, and a response written by another who designed the thing. What happens in that exchange determines whether the scheme is safer or merely audited. The audit is a formality if the responses are, and the responses are where the pressure sits — programme, budget, and the natural human position that the design was fine.

We edit what transportation engineers and highway designers produce — road safety audit reports and designer responses, exception and departure from standard documentation, transport assessments and travel plans, junction and corridor design reports, signal design and timing documentation, active travel and pedestrian infrastructure design statements, traffic modelling reports and their assumptions, speed and collision analysis reports, signing and lining schedules, temporary traffic management and diversion plans, road space allocation and consultation material, and design statements for approving authorities. Our editors work on the exchange that decides whether a finding is acted on.

The safety audit report and the designer's response together form the record that matters, and both fail in predictable ways. Audit findings drift into design preferences, and responses drift into justification. We work through these so each finding states the problem as a collision mechanism rather than a deviation from a standard, since "substandard visibility splay" describes a document and "a driver emerging is unlikely to see an approaching cyclist until 12 m, at an approach speed of 45 mph" describes what will happen; so who is at risk is named specifically — the child on the desire line, the driver turning right across two lanes, the pedestrian with limited mobility crossing in two stages — because a named person is harder to design around than a road user; so recommendations state the outcome required rather than a single solution, given that an auditor prescribing a solution invites a response arguing about the solution instead of the problem; so responses that reject a finding say plainly that the risk is accepted, by whom and on what basis, rather than describing why the design complies, as compliance and safety are different claims; so any finding accepted in principle but deferred is recorded with what triggers it; and so the language stays free of the passive constructions that remove the decision-maker. Exchanges written this way leave a record that stands up when a collision happens later.

Everything you send is treated in confidence, including scheme designs, audit findings and client information. We are editors rather than highway or safety engineers, and we offer no view on design, standards, risk or audit findings. What we can do is keep both halves of the exchange saying what they mean.