We're CiviLanso, a team of geotechnical engineers in Texas. We built CivilInspect because we kept running into the same problem on our own jobs: the measurement itself was rarely the hard part — it was what happened to it afterwards.
A reading without its place, its time, its conditions and a photo is a number you can't defend a month later. Photos end up scattered across phones, notes live in three places, and the report gets written from memory at the desk. On a monitoring job, that gap matters — the whole point of repeated observation is that each reading can be compared with the last one, and that only works if every record carries the same evidence.
What we built does the record-keeping at the moment of the measurement:
- A photo against every item — a structured checklist (Geotechnical Site Investigation, Earthworks & Compaction Quality Control, Dam Safety Inspection, and nine other packs), with a photo taken against each item as you go.
- Place, time and conditions attached automatically — every record logs the GPS location, weather and rainfall at the time, so the evidence is tied to the place and the conditions, not to someone's recollection.
- The report comes out of the records — the finished inspection exports as a Word or PDF document, ready to issue. Nothing is retyped.
The General Site Inspection pack is free to try; Pro unlocks the remaining packs, cloning, and unlimited custom sets.
Full disclosure: it's our own product. We're sharing it here because this is the group that lives with field measurements every day, and we'd rather hear what's missing or wrong with it than what's right.
For those of you running monitoring programmes — how do you keep the record straight between visits? Is it a spreadsheet, a field book, an app, or does it still depend on whoever was on site that day?
https://civilanso.com/web-apps/inspect/
60-second look: https://youtu.be/A22vLAe8zZ0
Posted: today, 20:34, updated: today, 20:36
Group: Field Measurement in Geomechanics (TC220)