SiteGuard's Unique Violation Forfeit: Penalties as First-Class Data

Why SiteGuard bakes the forfeit (penalty amount) into the violation object as a first-class field — turning SiteGuard into a fine-and-penalty ledger rather than just an inspection log — and what mainstream EHS suites and leading inspection apps do instead with separate spreadsheets.

Ukkera Team August 15, 2026 12 min read · 1,524 words

Written for: Buyers evaluating differentiation

Most EHS platforms log a violation as a description and a photo — the inspector types what they saw, attaches an image, and submits. The violation becomes an entry in an inspection log that the safety officer reviews and closes. What is missing from this picture is the penalty. In a GCC operating context, violations carry forfeits — financial penalties that the contractor deducts from subcontractor payments, that the Saudi Civil Defense issues for non-compliance, or that an Aramco contractor code levies against a subcontractor for safety violations. These forfeits are real money, and they need to be tracked as carefully as the violations themselves. SiteGuard takes a different approach: the forfeit amount is a first-class field on the violation object, captured at the moment the inspector raises the violation through Violation Reporting. This makes SiteGuard a fine-and-penalty ledger rather than just an inspection log, and it means the forfeit data aggregates naturally into contractor deductions, Civil Defense penalty reconciliations, and audit-grade evidence that the violation was tracked to its financial consequence. This article explains why forfeit-as-data is unique to SiteGuard, what competitors do instead, and why it matters for contractors who deduct forfeits from subcontractor payments and for Civil Defense fine tracking.

What the forfeit field actually captures #

When an inspector raises a violation through Violation Reporting on SiteGuard Field, the platform captures the violation type, the priority, the photo evidence, and the forfeit amount as first-class fields on the violation object. The violation type is a constrained value from a controlled vocabulary configured in Platform Settings — typically fall protection, PPE non-compliance, hot-work permit violation, scaffolding violation, electrical safety violation, or similar. The priority is a constrained value — typically low, medium, high, critical — that drives the closure timeline. The photo evidence is captured through Photo Evidence at the moment of observation, with EXIF metadata preserved. The forfeit amount is a numeric field that represents the financial penalty associated with the violation — whether it is a contractor-internal deduction from a subcontractor payment, a Civil Defense fine, or an Aramco code levy. Once captured, the forfeit amount lives on the violation object through its entire lifecycle: Recent Violations shows it to the worker in the current month, Violation Closure drives the violation through its status workflow with the forfeit attached, Corrective Action Programs assigns the corrective program that resolves the violation, Assigned Actions tracks the closure, and Compliance Reporting aggregates the forfeit amounts into a regulator-ready export. The forfeit is not a separate spreadsheet maintained outside the EHS system — it is a first-class data field that flows with the violation through its entire lifecycle.

What mainstream EHS suites and leading inspection apps do instead #

Mainstream EHS suites treat the violation as an incident record with a description and a severity, but the financial penalty is not a first-class field. The penalty is tracked in a separate spreadsheet the safety officer maintains by hand — typically a contractor-deduction ledger that lists each violation, the subcontractor, the forfeit amount, and the deduction date. The spreadsheet is the source of truth for the financial consequence, while the EHS system is the source of truth for the violation record — and the two are reconciled manually at month-end, which is exactly where the reconciliation errors and the audit failures actually happen. Leading inspection apps treat the penalty as a free-text field on an incident, if at all — there is no numeric forfeit field that aggregates into a fine ledger, no per-violation financial consequence that flows through the violation lifecycle. The result is that an auditor asking "show me the total forfeit amount levied against subcontractor X in the last quarter" gets a manual spreadsheet assembly exercise, not the aggregated forfeit export SiteGuard Compliance Reporting produces by default. The structural gap is that competitors treat the penalty as a side effect documented in a separate system, while SiteGuard treats the penalty as a first-class data field that flows with the violation through its entire lifecycle.

Why this matters for contractor deductions and Civil Defense fines #

For a Saudi contractor running 200 subcontractors across multiple sites, forfeit deductions are a monthly reconciliation event. Each subcontractor has a contract that specifies the forfeit schedule for safety violations — typically a fixed amount per violation type, with critical violations carrying higher forfeits. The safety officer needs to aggregate, by subcontractor, the total forfeit amount for the month, deduct that amount from the subcontractor payment, and produce a documented record of the deduction that the subcontractor can verify and the auditor can review. With SiteGuard, this is a Compliance Reporting export filtered by subcontractor and date range — the aggregated forfeit amount, the per-violation breakdown, the photo evidence, the closure status, all in one document. With a mainstream EHS suite and a parallel spreadsheet, this is hours of manual reconciliation per subcontractor per month, with the audit failure risk that the spreadsheet and the EHS system disagree. For Saudi Civil Defense fines, the same model applies — the regulator issues a fine for a non-compliance finding, the contractor needs to track the fine against the violation that triggered it, and the forfeit field on the violation object is the natural anchor for that tracking. For an Aramco contractor where the Aramco code levies forfeits against subcontractors for safety violations, the forfeit-as-data model is the difference between a defensible deduction ledger and a spreadsheet maintained outside the EHS system.

A worked example: monthly subcontractor deduction #

