The digital site diary is the electronic daily operational log that documents progress, attendance, events and site changes. When properly managed with a qualified digital signature, time stamping and compliant substitute preservation, it acquires full evidentiary value in the event of a dispute, acceptance inspection or audit. It is not simply a convenient alternative to paper: it is effectively mandatory for anyone working on public contracts governed by the D.Lgs. 36/2023 (Public Contracts Code), and a defensive choice for anyone who wants to document work in an irrefutable way.
Three actions to take immediately:
- Activate a platform with integrated digital signatures, an audit trail and certified substitute preservation.
- Define the log’s mandatory fields (date, weather, attendance, activities, variations and geotagged photographic attachments).
- Train the works director and foremen on the daily closing procedure, including validation by the end of the day.
One tip: Before choosing software, simulate an audit: export 30 days of diary entries, verify that the audit trail is complete and that the signature can be verified. If the platform fails this test within 10 minutes, it is not compliant.
Key points
The digital site diary has full evidentiary value only if a qualified digital signature, time stamping and AgID substitute preservation are all present and verifiable.
| Point | Details |
|---|---|
| Regulatory compliance | A qualified digital signature, time stamping and an AgID-accredited preservation provider are the three non-negotiable requirements. |
| Minimum mandatory fields | Date, weather, attendance, activities, progress, materials, variations, incidents and geotagged attachments. |
| Daily workflow | Complete the log by the end of the day and sign it immediately: entries added in bulk at the end of the week can be challenged. |
| Rapid compliance test | Export 30 days of diary entries and verify the audit trail and signature: if it does not work within 10 minutes, change platforms. |
| Edil-up for the digital diary | Edil-up integrates NFC/QR attendance, document management and progress monitoring, reducing management time. |
Contents
- What is the site log, and what is its Italian regulatory basis?
- Who completes, signs and can access the digital diary?
- What should be recorded in the digital diary each day?
- Does the digital format have legal value? Which features are essential?
- How is the digital diary completed each day? Operational workflow
- Which errors compromise the digital diary during an inspection?
- What features should site-diary software have?
- How Edil-up supports the digital site diary
- The real problem with the digital diary is not technology
- Edil-up: the platform for managing sites without losing control
- Sources
What is the site log, and what is its Italian regulatory basis?
The site log, in its technical sense, is the document that records chronologically all operations performed on site: an accounting and operational log that accompanies the entire life of the project, from handover of the works to acceptance. Its function is not merely descriptive. In a dispute, the log is the primary evidence for reconstructing when an activity was performed, who was present, which materials were used and whether suspensions or variations occurred.
From a regulatory perspective, the central reference for public contracts is D.Lgs. 36/2023, which updates the Public Contracts Code and transposes European directives on the digitalisation of procedures. The code does not prescribe a physical format: it recognises the validity of an electronic document provided it complies with the provisions of the Digital Administration Code (D.Lgs. 82/2005), particularly those on digital signatures, time stamping and substitute preservation. D.M. 49/2018 (Regulation setting out guidelines for works supervision) instead specifies the site log’s minimum contents and the works director’s responsibilities for maintaining it.
What this regulatory framework means in practice:
- The digital document must be signed with a qualified digital signature (not a simple electronic signature).
- A certain date is obtained through time stamping compliant with the eIDAS Regulation.
- Substitute preservation must comply with AgID technical rules (formerly DPCM 3 December 2013 and subsequent guidelines).
- Integration with accounting and state-of-progress (SAL) systems is not legally mandatory, but is strongly recommended for documentary consistency.
Note: for private works not subject to a public contract, the site log is not legally mandatory, but remains an essential contractual protection tool for contractors and clients.
Who completes, signs and can access the digital diary?
Responsibility for maintaining the site log formally rests with the works director (DL), who signs and validates it. In day-to-day practice, however, completion is shared among several roles.
Typical roles on a medium-to-large construction site:
- Works director: validates and signs each daily entry; is the document’s legal المسؤول.
- Single person responsible for the procedure (RUP): oversees consistency between the diary and SAL; may request additions.
- Site manager or contractor’s representative: enters daily operational data (attendance, activities, materials and events).
- Subcontractors: record their own activities and attendance in the dedicated section; the DL’s signature covers the entire document, but subcontractors’ notes must remain separately traceable.
At software level, this means granular permission management: people who enter data must not be able to modify entries that have already been validated; people who sign must not be able to alter records retrospectively. The audit trail must record every change with a timestamp and user identity. Construction-site attendance tracking via NFC, QR Code or virtual clock-in reduces discrepancies between declared and actual attendance, but always requires validation by the responsible person before daily closure.
One tip: Define in writing, before the site starts, who may enter data, who may validate it and who has read-only access. This access matrix should be kept with the diary: in an inspection, it demonstrates that the process was governed.
What should be recorded in the digital diary each day?
An effective daily template is not long: it is precise. The weekly report templates most commonly used in Italy include sections on progress, labour and materials, comments and key events. The daily diary is more granular, but follows the same logic.
Minimum mandatory entries:
| Field | Content to record |
|---|---|
| Date and time | Day, activity start time and end time |
| Weather conditions | Temperature, precipitation and wind (relevant to suspensions) |
| Worker attendance | Names, qualifications and hours worked for contractor and subcontractor |
| Vehicles and equipment | Type, registration/serial number and hours of use |
| Activities performed | Description by work activity, site area and quantities completed |
| Work progress | Percentage or measurement against the programme (e.g. metres excavated, sq m laid) |
| Materials used | Type, quantity, supplier and DDT reference |
| Variations and suspensions | Reason, authorisation and impact on the programme |
| Incidents and near misses | Event description, people involved and measures taken |
| Attachments | Geotagged photos, minutes, work orders and material certificates |
The Florence High-Speed Rail Passante weekly report shows how major works document progress using precise quantitative metrics (excavated volumes and activities completed by phase) alongside descriptive text. Applying the same logic to smaller sites makes the diary much more useful for SAL reporting.
One tip: Add a “dispute notes” field even when there are no disputes to record: systematically completing it (even with “none”) demonstrates that the process was active and not retrospective.
Does the digital format have legal value? Which features are essential?
Yes, the digital site diary has full legal value provided it meets three precise technical requirements: a qualified digital signature, time stamping and substitute preservation compliant with AgID guidelines. An unsigned PDF, or one signed with a simple electronic signature, is not equivalent to a paper document signed by hand: it has lower evidentiary value and may be challenged.
Compliance requirements to verify before choosing a platform:
- Qualified digital signature: compliant with the eIDAS Regulation, with a certificate issued by an AgID-accredited provider.
- Time stamping: applied by an accredited certifier; guarantees the document’s certain date.
- Substitute preservation: a process managed by an AgID-accredited preservation provider, with archiving packages (SIP/AIP) compliant with the guidelines.
- Immutable audit trail: every access, change and validation recorded with a timestamp and user identity; not modifiable even by the administrator.
- Granular permission management: separate roles for entry, validation, signing and read-only access.
- Structured export: signed PDF and CSV for integration with accounting and SAL systems.
Useful features that are not legally mandatory:
- Offline mode with automatic synchronisation when connectivity returns.
- Integration with NFC/QR attendance tracking (reduces missed clock-ins).
- Progress dashboard with visual indicators for the RUP.
- API for integration with accounting software and ERP management systems.
One tip: To test a platform’s compliance, ask the provider to show you the certificate of the AgID-accredited preservation provider and perform a live signed export with signature verification. If it cannot do so within 5 minutes, compliance is claimed but not demonstrated.
How is the digital diary completed each day? Operational workflow
A daily workflow works only if it is quick enough to be followed even on the busiest days. Here is the sequence that reduces omissions.
- Morning (before work starts): open the day’s entry; check expected attendance against NFC/QR clock-ins already captured. The Sisma 2016 system automatically generates the weekly report every Monday and updates clock-ins in real time, a model that can be replicated on any structured platform.
- During the day: the site manager records activities by work type and area; attaches geotagged photos for each critical phase; notes materials received with the DDT reference.
- End of day (by 6:00 p.m.): complete weather, quantitative progress and any suspensions or variations; add notes on incidents or near misses; upload all attachments.
- Validation: the works director checks that the entry is complete and applies the digital signature. If not physically on site, the signature is applied remotely through the platform.
- Closure and preservation: the platform applies the time stamp and sends the document to the accredited preservation provider. The file can no longer be modified.
Example of a completed daily entry:
Quick control checklist before closing:
- Has all attendance been recorded and validated?
- Do the progress quantities match the work programme?
- Have the DDTs for materials received today been attached?
- Are any suspensions or variations justified in writing?
- Has the “dispute notes” field been completed (even with “none”)?
One tip: For weeks with no entries, always add a standardised reason (e.g. “site closed for a holiday” or “suspension due to bad weather under order no. X”). An empty week without an explanation is a documentary gap that may be challenged during acceptance.
Which errors compromise the digital diary during an inspection?
The most frequent errors are not technical: they are procedural. The platform may be fully compliant, but if the completion process is careless, the diary will not withstand an inspection.
Recurring errors to avoid:
- Missing or late signature: an entry not signed by the end of the day loses its certain date; signing a week’s entries in bulk on Friday is a practice an inspector will recognise immediately.
- Blank fields without explanation: weather not completed, incomplete attendance or missing progress. Every blank field is an ambiguity that becomes a problem in a dispute.
- Photos without metadata: images uploaded without a geotag and timestamp prove neither where nor when they were taken.
- Failure to integrate with SAL: if diary data do not match the state-of-progress data, the discrepancy is the first thing an auditor will check.
- Subcontractors not tracked separately: their activities must be distinguishable from those of the main contractor, with attendance and work recorded independently.
The most vulnerable document in a dispute is not the one with a few formal errors: it is the one that appears to have been completed retrospectively. An audit trail showing all entries made at the same time, at the end of the week, is evidence against its creator, not in their favour.
Warning signs requiring immediate action:
- The audit trail shows retrospective changes to entries that had already been validated.
- NFC/QR clock-ins do not match the attendance declared in the diary.
- The accredited preservation provider cannot produce the archive package for a specific period.
What features should site-diary software have?
Choosing a platform is both a technical and legal decision. Software that does not meet mandatory requirements is not a solution: it is a risk.
Mandatory requirements (must-have):
- Integrated qualified digital signature (not external or manual).
- Time stamping by an AgID-accredited certifier.
- Substitute preservation with an AgID-accredited preservation provider.
- Immutable audit trail logging every access and change.
- Role-based permission management (entry, validation, signing and reading).
- Signed PDF and CSV export for accounting and SAL.
Recommended features (nice to have):
- Offline mode with automatic synchronisation.
- NFC/QR Code attendance integration to reduce missed clock-ins.
- Progress dashboard with visual KPIs for RUP and DL.
- API integration with ERP and accounting software.
- Automatic notifications for incomplete entries or validations nearing their deadline.
To assess scalability, check whether the platform can manage multiple sites in parallel with separate logs and export the entire archive in a standard format if you migrate. A platform that stores data in a proprietary, non-exportable format is a contractual constraint disguised as a feature.
Edil-up’s digital site register guide explains how to structure a register compatible with current regulations and proposes operational best practices for company adoption, including an audit simulation as a compliance test before go-live.
How Edil-up supports the digital site diary
Edil-up integrates into its platform the features a site manager looks for when moving from a paper log to a digital diary: centralised document management, attendance tracking with NFC, QR Code and virtual clock-in, work-progress monitoring and direct communication between contractors and subcontractors.
Relevant features for the digital diary:
- Document management with attachments (photos, DDTs and minutes) uploaded directly from the site via the mobile app.
- Attendance integration using NFC and QR Code technologies, with real-time updates and validation by the responsible person.
- Work-progress monitoring with dashboards for RUP and DL, useful for aligning diary data with SAL.
- Networking and communication between contractors to coordinate subcontractors and suppliers directly from the platform.
Edil-up states that adopting the platform can contribute to a significant reduction in site-management time for companies. For those managing multiple sites in parallel, centralising data on one platform eliminates information scattered across emails, Excel sheets and separate paper logs.
One tip: Start the trial on an active site, not a new one. Importing real data and verifying that the signing and preservation workflow works on an ongoing project is the quickest way to see whether the platform fits your process—or whether you are adapting to it.
The real problem with the digital diary is not technology
Anyone who has worked on site for years knows that the paper log had a practical advantage: it was physically present, completed on the spot, and signing it was automatic. Moving to digital breaks this habit without necessarily replacing it with something faster, at least during the first few weeks.
The real risk is not choosing the wrong platform. It is choosing the right one and using it badly: signing in bulk at the end of the week, uploading photos without geotags or leaving fields blank because “it will be remembered”. An audit trail showing this behaviour is more damaging than an incomplete paper log because it is traceable and dated.
Regulatory compliance is necessary, but not sufficient. What distinguishes a genuinely useful digital diary from one that exists only to satisfy a formal requirement is process discipline: who enters the data, when and at what level of detail. Technology can automate clock-ins and generate weekly reports, but it cannot replace a site manager’s decision to treat the diary as a working tool rather than a mere obligation.
Digitalisation in construction brings real benefits only when it changes the process, not just the format. Anyone adopting a digital diary without redesigning the daily workflow ends up with an electronic log containing the same problems as the paper version, plus a few extra technical complications.
Edil-up: the platform for managing sites without losing control
Managing the site diary in Excel sheets or separate paper logs for each site means multiplying the risk of omissions, discrepancies with SAL and documentary gaps that always emerge at the worst possible moment—during an inspection or acceptance.
Edil-up is the platform that centralises document management, attendance tracking and progress monitoring in one digital environment, accessible from the site via a mobile app. For those managing subcontractors, the platform makes it possible to track each contractor’s activities separately, with granular permissions that prevent retrospective changes to entries already validated.
Check the plans available from Edil-up and start with an active site: it is the quickest way to see whether the workflow fits your process before rolling it out across the company.
Sources
Regulatory and operational sources to keep at hand to substantiate the log in the event of a dispute or acceptance:
- Sisma Centro Italia 2016 Weekly Site Report and Badge User Manual
- Weekly Report Template for the Site Manager | PDF
In a dispute, the combination of a digitally signed diary, an exported audit trail and a substitute-preservation package is the documentation a lawyer requests first. Keep these regulatory sources with the site archive: they demonstrate that the process was compliant from the outset.