Construction
The weekly report takes longer to compile than to read.
The photos, the foreman’s notes and the site figures all exist. They are in different places and someone has to bring them together every week, in the format the client expects to receive.
The site is recorded every day. The report is still assembled by hand.
02 / 8
Context
Where the information lives today
On a site the information is born on a phone: photos, the foreman’s notes, a measurement, an incident. It ends up in a message group or a folder and stays there. The figures are somewhere else, in a spreadsheet or in the Drive. Whoever writes the weekly report is doing archaeology on the last seven days.
- The photos and daily notes the foreman posts in the site channel
- The site budget and what has already been invoiced, in the sheet linked to that channel
- The report format the client expects to receive
- The incidents that still have no answer, scattered through the conversation
Action
What starts happening on its own
What the foreman already posts becomes raw material. The agent gathers the week’s photos and notes, organises them by day, summarises what moved forward and assembles the report in the right format, with the photos embedded. And when you ask how much has been invoiced against budget on that site, the answer comes in the chat, on the spot, from the figures already connected to the channel.
- The weekly report assembled from what was posted, day by day
- The photos embedded in the format the client receives
- Budgeted, invoiced and the difference, answered the moment you ask
- What moved forward summarised, and what stalled said as having stalled
Who answers
Who answers when it gets something wrong
The report goes to the site manager before it goes to the client. A number the agent gives back brings the sheet it came from, so it can be verified instead of believed. And access is per site: whoever works on one site does not see another one’s costs, and that is written into the rules before the agent comes in.
- The report passes the site manager before it goes out
- A figure given back says where it came from, so it can be verified
- Access is per site, written into the agent’s rules
Two shapes
What comes off the ladder takes one of two shapes. We have built both.
Agent in the channel
Every site already has a channel, and that is where the information is born. The agent lives in that channel, reads what gets posted there and answers there, with nobody installing anything on site.
Archive with an agent
Earlier sites answer questions about the current one, as long as they can be consulted. An archive with an agent on top turns old reports into answers.
Where it starts
Start with one site, with the weekly report that already exists, and see what comes out with nobody compiling it.
See the three stepsRelated questions
People who ask this usually ask as well.
- 06What if my team does not know how to use this?The team uses the agent in the chat where it already works, and training and support are part of the delivery.
- 07We already tried AI before. Why did it not work?Because AI amplifies the processes a company already has, and with disorganised processes it amplifies the disorganisation.
- 02How much is it going to cost me to have AI running?The cost of the AI stays inside a limit you set with us before we start, and you see what it spends, day by day.