Introduction
The site visit takes an hour. The report, done the way it has always been done, takes another half: back at the office, with the photos on the phone's camera roll, the notes split between a pad and three voice messages, and memory quietly filling the gaps. That half hour rarely happens the same day, so the report gets written on Friday, sent on Monday, and signed... sometimes.
This is not a cosmetic problem. A late, unsigned report is precisely the document that fails when you need it: when the subcontractor says "that was never mentioned", when the client asks why a decision cost what it cost, or when a defect flagged in March is still open in May and nobody can find who was supposed to fix it.
This guide covers what site visit minutes must include to do their job, why the traditional method weakens them, and how the whole flow — look, dictate, photograph, sign — can close before you leave the site.
What a site visit report must include
There is no single mandated format, but practice — and the arguments that follow — have settled the minimum content fairly clearly:
- Identification: project, date and time of the visit, and who carried it out.
- Attendees: name and role of everyone present (site direction, site manager, trades, the client). The most commonly forgotten item, and the first one disputed.
- State of the works: what was reviewed and its condition, ideally organised by area or room rather than as one running paragraph.
- Checks performed: if the visit follows a checklist (setting out, services, finishes...), each point's result — pass, fail or not applicable — with its observation.
- Defects: every problem found, with its severity, its location, and — the line that separates useful minutes from decorative ones — who is responsible for fixing it.
- Decisions and agreements: what was decided, by whom, and to what deadline.
- Photographic evidence: dated photos tied to their area, not a generic annex of twenty captionless images.
- Signatures: from the attendees, on the spot if possible. Unsigned minutes are a version of events; signed minutes are the version of events.
If your current report covers all of this, the question is no longer content but cost: how much does producing it cost you, and how long before it exists?
Why the traditional method weakens it
The classic flow — notes on site, writing at the office — has three structural failures.
The evidence gets separated from the decision
Photos live on a phone, notes on paper, and the writing happens hours or days later somewhere else. Each step pulls the proof a little further from the agreement. When, six months on, you need to show that the bathroom damp was already flagged on the visit of the 12th, the photo exists... somewhere in a camera roll, undated, unlocated, unconnected to the report.
The report arrives late
Minutes written on Friday describe Tuesday's site with Thursday's memory. Nuance evaporates, attendee names drift, and "the tiler must redo the shower corner before Thursday" becomes "various snags were discussed".
Defects die inside the PDF
This is the expensive failure. Traditional minutes record the defect but do not pursue it: the PDF gets filed, and follow-up depends on someone remembering to re-read it. The defect noted and the defect fixed are two worlds connected only by one person's memory.
How to finish it in minutes, from a phone
The flow below is how the Tabiquo app implements it, but the logic is general: capture on site, assemble automatically, sign on the spot.
1. Open the visit: one tap
No form. Tap the button and the visit is created with today's date and a title; if a visit was already open today on that project, it resumes instead of duplicating. The phone is ready to capture before you are through the door.
2. Dictate instead of typing
The dictation button records what you say — "visit with Lucía from the client side and the site manager, we reviewed the ground floor and bathrooms, tiling is running two days late" — and AI turns it into structured data: the title, the notes and the attendee list with each person's role, extracted from the sentence itself. Transcription is built to survive site noise, and the structuring leaves everything ready to review, not to retype.
3. Photos per room, not in a pile
Each photo is taken from its room's card — kitchen, main bathroom, façade. It stays attached to that space, with its caption, and comes out of the final report ordered by area. Room observations can be dictated too. And if the basement has no signal, photos queue on the phone and upload themselves when coverage returns.
4. The checklist, from a template
Control points are defined once — one template per visit type — and applied on site with a single tap. Each point is marked pass, fail or not applicable, with its note, and the visit keeps a running pass rate as you go.
5. Defects are born as incidents, not paragraphs
When something is wrong, you don't write it down — you open an incident from inside the visit, with its ticket number, photo, severity and assignee. If the project's drawings are loaded, the incident is pinned at the exact spot on the floor plan, coloured by severity. That ticket will appear in the minutes, but — unlike a paragraph — it stays alive afterwards: open, assigned, in progress, resolved, verified, closed.
6. Generate the minutes: another tap
On completing the visit, one button generates the site minutes with everything assembled: date, project, attendees, notes, the control-point table with each result, and the incidents found with their severity. You review, adjust what needs adjusting, and lock. Locked minutes can no longer be edited; once anyone has signed, they cannot be unlocked either.
7. Sign on the spot, without accounts
Each attendee signs from their own phone: show them a QR code or hand them a link, and they sign with nothing to install and no account to create. Each signing link is individual, expires after a few days and can be regenerated; each signature is stamped with date and time. It works the same for site direction, for a trade, and for the client.
8. The PDF, sealed and on your letterhead
The final document carries your studio's letterhead and a cryptographic seal: the signed content is hash-bound to the PDF, so any later touch-up would be detectable. It shares from the phone through whatever channel fits — email, WhatsApp — before you start the car.
The same flow — write or dictate, lock, sign, share — also covers meeting, kick-off and handover minutes: the visit is the most frequent case, not the only one.
What happens after the visit
Here lies the real difference between minutes-as-document and minutes-as-process.
With traditional minutes, the day after the visit starts the invisible work: transcribing, chasing the trade by phone, forwarding photos, copying pending snags to yet another list.
With the on-site flow, that work is already done at the moment of signing:
- Every defect is a ticket with an owner, moving through its own workflow (open → assigned → in progress → resolved → verified → closed) without anyone re-reading the PDF.
- Photos live in their room and their minutes, findable months later without diving through camera rolls or chats.
- The office sees the visit that same afternoon in the panel, with the same incidents and the same photos, and nobody has to "write it up properly".
- The record defends itself: sealed minutes, signatures stamped with date and time, and a trail that does not depend on anyone's memory.
Common mistakes in site visit reports
- Writing it afterwards. Everything above collapses if the minutes are written from memory. The working rule: if the report doesn't exist when you leave the site, it half exists.
- Photos without context. Twenty photos in an annex with no caption and no room are almost as useless as none. Every photo needs its where and its when.
- Defects without an owner. "Damp found in bathroom" is not an agreement, it is a description. Without a name and a deadline, the defect is an orphan.
- Unsigned minutes. A version of events nobody signed is only your version. Signing on the spot — trivial today with a QR code — is what makes the minutes hold up.
- The report in one place, the follow-up in another. If the snags in the minutes must be copied to a separate list to be chased, they will be copied the first week and forgotten by the third.
Conclusion
Site visit minutes are one of the few documents used twice: once to organise the site this week, and again, months later, to prove what was said and who accepted it. They deserve to exist on the spot, with the photos inside, the defects owned, and the signatures of the people who were there.
With Tabiquo, that whole flow — dictation, photos per room, checklist, incidents with an assignee, minutes generated in one tap and signed via QR — is the site visits and minutes feature, integrated with the rest of the project: work reports, time tracking, planning and client communication. To see it on a real project, book a thirty-minute demo: your next visit can leave the site signed.