The real jobsite: documenting work without BIM

Two jobs starting the same Monday

One has an information delivery plan, someone whose title includes the word “information”, and a coordination platform bought before anyone set foot on site. The other has a WhatsApp group named after the street. Both will be handed over. Only one of them appears in the sector’s conversation about itself.

This article is about the second one. Not because the first is wrong — on complex projects, model-based coordination pays for itself and there is no argument to have — but because the second is, by volume, most of what actually gets built, and almost nothing is designed for the conditions it works in.

The invisible majority in construction site documentation

The profile repeats itself. A private client with no digital requirement anywhere in the contract. A contractor appointed on price. Subcontractors arriving with a folded paper drawing in a back pocket. And a handover pack that turns out, at the end, to be a PDF and a folder of photos.

The site manager keeps the running record in a notebook and a camera roll. The site engineer rebuilds the week on Friday afternoon. It is worth saying plainly: this is not the exception, and it is not the sector’s stragglers. It is how the four-storey residential block, the fit-out, the warehouse and the facade refurbishment get built.

Why the gap exists, and why it is not ignorance

The comfortable explanation is that these teams resist change. It does not survive contact with an actual site: the same foreman learned his bank’s app, the door manufacturer’s app and the timesheet app without anyone running a training day.

The real explanation is economic. On a job with a thin margin and a short programme, any tool that needs setup, licences and training has to prove itself before the second month. Most does not — because most is designed for a project with an information structure, defined roles, and somebody whose job is to maintain it. On this job, nobody has that job.

What these teams already have

Everyone on site is carrying a camera, a microphone and GPS. The capture device is already deployed, already paid for and already used a few hundred times a day. Nobody has to persuade a foreman to take a photograph; he is already taking it.

Which means capture was never the problem. The problem is what happens to the thing captured. A photo living in a camera roll next to Sunday lunch is not construction site documentation. It is a memory with a timestamp.

The real cost, described without drama

It is the photo that exists but that nobody can find in November. It is the change agreed verbally on a Tuesday at the third-floor slab, which four people remember slightly differently by the time it reaches a valuation. It is the dispute where both parties are honest and neither can prove anything.

None of those is a disaster on its own. The cost is cumulative and quiet: hours of reconstruction on Friday afternoons, decisions taken twice because nobody knows what was decided the first time, and end-of-job arguments settled by attrition instead of evidence. We have written before about how decisions disappear into messaging groups; the pattern is always the same.

The two-speed sector, and the seam between them

The seam is easiest to see at the edges. A job with mature coordination hands over to an operator who has none, and the model becomes a file nobody opens again. Or the reverse: a subcontractor with no digital process joins a modelled project, does perfectly good work, and delivers his part of the record as an unsorted folder of JPEGs.

In both directions, information dies at the joint. Not through bad faith, but because each side holds a different expectation about what gets documented and in what form.

What “digitalisation” should mean for this segment

Not adopting the methodology of the sector’s most mature end. That road is legitimate, and for anyone with projects that justify it, it is the right answer. But exporting it to a twelve-month job with three people in the technical office is handing someone a suit three sizes too big.

For this segment, digitalisation means something far more modest: making the gesture that already happens — taking the photo — produce something findable afterwards. Lower the ambition and raise the completion rate. A mediocre process that actually runs beats an excellent process abandoned in March.

The threshold that decides everything

There is a threshold, and it is unforgiving: if recording something takes longer than a few seconds, it does not happen. Not in the rain, not with gloves on, not when the foreman is waiting for you on the third floor.

From which follows a design rule the industry finds uncomfortable: any process that depends on people on site being more organised than they already are has failed before it started. Design around the behaviour that exists, not the behaviour you would prefer. In practice, that is the entire theory that field documentation needs at this end of the market.

What this looks like in practice

Very little, which is the point. Open the PDF drawing on the phone, tap the exact spot, dictate the Description by voice instead of typing it, attach the photo. The record is anchored to a place, with a date and an author, and six months later it can be found by looking at the area rather than by remembering. If someone needs to act on it, the pin gets an owner and shows up on a board. If nobody does, it simply stays as evidence.

That is what we build at PinMy, and at month end you can produce a PDF report for one file listing every pin and every comment on it. That report is in beta and publishes its own limits — we would rather tell you than let you discover them. For the operational detail, our site visit documentation checklist is most of what there is to know.

What PinMy is NOT

PinMy is the field-capture layer: pins carrying voice, photo, video and text on PDF drawings, photos and videos, with assignment and a board. It is not a model, it is not a common data environment, and it does not replace Revit or your coordination software. It does not write the report for you and it makes no engineering judgement — that stays yours. And it does not turn a job without BIM into a job with BIM. It is not trying to.

FAQ

Isn’t this just taking photos with extra steps? It is taking the same photo and having it keep its place, date and author. You do not notice the difference on the day you take it. You notice it on the day someone goes looking for it.

Does it work if my subcontractors will not install anything? Yes. You can share a guest link that they join with a name only — no account, no install. It is light collaboration, not an identity or access-control system.

And if we do move to BIM in a few years? Better. Field documentation does not compete with modelling; they are different layers. What is lost in the camera roll today would still be useful once a model exists, because a model describes what was intended and a dated photo describes what was executed.

The majority deserves tools too

The mature end of the sector will keep advancing, and that is good for everyone — today’s leading edge is the standard ten years from now. But in the meantime, most of what gets built is built by teams working under different conditions, and those conditions deserve tools designed for them rather than cut-down versions of somebody else’s.

Recognise the WhatsApp-group job? Send this to the colleague who will spend Friday evening rebuilding the week from a camera roll.

• Start free: pinmy.co
• Book 15 minutes: tidycal.com/pinmy