Anyone preparing for a summer stoppage pay audit quickly notices one thing: in the 2026 SOKA audit, scaffolding companies are often missing more than just individual records. What is frequently missing is the traceable link between the construction site report, weather conditions, time window, employee assignment, and lost working hours. Those are exactly the gaps that trigger follow-up questions.

Current signals from search, forums, and LinkedIn keep pointing to the same issues: stricter audits, more focus on GPS-related weather data, and clearly documented links between the affected crew and the recorded hours. For scaffolding companies, that does not automatically mean more bureaucracy, but it does mean much more structure in the file.

This article shows which supporting documents are often missing in practice and how to prepare your documentation for SOKA in scaffolding so that the site team, office, and payroll office all work from the same data basis.

* * *

What the audit comes down to in practice

At its core, providing evidence is not about collecting as many files as possible, but about plausibility. An auditable file should answer these questions directly: What happened, when, and on which construction site? What were the weather conditions? Who was affected? How many lost hours were assigned? And do these details appear consistently in the export for the payroll office?

A typical objection is not just “weather record missing,” but rather: the weather event, affected employees, and hours are not properly linked to each other.

From the current 2026 research brief

These 6 supporting documents are especially often missing in the 2026 SOKA audit

1. Missing initial report from the construction site

Many companies may later have weather data or hour lists, but no proper initial report from the construction site context. That means the starting point of the file is missing. Without an early report, it is difficult to understand when the stoppage was identified, who reported it, and exactly which site it refers to.

• The site name or a clear site assignment is missing
• The date and time of the report are not documented
• The reporting person cannot be identified
• The reason for the weather-related stoppage is described too vaguely

In practice, this means the construction site must trigger the case immediately rather than trying to reconstruct it later from memory. A standardized reporting route is helpful, as described in the article Weather documentation for site foremen in scaffolding.

2. Weather data without a clear location and time reference

A general weather note or a screenshot without a clear assignment is often not enough as reliable proof. If a weather record does not show which location and period it belongs to, it creates exactly the uncertainty that leads to questions during an audit.

Based on current signals, GPS-related or location-specific weather information stored together with the reported stoppage period is especially relevant. That does not mean every photo alone is sufficient. What matters is the link between place, time, and event.

• Weather screenshot without a date
• Photo without a reference to the construction site
• Weather record does not match the reported stoppage window
• Several construction sites use the same imprecise weather attachment

You can also read more about making weather records more audit-ready here: Scaffolding weather proof and in the article Weather photos as proof in scaffolding 2026.

3. No clearly documented stoppage time window

One common weak point is vague time information. “Rain in the morning” or “work not possible” is too imprecise for an audit. If the start and end of the stoppage are missing or only estimated, the later allocation of hours is difficult to validate.

Especially in combination with lost hours in scaffolding, it must be clear which specific time window was affected. Otherwise, the report, hours, and later CSV export will not line up.

4. Employee assignment is missing or exists only as a collective note

This is currently one of the most visible audit points. According to the research, the combination of weather event, affected crew, and recorded hours is often challenged. A file is incomplete if it documents only a general site stoppage without showing which employees were actually affected.

• Only the crew name is listed, without individual employees
• Employees are added later by the payroll office
• Different spellings appear between the report and payroll documents
• There is no clear assignment of who was on site and who was not

That is exactly why the construction site report should not remain isolated. The office and payroll office need a shared, auditable structure. The related follow-up article is SOKA stoppage pay report: Who provides which data?.

5. Photos exist, but without file logic

Photos are often overestimated and at the same time filed incorrectly. An image of rain, wet conditions, or wind can be helpful, but it does not replace complete documentation. If photos are not linked to the site, timestamp, and report, they remain only isolated supplementary files.

Photos make sense as additional evidence within a structured file, not as the sole proof strategy. If you want to read more, you will find a practical classification in the article Weather photos as proof in scaffolding 2026.

6. PDF and CSV do not match

A very practical problem arises at the end of the process chain: the construction site report looks different from the hour list, and the export for the payroll office uses different labels again. Then the construction site, employees, date, or hours in the PDF file and CSV no longer match.

These breaks become especially visible when cases are handed over to the payroll office. That is why companies should check early on whether the information from the report, internal review, and export really carries through identically. Related reading: CSV export for the payroll office: These fields must match and Scaffolding payroll SAG: Handover to the payroll office without breaks.

* * *

Quick check: Is your SAG file audit-ready?

If one of these columns can only be answered with emails, chat histories, or loose screenshots, the file is usually not yet robust enough for an audit-oriented handover.

How the office, construction site, and payroll office can close the typical gaps

1. Standardize construction site reports: use the same mandatory fields on every report.
2. Store weather records directly with the location and time window instead of collecting them separately in folders.
3. Verify employees first, then assign hours, instead of adding them later from memory.
4. Use photos only as supplementary evidence and always attach them to the specific report.
5. Before handing the case to the payroll office, run a consistency check between the report, PDF, and CSV.

This structure is exactly what makes the difference between “documents available” and “documents audit-ready.” Companies that consolidate their summer stoppage pay supporting documents early reduce follow-up questions and, above all, save time in internal coordination.

Practical thinking: complete cases are better than late bulk fixes

Many scaffolding companies do not work with a large ERP system, but with site communication, office review, and external payroll preparation. That is exactly why a simple, clear process is worthwhile. A good file is not created shortly before the audit, but at the first weather-related stoppage on the construction site.

If the report, weather snapshot, optional photos, and employee hours are brought together from the start, you can later generate a traceable PDF file plus a CSV for the payroll office. This is especially relevant for companies that want to document summer stoppage pay in scaffolding without media disruptions.

Conclusion

In the 2026 SOKA audit for scaffolding, what is often missing is not spectacular paperwork, but the clean connection between the data that already exists. Companies that bring together the construction site report, weather record, time window, employee assignment, and export structure are far better prepared than companies relying on individual documents collected afterward.

The best time to build an audit-ready file structure is not during the audit itself, but with the next documented weather-related case. If you want to set up your 2026 season properly, that is exactly where your process should begin.