Consider a Saudi construction contractor running 12 subcontractors across a NEOM package, with each subcontract agreement specifying a forfeit schedule: 500 SAR for a missing-PPE violation, 2,000 SAR for a fall-protection violation, 5,000 SAR for a hot-work permit violation. Over a given month, subcontractor X accumulates six violations: three missing-PPE, two fall-protection, one hot-work permit — a total forfeit of 16,500 SAR. With SiteGuard, the safety officer opens Compliance Reporting filtered by subcontractor X and date range, and the export carries the aggregated 16,500 SAR, the per-violation breakdown (3 × 500 + 2 × 2,000 + 1 × 5,000), the photo evidence for each, and the closure status of each violation — all in one document. The contractor deducts 16,500 SAR from subcontractor X's monthly payment, attaches the Compliance Reporting export as the deduction evidence, and the subcontractor can verify the deduction against the violation records. With a mainstream EHS suite and a parallel spreadsheet, the same reconciliation requires the safety officer to manually aggregate the violations from the EHS system, manually match them against the spreadsheet ledger, manually cross-check the photo evidence, and manually produce a deduction document — a process that takes hours per subcontractor per month and is exactly where reconciliation errors and audit failures happen. For a contractor running 12 subcontractors, the difference is hours per month versus days per month of manual reconciliation work.

How forfeit-as-data fits the violation lifecycle #

The forfeit field does not sit in isolation; it flows with the violation through the entire violation-to-certificate closed loop. Violation Reporting captures it at the moment the inspector raises the violation, with type, priority, photo evidence, and forfeit amount. Recent Violations shows the worker the violation and its forfeit in the current month, so the worker has full visibility of the financial consequence of their safety behaviour. Violation Closure drives the violation through its status workflow — open, under review, corrective action assigned, closed — with the forfeit attached throughout, so the closure record carries the financial consequence. Corrective Action Programs defines the correction program with the type of training required and the certificate that will be issued on completion, so the worker can clear the violation through training. Assigned Actions assigns the program to the specific worker with tracked closure. Certificates and Worker Compliance issue and manage the certificate that resolves the violation. Compliance Reporting aggregates the forfeit amounts into a regulator-ready export filtered by subcontractor, by site, by date range, or by violation type — the natural unit for contractor deductions and Civil Defense fine reconciliations. The forfeit is a first-class data field that flows through the entire lifecycle, not a separate spreadsheet maintained outside the EHS system.

Key Insight

Key takeaways: (1) SiteGuard bakes the forfeit amount into the violation object as a first-class field, captured at the moment the inspector raises the violation through Violation Reporting alongside type, priority, and photo evidence. (2) The forfeit flows with the violation through the entire violation-to-certificate closed loop — Recent Violations, Violation Closure, Corrective Action Programs, Assigned Actions, Certificates, Worker Compliance, Compliance Reporting — making SiteGuard a fine-and-penalty ledger rather than just an inspection log. (3) Mainstream EHS suites track penalties in a separate spreadsheet the safety officer maintains by hand; leading inspection apps treat the penalty as a free-text field if at all. (4) For a Saudi contractor running 200 subcontractors, the forfeit-as-data model is the difference between a Compliance Reporting export that takes minutes and a manual spreadsheet reconciliation that takes hours per subcontractor per month. (5) For Saudi Civil Defense fines and Aramco code levies, the forfeit field on the violation object is the natural anchor for tracking the financial consequence against the violation that triggered it.

Tags violation forfeit trackingpenalty ledger EHSsafety fine trackingcontractor penalty deductionCivil Defense fine reconciliationviolation lifecycleSiteGuard featuresmainstream EHS gap

Frequently Asked Questions

1 What is the forfeit field in a SiteGuard violation?

The forfeit field is a numeric field on the SiteGuard violation object that captures the financial penalty associated with the violation — whether it is a contractor-internal deduction from a subcontractor payment, a Saudi Civil Defense fine, or an Aramco code levy against a subcontractor. It is captured at the moment the inspector raises the violation through Violation Reporting, alongside the violation type, priority, and photo evidence, and it flows with the violation through its entire lifecycle — Recent Violations, Violation Closure, Corrective Action Programs, Compliance Reporting. The forfeit is a first-class data field, not a separate spreadsheet maintained outside the EHS system.

2 How does SiteGuard aggregate forfeits for subcontractor deductions?

SiteGuard Compliance Reporting aggregates forfeit amounts by subcontractor, by site, by date range, or by violation type, producing a regulator-ready export that carries the aggregated forfeit amount, the per-violation breakdown, the photo evidence, and the closure status in one document. For a Saudi contractor running 200 subcontractors, this is the difference between an export that takes minutes and a manual spreadsheet reconciliation that takes hours per subcontractor per month. The export is the natural input to the contractor's monthly deduction reconciliation with each subcontractor, and it carries the audit-grade evidence that the deduction was tracked against the violation that triggered it.

3 How do mainstream EHS platforms track violation penalties?

4 Does SiteGuard support Saudi Civil Defense fine tracking?

Yes. For Saudi Civil Defense fines, the regulator issues a fine for a non-compliance finding, and the contractor needs to track the fine against the violation that triggered it. The forfeit field on the SiteGuard violation object is the natural anchor for that tracking — the fine amount is captured on the violation, the violation flows through its closure lifecycle, and Compliance Reporting aggregates the fines into a regulator-ready export that carries the per-violation fine amount, the photo evidence, and the closure status. For an Aramco contractor where the Aramco code levies forfeits against subcontractors for safety violations, the same model applies — the forfeit field is the first-class data anchor that turns SiteGuard into a fine-and-penalty ledger rather than just an inspection log.