0.5mm or 6mm: Why the Rate of Movement Matters More Than the Number

Amara had been facilities manager at a twelve-storey commercial building in Brisbane's inner north for seven years. She knew the building's quirks — the way the basement carpark smelled after rain, the third-floor corridor that always ran warm, the hairline crack along the eastern stairwell that had been there since she started.

Every year, the building's routine inspection noted the crack. Every year, the report said *monitor and review*. And every year, Amara did exactly that — photographing it with her phone, comparing it to last year's photo, deciding it looked about the same.

In late 2024, a concrete spall fell from the stairwell soffit. Nobody was hurt. The subsequent investigation found that the crack had been widening — slowly, consistently, and in a pattern that pointed directly to long-term differential settlement in the foundations. The photographic record showed nothing useful. The sensor data that could have told the story simply didn't exist.

The remediation cost $340,000. The monitoring system that would have caught it early costs a fraction of that per year.

The Fundamental Problem With Periodic Inspection

Structural inspection is, by its nature, a snapshot. An engineer visits, observes, measures, and leaves. What happens between visits — the 51 weeks between annual inspections, or the 103 weeks between biennial ones — is invisible.

For stable structures in benign environments, that gap is acceptable. But for buildings subject to ongoing loading, ground movement, moisture cycling, or the cumulative effects of age and deterioration, the gap is where the story unfolds.

A crack that measures 1.2mm at inspection and 1.4mm at the next inspection twelve months later might look like minor progression. But if that movement happened over three days following a heavy rainfall event, and the crack was stable for the other 362 days, the story is completely different. You're looking at a moisture-driven mechanism — possibly swelling clay beneath the footing, possibly water ingress affecting a load path. That distinction changes everything about how you respond.

Without continuous data, you cannot make that distinction. You are, in effect, reading a book with 51 of every 52 pages missing.

What Sensor Networks Actually Measure

Modern structural monitoring systems deploy a range of instruments depending on what the structure needs to tell you. The four most common sensor types in building applications are:

Crack displacement gauges measure the width of a specific crack at a defined point, typically to 0.01mm resolution. They are mounted across the crack face and log continuously. When a crack is stable for months and then opens 0.3mm in a single event, the timestamp tells you exactly when — and that timestamp can be correlated with rainfall records, temperature logs, or nearby construction activity.

Tiltmeters measure angular rotation of structural elements — columns, walls, or slabs. A column that is tilting at 0.001 degrees per month is behaving differently from one that tilted 0.05 degrees during a single loading event. Tiltmeters are particularly valuable in heritage masonry buildings, where wall out-of-plumb can indicate footing movement or loss of lateral restraint.

Accelerometers capture dynamic response — vibration, impact, and the natural frequency of structural elements. Every structure has a characteristic frequency at which it prefers to vibrate. When that frequency changes, the structure's stiffness has changed. This can indicate cracking, connection loosening, or material degradation that is not yet visible. Accelerometers are standard in bridge monitoring and increasingly common in high-rise buildings subject to wind loading or nearby construction vibration.

Strain gauges measure deformation in structural members directly — the elongation or compression of steel or concrete under load. In a post-tensioned slab, for example, strain gauges can track whether prestress losses are occurring over time, which is information no visual inspection can provide.

These instruments are now small, low-power, and wireless. A monitoring network that would have required significant cabling infrastructure a decade ago can now be deployed with minimal disruption to building operations. Data is transmitted to cloud-based platforms, where it is stored, visualised, and — critically — assessed against pre-set thresholds that trigger alerts.

The Rate of Change Is the Signal

This is the point that separates monitoring from simple measurement: the rate of change carries more diagnostic information than the absolute value.

Consider two buildings. Building A has a crack that measures 3.5mm wide. Building B has a crack that measures 1.8mm wide. Which building has the more serious problem?

Without rate data, you cannot answer that question. If Building A's crack has been 3.5mm for eleven years and has not moved, it is a historical artefact — the structure has long since redistributed load around it and reached equilibrium. If Building B's crack was 0.2mm six weeks ago and has grown 1.6mm in that time, you have an active mechanism that demands investigation now.

This is why TRSC's monitoring programs are designed around threshold-based alerting rather than periodic reporting. The system watches continuously. When movement exceeds a defined rate — not just a defined magnitude — it flags for engineering review. The distinction between *this crack is large* and *this crack is growing* is the difference between a maintenance item and an emergency.

Separating Seasonal Behaviour From Structural Deterioration

One of the most practically useful things a monitoring dataset provides is the ability to distinguish reversible from irreversible movement.

Concrete and masonry structures move with temperature. A concrete frame building in Brisbane will expand measurably in summer and contract in winter. Joints open and close. Cracks that appear to widen in July may close again by January. This is normal behaviour, and it should not trigger remediation.

