[ TL;DR ]
Construction and engineering teams need reliable site reports. Producing them can involve several people gathering messages, finding photographs, checking what happened and putting the information into the right format. Much of that preparation falls to supervisors, engineers and project managers who are already responsible for keeping the work moving.
CSM built a demonstration workspace around this process. It connects a site update with the records, follow-up questions, commercial review and report preparation that come afterwards. The finished example shows the output: a company-branded report covering progress, resources, delays, potential additional work, photographs and named actions.
The approach combines software, automation and AI assistance around each company’s reporting requirements. Previous reports help establish the structure and standard. Agreed criteria determine what information is needed, what should be questioned and what requires a person’s decision.
The team remains responsible for checking the facts and approving the report. The opportunity is to remove repeated preparation around that review, giving experienced people more time for site coordination, customer communication and project delivery.
• Time returned: less gathering, copying and rewriting between the site update and the report.
• Information connected: the original account, supporting evidence and outstanding questions remain together.
• Clear responsibility: reporting review and commercial approval remain distinct, with a person accountable for each decision.
[ The Challenge ]
The day’s work is finished, but the report is still waiting. A supervisor has sent an update. Someone has taken photographs. A customer has requested a change. Part of the team was delayed, although the reason and duration have not been recorded together.
The project manager needs an account that other people can understand and act on. Getting there means reading through messages, checking locations, asking who gave an instruction and finding the photographs that belong to each event.
This matters because a useful daily record covers more than progress. It can include labour, resources, inspections, deliveries, interruptions and the next actions needed. Consistent reporting makes that information easier to find and review. Source: Procore
The workload grows when several projects need updates at once. Information arrives in different formats, people describe similar events differently, and managers repeat the same questions. Additional work may remain buried inside a general message until someone revisits it later.
The opportunity is to capture the detail while it is fresh and carry it through the reporting process, reducing the work needed to assemble a reliable account.
[ What CSM Built ]
We built a working proof of concept to make the reporting process visible from beginning to end. A project holds its updates, supporting attachments, individual event records, outstanding questions and report drafts. Each stage uses information already captured in the previous one.
The demonstration begins with the finished output: a nine-page report for a fictional electrical contractor. It includes a daily summary, work completed, a potential variation, an access delay, source information, photographs and an action register.
Behind that output, the workspace shows how an update can become separate records that people review and develop. A progress statement follows one route. A request for additional work needs commercial information. A delay needs its timing, affected resources and circumstances clarified.
For a client implementation, we would configure AI assistance around the company’s previous reports and agreed reporting criteria, then connect and test the required capture channels. The POC uses a prepared example to demonstrate that behaviour.
The purpose is a repeatable process that helps people get from a short site update to a report they can confidently review.
[ On Site ]
The site team should be able to contribute useful information without spending the end of the day formatting documents. The starting point is a brief account of the work, supported by photographs and any relevant details.
Depending on the company’s workflow, that could be a typed update, a voice recording or a combination of both. The capture method would be agreed around the people using it and the systems already in place.
01
Identify the project. The update belongs to a specific job and reporting date. Location details help distinguish work on different floors, areas or work packages.
02
Capture the activity. The supervisor describes completed work, requested changes and anything that interrupted progress. Photographs stay available alongside the account for human review.
03
Organise the record. The information is separated into useful categories, such as progress, potential additional work and delay. The original wording remains available behind each record.
04
Ask for missing detail. A change may need the requester’s name. A delay may need a start time. Missing answers remain visible until someone provides or reviews them.
The reporting standard would be agreed before deployment. A company’s previous reports can show useful terminology and layout, but the team also needs to define what a complete record requires. That prevents an old omission from becoming a repeated habit in the new process.
[ An Update from Site to Report ]
The demonstration follows a fictional office fit-out. It uses one prepared site update to show how different events move through the workspace.
The supervisor reports:
“Four electricians on site today. Finished first-floor containment. Client asked us to move six sockets in the meeting room. Two lads held up for two hours waiting for access to the riser. Photos attached.”
That message contains useful information, but it is not yet a complete report. The workspace separates what has been said, shows what still needs clarification and gives the reviewer a starting point.
01
Work completed. The containment installation becomes a progress record linked to the first floor. Completion is recorded as the supervisor’s account; it does not automatically establish inspection or acceptance.
02
Potential additional work. The six socket relocations become a separate change record. The team can confirm the instruction, establish the scope and prepare a price.
03
An access interruption. Two people delayed for two hours means four affected person-hours. The elapsed interruption remains two hours; any wider programme effect still needs assessment.
04
Evidence and unanswered questions. The original update stays connected to the records. The reviewer can see which details came from that account and which were supplied afterwards.
05
A report and action list. Reviewed information feeds the draft report. Unresolved items remain visible, with responsibilities and follow-up actions assigned as appropriate.
The manager can concentrate on the information that needs judgement. They can check the instruction, confirm the access arrangements and review the draft without first reconstructing the entire day from separate messages.
[ Recording Additional Work ]
A request made on site can create work beyond the original scope. Recording it early gives the commercial team a better starting point for deciding what needs clarification, pricing or approval.
In the example, moving six sockets is treated as potential additional work. The initial message does not establish who had authority to instruct it, whether it was confirmed in writing or exactly what the relocation involves. Those questions are kept with the event.
The review works through five parts:
01
Establish the request. Record who requested the change, when it happened and whether the instruction was verbal or written. Preserve the original account.
02
Confirm the scope. Clarify the locations, quantities and work involved, including any associated removal, reinstatement or testing that needs consideration.
03
Prepare the estimate. Use the entered labour allowance, applicable rate and material costs. In the demonstration, six hours at €55 plus €90 of materials produces a €420 draft estimate.
04
Keep separate impacts separate. The riser access delay has its own record. Its cost is unknown and is not quietly included in the socket-relocation price.
05
Record the decision. Commercial review, submission and client approval are different stages. The workspace keeps the estimate’s status visible as the team decides what happens next.
This gives the commercial team the event, supporting information and calculation together. The system does not establish contractual entitlement or turn a draft estimate into approved revenue. Its role is to help the team identify the issue and prepare the information needed for a decision.
[ Reviewing and Issuing ]
A professional-looking document still needs a responsible reviewer. The report should accurately describe the work, distinguish confirmed information from open questions and make the next actions clear.
In the POC, reviewed records feed the report while events awaiting review are listed separately. The manager can add commentary, approve a snapshot and export the document. The finished PDF illustrates how that information can be presented in the company’s own format.
The review focuses on three questions:
01
Does this accurately describe the day? Check the project, location, completed work, labour information and interruptions against the available source records.
02
Are the important gaps and decisions visible? Check that an unconfirmed instruction, missing inspection record or unpriced impact has not been written as an established fact.
03
Can the recipient act on it? Check the summary, photographs, references and action owners so the reader understands what requires attention.
The next step should remain clear when something cannot be completed. The supervisor may need to confirm a time. The project manager may need a drawing. The commercial lead may need to review a price.
Those answers can be added to the existing record, preserving the context already gathered. The team can then finish the report without restarting the handover.
[ Results ]
The work produced two connected demonstration assets: a functioning site-record workspace and a detailed report showing the output a construction or engineering team could review and share.
The prepared example carries one update into three records, develops a draft price for additional work and separates reviewed findings from unresolved items. The accompanying report presents the same scenario with project details, captions, commercial status and named follow-up actions.
Less document preparation
The workflow shows how captured information can support report preparation without being rewritten at every stage. A client pilot would measure the reduction in gathering, transcription, formatting and checking effort.
More consistent reporting
Agreed fields, clear questions and a defined review process help establish a common reporting standard. The quality check is whether the report contains the required information and represents the source accurately.
Earlier attention to changes
Potential extras and interruptions become identifiable records. The relevant person can review the information and decide what needs to happen before the detail is lost.
These are demonstrated workflow capabilities and intended operational benefits, rather than measured results for a named client. A pilot would compare the current process with the new one across representative reporting days, including capture, follow-up, review and corrections.
That establishes the net time returned and whether the reporting improvement justifies wider implementation.