Ask any site engineer where the project stands and you will get a precise answer — which pour finished today, which drawing is holding the next activity, which material will run short by Thursday. The knowledge exists, and it is fresh. It just lives a few hundred kilometres from the people planning around it.
The bridge between site and head office is usually a ritual: the evening phone call, the Friday format, the monthly review deck assembled the night before the review. Each hop translates fresh knowledge into stale summary, and each summariser decides — reasonably, invisibly — what not to mention.
The distance between a project and its management is not really geographic. It is informational — and unlike geography, it can be closed. Closing it does not require more reporting from the site. It requires the reporting that already happens to land somewhere useful the first time.
The evening call is a bad database
A phone call captures whatever the two people on the line remember, in the order they remember it, shaped by what each believes the other wants to hear. Nothing is timestamped. Nothing is comparable across projects. Nothing survives the call except what somebody chose to write down.
Multiply that across a dozen sites and the head-office picture becomes a mosaic of secondhand impressions. Two projects can both report that they are on track and be in entirely different conditions — one genuinely ahead, the other one surprise away from a delay nobody has priced.
This is not a discipline failure. The phone call is simply the wrong instrument for the job it has been given, and the people using it are doing their best with a bad tool.
Reconstructed reports, real decisions
The weekly format is the second instrument, and it has the opposite flaw. Where the call is immediate but unstructured, the report is structured but late. It is assembled from memory, days after the fact, usually under deadline, often by the most junior person available.
Decisions are then made on those reconstructions. Material gets ordered against a progress figure that was estimated on Thursday evening for a meeting on Monday. An issue that surfaces on the 3rd can reach the person able to solve it on the 14th, wearing three layers of summary.
And the review meeting spends its first half arguing about what the numbers actually are, before anyone reaches the only question that matters — what should be done about them.
Capture at the moment of work
The alternative is to let the site record reality as it happens, on the device already in every engineer's pocket. A mobile app for site teams, built for the field first: progress logged when the work is done, issues raised the moment they appear, updates sent without waiting for the evening.
For that to work, the entries have to be quick, structured and possible in the middle of a working day — a few taps between tasks, not a form that needs a desk. The field is the primary user here, and the design has to admit it.
Paired with the app, a dashboard for management. What the site enters is what head office sees — the same data, at the same moment, with no relay in between to shorten it, soften it or sit on it.
Progress, issues and updates flow from field to head office in real time. The evening call can still happen. But it becomes a conversation about decisions, not a dictation of status.
Know where every project stands without a phone call.
What reviews look like with live data
When the dashboard is current, the review changes shape. Nobody presents status, because status is already known before anyone sits down. The meeting starts at the exceptions — the site trending late, the issue that has stayed open too long, the project whose updates have gone quiet. Questions arrive sharper too — about a specific slippage on a specific site — and they get answered faster, because they are answerable.
Head office also stops being a place sites perform for. When reporting is continuous and factual, there is less room and less reason to save bad news for the moment it can no longer be hidden. Problems surface while they are still small enough to be cheap.
Planning improves in a quieter way too. The numbers being planned against are the numbers that are true today — not the numbers that were true when the last format was filled in.
What the site team gets back
It is tempting to read field reporting as one more demand on people who already work long days. Done properly, it is the opposite: it removes demands.
Every phone call that used to harvest status was ten minutes taken from someone supervising actual work, usually at the day's most tired hour. Every Friday format was an evening lost to reconstructing a week from memory and a site diary.
When updates are captured at the moment of work, those interruptions fall away — and the site's effort becomes visible to head office as it happens, not as a summary someone may or may not read the following week. Credit follows visibility: the site that quietly recovered a lost week now has the recovery on record.
Built for the people holding the phone
A field app lives or dies on whether site teams actually use it, which is why it cannot be an afterthought bolted onto a management system. If updating the app is harder than taking the call, the call wins, and the dashboard quietly dies. Adoption is a design outcome before it is a training outcome.
That is why, when we build project tracking for field teams, we pair a mobile app for the site with a dashboard for management — and why we design around how the site really works before anything is built. It is also why we hand over properly: SOPs and decision flowcharts for every module, structured test scripts with role-wise accounts, and kickoff training, so the team runs it confidently long after go-live.
Site teams already know where every project stands. With the right tool in their pocket, so do you — while it is happening, not after the phone finally gets answered.