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

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

In a small firm, a phone call to the gang leader may be enough. But as the number of sites, collaborators, external contractors and last-minute replacements increases, that method starts to show its limitations.

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

Managing attendance on site therefore becomes more than simply clocking in and out.

It helps create a reliable operational snapshot: who is present, on which site, in what role and according to how the day is organised.

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

Before you start: do not confuse three different problems

When a firm says it wants to ‘digitise attendance’, it may actually be trying to solve very different problems.

For example:

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

These objectives are connected, but they are not equivalent.

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

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

Knowing that a person is recorded as present can help with organisation. It does not automatically prove that the person is trained, authorised or fit to carry out a particular 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 really happens.

Choose one or two representative sites and record:

• the number of people normally present;
• the number of crews;
• the companies involved;
• the contact for each crew;
• the current method for recording attendance;
• who corrects any errors;
• how absences and replacements 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 the administration team currently takes forty minutes to reconstruct a day, that figure can be compared with the result after the new method is introduced.

That is much 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 figures do not measure site safety.

They measure the quality of the organisational process.

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

We can now 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 forgotten clock-in is handled;
• who can correct a record;
• how a replacement 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 recording 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?

The manager can then decide whether the work can continue, whether to change the programme or whether to request a replacement.

The system does not decide.

It makes visible the difference on which a decision must be made.

Days 15–18: test everything with one crew

I would not immediately extend the new procedure to the whole 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 long it took;
• which errors appeared;
• which questions were repeated;
• how much additional work it generated for the gang 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 organised.

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

• who is the operational contact;
• which people are part of 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 wording, however.

Assigning a role within software does not automatically create a legal responsibility or alter those established by law, contract or company organisation.

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

In 2026, workplace safety remains primarily an organisational issue

The subject is particularly timely.

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

The principle is consistent with our plan.

Technology can make better information available.

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

Days 24–27: link attendance to what is happening on site

Attendance on its own says little.

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

For example:

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

This allows you to ask more interesting operational questions.

Not only:

‘How many hours did Mario work?’

But:

‘Was the crew planned for this phase actually available?’

Or:

‘Is this activity using more working days than planned?’

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

A presence does not automatically equal a cost attributable to a single activity. That requires company rules and, where necessary, dedicated administrative tools.

You can explore the subject 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 ease must not turn into indiscriminate information gathering.

The following must be defined consistently with the applicable regulations:

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

One point deserves particular attention.

In the provision of 29 April 2026, the Italian Data Protection Authority reaffirmed that current law does not permit 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 figures

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

‘Do we like the new system?’

Return to the indicators from the first week.

Compare:

• the time needed before and after to reconstruct attendance;
• the number of corrections;
• the number of missing data points;
• replacements reported late;
• the 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 correcting.

Seven mistakes that can make the project fail

1. Start with the device instead of the process

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

2. Impose too many steps

If recording takes too long, staff 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 authorised to carry out 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. Leave the entire process on the gang leader’s shoulders

The contact should manage exceptions, not become a secretary entering everyone’s data manually.

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 manager to decide how to reorganise the day.

Scenario 3 — A clock-in was forgotten

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

Where Edil-Up can help with the process

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

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

Attendance management and the digital badge can therefore be read within the context of the project, rather than 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?
• 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, an employment adviser, safety obligations, health monitoring or privacy compliance.

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

To explore the subject 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 on each site?
• Do we know which crew was planned and which actually turned up?
• Does every crew have an identifiable contact?
• Are replacements communicated in an orderly 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 organisational and prevention obligations.
• Ministry of Labour — Integrated Plan for Health and Safety in the Workplace 2026, adopted by Ministerial Decree no. 20 of 12 February 2026.
• Italian Data Protection Authority — Provision of 29 April 2026, also concerning the use of biometric data to record workers’ attendance.
• INAIL — Construction and workplace safety, technical and information 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?

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 more quickly 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 linked to a site, crew and role becomes operational information.

Edil-Up Team