Eight people are standing in a shell structure, two of them on the phone, an angle grinder running in the background. The site manager holds the drawing against the hoarding and scribbles in the margin. Three weeks later the question comes up of who agreed to bring the electrical rough-in forward. Construction meeting documentation is hard because every problem that usually appears on its own shows up here at the same time.
Noise belongs to the place. The people present come from several different companies. And whoever writes things down is the person who should be arguing the technical point. Fixing that means starting with how the meeting is captured, not with a better minutes template.
Why the site meeting is the hardest case for minutes
Some meetings a recorder on the table handles without any trouble. The site meeting is not one of them, and there are three independent reasons for that.
Noise belongs to the place, not to the exceptions
In a meeting room a jackhammer is a disruption. On a building site it is the normal state. Continuous noise raises the noise floor, and any microphone captures noise and speech with equal weight. The software then has to pull speech out of a mixture in which the interference is about as loud as the signal you want.
Many people speak, and not all of them are known
In an internal meeting you know the voices. On site the client, the architect, the site management, two subcontractors and the structural engineer stand together, some of them meeting for the first time. Attribution by voice character has no reference to work from here. The result is Speaker 3 in the minutes, and nobody later knows which company that was.
Whoever takes notes cannot join the discussion
This is the most expensive point and it is rarely named. Writing costs attention. Whoever holds the pen misses exactly the follow-up question that matters later, or joins in and stops writing. Either way you end up with minutes in which the decisions are missing and the statements of intent are present.
What rides on the record commercially
On a construction project, documentation is not diligence for its own sake. It is the basis on which additional work and delays can be substantiated at all.
Variations are agreed in conversation, not in the contract
The contract describes the intended state. The deviation happens in a throwaway line on site: "Just do that while you are at it." If that sentence is documented nowhere, the instruction later exists only as an assertion. That usually hurts the party who did the work and now wants to invoice it.
Delays need a date
Delays are only usable if it is traceable when they were reported. Where the German VOB/B standard construction terms are agreed, they require written notice of a hindrance without delay, and "without delay" is hard to prove without a dated record. Whether and how that applies in a specific case depends on the contract and belongs with your own legal advisers. For documentation practice the consequence is the same regardless: you need a record with a date and the people involved, not a recollection.
The usual approaches and their limits
Three methods have established themselves in practice, and each solves part of the problem while leaving another part open.
Handwritten notes on the drawing
Fast, robust, works in the rain and without a battery. The drawback: what you get is a selection, not a record. What gets written down is what the writer considers important, in their own words. The exact wording of a commitment, which is what matters in a variation claim, cannot be reconstructed afterwards.
A voice recorder in a jacket pocket
This is the obvious next step, and it only moves the problem. The device records from one position, usually from the site manager's pocket. Distance acts quadratically, and every doubling costs roughly 6 decibels, so the subcontractor standing three metres away is captured proportionally quieter and is more easily buried by the noise. What remains afterwards is an audio file somebody has to listen to. Why that approach hits a wall is set out in the article on the dictaphone alternative.
The site diary app that only knows text
Site diary apps structure things well, but they assume somebody types. Filling in a form with work gloves on is not a realistic expectation, so it happens in the office in the evening, from memory. The structure is better than a scrap of paper, but the source is the same.
The approach that works on site
If one microphone in one place is the problem, the answer is not a better microphone but several microphones that are already there. Everybody present has a smartphone in their pocket.
Several phones instead of one microphone
Whoever attends joins the appointment in the app, and the devices record together as a single appointment. Each phone is a close microphone for the person carrying it, and proximity is the only variable that genuinely helps against noise and distance. One phone is enough for the documentation, every additional one improves the result. Sally states an accuracy of up to 98.8 percent for this setup.
Names instead of Speaker 1 and Speaker 2
The second effect matters more on site than raw text quality. Because every voice arrives through a known device, each statement carries a person and therefore a company. "Speaker 3 says it was included in the order" becomes a name with a timestamp. That is the difference between a note and a record.
Tasks that leave the meeting already assigned
After the meeting there is no raw material but a transcript with names, a summary and a task list with owners. Sally works in 99+ languages, which on sites with crews from several countries is not a side issue, hosts exclusively in Germany and hands the results to 8,000+ tools so they land in the project controls already in use rather than in a second system. How it works for on-site appointments is on the page about transcription of in-person meetings.
Site minutes compared
| Criterion | Note on the drawing | Voice recorder | Linked phones |
|---|---|---|---|
| Exact wording of a commitment | summarised | preserved, but only as audio | preserved and searchable as text |
| Attribution to a company | only if noted | to be reconstructed later | via the device channel |
| Behaviour under noise | unaffected | vulnerable | far more robust through proximity |
| Note-taker tied up | yes, completely | no | no |
| Effort after the meeting | writing it up | listening and typing | reviewing and approving |
| Works without a signal | yes | yes | recording yes, processing later |
What stays difficult even with the best approach
Two limitations belong here, otherwise the recommendation is not credible. Anyone who is not linked stays a distant speaker, and on a building site not every subcontractor will install an app. The result is then better than a single recording, but not perfect for everyone present.
And the principle needs to be announced. Recording without consent is a criminal offence under Section 201 of the German Criminal Code, and with people from several companies present that is not a formality but a real agreement at the start of the meeting. Skipping it does not leave you with a documentation problem, it leaves you with a bigger one.
Conclusion
Site minutes rarely fail because of the template. They fail because one person is expected to listen, think and write at the same time while the location works against them.
The way out is not to demand more discipline but to organise the recording so that it matches the conditions on site: close to the voices, with unambiguous attribution, and without anybody holding the pen. Anyone who wants to try it at the next meeting can test Sally free for 30 days. Which digital tools in the trades actually deliver beyond that is assessed in the piece on the best AI tools for tradespeople, and the wider picture of the recording principle is in the article on transcribing in-person meetings.
