Hard Rock Mining Editing and Proofreading Services

A geotechnical inspector walks a drift, notes "ground conditions satisfactory" in the daily log, and moves on. Two shifts later, a section of that same drift experiences a fall of ground. The inspection log shows nothing wrong right up until the moment something was very wrong, because "satisfactory" was the only word the log was actually built to record, and whatever specific signs — a new hairline crack, a change in water seepage, a slight change in the sound the rock made when scaled — the inspector may or may not have noticed were never captured in a form anyone could later check.

We edit what hard rock mining operations produce for ground control and geotechnical monitoring — daily geotechnical inspection logs, ground support installation and condition records, fall-of-ground incident investigation reports, seismic and convergence monitoring documentation, and the correspondence explaining a ground control decision to workers or regulators. Our editors work on the record that is supposed to notice instability before it becomes an incident.

The specific observed indicator is what a geotechnical inspection log is actually for, and its failure is a summary judgement that records a conclusion with nothing underneath it a reader could later check against what actually happened. Ground conditions satisfactory tells a reader that an inspector looked and formed an opinion, and nothing about what that opinion was based on. We work through these so specific indicators are recorded at each inspection point — crack width and any change from the last reading, water seepage rate, scaling sound, visible spalling — rather than a single overall rating, since a fall of ground rarely happens with zero warning, and warning signs recorded specifically can be compared across inspections in a way a repeated word like "satisfactory" cannot; so any change from the previous inspection is stated explicitly, given that a new hairline crack matters far more as a change than as an isolated observation, and a log that does not compare against its own history cannot show a trend developing; so ground support condition is inspected and recorded separately from natural ground condition, because support that is degrading is a different problem from ground that is naturally unstable and the two require different responses; so an inspector's uncertainty is recorded as uncertainty rather than resolved into a confident rating either way, as "satisfactory" chosen because the alternative felt like an overreaction is a decision the log should be able to show was actually made, not hide; so access restrictions or additional support triggered by an inspection are logged with what specifically triggered them, given that this is the information a later investigation most needs; and so a fall-of-ground investigation compares the incident against the inspection history for that specific location, rather than treating the incident as a standalone event with no prior record to learn from. Logs written this way give ground control something to actually notice trouble developing in, rather than a record that only agrees something was wrong after it already happened.

Everything you send is treated in confidence, including geotechnical data, inspection records and incident information. We are editors rather than geotechnical engineers, ground control specialists or mine safety officers, and we offer no view on ground stability, inspection findings or incident causation. What we can do is make sure the log records what was actually observed.