Fibre and Network Infrastructure Editing and Proofreading Services

A contractor building out a fibre route receives as-built documentation from a previous phase showing a duct bank crossing under a roadway. The drawing shows the crossing but never records the actual depth as built, which differed from design by nearly a metre. Two years later a crew excavating for a water main strikes the duct, severing service to a hospital and a data centre, and the investigation turns on a single field that nobody filled in because the form did not clearly require it.

We edit what fibre and network infrastructure teams produce — as-built records and route documentation, splice records and fibre assignment schedules, OTDR test reports and acceptance documentation, permit applications and municipal right-of-way submissions, make-ready and pole attachment records, locate request procedures and damage prevention documents, construction method statements and traffic management plans, IRU and dark fibre agreements, and network diagrams and cable schedules. Our editors work on the record a crew relies on years after the people who wrote it have moved on.

The as-built record is the document a future excavation depends on, and its failure is a field that describes what was designed rather than what was actually installed. We work through these so as-built values are recorded as measured in the field with the date and method of measurement, kept visibly distinct from the design values they replaced, since a record that silently carries the design figure forward tells a future crew something confidently untrue; so any deviation from design is flagged as a deviation with its reason, given that a crossing installed a metre shallower than drawn is exactly the fact a future locate depends on and exactly the fact most likely to go unrecorded; so each field required for a safe future dig is marked as mandatory rather than optional, because a form that permits a blank depth will collect blank depths, and the gap surfaces only when someone puts a backhoe through the duct; so references to physical landmarks are tied to something durable and surveyed rather than to a feature that may not exist in five years, since a measurement taken from a fence line or a tree stump becomes unusable the moment it is removed; and so the record states plainly what was not verified, given that a future crew treating an unverified assumption as a confirmed measurement is the specific failure these documents exist to prevent. Records written this way still work when the people who made them are gone.

Everything you send is treated in confidence, including route data, network records and construction documentation. We are editors rather than engineers, surveyors or locate technicians, and we offer no view on construction methods, measurements or safety determinations. What we can do is make sure the record distinguishes what was measured from what was assumed.