But if the crack opens in July and closes in January — but closes to 0.15mm wider than it was the previous January — that residual offset is the signal. The structure is not fully recovering. Something is accumulating. Over three or four seasonal cycles, that pattern becomes unmistakable in the data.

Without continuous monitoring, that pattern is invisible. Annual inspections in July every year would show a crack that appears to be growing. Annual inspections in January every year might show one that appears stable. The timing of the snapshot determines the conclusion.

Real-World Application: What the Data Looks Like in Practice

TRSC's monitoring work at [Marina Mirage](/preview/trsc/projects/marina-mirage) illustrates how this plays out in a marine infrastructure context. A 37-year-old boardwalk system with 120 piles — many showing chloride-induced corrosion — needed a defensible evidence base for capital planning. Rather than committing to wholesale pile replacement based on visual condition alone, the program combined structural assessment with ongoing monitoring to identify which elements were actively deteriorating and at what rate.

The distinction matters enormously for budget. Replacing 120 piles is a very different proposition from replacing the 18 that are actively moving beyond acceptable thresholds while monitoring the remainder through their next maintenance cycle.

In heritage building applications, the logic is similar but the stakes are different. At the [Prince Consort Hotel](/preview/trsc/projects/prince-consort), a 130-year-old masonry structure, understanding how the building moved under load — and whether that movement was elastic or progressive — was central to designing remediation that preserved the fabric rather than over-engineering it. Monitoring provides the evidence that heritage-sensitive interventions are performing as intended after installation.

Building the Evidence Base for Capital Planning

For facilities managers and asset owners, the most immediate practical value of structural monitoring is what it does to capital planning conversations.

Without monitoring data, every structural defect is a negotiation between worst-case and best-case scenarios. Remediation contractors price the worst case. Engineers, without data, cannot confidently argue for less. Owners are caught between a quote they cannot verify and a risk they cannot quantify.

With monitoring data, those conversations change. A dataset showing 0.4mm of movement over eighteen months, with no acceleration and clear correlation to seasonal temperature cycles, is a defensible basis for deferring major remediation. A dataset showing 2.1mm of movement in six weeks, with no correlation to temperature and a clear step-change following a rainfall event, is a defensible basis for urgent investigation.

In both cases, the decision is grounded in evidence rather than assumption. That evidence protects the asset owner from unnecessary expenditure and from the liability of inaction in equal measure.

This aligns directly with how TRSC approaches existing assets: Make Safe first, then Monitor, then Investigate based on what the monitoring reveals. The sequence exists because premature remediation — before the mechanism is understood — frequently addresses symptoms rather than causes. Monitoring provides the evidence that makes investigation targeted and remediation precise.

What a Monitoring Program Actually Involves

For those considering a monitoring program for the first time, the practical questions are usually the same: How many sensors? Where? Who reviews the data? What happens when an alert fires?

The answers depend on the structure and the risk profile, but a typical building monitoring program involves:

• Instrument selection and placement: based on a prior condition assessment identifying the elements of concern
• Baseline establishment: typically four to twelve weeks of data collection before thresholds are set, to understand the structure's normal behaviour
• Threshold configuration: alert levels set at rates of change that warrant engineering review, not just at absolute magnitudes
• Data review protocol: defining who receives alerts, what the first-response procedure is, and at what point an engineer needs to attend site
• Reporting cadence: monthly or quarterly summaries for asset owners, with trend analysis rather than raw data

The cost of a monitoring system scales with the number of instruments and the complexity of the data platform. For most commercial buildings, the annual cost of a targeted monitoring program is a small fraction of the remediation decisions it informs. For heritage assets, high-rise facades, or marine infrastructure where the consequence of misjudgement is high, the economics are even more compelling.

The Question Is Not Whether to Monitor

For assets that carry meaningful structural risk — whether from age, environment, modification history, or known defects — the question is no longer whether continuous monitoring is warranted. It is which elements to monitor, at what resolution, and with what review protocol.

Amara's building did not need sensors everywhere. It needed sensors on the elements that were showing signs of active behaviour — the stairwell crack, the eastern foundation zone, the post-tensioned transfer slab on level two. Three instruments, a cloud platform, and a monthly engineering review would have changed the outcome entirely.

The data that structures generate continuously is available. The technology to capture and interpret it is mature and affordable. The gap is simply in knowing what to ask the building — and having the instrumentation in place to hear the answer.

For facilities managers, asset owners, and engineers managing existing structures in Queensland, New South Wales, or Victoria, TRSC's structural monitoring programs are designed to provide exactly that evidence base. More information is available at [trsc.com.au](https://trsc.com.au).