Skip to content
VelkriVelkri

Blog

Construction site meetings: recording on a phone, decisions everyone can find

Site walks happen standing up, in the noise, with nobody free to write. How to record them on a phone and end with decisions and actions the whole project can find.

A site meeting does not happen at a table. It happens walking a floor in boots, pointing at a wall, with a generator running somewhere below. The architect, the contractor's site manager and the client's representative agree five things in forty minutes, and nobody has a free hand to write any of them down.

So the minutes get written that evening, from memory, by whoever drew the short straw. A week later the electrician installs the sockets at the old height, because the change was "agreed on site" and never made it into anything the electrician reads.

This post is about closing that gap: recording a site meeting on a phone, and ending it with decisions and actions the whole project can find, including the people who were not on the walk.

What goes wrong with site minutes

Site minutes fail for practical reasons, not lazy ones.

  • Nobody can write while walking. The person who knows what matters is the one doing the talking.
  • Decisions point at things. "Move this one across to there" is clear on the floor and meaningless in a notebook.
  • The record arrives late. Minutes written that night go out the next day, after the trades have started work.
  • The people who need it were not there. The subcontractor who has to act on a decision often hears about it second-hand, by phone, in a shortened version.

The usual answer is a stricter minutes template. Templates help with what to write. They do nothing about when, or about who can find it later.

Record the walk, not the memory

The simplest fix is to record the meeting itself. A phone in a top pocket picks up the people closest to it, and anyone else with a phone can add theirs as an extra mic.

Here is how that works in Velkri. Start a recording from the project, on a phone or in a laptop browser. If you organised a meeting in a room on your calendar, Velkri asks whether to record it when it begins. Other people on the walk can join as mics from their own phones, so the person at the far end of the corridor is heard too. The Velkri phone apps are in beta, and recording also works in the browser.

Recording a site walk on a phone, with two more phones in the room as extra mics. The screen shows that it is recording.

While it records, the screen shows that it is recording. Recording consent is handled per workspace, as it is for calls, and the people on the walk should be told. On most sites a quick "I'm recording this so we get the minutes right" at the start is all it takes.

Three things make site recordings far more useful:

  1. Say where you are. "We're on level 2, grid line C." It costs two seconds and makes every decision that follows findable.
  2. Take marks and photos as you go. A mark during the walk becomes a chapter in the recap, and each photo sits in the recap at the moment it was taken, so "the doors on level 2" has a picture next to it.
  3. Read decisions back. "So, sockets at 450 on this wall, agreed?" A clear sentence with a yes after it is the most useful ten seconds of the meeting.

If you want, turn on a live transcript and read along. With the live transcript on, you can also ask Velkri a question out loud during the walk, starting with "Velkri, ...", for example to check what was agreed about the same wall last month.

What you get after the walk

When the recording stops, Velkri writes the recap. It plays the recording, and every line, decision and task jumps to its moment. "Sockets at 450" plays the twenty seconds where it was agreed, next to the photo you took there.

The recap of the walk: the mark and the photo at their moments, the decisions and the action with the time to play each from, and the confirmed action as a task with its owner.

Decisions and actions from the walk arrive as proposals for the people who were there. The site manager confirms the decisions that were really made, edits any that need a detail added ("sockets at 450 mm to centre"), and dismisses anything that was only discussed. Only what is confirmed goes on the project's record.

Confirmed actions become tasks with an owner. "Joe to resubmit the door schedule by Friday" is a task in the project with Joe's name on it, not a line in a document Joe may never open.

Decisions everyone can find

Recording the walk solves the writing. The bigger win is what happens next: the decision is now in the same place as the rest of the project.

  • The electrician who was not there can be in the project and see the confirmed decision the same day, with a link to the moment it was agreed. Outside companies can be guests: they see that one project and nothing else, and they are not billed as seats.
  • The project manager in the office sees the walk's decisions on the project's timeline alongside the decisions made on calls and in imported WhatsApp chats.
  • Anyone, months later, can ask the project "what did we decide about the level 2 doors?" and get an answer with a footnote that plays the walk from that moment.

Site teams also agree things on WhatsApp, often in the same week as the walk. Those groups can be imported into the same project, so a decision made by message and one made on the floor end up side by side. Our post on bringing a WhatsApp group's decisions into one place walks through it.

If you are not ready to record

Not every client or site is comfortable with recording, and that is their call to make. A disciplined set of written minutes still beats memory. Our free site meeting minutes template is built for walks: location, attendees, decisions with who approved them, actions with owners and dates, and space for photo references.

Whatever you use, three rules carry most of the value:

  1. Write decisions down on site, before you leave the floor, even as a voice note to yourself.
  2. Give every action one owner and one date.
  3. Send the minutes the same day, to everyone who has to act on them, not only the people who were there.

A typical week, with and without the record

Without a record, a decision made on Tuesday's walk reaches the trades on Wednesday by phone, gets questioned on Friday, and is argued over the following Tuesday, on the next walk, from memory.

With one, Tuesday's decision is confirmed on Tuesday afternoon, visible to the trades in the project that evening, and settled on Friday by playing twenty seconds of the walk. The next walk starts with what was decided, not with what people remember.

Site meetings will always happen standing up, in the noise, with nobody free to write. They no longer have to end with one tired person writing minutes in the evening. See how a project looks with the walks in it on the construction page.