The single most common question in any HSE audit — whether internal, regulator-led, or client-led — is whether the inspector was physically present at the site on the day and time the inspection record claims. For decades, the answer relied on a paper sign-in sheet at the site gate, a supervisor's verbal confirmation, or a photo with no metadata. None of these withstand modern audit scrutiny. SiteGuard GPS Check-in was built specifically to answer the presence question with verifiable geographic data: when an inspector arrives at a site, they tap Check-in on SiteGuard Field, and the platform stamps the visit with the device's real GPS coordinates, the timestamp, the inspector identity, and the site code. That stamp propagates through every checklist response the inspector completes during the visit, every photo they attach through Photo Evidence, and every violation they raise through Violation Reporting. The result is an audit trail where every record is geographically anchored to a verified site presence, which is what ISO 45001:2018 clause 9.1.1 monitoring evidence and Saudi Civil Defense inspection records actually demand.

What GPS Check-in actually stamps #

A GPS Check-in is not a single data point; it is a composite record that becomes the anchor for the entire visit. At the moment the inspector taps Check-in on SiteGuard Field, the platform captures the device's latitude and longitude from the device GPS hardware, the timestamp from the device clock, the inspector identity from the authenticated user session, and the site code from the plan the inspector was assigned. If the device is online, the platform validates the coordinates against the site's recorded GPS boundary in the Sites master record; if the inspector is more than the configured tolerance radius from the site, the check-in is flagged as off-site and the inspector is asked to confirm or correct. If the device is offline, the check-in is still captured — the GPS coordinates, the timestamp, and the site code are stored locally on the device and queued for sync the moment connectivity returns. This offline capability is not a fallback; it is the part of the feature that matters most for remote GCC sites, where oilfields, mines, and large construction sites routinely have no connectivity for hours or days at a time.

How the stamp propagates through the visit #

The GPS Check-in stamp does not sit in isolation. Once the inspector is checked in, every checklist response they complete on the Dynamic Checklists module is stamped with the same visit identifier — so a Civil Defense auditor reviewing a checklist response can trace it back to the specific check-in that anchored it, including the GPS coordinates, the timestamp, and the inspector. Every photo attached through Photo Evidence inherits the visit stamp and adds its own EXIF metadata on top, so the photo carries both the inspector's check-in coordinates and the moment-of-capture coordinates from the camera. Every violation raised through Violation Reporting is stamped with the visit, so a violation cannot be raised remotely from an office; it must be raised from a checked-in site presence. This propagation is what turns a single check-in into a complete audit trail. The auditor does not see "the inspector says they were there"; they see "the inspector was at latitude 24.7136, longitude 46.6753, on 14 March 2026 at 09:42, the device GPS confirms it, the site master record confirms the coordinates fall within the site boundary, and every checklist response and photo and violation from that visit is anchored to that verified presence".

Offline GPS capture: the part that matters for remote sites #

The hardest part of building GPS check-in is not the check-in itself; it is the offline check-in. A GCC oilfield inspector working a Shaybah or Ghawar remote site may have no mobile signal for an entire shift. A construction inspector on a NEOM or Red Sea mega-project may be in a basement or a tunnel with no signal. A mining inspector in a Saudi phosphate operation may be kilometres from the nearest cell tower. In all three scenarios, an online-only check-in feature would be useless — the inspector could not check in, could not start a visit, could not capture a checklist response, could not raise a violation. SiteGuard Offline-First architecture is what makes GPS Check-in real for these sites. When the device is offline, the GPS coordinates are captured from the device GPS hardware (which works without connectivity), the timestamp is captured from the device clock, the inspector identity is captured from the authenticated session, and the entire record is stored in a local queue on the device. The moment connectivity returns — when the inspector drives back into signal range, or when they return to the site office with WiFi — the queued records sync to SiteGuard Manager with the original offline timestamp preserved. The auditor sees the same record they would see if the check-in had been online: the same GPS coordinates, the same timestamp, the same inspector, the same site code. This is the operational difference between a GPS check-in that works in the desert and one that works only in the demo.

The audit trail: Visit History and Compliance Reporting #

The GPS-stamped visit does not disappear after the inspector leaves the site. Visit History on SiteGuard Manager records every completed visit with its check-in stamp, the inspector, the site, the plan, the checklist responses captured, the violations raised, and the photos attached. The safety officer can filter Visit History by inspector, by site, by date range, or by plan — and every record carries the GPS coordinates that prove presence. Compliance Reporting rolls Visit History into regulator-ready evidence exports, so when a Saudi Civil Defense inspector asks for proof that the contractor's safety officer visited a specific site on a specific date, the safety officer produces the visit record with the GPS stamp in under a minute. The same evidence satisfies ISO 45001:2018 clause 9.1.1 (monitoring and measurement) and clause 9.2 (internal audit), because the platform produces documented information that proves monitoring happened, with verifiable geographic anchoring. For an Aramco contractor where the Aramco HSE Code requires documented evidence of safety officer site visits at a specified frequency, GPS-stamped Visit History is the difference between compliant and non-compliant — and between a defended audit finding and an undefended one.

How GPS Check-in fits the rest of SiteGuard #

GPS Check-in does not run in isolation; it is the geographic anchor of the daily-plan workflow. Daily Plan Management creates the plan that assigns the inspector to the site; Plan Approval approves the plan with a reviewer; Today's Plans surfaces the plan to the inspector on SiteGuard Field; the inspector taps Check-in when they arrive, which stamps the visit with GPS. Plan Actions completed during the visit inherit the stamp. Checklist Items captured during the visit inherit the stamp. Photo Evidence attached during the visit inherits the stamp and adds its own capture metadata. Violation Reporting raised during the visit inherits the stamp. Sites holds the master GPS boundary that the check-in is validated against. Site Import bulk-loads the site master from spreadsheets, including the GPS coordinates. Company Scope ensures the entire flow runs within the right legal entity for multi-subsidiary holdings. Notifications push check-in events and visit completions to the safety officer, so the manager knows in real time which inspector is on which site. The GPS check-in is the keystone of the visit — pull it out and the audit trail falls apart; with it, every other feature that touches the visit has a verifiable geographic anchor.