Most safety software rollouts stall in week three — somewhere between the vendor demo and the first real inspection on a real site. SiteGuard was built to invert that pattern: register at apps.ukkera.org/sg-manager/register, import your Sites from a spreadsheet, create your first Daily Plan, and watch an inspector close a GPS-stamped visit with photo evidence on the same afternoon. The 15-minute benchmark is not a marketing line; it is the threshold at which a safety system stops being an IT project and starts being a daily habit. This guide walks a new HSE manager through the six concrete steps that take SiteGuard from zero to a closed-loop violation report, in Arabic or English, on a real site.
Why 15 minutes is the right benchmark #
Fifteen minutes is the maximum elapsed time a foreman or HSE manager will tolerate between signing up and seeing the system produce value. Beyond that threshold, attention moves to the next fire and the rollout stalls. SiteGuard collapses onboarding to that window because the platform was designed around the daily-plan-to-violation-to-closure loop, not around a configuration wizard. The six steps below require no consultant, no implementation call, and no SQL — only a spreadsheet, a phone with the SiteGuard Field app, and a real site to inspect. If you can open a browser, you can finish this guide in one sitting, the same afternoon you decided to evaluate SiteGuard.
Step 1 — Register your SiteGuard Manager account #
Open apps.ukkera.org/sg-manager/register in your browser and complete the registration form with your work email, company name, and a password. SiteGuard sends a verification link that activates your Company Scope, the multi-entity container that lets you later split operations across subsidiaries, contractors, or business units if needed. Within a minute, you land on the SiteGuard Manager dashboard — the command center for safety officers, with Sites, Daily Plan Management, Violation Closure, and Corrective Action Programs visible in the navigation. There is no implementation consultant, no kick-off call, and no SSO configuration blocking your first inspection. The platform's self-serve registration is the same path Aramco-tier contractors and tier-3 subcontractors both follow, which is exactly the point.
Step 2 — Import Sites from a spreadsheet #
Site Import is the feature that turns a spreadsheet into your site master in one upload. Open Sites from the navigation, click Import, and upload a CSV or Excel file with columns for site code, name, GPS latitude, GPS longitude, and the responsible HSE contact. SiteGuard validates the rows, flags duplicates or malformed coordinates, and creates a Site record for each valid row, complete with GPS location and a linked Corrective Action Programs ledger. For a contractor with 30 active sites across NEOM, Red Sea, and Diriyah, the entire import typically completes in under two minutes — a task that would have consumed a full week of manual entry in a legacy EHS system. Every Site record becomes the anchor that GPS Check-in later validates against when an inspector arrives on site.
Step 3 — Create and assign your first Daily Plan #
Open Daily Plan Management and click New Plan. Select the Site, the inspector who will execute it, the planned date, and the Checklist Template that defines what the inspector must verify on arrival. SiteGuard stores the plan in Draft status until you publish it. Publishing pushes the plan to the inspector's SiteGuard Field app under Today' Plans, where it appears alongside any other plans assigned for the same day. Assignment happens the moment you select an inspector in the plan form — the inspector receives a push notification through SiteGuard Field that includes the site name, the planned checklist, and any Plan Actions, the supplementary tasks like verifying a permit or witnessing a toolbox talk. For your first plan, skip Plan Approval and publish directly so you can see the end-to-end flow within minutes; on high-hazard sites you will later enable approval to require a senior HSE manager's second pair of eyes before the plan reaches the field.
Step 4 — Your inspector’s first GPS-stamped visit #
On site, the inspector opens the plan in SiteGuard Field and taps Check-in. The app captures the device GPS coordinates and compares them against the site's stored GPS. If the inspector is within the configured radius — typically 100 metres for a construction site, tighter for a confined-space entry — the visit is marked as on-site and the timestamp is locked. This single record is the most valuable piece of evidence SiteGuard produces, because it answers the auditor's first question: was the inspector actually there? Once checked in, the inspector proceeds to the Dynamic Checklist, which adapts its items to the site type and hazard profile defined in the template. A site classified as high-rise construction surfaces edge-protection and harness items that a civil-works site will not, and a positive answer about hot work triggers a sub-list of permit-to-work and gas-test records.
Step 5 — Log your first violation report #
Inside the checklist, when the inspector encounters a nonconformity — an unprotected edge, a worker without a harness, an expired fire extinguisher — they tap Report Violation and the Violation Reporting form opens. The form captures the violation type from a configured list, the priority (low, medium, high, critical), a textual description, one or more Photo Evidence attachments, and the forfeit amount if your organisation applies financial penalties to subcontractors. Submitting the violation pushes it to Recent Violations on the inspector's device and to the manager's Violation Closure queue in SiteGuard Manager. From there, the violation moves through statuses — Open, In Review, Corrective Action Assigned, Closed — until a Corrective Action Program is created, assigned to a responsible user, and closed with a reviewer and a certificate. That closed loop is the moment SiteGuard stops being an inspection app and becomes a safety management system, satisfying ISO 45001:2018 clause 10.2 (incident, nonconformity, and corrective action) without any additional configuration.