A construction site doesn't always go off track because of a major unforeseen event. Often, it happens because information stays in a text message, a photo is never sent to the office, or hours are logged three days too late. This site tracking example shows how to maintain a clear view of the work, from the first mandate to the final invoice, without asking teams to fill out three different tools.
The principle is simple: the site must have a single file. This file becomes the reference point for all stakeholders. The project manager prepares the work there, the field team records what is done, and the administration finds the necessary elements to invoice.
Site tracking example: a commercial renovation
Let's take an SME carrying out the layout of a commercial space. The mandate includes the demolition of a partition, electrical work, flooring installation, and several corrections requested by the client along the way.
Before work begins, the coordinator creates a site document from the accepted bid. They enter the address, the on-site contact, scheduled dates, plans, safety instructions, and the list of included work. They then assign the relevant team members and subcontractors.
This is not just a project sheet. It is the document that tracks the actual work. Every task, photo, expense, hour worked, and important exchange is attached to it. Thus, when a manager wants to know the status of the site, they don't have to call three people or open a series of emails.
Day 1: preparing a start without gray areas
In the morning, the team leader opens the work order on their phone. They see the tasks planned for the day: protecting common areas, demolishing the partition, removing materials, and taking photos before work.
They also know what is expected for each task. For example, the demolition procedure can specify the required equipment, areas to protect, and photos to provide once the work is finished. This precision reduces interpretation, especially when a new person joins the team or a subcontractor intervenes occasionally.
At the office, the coordinator can see that the team has arrived, that the first task has started, and that the initial photos have been added to the file. They are not monitoring people remotely. They are tracking the progress of the mandate with concrete evidence.
Day 3: managing a request that changes the mandate
The client eventually asks to move two electrical outlets. On many sites, this request circulates verbally. The electrician does the work, the team leader thinks it's included, and then the administration discovers the cost when preparing the invoice.
In a structured tracking system, the team leader adds a change request directly to the file. They take a photo of the location, describe the requested correction, estimate the time required, and indicate the necessary material. The project manager receives a notification and can validate the extra cost with the client before work begins.
Once approved, the correction becomes a tracked task. The hours, materials, and end-of-work photos remain attached to the same document. It then becomes easy to distinguish what was part of the initial mandate and what must be billed as an extra.
Information to track on every site
Good tracking is not about accumulating notes. You must capture information that allows you to make decisions, protect margins, and respond to the client with precision. For most SMEs, four categories make the difference: progress, proof of execution, actual costs, and validations.
Progress indicates what is to be done, in progress, blocked, or finished. It gives the manager a quick read of the week and allows them to react before a delay becomes a scheduling problem.
Proof of execution includes photos, signed documents, measurements, client comments, and intervention reports. They are useful in case of questions, but also to avoid re-doing a check already performed in the field.
Actual costs include hours, expenses, material taken from inventory, and necessary purchases. A timesheet that arrives at the end of the month is not useful for managing a site. Entered as the work progresses, it allows you to compare planned and actual efforts while adjustments are still possible.
Validations confirm important decisions: authorized change request, step accepted by the client, receipt of material, or end of mandate. They avoid the classic "I thought it was included."
Statuses that serve to act
Statuses must reflect the way your team works, not a generic model imposed by software. A company may need to distinguish a site "waiting for material" from a site "waiting for the client." Another will prefer to track the quality control step before considering the work finished.
In our example, the site document can go through the following statuses:
- To be planned, when resources and dates remain to be confirmed.
- Ready for the field, when documents, tasks, and instructions are complete.
- In progress, when hours, photos, or activities are recorded.
- On hold, when a blockage requires a decision, material, or authorization.
- To be validated, when execution is finished but a check is required.
- Ready to invoice, when work and approved extras can be sent to the administration.
The goal is not to add an administrative step. Each status must trigger a clear action. "On hold" alerts the manager. "To be validated" invites a check. "Ready to invoice" prevents finished work from being forgotten in a closed file.
Moving from field to office without double entry
The real gain of site tracking is often measured after the work is done. When the file contains hours per employee, expenses, delivery slips, photos, and approved changes, the administration does not start from scratch.
They consult the executed work and prepare the invoice from the data already entered. The project manager can check the gaps between the planned budget and actual costs before sending. If an expense seems unusual, they quickly find who added it, on what date, and for which task.
This continuity is particularly useful for companies that manage several small sites at once. The risk is not just a large overrun on one project. It is also the accumulation of small unbilled hours, forgotten materials, and extras never formalized.
A platform like Sequentia allows you to adapt the work document to the company's habits: work order, mandate, project, or intervention sheet. The goal remains the same: let teams work with a tool that fits the trade, then transform this data into tracking, reports, and invoices.
Errors that make tracking useless
A tracking table can exist and solve nothing. This is the case when information is requested too late, when teams must repeat the same entry in multiple systems, or when no one knows who is supposed to validate a blockage.
Also, avoid asking for long comments for every action. In the field, a checkbox, an annotated photo, or a well-chosen status is often more reliable than a report written at the end of the day. On the other hand, an incident, a client refusal, or a change in scope deserves a detailed note and formal validation.
The level of control depends on the nature of the work. A multi-month site will require milestones, a budget per phase, and follow-up meetings. For a one-day intervention, a clear work order, photos, hours, and a signature may be enough. The essential thing is to keep the same logic: information entered once, at the moment it is known, in the site file.
Useful site tracking should not complicate the team's day. It should make decisions, costs, and work accomplished visible, so that the field can move forward and the office can invoice what was actually done.
