Skip to main content

Reading Time - 7 minutes

Scaffolding Compliance for SAG: Who Documents What?

When it comes to summer bad weather allowance in scaffolding, auditability often fails not because of the weather itself, but because responsibilities are unclear. This article shows a clear role-based logic between management, site management or foremen, the office, and payroll, so that individual reports become a traceable SAG file.

Scaffolding Compliance for SAG: Who Documents What?

In scaffolding, the key question for summer bad weather allowance is rarely just whether a weather-related stoppage occurred. In practice, most of the work arises where it is unclear who must provide which information. That is exactly what leads to follow-up questions from the office, breaks in the handoff to payroll, and gaps in the documentation file later on.

For 2026, it is therefore not only important to maintain clean weather-related stoppage documentation, but also a reliable distribution of roles. Management sets the standard. Site management or the foreman reports the stoppage. The office reviews it, adds details, and assigns hours. Payroll should only take over once the file is complete and has been internally validated for plausibility.

An auditable SAG file is not created by a single form, but by a clear sequence of responsibilities.
Practical logic for scaffolding in 2026

Why the question of responsibility matters so much

Current industry signals strongly revolve around audit pressure, the SOKA context, and recurring follow-up questions about weather, time periods, and employee hours. At the same time, many companies report that notifications come in via WhatsApp, phone calls, or loose Excel files. The issue is then not just the format, but the missing separation between recording, review, and payroll preparation.

When everyone documents everything a little bit, it often ends up being unclear who originally reported the issue, who reviewed the information, and on what basis hours were handed over to payroll. This gap is exactly a compliance issue in the operational sense: traceable, consistent, and internally auditable.

* * *

The 4 roles in SAG documentation

Role Main task What is documented What should not rest solely with this role
Management Define the process and standards internal guidelines, responsibilities, approval logic individual reporting of site events
Site management or foreman Report from the place where it happened construction site, period, weather reason, location, optional photos, initial description final payroll allocation
Office Review and maintain the file plausibility check, assignment of employees and lost hours, documentation file inventing missing site data afterward
Payroll Process the data handed over payroll-relevant processing based on complete documentation retrospective research into the weather event on site

1. Management: set standards, do not collect individual cases

Management is responsible within the company for making sure the process works in the first place. That does not mean documenting every weather situation personally. What matters is that before the season begins, it is clear which fields must always be captured, who approves cases, and by when reports must reach the office.

  • Which construction sites are set up for reporting
  • Who is allowed to submit reports from the site
  • Which minimum data is mandatory
  • How missing or contradictory information is handled
  • When a case may be forwarded to payroll

If these rules are missing, responsibility shifts informally to the foreman, the office, or payroll accounting. That is exactly how situations arise in which no one can later say with confidence whether the documentation was compiled completely.

2. Site management or foreman: report the stoppage immediately and specifically

Site management or the foreman provides the primary information. This role is closest to the construction site and should therefore report the event directly. The closer in time the report is to the stoppage, the more reliable it is. For weather evidence in scaffolding, what matters above all are specific data points, not general statements such as "weather too bad."

  • Construction site or project reference
  • Date and period of the stoppage
  • Reason for the weather-related work stoppage
  • Location or GPS reference of the report
  • Weather snapshot at the time of reporting
  • optional photos as a supplement, not as the only evidence
  • brief description of why work was specifically interrupted

The distinction is important: the foreman reports the facts, but should not single-handedly determine the final hour allocation for all affected employees if that still needs to be reviewed by the office. This separation is exactly what keeps the process clean.

If you want to go deeper into the site perspective, see the related SAG Foreman Checklist 2026 for Weather-Related Stoppages.

3. Office: review, assign, complete the file

The office is the central hub for compliance-oriented preparation. This is where site reports are not reinvented, but reviewed and turned into a traceable structure. That includes checking whether the report is complete and whether the period, site, and weather reference fit together plausibly.

  • Check the completeness of the report
  • Clearly assign reports to a specific construction site
  • Add the affected employees
  • Document lost hours per employee
  • Combine supporting records into an organized documentation file
  • Create CSV and PDF only after internal review

Especially for lost hours in scaffolding, this is a typical source of errors: hours are sent to payroll even though the original weather-related stoppage report is still incomplete. A better sequence is the reverse: first review the facts, then assign the hours, then prepare the export.

The article Preparing an SAG File Properly for the SOKA Audit also shows how such a file can be structured.

4. Payroll: take over, do not investigate afterward

Payroll needs structured, understandable, and complete records. It should not have to take on the role of piecing together a case from individual messages. If follow-up questions about the construction site, period, employees, or supporting records only arise there, the process had already become too messy beforehand.

In practical terms, this means the handoff should include an SAG file with traceable supporting records and a consistent basis for hours. This also aligns with the requirements around payroll documents and a clean SAG export without returns.

* * *

Which data should at minimum be available for each role

Data point Primarily responsible Reviews or supplements
Construction site Site management or foreman Office
Date and time Site management or foreman Office
Reason for weather-related stoppage Site management or foreman Office
Weather snapshot or location reference Site management or foreman Office
Photos optional Site management or foreman Office
Affected employees Office based on the construction site internal approval
Lost hours per employee Office Payroll takes over
PDF documentation file Office internal review before handoff
CSV for payroll Office Payroll

The 6 most common gaps in practice

  1. The weather-related stoppage is reported, but without a clear time period.
  2. There are photos, but no clear construction-site reference.
  3. The site report exists, but the affected employees are missing.
  4. Hours are estimated before the office has reviewed the case.
  5. Payroll receives CSV data without a connected documentation file.
  6. Responsibilities are only agreed verbally and change from one construction site to another.

These patterns keep appearing when companies apply for summer bad weather allowance or prepare for a later audit. Standardizing here saves less on clicks than on follow-up questions. That is exactly what makes the difference between an improvised collection and reliable documentation.

Practical role logic for 2026

A working structure for 2026 is deliberately simple: the construction site reports quickly and specifically. The office reviews centrally. Payroll receives only finished cases. This keeps responsibility clear and makes the file much more auditable from an operational perspective.

If you want to set up the overall process even more cleanly, these articles are useful complements: Scaffolding Compliance 2026 for Weather-Related Stoppages, SOKA Allowance Evidence 2026: What Really Has to Be Available and Payroll and Summer Stoppages: These Handover Errors Cost Time.

For scaffolding companies, the core question is therefore not only: Have we documented a weather-related case? It is also: Is it clear throughout the process who provides which information first, who reviews it, and who processes it further? Only then does a single report become an SAG file that the office and payroll can actually work with.