A site engineer's real day: where the time actually goes
The site engineer is the person technically responsible for execution in the field: they direct, supervise and check that the works are built in line with the design, the budget and the schedule. That is the job description. In practice, a large share of their day goes on administrative work that needs none of their technical judgement, and the imbalance is so common that hardly anyone questions it.
This article walks through a typical day and breaks it down by type of activity. The point is not to complain: it is to work out which part of that load is intrinsic to the job and which part is a process problem that can be solved.
Note: the breakdown below is reconstructed from field observation and conversations with site engineers, not a formal time study. Treat it as a qualitative reference. If you recognise yourself in it, that is exactly the use it is meant to have.
A day
6:40 · Arrival. Ahead of the crews. A quick walk to see how the work face was left yesterday and what material turned up.
7:00 · Start. Allocating crews with the foreman. Who goes to which face, what they need. Ten or fifteen minutes that decide the output of the whole day.
7:20 · First walk. Checking what is about to be built: levels, setting out, that the face is clear. This is where the job earns its existence.
8:30 · First interruption. Material missing on one face, or a subcontractor turns up with a question only the site engineer can answer, or a supplier is at the gate unannounced.
9:00 · Supervising a pour or another critical activity. Attendance is mandatory. It can take an hour or four.
11:00 · Calls and coordination. Head office, suppliers, the client’s supervisor. Fragmented, impossible to schedule.
12:00 · Verification walk. Measuring what was built during the morning, notes in the pocket book.
13:00 · Lunch, interrupted.
14:00 · Second block of execution. Walks, sorting out the unexpected, attending to the supervisor if they came to inspect.
16:00 · Planning tomorrow. Material to order, faces to release, crews to move.
17:00 · Closing out the crews. Final check, attendance, what was left outstanding.
17:30 · The part nobody sees. Keying into the system what was written in the pocket book during the day. Daily report. Emails. Photos to download, name and file. If it is month end, the quantity backup.
19:00 or later · Leaving.
The breakdown
| Activity | Hours | % of the day |
|---|---|---|
| Technical supervision in the field | 2.5 | 20 % |
| Coordinating crews and subcontractors | 2.0 | 16 % |
| Dealing with the unexpected | 2.0 | 16 % |
| Internal travel and waiting | 1.5 | 12 % |
| Admin, data entry and reporting | 3.5 | 28 % |
| Calls and emails with the outside world | 1.0 | 8 % |
| Total | 12.5 | 100 % |
The uncomfortable figure: technical supervision — the only part that requires an engineering degree — takes up a fifth of the day. Admin takes up more.
Where the real waste is
Not all admin is waste. A site engineer has to report, coordinate and document; that is part of the job. The waste sits in three specific things.
Double entry. Writing it in the pocket book during the day and keying the same thing into the system in the evening. It is literally the same data written twice. It is the single largest source of lost time, and the easiest to remove.
Reconstructing from memory. Anything not written down at the moment has to be recalled hours or days later. It costs time and produces worse data. The day-28 measuring session to assemble the quantity backup is the extreme case.
Hunting for information. Finding the photo from three weeks ago, the email where the client authorised something, the current revision of a drawing. When the record is scattered across a pocket book, the phone’s camera roll, WhatsApp and email, searching costs more than recording.
Between the three, an hour and a half to two hours a day is a reasonable estimate. Eight to ten hours a week. Close to a full working day every week, on work that produces nothing.
What it costs
It is worth looking at in money, even roughly.
If a site engineer costs the company $2,500 a month fully loaded, their hour is worth around $12. Two wasted hours a day is roughly $500 a month per engineer. With five engineers, $30,000 a year.
But the direct cost is the smaller one. The real cost is second order:
Late decisions. Time spent on admin is time not spent catching problems in the field. A quality problem caught the same day costs a fraction of the same problem caught in week 3.
Worse data. A report reconstructed from memory at seven in the evening has less detail and more errors than one captured at the moment. And that report feeds the payment applications, the cost control and any future claim.
Turnover. Good site engineers are scarce and expensive to replace. Leaving at seven every day to do data entry is one of the reasons they go.
What can actually change
Capture once, at the moment. This is the highest-impact intervention. It is not about reporting less; it is about the record you already make in the field being the definitive one, with no later transcription.
Move the record to the channel they already use. Any tool that demands opening a separate app, with dirty hands, will lose to the pocket book. The pocket book wins because it has no friction, not because it is better.
Separate what needs judgement from what does not. Ordering material, flagging a delivery, confirming attendance: none of that needs the site engineer. A good deal of coordination can be delegated once there is a channel where information arrives structured.
Cut the hunting with a single record. Everything — notes, photos, measurements, sign-offs — living in one place, searchable by date and by work face. It is less glamorous than any advanced feature and it saves more time.
Frequently asked questions
- How many projects can one site engineer run at the same time?
- It depends on size and complexity, but it is usually the admin load that sets the ceiling, not technical capacity. Someone spending 28 % of the day keying data in will struggle to hold more than two projects. Cutting that load is what lets a firm scale without hiring.
- What is the difference between a site engineer and a superintendent?
- It varies by country and by company. Broadly, the site engineer is responsible for one specific project and lives on it; the superintendent oversees several and allocates resources between them. On small projects the same person does both.
- Should the site engineer keep the site record personally?
- Normally yes, because they carry the technical responsibility and can attest to what happened. They can lean on an assistant for data entry, but the responsibility and the sign-off are theirs and cannot be delegated.
- How is a site engineer's performance measured?
- The usual indicators are progress against schedule, cost variance, safety incidents and quality observations. It is worth adding one almost nobody measures: the rejection rate on payment applications, which reflects the quality of their record directly.
- Is it worth hiring an assistant purely for the admin?
- It can make sense on large projects. On mid-sized ones the assistant usually costs more than fixing the problem at source, and it adds a transcription step, which is exactly where information gets lost.
Chilean, designing for Latin America. Field research surfaces what actually matters to clients, and that becomes products non-technical people adopt on their own — legal, education, accounting — and that show up in productivity from week one.
See all their articles →
