Table of contents
The 3 Major Site Risks
- Financial / Margin: Time wasted searching for unfiled addenda and delayed invoicing of daywork, eroding margins by roughly 15 000 CHF to 35 000 CHF per financial year under the Code of Obligations (CO).
- Legal / Joint Body / SUVA: Inability to produce the safety plan required by art. 4 OTConst or briefing records during a SUVA inspection, halting operations until documentation is clarified.
- Administrative / Handover: Lost technical data sheets and working drawings leaving the as-built documentation incomplete during joint inspection, delaying the release of retention money under standard SIA 118.
Scattering written records across personal email inboxes, foremen's mobile phones, or disorganised local folders exposes Swiss construction firms to critical losses of technical data. For a business in French-speaking Switzerland with 5 to 50 employees, lacking a shared storage setup impairs day-to-day coordination between the technical office, the workshop foreman, and site managers in the field. A disciplined folder structure on an in-house server or cloud host provides the essential baseline to secure workflows, track addenda reliably, and safeguard each project's overall profitability.
This operational guide outlines a proven methodology to roll out a standardised naming system and a repeatable folder template for every project, from the initial sales contact to final administrative closeout. By aligning folders with project phases, managing access permissions under the Federal Act on Data Protection (LPD), and filing safety procedures correctly, management removes duplicate files and guarantees access to contract documents at all times.
Standardised folder architecture for site files
Filing technical and administrative records in a Swiss building contractor requires a single standard template, applied from contract award through to the end of guarantee periods. Fragmented files waste considerable time and make tracking variation orders difficult. To meet traceability rules and the prevention duties defined in CFST 6508 directive, the folder structure must clearly separate contract documents, operational data, occupational safety, and accounting records.
The root folder for each job uses a prefix combining the year and the internal project number (for example 2026_C104_ProjectName). Within this folder, the directory tree branches into subfolders set to read-only for unauthorised staff, minimising the risk of overwriting critical files:
- 01_Offer_Contract: Initial quote, works contract based on the Code of Obligations (CO) or standard SIA 118, signed addenda, formal correspondence with site management. Detailed quantity surveys and tender pricing belong in specialised Soumissions tools.
- 02_Technical_Plans: Fabrication drawings, material data sheets, working drawings approved by civil engineers. Technical drafting and geometric coordination under standard SIA 400 are handled in dedicated CAD software.
- 03_Safety_MSST: Preventive measures, first-aid organisation, chemical safety data sheets, plant operator training certificates, pursuant to LAA and OPA requirements.
- 04_Site_Supervision: Daily site supervision logs, daywork sheets countersigned by local site management, dated progress photos. Formal handover tracking and snagging notices are managed via the dedicated portal features.
- 05_Purchasing_Suppliers: Material purchase orders, checked delivery notes, supplier invoices, and subcontract agreements.
- 06_Invoicing_Closeout: Approved monthly progress payment statements, final account, releases of advance payments, and completion certificates. Wage scales and collective labour agreements (CLA) applying to staff are maintained in human resources folders.
Naming conventions and version control
A rigorous folder tree remains useless if team members save files under vague names such as plan_final.pdf or revised_addendum.xlsx. Your business needs a strict naming convention, documented in your quality manual:
[Date_ISO]_[ProjectNumber]_[DocType]_[Author]_[Subject]_[RevisionIndex]
A formwork drawing issued by the structural engineering office on 14 April 2026 is saved as: 20260414_C104_PLN_ING_Slab-Formwork_RevB.pdf. As soon as a revised version reaches the technical office, the earlier version is immediately moved into an _Archives subfolder. This technical discipline prevents workers on the construction site from reading an outdated plan, a frequent cause of costly building errors.
Regarding data privacy, the employer implements organisational measures compliant with the Federal Act on Data Protection (LPD). Access rights are configured by role: team leaders hold read-only access to drawings and safety files via their site tablets, while financial folders remain strictly restricted to directors and administrative staff.
Comparing document management models for SMEs
Choosing between an on-premise physical server (NAS) and certified Swiss cloud hosting depends on mobility requirements, yard network bandwidth, and team size:
| Operational criterion | On-premise server (NAS / Physical server) | Certified Swiss cloud | Unsynchronised local folders |
|---|---|---|---|
| Access on the construction site | Requires a VPN connection, often slow in rural areas | Direct access on mobile and tablet via dedicated app | Impossible without prior manual file transfer |
| Security and backups | Off-site backup on tape or external drive managed manually | Automated daily backups hosted redundantly in Switzerland | No overall backup, high risk of total data loss |
| Access rights management | Granular management via local directory, complex setup | Easy assignment by user profiles and projects | Non-existent control, open access to local files |
| Compliance audits | Manual search on desktop workstation during safety audits | Immediate availability of MSST files out on site | Documents impossible to find during unannounced checks |
| Maintenance cost | Hardware replaced every 5 years, IT support contract | Predictable subscription per active user, support included | Hidden cost, but heavy financial losses on disputes |
Common filing errors and operational consequences
A lack of filing discipline creates severe operational disruption for day-to-day operations:
- Keeping daywork sheets on foremen's phones: Daywork completed on site that is not forwarded to the technical office within the week slips through monthly billing. In a ten-person firm, failing to validate these billable hours represents an annual margin loss of roughly 18 000 CHF to 42 000 CHF.
- Working from superseded plan revisions: Installing rebar or builder's work openings using an earlier drawing revision forces core drilling and remediation at the contractor's expense. The average extra cost of such non-conformities frequently ranges between 4 500 CHF and 15 000 CHF depending on the structural element.
- Safety documents unavailable on site: During a visit by a SUVA inspector or cantonal authority, failing to produce safety instructions for hazardous substances under the Ordinance on the Prevention of Accidents and Occupational Diseases can trigger a temporary stop-work order on the tasks involved. Sidelining a structural work crew costs around 3 200 CHF in downtime for every lost working day.
- Lack of email instruction tracking: Directives sent by local site management via email must be converted into PDF format and filed in the project correspondence folder. Without them, the contractor faces an uphill struggle establishing claims in financial disputes over breaches of duty under the Code of Obligations (CO).
Illustrative practical cases (typical scenarios on Swiss construction sites)
The following practical scenarios illustrate how Swiss trade contractors handle document management decisions.
Scenario 1: Heavy refurbishment in an urban centre (Canton of Geneva)
A general contractor specialising in masonry with 24 employees is refurbishing a residential building in central Geneva. Fast-paced architectural revisions require weekly updates to drawing revisions. The firm previously operated an on-premise server accessible only from its Carouge headquarters. Site foremen routinely relied on outdated paper prints, causing recurrent errors on floor slab penetrations.
Management migrated all project folders to a Swiss cloud environment structured using the standardised folder template. Permissions were locked down: foremen have synchronised tablet access to approved plan folders and safety instructions. Outdated drawings are routed straight into the archive folder. When the engineer made an unexpected adjustment to a ventilation shaft, the updated drawing was checked in real time on the construction site, averting partial demolition work with an estimated remedial cost of around 8 500 CHF.
Scenario 2: Carpentry and Sheet-metal Work SME (Canton of Fribourg)
A Fribourg workshop with 12 craftsmen is erecting the timber frame and roofing of an industrial hall in the Glâne district. Variation dockets and safety induction records were historically kept in carbon-copy books inside the vans. During an occupational safety inspection focusing on fall protection, the foreman could not produce the written training records mandated by CFST 6508 directive, triggering administrative friction with site management.
The business adopted a strict naming scheme alongside instant uploads of signed, photographed forms into the 03_Securite_MSST directory straight from company phones. At the same time, every daywork slip signed off by the client's representative is uploaded to the 04_Suivi_Chantier folder the very same day. This automated process allowed the firm to recover every single daywork hour at final account closeout, securing an additional billing amount of about 14 250 CHF that would have been disputed without indexed documentation.
Frequently asked questions
How can safety files be organised under CFST 6508 directive without cluttering the server?
MSST documentation belongs in a dedicated company root folder, then branches out by construction site under art. 5 OTConst naming the appointed competent person. Chemical safety data sheets remain centralised to prevent duplicates.
Where should detailed quantity take-offs and tender estimates be stored without cluttering the execution folder?
Price calculations and preparatory take-offs are kept apart in the project's upstream commercial folder. For everything concerning ACIP unit prices, CAN quantity surveys, and tender estimates, link to /soumissions/ to keep the technical folder structure clean.
Where should handover and acceptance minutes drawn up under standard SIA 118 be filed?
Final contract closeout records belong in the project's administrative closeout directory. To track joint inspection records, acceptance minutes, and client snags under standard SIA 118, refer to /portail/.
Where should payslips and employment contracts for construction site staff be stored?
These personal records must strictly remain in the secure HR folder of the fiduciary or management. To handle collective agreement wage scales, recruitment, and employment contracts, refer to /jobs/ without cluttering operational folders.
How can you manage successive versions of architect plans without risking dimensioning errors?
Every newly received file replaces the direct access link and archives the previous revision index in a dedicated subfolder. For drawing plans according to standard SIA 400 and tracking revision indices, refer to /plans/.
What budget should a French-speaking Swiss SME anticipate to restructure the cloud for ten users?
Technical configuration, migration of active folders, and training for site supervisors typically require external consulting support ranging from 3 500,00 CHF to 6 200,00 CHF, which pays for itself in the first year through saved administrative time.
A standardised cloud folder structure safeguards the profitability of French-speaking Swiss SMEs by eliminating file loss and versioning errors on site. Enforcing strict naming conventions guarantees direct access to technical and safety records for every site manager.
To further develop operational standardisation across your company, explore our professional guides and tools:
- MSST System Under CFST Directive 6508: Standardising Procedures and Quality for a Building Contractor
- "5 Whys" Analysis Generator for Incidents and Non-Conformities
- CFST Directive 6508 Explained to Construction SMEs: Industry Solutions
- Drafting a Visual Operating Procedure Understood by Multilingual Teams
- Deploying QR Codes on Plant, Power Distribution Boxes, and Vans
