How to close the gap between the office and the site at construction firms

The office–site gap is when what happens on the construction site reaches the office late, incomplete or already interpreted, and decisions made in the office are not followed up on site. At construction firms this gap is often assumed to run one way, but it runs both ways: information does not flow from the site to the office, and work does not flow from the office to the site.

In this article we treat the two directions separately. The site-to-office side is handled by SahaSesi AI, which works through WhatsApp, and the office-to-site side by the task module of KurumsalPortal. The two products work separately; the aim is to show which one closes which gap.

Where exactly does the gap occur?

• Delayed information: the messages the foreman writes during the day are gathered by hand in the evening; the office learns the day’s summary only the next morning, and only by going from phone call to phone call.
• Incomplete timesheets: how many people each subcontractor worked with is filled in by estimate at month end, which means arguments over both cost and payment.
• Verbal requests: “we need concrete tomorrow” is said over the phone, there is no record, and when the delivery does not arrive, people argue over who said what.
• Scattered defect lists: the photo goes to one group and the explanation to another; nobody knows whether the defect was closed.
• Decisions without follow-up: “this will be fixed in Block B” is said in the office, but because no owner or date is written down, the work is forgotten on its own.

Site to office: from WhatsApp to a record

Foremen and crew already use WhatsApp; if they are expected to learn a new app, no records get kept. SahaSesi AI does not change this habit. The foreman sends text, a voice message or a photo to a single number, and the AI sorts the message into one of five record types: work log, timesheet, material request, defect and incident (including OHS).

Every record is read back to the foreman as “Saved: …”, and the foreman corrects it if it is wrong. Messages the system is unsure about land in a “pending review” list in the office, so no record is silently lost. When the site chief approves, the daily report is locked, and a single PDF divided by site goes to managers every evening at 7 p.m. An OHS incident appears at the top of this report. A reminder goes on WhatsApp to the foreman of a site whose timesheet has not arrived by the reminder time, and the daily report is also prepared with that day’s weather information for the site.

“We need 20 cubic meters of C30 concrete by tomorrow morning.” is lost on the phone; in the panel, it stays as a request.

Office to site: following up on the decision

The other direction of the gap is not being able to see whether the decision the office gave actually happened on site. In the Task & Action Management module, every job is opened as a task card with its category, and an owner is assigned; who has the job rests on the record, not on memory. The priority, status and deadline fields show which job should be handled first and when it must be finished.

Files and notes are attached to a task, and the work is completed with evidence. Reminders are sent for tasks past their deadline, and results turn into reports that show team performance. Project managers and unit managers learn who is late on what not by asking in a meeting but by looking at the list.

A fictional example: a project manager opens a task to check the Block B façade scaffolding, with high priority, assigns the site chief as owner and gives Friday as the deadline. When the chief finishes the job, they attach a file and a note to the task, and the task is completed with this evidence. The manager does not have to call and ask “is it done?”; if it has not been done, the reminder goes out anyway once the deadline passes.

The flow of a fictional day

1. Morning: the project manager opens the decisions taken in the office as task cards and assigns owners and deadlines.
2. During the day: the foreman writes the concrete, the crew count and a defect on WhatsApp; the messages are sorted by type and read back with “Saved”.
3. 7 p.m.: the site report reaches managers; a site that sent no records also shows up in the report.
4. Next morning: the office clears the “pending review” list, looks at the status of tasks with defined owners and re-prioritizes where needed.

The reason to think about both directions together is simple: if you fix only the site-to-office flow, the office gets information on time but cannot follow up on the work it turns into decisions. If you set up only task follow-up, you end up assigning work without knowing the real situation on site. It is a loop that needs to close: the real situation on site reaches the office, the office decides, and the result of the decision returns from the site to the record.

Where should you start?

Pick the gap that hurts most. If month-end timesheet arguments and material requests wear you down, start with the site-to-office side; if decisions taken in the office go unfollowed, start with the office-to-site side. In both cases the first goal is small: a single site, a single crew, a single week. Starting small also makes it easier for the team to get used to the new way of working: the foreman simply writes on WhatsApp as usual, and the office sees the incoming records and open tasks at a glance.

For records coming from the site, see SahaSesi AI; for following up on office decisions, see Task & Action Management.