Construction vibration monitoring software
Piling, compaction, rock breaking and blasting near existing buildings are often allowed only with vibration monitoring at the nearest sensitive structures. The monitoring contractor installs geophones, checks them on a schedule, and reports peak particle velocities against the limits in the project approval. When a neighbour complains of cracking, the report and the site notes from that day are what get read.
Built for construction firms running teams of roughly 3–50 inspectors.
Sample Vibration compliance report
An illustrative excerpt. The site, readings and findings are fictional; the layout is yours to set.
Vibration compliance report
Weekly vibration summary — Week 14
- Project
- Harbourside basement excavation (fictional)
- Period
- 6–12 April 2026
- Limit
- Project approval transient limit for heritage structure
| Monitor | Peak / activity | Status |
|---|---|---|
| V1 Heritage terrace | Peak 2.1 mm/s during rock breaking, Tue | Status: Below limit |
| V2 Apartment block | Peak 1.4 mm/s | Status: Below limit |
| V1 Heritage terrace | Alert trigger Thu 10:42, hammer within 6 m | Status: Alert |
| V3 Footpath | Unit offline Wed–Thu, battery fault | Status: Data gap |
Fields captured on site
Your firm builds the form in-app, so these are a starting point rather than a fixed schema. Every field is captured on the device, with or without signal, and lands in the vibration compliance report where your template puts it.
Per monitor visit
- Monitor ID and location
- Mounting condition
- Battery and memory status
- Trigger events since last visit
- Photo of installation
Per event
- Date and time
- Peak reading reported
- Activity and plant at the time
- Response taken
Dilapidation link
- Structure monitored
- Existing cracks referenced
Standards the report works to
- AS 2187.2-2006Explosives — Storage and use — Use of explosives
- Includes guidance on ground vibration and airblast limits referred to for blasting works.
Load the standards you hold into your reference library and the drafted prose is written against them rather than against a general model.
How the vibration compliance report gets built
Capture it once, offline
Your firm builds the vibration monitoring form in-app — 25 field types, nesting repeatable groups, compound AND/OR visibility rules, reusable modules and calculated fields. Field capture works with no signal: jobs, forms, photos, notes and audio all queue in an idempotent outbox that only clears once the server confirms receipt.
Link it to your sample locations
Enter sample locations once, as a register. Every one of your samples, bores and monitoring rounds then points at a stored row rather than a name somebody typed — and the links survive a disconnected device.
Render your own template
The vibration compliance report renders into the Word template you already use — your letterhead, your section order, your clause library — with conditionals, loops over repeats, composable sub-templates and photo grids.
Reviewed before it leaves
You write the review framework: a checklist of what a vibration compliance report must contain, plus the prose standards you would mark a junior against. Link it to a report template and it runs every time that template renders. Each finding comes back graded info, minor or major, quoting the sentence at fault, and a person accepts or dismisses every one.
Because the structured submission behind the report is held too, the review is a comparison rather than a proofread: The report says every bore was sampled to three metres; the form has BH07 refused at 1.2 m.
Checks a environmental framework usually carries
- Every exceedance in the results tables is discussed in the assessment text
- The guideline values cited match the land use actually being assessed
- No sample or bore ID appears in the prose that is absent from the data
- Data gaps, refusals and deviations from the sampling plan are stated as limitations
Questions
- Can alert events be linked to what was happening on site?
- Each event is a row with the activity and plant recorded, so the report can explain an exceedance rather than just list it.
- Can monitors be cross-referenced to a dilapidation survey?
- Structures can be a shared register, so the vibration monitor and the dilapidation record point at the same building.
- Will a data gap be called out in the report?
- Monitor status is recorded at every visit, and your review framework can require any outage to be stated.
What this is not
Worth knowing before you book a demo, so neither of us wastes the half hour.
- Not field-service dispatch. No timesheets, no parts, no inventory. Scheduling exists to get an inspector to a site.
- No signature capture. If your deliverable has to carry a signed sign-off on the artefact itself, this is not the tool yet.
- Field capture is what works offline — jobs, forms, photos, notes and audio. Reports, chat, scheduling and the inbox need a connection.
- No client portal. Reports go out as a file or a password-protected link.
Other environmental work we cover
- Erosion and sediment auditsESC compliance report
- Groundwater monitoring roundsMonitoring event report
- Hazardous materials surveysHazmat register
- Illegal dumping investigationsDumping incident report
- Landfill cell inspectionsCell condition report
- Landfill gas monitoringGas monitoring report
- Litter auditsLitter count report
- Noise monitoring surveysAcoustic report
Other disciplines
Rebuild your vibration compliance report in SurveyThanks
Bring the Word template you already send clients. If you are coming off another field-forms tool, a filled report can be uploaded, read field by field, and re-rendered into your template.