Table of contents
The 3 Major Site Risks
- Financial / Margin: Dispersed supporting documents lead to lost traceability for daywork or addenda. On an average project, untracked hours represent a gross margin loss in the range of 15 000 CHF to 35 000 CHF per year under the Code of Obligations (CO) rules governing contracts for work and services.
- Legal / Joint Body / SUVA: The lack of direct tablet access to mandatory records exposes management to work stop orders during labor inspectorate or SUVA audits. Under art. 4 OTConst, the employer ensures there is a plan detailing the required measures for the work performed, drawn up in writing or in a form that allows proof by text.
- Administrative / Acceptance: An inability to produce quality inspection reports, technical data sheets, or daily site logs delays the joint inspection required by standard SIA 118, holding up the final account and the release of retention money.
In a French-speaking Swiss construction SME of 5 to 50 employees, scattered documents across email inboxes, local drives, and site messaging apps waste considerable time. Applying a standard folder structure and naming convention ensures every site manager, foreman, or administrative assistant retrieves any technical record in under ten seconds. This standardized setup removes duplicate versions, steadies core workflows in your enterprise management system, and makes end-to-end project records dependable.
This digital filing protocol relies on a strict chronological root and universal topic folders, ready for use in the office or out in the field. Methodical folder organization ensures compliance with CFST 6508 directive requirements by centralizing safety plans and compulsory certificates. This approach also protects business data under the Federal Act on Data Protection while making it easy to hand administrative files over to site management and your fiduciary without unnecessary handling.
Filing system architecture and algorithmic logic
Filing standardization relies on a deterministic rule that eliminates data entry discrepancies between desktop workstations and mobile devices. To ensure technical interoperability across Windows, macOS, Linux, and the NAS servers common in French-speaking Swiss SMEs, the generator applies strict filtering to the root folder string:
Root = YYYY-NNN_Client_Location
The sanitization algorithm runs four sequential operations during client-side input:
- Complete removal of diacritics (accented letters like "é", "è", or "à" become "e" or "a", cedillas "c").
- Replacement of any non-alphanumeric character (spaces, slashes, apostrophes, punctuation marks) with a single hyphen "-".
- Truncation of the "Client" and "Location" segments to 30 characters each to prevent exceeding maximum system path limits.
- Incrementation of a two-digit numeric prefix (00, 01, 02...) on every subfolder to enforce a strict alphanumeric sort order on all browsing devices.
This directory tree aligns directly with the recordkeeping requirements of CFST 6508 directive. Immediate centralization of safety data sheets, training certificates, and accident reports prevents administrative penalties during joint-commission audits or SUVA inspections. Likewise, safety plans required by federal ordinances receive a fixed, predictable location, eliminating scattered records.
Standardized Operational Subfolder Structure
The default directory tree generated for each new project covers the entire construction lifecycle, from initial contract set-up to as-built documentation:
| Index | Subfolder title | Standardized document contents | Average access time | Organizational impact |
|---|---|---|---|---|
| 00 | 00_Administrative-Contract | Contract for work, purchase orders, insurance policies | < 10 seconds | Immediate verification of specific contract clauses |
| 01 | 01_Safety-MSST | Safety plan, CFST 6508 directive, job safety sheets | < 5 seconds | Immediate compliance during unannounced SUVA checks |
| 02 | 02_Drawings-Technical | Approved shop drawings, material technical sheets | < 15 seconds | Elimination of version errors on the jobsite |
| 03 | 03_Site-Tracking-Meetings | Daily site reports, site meeting minutes | < 10 seconds | Clear traceability of site management instructions |
| 04 | 04_Addenda-Daywork | Signed daywork sheets, variation notices | < 10 seconds | Full protection of additional billing claims |
| 05 | 05_Billing-Closeout | Monthly payment certificates, final account, acceptance minutes | < 10 seconds | Fast financial closeout with your fiduciary |
Financial Impact of Unstandardized Document Storage
In a firm with 15 field workers and 2 site managers, time spent hunting down scattered backup documents (especially daywork sheets and technical sheets) directly erodes project margins. Here is an indicative cost estimate for a company running 45 construction sites per year:
- Average time wasted per construction site without uniform naming: 3,50 hours (email searches, outdated drawings, misplaced daywork slips).
- Cumulative unproductive hours across 45 construction sites: 157,50 hours of site management time.
- Standard hourly rate for site management: 110,00 CHF excl. VAT.
- Annual gross financial loss (direct labor): 17 325,00 CHF excl. VAT.
- Incidental costs for duplicate printouts and phone calls: 1 250,00 CHF excl. VAT.
- Total direct disorganization costs: 18 575,00 CHF excl. VAT.
- Value added tax (Swiss VAT 8,1%): 1 504,60 CHF.
- Total cost attributable to lack of naming conventions: 20 079,60 CHF incl. VAT.
Illustrative practical cases (typical scenarios on Swiss construction sites)
The following two cases are standard scenarios developed for methodological analysis to illustrate how standardized folder structures work in representative regional settings.
Scenario 1: Major Urban Renovation (Canton of Vaud)
A Vaud masonry and plastering contractor with 18 workers is renovating a residential rental building in Lausanne. The contract amount is 420 000,00 CHF. With no common standard in place, the foreman was keeping photos and daywork slips in a messaging app, while the technical office filed addenda in a local folder inaccessible from the site.
Using the generator produced the root folder 2026-018_Caisse-Pensions-VD_Lausanne-Grand-Chene. Modification slips were consistently stored under 04_Avenants-Regies using the pattern 2026-03-12_2026-018_regie-demolition-radier.pdf. During the final account review with site management, all 14 contested daywork slips were produced on the spot along with matching digital signatures. The contractor recovered 18 450,00 CHF excl. VAT in daywork that would otherwise have been written off for lack of verifiable records.
Scenario 2: Steel-Framed Industrial Building (Canton of Fribourg)
A Fribourg steel construction firm with 8 shop workers and 4 erectors is building a logistics hall in Bulle. During an unannounced labor inspectorate visit checking compliance with CFST 6508 directive, inspectors demanded immediate access to safety data sheets for chemical anchors and the personal protective equipment inspection register.
The erection foreman brought up folder 2026-007_Logistique-Gruyere-SA_Bulle-Planches on his tablet and opened 01_Securite-MSST. The required inspection certificates and technical sheets were displayed in less than two minutes. Immediate compliance avoided any stoppage of erection operations, keeping the schedule on track and preventing standstill expenses estimated at an illustrative 4 800,00 CHF per downtime day.
Frequently asked questions
How should safety records be structured under CFST 6508 directive?
Create the 02_Securite subfolder to organize certificates, safety notices, and technical sheets. This keeps traceability effortless during regular SUVA audits across your French-speaking Swiss construction sites.
Where should the plan required by art. 4 OTConst be filed?
The plan required by art. 4 OTConst is filed under 02_Securite. This folder layout ensures site management has verifiable textual access before field operations actually start.
How much does time wasted searching for misnamed files really cost?
For a ten-person SME, misplaced records cause an estimated loss in the region of 450.00 CHF per month. A standardized root folder puts a stop to these recurring administrative drains.
Why avoid accents and spaces in folder and file names?
Remote servers and mobile operating systems often mishandle diacritics. Replacing spaces with hyphens prevents broken cloud links for installation teams working in the field.
Where should detailed quantity takeoffs and unit prices be archived?
Detailed statements and CAN itemized bills belong in the tenders workspace. Keep only confirmed and signed order confirmations in the project contract subfolder at the office.
How should SIA 118 joint inspection reports be managed?
Work acceptance records and formal notice of defects submissions under standard SIA 118 are managed through our dedicated portal to maintain proof of delivery without cluttering root folders.
Rolling out a standardized naming structure makes daily operations reliable and safeguards your firm's margin. Keep improving your operational processes with our organizational engineering guides:
