Site attendance: the effective 30-day plan for coordinating crews and responsibilities

Knowing who should be on a construction site is not the same as knowing who is actually there.

In a small company, a phone call to the crew leader may be enough. But as the number of sites, collaborators, outside contractors, and last-minute substitutions increases, that method begins to show its limits.

Someone is moved to another project. A worker is absent. A crew arrives later. A supervisor changes the schedule. The office discovers the new site composition only when it has to reconstruct the hours worked.

Construction-site attendance management then becomes more than simply clocking in and out.

It serves to create a reliable operational snapshot: who is present, at which site, in what role, and according to what organization of the day.

This article proposes a 30-day process for building a more organized method without trying to transform the entire company in one week.

Before you start: do not confuse three different problems

When a company says it wants to “digitize attendance,” it may actually be trying to solve very different problems.

For example:

• quickly know who is present at each site;
• reconstruct hours worked;
• coordinate crew composition;
• know who is the operational point of contact;
• reduce manual corrections by administration;
• support workforce planning.

These objectives are related, but they are not equivalent.

And above all, attendance recording does not replace health and safety obligations.

The Ministry of Labour reminds employers that they retain specific obligations concerning risk assessment, training, supervision, PPE, health surveillance, and safety organization.

Knowing that a person is recorded as present can help with organization. It does not automatically prove that the person is trained, authorized, or fit to perform a specific activity.

Days 1–7: take a snapshot of how you work today

The first week is not for installing software.

It is for understanding what actually happens.

Choose one or two representative sites and record:

• the number of people normally present;
• the number of crews;
• the companies involved;
• the contact person for each crew;
• the current method for recording attendance;
• who corrects any errors;
• how absences and substitutions are communicated;
• how long the office takes to reconstruct the information.

You do not need to create a perfect report.

You need a baseline.

If administration currently takes forty minutes to reconstruct a day, that figure can be compared with the result after the new method is introduced.

That is far more useful than deciding in advance that “we need to save 50%.”

Choose KPIs that describe a real problem

For the first month, a few indicators may be enough:

These data do not measure site safety.

They measure the quality of the organizational process.

Days 8–14: design a process that takes only a few seconds

Now we can decide how the ideal day should work.

For attendance recording, you need to establish at least:

• who must record arrival and departure;
• how the site is identified;
• how a missed clock-in is handled;
• who can correct a record;
• how a substitution is recorded;
• who can see the information;
• which data must reach the office.

The procedure should be simple enough to explain in a few minutes.

If recording attendance requires too many steps, the problem is not training.

It is the process.

Separate attendance from crew planning

This distinction is important.

Planning says:

“These people should be there tomorrow.”

Attendance tracking says:

“These people are recorded as present today.”

Comparing the two sets of information makes it possible to identify a difference quickly.

A crew planned for six people has five?

At that point, the supervisor can decide whether the work can continue, whether to change the schedule, or whether to request a substitution.

The system does not decide.

It makes the difference that requires a decision visible.

Days 15–18: test everything with one crew

I would not immediately extend the new procedure to the entire company.

I would choose a sufficiently representative site and crew.

For four days, the test should be almost brutally simple.

Every morning, check:

• how many workers correctly recorded their arrival;
• how much time it took;
• which errors appeared;
• which questions were repeated;
• how much additional work it created for the crew leader.

If half the crew forgets the procedure, you should not automatically conclude that people “do not want digital tools.”

It may mean that the method is not simple enough.

Days 19–23: make roles and responsibilities visible

Knowing that twelve people are present does not automatically mean knowing how the day is organized.

For each crew, at least the following should be clear:

• who serves as the operational point of contact;
• which people belong to the crew;
• which phase or area their work concerns;
• who must be contacted if something changes;
• who can correct or validate the operational information.

Be careful with the terminology, however.

Assigning a role within software does not automatically create a legal responsibility or change responsibilities established by law, contract, or company organization.

The system must represent the real process, not invent it.

In 2026, workplace safety remains primarily an organizational issue

The topic is particularly timely.

With the Integrated Plan for Health and Safety in the Workplace 2026, adopted by Ministerial Decree no. 20 of February 12, 2026, the Ministry of Labour reaffirmed the importance of prevention, training, responsibility, supervision, and clear behavioral rules.

The principle is consistent with our plan.

Technology can make better information available.

But it does not replace organization, training, risk assessment, supervision, or the other measures required by regulations.

Days 24–27: connect attendance with what is happening on site

Attendance alone says little.

It becomes more useful when it can be read together with the project.

For example:

• which site;
• which crew;
• which contact person;
• which planned phase;
• which changes in composition have occurred.

This makes it possible to ask more interesting operational questions.

Not just:

“How many hours did Mario work?”

But:

“Was the crew planned for this phase actually available?”

Or:

“Is this activity using more workdays than planned?”

The connection with cost control must, however, be built carefully.

Attendance does not automatically equal a cost attributable to a single task. That requires company rules and, when necessary, dedicated administrative tools.

You can explore the topic further in the guide to construction-site cost control, estimates, and budgets.

Digital badge, yes—but that does not mean collecting every type of data

When digital attendance tools are introduced, technical convenience must not turn into indiscriminate data collection.

The following must be defined consistently with the applicable regulations:

• purposes of processing;
• data that is actually necessary;
• people authorized to access it;
• retention periods;
• privacy notices and other necessary privacy measures.

One point deserves particular attention.

In the provision of April 29, 2026, the Italian Data Protection Authority reaffirmed that current law does not allow the use of employees’ biometric data for ordinary attendance recording.

So “digital badge” should not automatically be translated into fingerprinting, facial recognition, or other biometric data.

Days 28–30: return to the initial numbers

At the end of the month, do not ask generally:

“Do we like the new system?”

Go back to the indicators from the first week.

Compare:

• time before and after to reconstruct attendance;
• number of corrections;
• number of missing data points;
• substitutions reported late;
• time needed to know which crew is actually present.

Then add a qualitative question:

Is the process simple enough to be used every day without constant reminders?

If the answer is no, there is no need to extend the system immediately.

It needs to be corrected.

Seven mistakes that can cause the project to fail

1. Start with the device instead of the process

Buying badges, terminals, or apps before deciding what needs to be recorded only creates a more confusing digital procedure.

2. Require too many steps

If recording takes too long, personnel will inevitably look for shortcuts.

3. Fail to plan for exceptions

Dead phone, forgotten badge, worker moved to another site: exceptions are part of the process and need a simple procedure.

4. Confuse clocking in with safety

Being recorded as present does not automatically mean being authorized to perform any activity or having fulfilled the required safety obligations.

5. Use biometric data because you think it is simply “more secure”

Biometrics involves particularly sensitive processing and, for ordinary employee attendance recording, the Authority reaffirmed in 2026 that there is no legal basis allowing its routine use.

6. Put the entire process on the crew leader

The contact person should manage exceptions, not become a clerk who manually enters everyone’s data.

7. Extend the system before measuring the pilot

The first site should be used to correct the method, not to prove that a decision already made was right.

Three everyday scenarios the process should handle

Scenario 1 — A worker is moved to another site

The change must be visible to the people managing both projects without requiring a chain of phone calls.

Scenario 2 — A crew planned for five people arrives with four

The difference must emerge quickly, leaving the supervisor to decide how to reorganize the day.

Scenario 3 — A clock-in was missed

There must be an identifiable correction procedure, avoiding changes that are invisible or impossible to reconstruct.

Where Edil-Up can help in the process

Edil-Up is developed as a Construction Operating System with the goal of bringing information about people closer to the rest of site operations.

Within site management, the company can organize sites, phases, collaborators, roles and permissions, documents, communications, basic budgets, and attendance.

Attendance management and the digital badge can therefore be viewed within the context of the project instead of remaining a completely separate register.

This can make it easier to answer operational questions such as:

• who is recorded as present today?
• which site are they assigned to?
• what is their operational role?
• who is the crew contact person?
• which people are recorded as involved in the project?

The mobile app also makes it possible to take part of the process directly into the field.

Edil-Up does not replace payroll, labor consultants, safety obligations, health monitoring, or privacy compliance.

Its role is organizational: to connect people, attendance, and operational information to the project they are helping to deliver.

To explore the topic further, you can also consult the guide to managing documents and responsibilities on site and the comparison of construction-site management software.

Day 30 checklist

• Do we know who is recorded as present at each site?
• Do we know which crew was planned and which actually showed up?
• Does every crew have an identifiable contact person?
• Are substitutions communicated in an organized way?
• Is it clear who can correct a record?
• Does the procedure work from a smartphone?
• Have we avoided collecting unnecessary data?
• Is the system non-biometric for ordinary attendance recording?
• Has administrative time actually decreased?
• Are people using the new process without constant reminders?

Official reference sources

• Ministry of Labour — Employer obligations concerning health and safety, institutional framework on organizational and prevention obligations.
• Ministry of Labour — Integrated Plan for Health and Safety in the Workplace 2026, adopted by Ministerial Decree no. 20 of February 12, 2026.
• Italian Data Protection Authority — Provision of April 29, 2026, also concerning the use of biometric data to record workers’ attendance.
• INAIL — Construction and workplace safety, technical and informational resources dedicated to prevention on construction sites.

Conclusion: attendance becomes useful when it stops being just a clock-in

The result of a good 30-day project should not simply be more digital clock-ins.

It should be fewer uncertainties.

Who is present?

Which crew is working?

Who is the contact person?

Does the planned crew match the one actually available?

Can the office reconstruct the day without calling three people?

If after thirty days the answers arrive faster and with fewer manual corrections, the process is improving.

It can then be gradually extended to the other projects.

A recorded attendance entry is data. Attendance connected to a site, crew, and role becomes operational information.

Edil-Up Team