Reading Time - 7 minutes
Prepare the SAG file cleanly for a SOKA audit
For a SOKA audit, a loose collection of Excel sheets, photos, and emails is often no longer enough. What matters is a traceable file in which site report, weather reference, downtime, and employee hours are consistently linked.
Anyone preparing for a SOKA audit in scaffolding should not treat the SAG file as a place to dump documents afterward. The real audit object is the chain of evidence: what was reported on which site and when, what weather conditions applied, what work was unable to take place, and how the hours were assigned to the affected employees?
This is exactly where, based on current signals from practice, most follow-up questions arise. The main issues are Excel lists compiled after the fact, unclear weather evidence, and missing links between the site report and the hours. For summer bad weather allowance 2026, a clean file structure geared toward auditability is therefore more important than collecting as many individual files as possible.
* * *
What auditors typically want to see in an SAG file
The available evidence does not produce a rigid official template, but it does create a clear expectation: the file must be built promptly, plausibly, and case by case. A good SAG file answers the auditor’s core questions without long searches.
- Which site is affected?
- For which day and time period was the weather-related stoppage reported?
- What weather-related reason was documented?
- Which weather record or snapshot supports the report?
- Who reported the case or reviewed it in the office?
- Which employee hours were assigned to this exact case?
The faster these points can be found in a file, the lower the risk of follow-up requests. That is exactly why loose folder structures with screenshots, chat histories, and hours lists added later often perform poorly in audits.
A practical structure for an audit-ready SAG file
In practice, a structure by individual case works better than one organized only by month. Each weather-related stoppage should be readable as its own case. That keeps the audit trail understandable even when several sites, crews, or stoppage days are running in parallel.
| Component | Purpose in the audit |
|---|---|
| Site details | Clearly assigns the case to a specific work location |
| Date and time period | Shows when the stoppage occurred |
| Weather reason | Makes the trigger for the report understandable |
| Weather snapshot or weather record | Supports the report with a timely reference |
| Optional photos | Add context, but do not replace the core data |
| Office review | Documents that the case was reviewed internally |
| Employee and hours assignment | Links the weather case to payroll preparation |
| PDF or file export | Makes the case complete and ready to hand over |
The order matters. First comes the report of the event on site, then the office review, and only after that the assignment of hours. If this sequence is reversed, the file quickly looks assembled afterward rather than maintained as events happened.
These types of evidence must match consistently
In practice, cases rarely fail because a document is completely missing. More often, several records do not fit together cleanly. Then there is data, but no reliable story of the case.
- The site name in the report and in the hours assignment is not identical
- The times in the weather record do not match the reported stoppage window
- The weather reason is phrased too generally and is not tied to the time period
- Photos exist, but without a clear reference to the date or site
- Employee hours are assigned in bulk by month rather than by weather case
- It remains unclear who reported the case and who approved it internally
A strong SAG file does not consist of as many attachments as possible, but of a small number of records that clearly point to one another.Audit logic instead of a file collection
Anyone preparing their summer bad weather allowance evidence should therefore read each file once like an external auditor would: is the connection understandable without prior knowledge? If not, the problem is usually not lack of volume, but lack of structure.
How to keep the weather reference traceable
One central trend from current search and practical signals is the growing expectation for timely, verifiable weather documentation. Pure retrospective lists are viewed more critically when no clear connection to the reported event is visible.
For a robust file, at minimum the location, time, weather reason, and the corresponding site report should be brought together. Additional photos can be useful, but they are only supplementary evidence. The decisive point is that the weather reference is linked directly to the stoppage case.
You can find more on which details are typically missing from weather evidence in How to document weatherproof evidence correctly in scaffolding and Audit-proof weather file in scaffolding: what really needs to be included.
Hours assignment: the most common break in the file
The second critical point is the link between the weather case and employee hours. This is exactly where questions arise from the payroll office and later during the audit when a stoppage was reported, but it is not clearly visible which people and which hours were specifically affected.
- First, record the weather case clearly.
- Then review internally whether the case is complete.
- Only after that assign the affected employees.
- Document the lost hours per employee on the specific case.
- Transfer the data as a complete set to PDF and CSV.
For the handover to payroll, it helps to separate the formats: the file explains the facts, while the structured export passes on the data relevant for payroll processing. This split is also attractive for companies that do not want major ERP integration but still need auditable records.
Read more about a clean handover in Payroll office SAG export: how to avoid returns and Prepare SAG for the payroll office: what must be finished first.
Who should handle which task during preparation
An SAG file usually becomes confusing when responsibilities are not clearly separated. For audit-ready processes, each role needs a clear contribution.
| Role | Responsibility |
|---|---|
| Foreman or site lead | Reports the weather-related stoppage promptly with location, time period, and reason |
| Office team | Checks completeness, assigns the case correctly, and requests missing details |
| Site management | Helps validate the connection to the site |
| Payroll office or payroll team | Takes over the structured hours and case data for further processing |
| Management | Ensures the process and document retention are in place |
If these tasks are already clear before the audit, the file is not assembled only at the end, but built continuously. That reduces the risk that data has to be reconstructed from memory.
Also relevant: SOKA allowance report: who provides which data?.
Practical checklist before the SOKA audit
- Can each weather case be found as an individual record?
- Are the site, date, and time period clearly documented for each case?
- Is the weather reason specifically stated for each case?
- Is there a timely weather record or snapshot?
- Are optional photos correctly assigned to the case?
- Is it visible who reported the case and who reviewed it?
- Are employees and lost hours assigned by case rather than only by month?
- Is there a complete PDF record and, if needed, a CSV export for the payroll office?
- Can follow-up questions be answered without first searching through chats, emails, or folders?
Typical mistake
How digital SAG files simplify audit preparation
Especially in scaffolding, the effort is high when reports have to be gathered from many sources. That is why the product logic of the SAG file focuses on a lightweight process: the office creates the organization, sites, and employees; foremen report via a token-protected link without an admin login; the office reviews the case, assigns hours, and exports PDF and CSV.
This is especially helpful where companies are looking for an auditable documentation chain without introducing a complex ERP system. It is important not to create false expectations: this is not legal advice or full payroll automation, but structured, audit-oriented documentation for summer bad weather allowance.
If you want to go deeper into the overall process, Introducing digital SAG documentation 2026 in scaffolding and Scaffolding SOKA audit 2026: these records are often missing are also relevant.
Conclusion
A clean SAG file for a SOKA audit is not created shortly before the appointment, but through a clear day-to-day documentation logic. When the site report, weather reference, responsibility, and hours are brought together for each case, many individual data points become a traceable file.
For scaffolding companies, this means in practice: fewer records, but well linked, are better than large collection folders with no audit trail. That reduces follow-up questions and makes documents much cleaner to prepare for the office, payroll office, and the audit.