Knowing how many people should be on a construction site is not the same as knowing who is actually present, which team they belong to and which activity they are supporting.
It may seem like a small difference, but it affects the ability to organise shifts, replacements, work phases and communication between the site and the office.
In companies where attendance is reconstructed at the end of the day using sheets, messages, telephone calls and foremen’s memory, even a very simple question can take time:
Who was actually on the construction site this morning, and which team were they with?
Managing construction site attendance becomes genuinely useful when it does not merely produce a list of clock-ins and clock-outs, but helps build an up-to-date operational picture of the people involved in the project.
In this guide, we look at how to set up a gradual 30-day process to bring order to the workflow without introducing overly complex procedures overnight.
Why starting with attendance changes how you organise the construction site
Attendance is one of the simplest operational data sets produced by a construction site every day.
On its own, however, it says relatively little.
Knowing that 18 people are present this morning is useful. Knowing that those 18 people are distributed across structural work, systems and finishes, however, makes it possible to start thinking about how the work is organised.
The qualitative leap occurs when the data progressively answers questions such as:
- who is present?
- which company do they work for?
- which team are they assigned to?
- what operational role do they have?
- which construction site should they be at?
- which anomalies need to be checked?
This does not mean that the software should automatically decide who may carry out a particular activity or certify a worker’s compliance.
It simply means turning data that normally remains fragmented into a context that is easier to consult.
Days 1–7: don’t digitise yet—observe how attendance actually works
The first mistake would be to purchase or configure a tool before understanding the process it is supposed to replace.
During the first week, choose one pilot construction site and reconstruct the current workflow.
For example:
- how arrival is recorded today;
- how departures are handled;
- who reports an absence;
- who corrects an error;
- how subcontractors and external collaborators are handled;
- who uses the data at the end of the day or month;
- how many times the same data is transcribed again.
The goal is not to judge the existing system.
It is to understand where unnecessary activities arise.
If the foreman fills out a sheet, sends a photograph to the office, and someone else later re-enters the hours in a file, you have already identified a process that could be simplified.
What to measure during the first week
Record only data that you will be able to compare at the end of the month:
- number of missing records;
- number of manual corrections;
- time required to reconstruct attendance;
- number of requests from the office to foremen;
- number of tools used to complete the process.
There is no need yet to set an arbitrary percentage target.
First, collect the actual data.
Days 8–14: from people to teams
A list of names does not describe how the construction site is organised.
During the second week, progressively connect people to the actual operational structure.
You can start with:
- company;
- team;
- operational role;
- construction site;
- contact person or foreman.
This classification should not be confused with the allocation of responsibilities required by law.
Writing “responsible” next to a profile in an app does not create or change legal, professional or safety responsibilities.
The goal is to represent the company’s operational organisation more accurately.
Don’t create twenty roles if you only need five
During the pilot phase, it is preferable to keep the structure easy to understand.
If every collaborator has to choose from dozens of categories, the system becomes harder to use and the data becomes less consistent.
The rule should be:
Collect only information that someone will actually use to make a decision.
Days 15–20: digitise attendance without turning it into surveillance
At this point, the process can be moved to a digital tool.
The technology selected will depend on the company’s organisation: badges, digital identifiers, apps or other methods compatible with the company process.
The point is not to choose the most sophisticated technology.
It is to collect consistent data with as few operations as possible.
To get started, the following are often enough:
- person;
- construction site;
- attendance status;
- date and time;
- any anomaly requiring verification.
The procedure should also specify what happens when the tool does not work.
A digital process without a fallback procedure risks being less reliable than the sheet it was meant to replace.
Digital attendance, privacy and worker monitoring: choose technology carefully
Digitising attendance means processing data related to workers and therefore also requires attention to data-protection regulations and, where relevant, rules on remote monitoring.
A particularly important clarification came from the Garante per la protezione dei dati personali in its decision of 29 April 2026.
The Authority reiterated that, under the current regulatory framework, it is not normally permitted to use employees’ biometric data to record attendance at work.
In other words, facial recognition or fingerprints do not become lawful simply because they are more convenient or harder to circumvent.
The Garante also recalled the principle that when an objective can be achieved using less invasive tools, those tools must be preferred.
What about geolocation?
Geolocation should not be treated as a simple feature to switch on either.
Locating a smartphone may indirectly reveal a worker’s position and requires an assessment of the purposes, the data actually needed, retention periods and the applicable safeguards.
The Ispettorato Nazionale del Lavoro also maintains specific procedures relating to satellite-location systems and other tools that may enable remote monitoring.
For a standard business implementation, it is therefore appropriate to assess the system with privacy and employment-law advisers when the functions used may have monitoring effects.
Days 21–24: connect attendance to planning without inventing data
After about three weeks, you should have a reasonably stable workflow.
At this point, you can start using attendance as context for planning.
Example:
The programme calls for a team of six people on finishing work. Four are recorded as present in the morning. The data does not automatically say what the impact on production will be, but it allows the manager to immediately identify a difference between planned and available resources and decide how to respond.
That is the correct logic.
The system highlights the context; the manager interprets the situation.
Over time, it is possible to connect the data to construction-site phases as well, while avoiding automatically inferring individual productivity from a simple clock-in.
Attendance and production are not the same thing.
Attendance and safety: what the system can and cannot tell you
In Italy, the general reference remains D.Lgs. 81/2008.
The Ministero del Lavoro, on the page updated 22 September 2026, summarises numerous employer obligations, including training and instruction, emergency management, PPE and, in cases of contracting and subcontracting, an identification card.
Knowing who is recorded as present can therefore be useful organisational information, including when managing an emergency.
But a recorded attendance entry does not by itself demonstrate that all health and safety obligations have been met, that training is valid or that a worker may perform a specific task.
Software supports organisation. It does not replace assessments, checks, professional roles or responsibilities required by the regulations.
The INAIL also has a dedicated section for construction, a sector characterised by a high risk of workplace accidents.
Days 25–28: look for anomalies, not confirmation
During the final days of the fourth week, avoid limiting yourself to asking whether “people like the new system”.
Instead, check where the process continues to break down.
For example:
- how many records are still corrected manually;
- how many people forget the required step;
- which teams show the most anomalies;
- how long it takes the office to verify the data;
- how many duplicate steps remain;
- which pieces of information are collected but nobody uses.
The last indicator is particularly important.
Every mandatory field that nobody uses is added administrative work with no operational value.
Days 29–30: turn the experiment into a procedure
If the pilot works, the final two days are used to prevent the process from gradually returning to where it started.
Formalise a short procedure that clarifies:
- who must record attendance;
- when they must do it;
- what happens in the event of an error;
- who may correct the data;
- who checks anomalies;
- how external collaborators are added;
- which data is used in reports.
The procedure should be simple enough to explain to a new foreman in a few minutes.
If it requires a fifty-page manual, the process can probably still be simplified.
Useful KPIs after 30 days
I would avoid sophisticated indicators during the first month.
Five measures are enough:
- incomplete records: how many attendance entries still require correction;
- administrative time: how much time is spent reconstructing or validating the data;
- team variance: difference between planned people and people actually recorded;
- recurring anomalies: problems that recur on the same construction site or in the same process;
- manual steps: how many times the data is still copied from one system to another.
The final question should not be:
“Have we digitised attendance?”
But:
“Do we now spend less time understanding who is available and organising the work?”
Three practical scenarios, without inventing results
Consider three hypothetical examples.
Scenario 1 — Unexpected absence
A team scheduled for five people has four available at the start of the shift. The manager immediately sees the variance and decides whether to reorganise the activities or assign a different resource.
Scenario 2 — Multiple companies on the same construction site
The main contractor needs to quickly understand which collaborators from outside companies are present. A shared environment avoids reconstructing the information by calling each contact person separately.
Scenario 3 — Incomplete administrative data
At the end of the month, the office identifies several anomalous records. If the correction is handled in the same workflow, there is no need to reconstruct the information weeks later through telephone calls and paper sheets.
These examples do not demonstrate predetermined savings.
They simply show which steps can be measured before and after the new process is introduced.
The mistakes that make an attendance system fail
Starting with technology
The process must be defined first. Then choose the tool.
Collecting too much data
Every additional piece of information must have a clear purpose and, when processing personal data, must comply with the applicable principles of necessity and minimisation.
Confusing attendance with productivity
Being present for eight hours does not automatically mean producing eight hours of value.
Confusing attendance with safety
A record does not replace training, instruction, fitness assessments, checks or other verifications required by the organisation and regulations.
Using invasive technologies simply because they are available
Biometrics, geolocation and monitoring tools require specific assessments. More technology does not automatically mean a better process.
How Edil-Up connects attendance, people and the construction site
Edil-Up is developed as a Construction Operating System to connect operational information that normally remains separate.
In construction site management, the company can organise sites, phases, collaborators, documents, communications, permits and attendance information in the same environment.
The attendance and badge system provides greater visibility into the people associated with construction sites, without turning the data into an automatic declaration of compliance or safety.
The logic is to connect:
Person → Company → Construction site → Team → Attendance → Operational context
The mobile app brings part of this workflow directly to the site, while roles and permissions make it possible to differentiate access to information.
The goal is not simply to replace the sign-in sheet with a screen.
It is to prevent attendance from remaining isolated data that the office has to reconstruct later.
To explore the overall organisation of work, you can also read the guide to managing documents and responsibilities on the construction site and the comparison of the best construction site management software.
30-day checklist
- Choose one pilot construction site.
- Measure the process before changing it.
- Define teams and operational roles.
- Establish who manages anomalies.
- Digitise only the data that is genuinely necessary.
- Provide a procedure for malfunctions.
- Assess privacy and employment rules before using invasive features.
- Compare planned and available people.
- Measure administrative time before and after.
- Standardise the process only after testing it.
Official sources
- Normattiva — D.Lgs. 81/2008 , current text on occupational health and safety.
- Ministero del Lavoro — Employer obligations regarding health and safety , page updated 22 September 2026.
- Garante Privacy — Decision of 29 April 2026 , concerning the use of biometric data to record worker attendance.
- Ispettorato Nazionale del Lavoro — Monitoring and location systems .
- INAIL — Construction and occupational safety .
Conclusion: after 30 days, you should have fewer questions, not more data
The success of the plan is not measured by the amount of information collected.
It is measured by the company’s ability to answer operational questions more quickly—questions that previously required telephone calls, sheets and manual checks.
Who is present?
Which team is available?
Where is someone missing compared with the plan?
Which anomaly needs to be checked?
Who needs to step in?
When this information becomes easy to obtain, attendance stops being merely an administrative task and becomes part of the day-to-day management of the construction site.
The real goal is not to monitor people more closely. It is to organise the work better.
The Edil-Up team
