When a construction defect surfaces six, twelve, or twenty-four months after handover, the argument almost never turns on the inspection itself. It turns on the conditions at the time of inspection. What was the temperature when the slab was poured? What was the humidity when the membrane went down? Was the inspector even on site, or did they sign the ITP from the office?
These are answerable questions — but only if you captured the answer at the time. Retrofitting weather data from the Bureau of Meteorology three years later is technically possible, but it's a weak defence. The contractor's lawyer will argue that BoM is twenty kilometres away, that conditions on a high-rise level 14 differ from a ground-level reading, and that there's no record the inspector saw those conditions, only that they existed somewhere in the postcode.
This post is about why site conditions evidence belongs on the ITP itself, what counts as defensible, and how HoldPoint records GPS coordinates and live weather under every signature on the approved PDF.
Why site conditions are the most argued-over part of an ITP
The Australian Standards that govern construction quality almost universally include conditional requirements:
- AS 1379 (Concrete Supply) sets ambient and concrete temperature limits at delivery and placement. Concrete delivered above ~32°C without specific mix design provisions is non-conforming.
- AS 3600 (Concrete Structures) specifies curing conditions — temperature ranges, moisture retention windows — that determine strength development.
- AS 4654 (Waterproofing) and most membrane manufacturer instructions specify a humidity ceiling — typically below 85% RH — for primer and membrane application.
- AS/NZS 2312 (Protective Coating) sets a dew-point margin and humidity limit for paint application.
- AS 4654 / AS 3740 require flood-test conditions to be recorded, including duration and ambient.
Every one of those conditions is a free defect-claim variable. If a coating fails three years later and the conditions at application aren't on record, the claim becomes a debate about probabilities. If the conditions are on record, and they were within spec, the claim moves to a different theory.
A signed ITP without conditional evidence is an inspection record. A signed ITP with GPS coordinates and live weather at the sign-off moment is an inspection record that's hard to argue with.
What "good" site-conditions evidence looks like
If the goal is to defend the ITP later, the evidence has to satisfy three tests.
Specific to the location. A weather reading from twenty kilometres away on a different elevation is not the same as a reading on the actual pour deck. The defensible reading is one tied to the inspector's GPS at the moment they signed. On a high-rise, conditions on level 14 in shade can differ by 5°C from the BoM reading at the airport.
Specific to the moment. Weather changes over the course of a pour. A reading at 06:00 and a reading at 11:00 on the same day can place the work on either side of an AS 1379 limit. The defensible reading is the one captured at the same instant the inspector hit "sign".
On the document, not in a separate system. A weather log in a different app, a screenshot pasted into a daily diary, or a hand-written entry in a paper logbook is detachable evidence. It can be lost, contradicted, or claimed to be reconstructed after the fact. The defensible record is the one printed on the same page as the signature, on the same PDF that was signed and distributed.
These three tests are why HoldPoint stamps the data directly onto the signature row in the database, displays it under the signature in the document UI, and prints it on the approved PDF — not in a side log.
How HoldPoint captures GPS and weather at sign-off
When an inspector signs a hold point, witness point, or document-level signature in HoldPoint, the app does the following automatically, in the background, without slowing the workflow:
- Asks the browser for geolocation. On the inspector's first sign-off of the session, the OS prompts them to allow location access. After that, it's silent.
- Reads the GPS coordinates and accuracy from the device.
- Calls the OpenWeatherMap API with those coordinates and pulls the live weather: temperature in Celsius, humidity percentage, wind speed, sky condition, and observation timestamp.
- Submits all of it alongside the signature image and the role.
- Stores the data on the signature row, alongside the signer name, role, and timestamp.
The result appears on the document page next to the signature ("-33.8688°, 151.2093° · 32°C · clear sky · 41% RH · 12 kph wind") and on the approved ITP PDF as small lines under the signer's name reading "Site: 32°C · clear sky · 41% RH · 12 kph wind" and "GPS: -33.8688°, 151.2093°".
If the inspector denies location access, the signature still records — the workflow doesn't break. The data fields are simply null for that signature, and the rest of the audit trail (signer name, email, role, IP, timestamp, device) carries on as before.
What this changes in real disputes
A few scenarios where site-conditions evidence quietly does the heavy lifting:
Concrete strength dispute. A test cylinder result comes back below specification six weeks after a slab is poured. The first question is whether the slab was placed in compliant ambient and concrete temperature conditions per AS 1379. With the live weather stamped on the pre-pour and post-pour signatures, the conditions are part of the document. Without it, the contractor needs to manually pull BoM records, prove the BoM station is representative of the site, and explain why the data wasn't already on the ITP.
Coating failure on external steelwork. Six months after handover, a balustrade shows premature corrosion through the topcoat. The coating system specified a 5-30°C surface temperature range and 85% maximum RH at application. With the conditions recorded on the application sign-off, the contractor produces the PDF and the conversation moves on. Without it, the painter's defence is "I'm sure I checked" against a defect inspector with a moisture meter.
Membrane adhesion failure on a podium deck. Tiles lift two summers after installation. The waterproofing manufacturer disputes the warranty claim because they can't tell whether the membrane was applied within the specified humidity range. With the conditions stamped on the waterproofing ITP sign-off, the manufacturer either honours the warranty or accepts they can't dispute the application conditions. Without it, the manufacturer denies the claim and the contractor wears the cost.
Was the inspector actually on site? This sounds insulting until you've been in a defects claim where the evidence is "yes, I signed the ITP" and the principal's QA team is asking how a single inspector signed off on twelve hold points across three sites in one afternoon. GPS coordinates on each signature are the cleanest possible answer.
What this isn't
Site-conditions evidence isn't a replacement for the actual on-site QA work. It doesn't make a bad inspection good. It doesn't excuse skipping a hold point. It doesn't replace photographic evidence of the work itself.
What it does is close the gap between "we did the inspection correctly" and "we can prove we did the inspection correctly, on this exact spot, in these exact conditions." That gap is where most defect claims live.
It also isn't a privacy concern in the way some contractors initially worry. The location captured is the inspector's location at the moment they consented to sign — which is, by definition, the location where the inspection took place. It's not a continuous track. It's a single coordinate per signature, the same way a notary stamp records the place of signing.
Where this fits in the ITP workflow
For a typical multi-level build, the practical setup is:
- Master ITP templates are built once at company level (or generated from the free AI ITP generator).
- The ITP is applied across every level via the Areas feature.
- Each level's sign-off pack is sent to the principal's representative as one email with one combined PDF.
- When the rep signs, GPS and weather are captured automatically. The combined PDF prints them under each signature.
- Years later, when a defect emerges on level 9, you open the level 9 sign-off pack PDF and the conditions at every hold point are right there.
There's no extra form for the inspector to fill, no separate logbook to maintain, and no "did we capture that?" anxiety after the fact. The audit trail is the document.
Getting set up
Site-conditions capture is included on every paid HoldPoint plan. There's nothing to switch on — when you sign in, it's already running. The first sign-off on a new device prompts the browser for location once; after that, everything is automatic.
If you want to see it before signing up, the free ITP generator gives you a complete inspection plan for any trade in seconds. The full HoldPoint workspace adds the sign-off, the area-based bulk apply, and the live site-conditions evidence on every approved PDF. Start free — 14 days, no credit card.