Most EHS tools track people and sites but not assets. They know which inspector visited which site on which day, but they do not know which vehicle the inspector drove, when its registration expires, or whether the scissor lift on site B had its monthly inspection. Asset compliance lives in a different spreadsheet, owned by a different team, and the safety officer discovers the gap only when an Aramco or SABIC auditor asks for a vehicle inspection record or a Saudi Civil Defense inspector flags an expired vehicle registration during a site visit. SiteGuard was built to close that multi-asset gap. Five features — Vehicle, Fleet Management, Fleet Expiry Alerts, Equipment Registry, and Equipment Inspections — extend the platform beyond people-and-sites into a genuine multi-asset EHS environment where the same inspector who logs a fall-protection violation can also log a vehicle defect on the same plan, on the same site, in the same app. This article walks through the five features in concert, the Fleet Expiry Alerts workflow that prevents registration lapses, the integration with Violation Reporting for vehicle violations, and a real-world scenario of a contractor running eighty vehicles and two hundred pieces of equipment across twelve sites.
The multi-asset gap in most EHS tools #
Mainstream EHS suites were built around people and sites. The data model has an employee table, a site table, an inspection table, and a violation table, but no first-class asset table. Vehicle inspections, equipment inspections, license renewals, and insurance expiries end up as custom fields on a generic form, which means the safety officer cannot answer the question "show me every vehicle with an expired registration" without manual filtering. SiteGuard takes a different approach: Vehicle and Equipment are first-class objects in the data model, alongside Site and Worker. The inspector sees their assigned Vehicle in their Safety Profile on SiteGuard Field; the safety officer manages the fleet through Fleet Management in SiteGuard Manager; expiries surface through Fleet Expiry Alerts; equipment lives in Equipment Registry; and per-equipment inspection history lives in Equipment Inspections. The result is that the same platform that produces the daily-plan-to-certificate loop for people also produces the registration-to-inspection loop for vehicles and equipment — one source of truth, one audit trail, one set of Compliance Reporting filters that span people, sites, vehicles, and equipment.
The five features in concert #
The five features are not a list of independent modules; they are a layered system. Vehicle is the field-facing view of a single asset assigned to a single worker. Fleet Management is the manager-side master data layer for every vehicle in the company, with VINs, registration numbers, insurance details, and expiry dates. Fleet Expiry Alerts is the proactive layer that filters Fleet Management by expired or soon-to-expire status and pushes the result to the safety officer before a Civil Defense inspector finds it. Equipment Registry is the master data layer for every piece of equipment on every site, with serials, status, and inspection history. Equipment Inspections is the per-equipment inspection workflow that tracks inspector, date, and result for each inspection event. Together, the five features cover the asset-compliance lifecycle from assignment through inspection through expiry alert through renewal, all inside one platform. A safety officer running SiteGuard never has to leave the platform to find a vehicle registration number, an equipment serial, or an inspection history; it is all there, queryable, and exportable through Compliance Reporting.
Real-world scenario: 80 vehicles, 200 pieces of equipment, 12 sites #
Consider a Red Sea gigaproject subcontractor with eighty light and heavy vehicles, two hundred pieces of equipment (scissor lifts, generators, welders, compressors), and twelve active sites. Without SiteGuard, the safety officer would manage vehicles in one spreadsheet, equipment in another, and inspections in a third, with site visits logged on paper. The result, predictably, is expired registrations discovered during client audits, equipment inspections skipped because no one could find the spreadsheet row, and violations logged against drivers that never link back to the vehicle. With SiteGuard, the same subcontractor runs the entire asset-compliance operation in one platform. Each driver sees their assigned Vehicle in their Safety Profile on SiteGuard Field, with the license-validity status visible before they start the engine. The safety officer opens Fleet Management in SiteGuard Manager and sees all eighty vehicles in one filterable view, with registration and insurance expiries colour-coded by status. Fleet Expiry Alerts surfaces the three vehicles whose registrations expire within thirty days, and the safety officer initiates renewals before any of the twelve sites is exposed. Equipment Registry holds the master data for all two hundred pieces of equipment, scoped by Company Scope so the subcontractor can roll the data up to the parent contractor or down to the site level. Equipment Inspections tracks inspector, date, and result for each of the two hundred assets, so the safety officer can answer the question "when was the scissor lift on site B last inspected?" in seconds, not hours.
The same twelve-site operation now produces one audit trail that spans people, sites, vehicles, and equipment. When the parent contractor or an Aramco-tier client asks for evidence that the subcontractor's vehicles are road-legal and its equipment is inspection-current, the safety officer does not assemble a binder — they open Compliance Reporting, filter by entity, and export the result. The audit takes an hour instead of a week, and the subcontractor wins the next contract because they can produce asset-compliance evidence on demand while their competitors are still emailing spreadsheets. This is the strategic value of multi-asset EHS: it is not about tracking more things, it is about closing more bids.
The Fleet Expiry Alerts workflow #
Fleet Expiry Alerts is the feature that turns Fleet Management from a registry into a workflow. The safety officer opens the view and immediately sees vehicles filtered by expired license, expired insurance, license expiring within thirty days, or insurance expiring within thirty days. Each alert links back to the originating vehicle record, so the safety officer can initiate the renewal without leaving the view. The renewal itself — proof of payment, new registration document, new expiry date — is uploaded back into Fleet Management against the same vehicle record, which means the audit trail for that vehicle is continuous: previous registration, expiry alert, renewal evidence, new registration. Saudi Civil Defense and traffic-authority inspectors who flag expired registrations during site visits expect exactly this kind of continuous record, not a stack of renewed registrations with no link to the originating alert. Fleet Expiry Alerts also integrates with Notifications, so the safety officer receives a push when a new expiry alert is generated, and with Company Scope, so a holding company with multiple subsidiaries sees alerts scoped to the right entity. The result is that the safety officer cannot accidentally miss a renewal, because the platform surfaces every expiry before it becomes a regulatory exposure.
Integration with violation reporting for vehicle violations #
The multi-asset story gets stronger when violations enter the picture. A SiteGuard Field inspector who observes a vehicle defect — broken headlight, worn tyre, missing fire extinguisher — opens the same Violation Reporting workflow they use for safety violations, but selects a vehicle as the subject. The violation links to the Vehicle record in Fleet Management, which means the safety officer can later filter Recent Violations by vehicle, by driver, or by violation type, and the closure workflow runs through the same Violation Closure and Corrective Action Programs features used for any other violation. A vehicle defect that requires a corrective program — for example, a fleet-wide recall of a specific tyre model after a blowout — produces a Corrective Action Program assigned to the fleet manager, with closure tracked through Assigned Actions and a certificate-equivalent verification recorded in Equipment Inspections once the corrective work is complete. The same seven-feature closed loop that handles a fall-protection violation also handles a vehicle defect, because the underlying data model treats vehicles and equipment as first-class objects rather than custom fields. That is what multi-asset EHS actually means in practice: one workflow engine, many asset types, one audit trail.
From asset register to ISO 45001 and Aramco/SABIC audit #
ISO 45001:2018 clause 7.1 requires organisations to provide the resources needed for the OH&S management system, including infrastructure and equipment; clause 8.1 requires operational planning and control of those resources; clause 9.1.1 requires monitoring and measurement with documented information. Aramco and SABIC safety standards extend those requirements with motor-vehicle safety specifications — driver qualification, vehicle inspection cadence, equipment maintenance records — that tier-1 contractors must demonstrate before they bid on upstream work. SiteGuard's five-feature Fleet & Equipment cluster produces the documented information those clauses and standards expect. Fleet Management is the clause 7.1 infrastructure record. Equipment Inspections is the clause 9.1.1 monitoring evidence. Fleet Expiry Alerts is the proactive control clause 8.1 demands. Violation Reporting linked to a Vehicle record is the clause 10.2 nonconformity evidence when a defect is found. Company Scope ensures the entire asset-compliance operation rolls up correctly across entities, so a holding company with twelve subsidiaries produces one audit-grade evidence pack rather than twelve. When an Aramco auditor or a Saudi Civil Defense inspector asks for evidence that your vehicles are road-legal, your equipment is inspection-current, and your drivers are qualified, you open SiteGuard and produce it in minutes — not in the weeks of binder-assembly that legacy EHS tools require.