When plans stop being static: the case for connected field documentation

When the whole industry agrees on one thing

This year, at the UIA World Congress of Architects in Barcelona, one of the biggest names in technology built its message around a single, very concrete idea: site plans should stop being static documents and become part of a connected workflow. When a company that size points its spotlight at a problem, it usually confirms something the people doing the work already knew.

And the message is hard to argue with. The gap between what gets designed and what actually happens on site is real, expensive, and still mostly unsolved. The fix has a name now — connected field documentation — and it’s worth being precise about what that means on the ground, not just on a keynote slide.

The problem was never a lack of apps

Construction teams aren’t short on software. Most sites have plenty of digital tools floating around. The friction is somewhere else entirely.

The real issue is the disconnect between digital design and physical execution. The plan lives in one place, the office uses another system, and the person standing in front of the actual wall is documenting the problem in a WhatsApp group or a long email chain. By the time that observation reaches the right person, the context is gone — which is exactly the failure we picked apart in the WhatsApp voice message nobody can find again and the hidden cost of coordinating a site by email.

What connected field documentation actually means on site

A connected observation isn’t just a faster message. It’s an observation anchored to its place.

When you can see where on the drawing something was flagged, what it looked like, who responded, and when — you no longer have a floating note. You have a record. That’s the whole point of connected field documentation: a site note that carries its own context and history, instead of dissolving into a chat scroll. The plan stops being a static PDF and becomes the place the work is documented.

Two roads to the same goal

There’s more than one way to get there, and both are valid.

One road is to make paper smarter: keep the printed sheet, add version control, and scan the marked-up drawing back into a system so updates aren’t lost. It respects how a lot of teams still work today.

The other road is to let the annotation be born digital — anchored directly on the drawing, traceable from the very first second, with no paper round-trip at all. This is the road PinMy takes, and the rest of this piece is about what that looks like in practice.

How PinMy approaches connected documentation

The idea is deliberately simple. A field worker opens a plan, a site photo, or a PDF, taps the spot where the issue is, and drops a pin. From the menu, that pin can be a voice note, text, or an area — a rectangle dragged over a whole zone instead of a single point. Add a photo or a short video, and the pin holds the location and the evidence together.

Voice notes auto-transcribe across 20+ languages, so the pin carries both the audio and searchable text — and a note spoken in one language is readable by a teammate who reads another. Each pin keeps its own conversation thread, so the back-and-forth happens in context instead of in a separate channel. That’s construction site documentation that stays anchored: traceable from the first second, on the drawing everyone already recognises.

From a pin to a tracked task

Connected documentation only earns its keep if it drives action. So on any pin you @mention the right person and assign it, and it lands on a Kanban board — To-do, In Progress, Done — that’s the live state of your pins. When the work’s done, mark it resolved and it dims on the plan. The observation doesn’t just get captured; it gets tracked to done, with its full history attached.

And because sharing matters, guest links let the rest of the team — even people without an account, who join with just a name — follow what’s going on and pin their own feedback. The record is connected outward, not locked in one person’s phone.

No hardware, no round-trip

There’s nothing to install on a wall and nothing special to buy. It works from the phone already in your pocket.

That matters, because the moment to capture a problem is when you’re standing in front of it — not three hours later, back at the office, trying to remember which corner of which floor you meant. A field documentation app that needs a round-trip has already lost the context it was supposed to preserve.

Why this matters most for small teams

For a large organisation, “connected plans” is an ecosystem strategy: new platforms, new devices, real capital cost, and a rollout plan. That’s a serious commitment, and at scale it can make sense.

For a small team — a couple of aparejadores on a rehabilitation job, a contractor running two sites at once — the same outcome can be far lighter. Open the app, drop the pin, move on. The traceability is there without the project to deploy it. If you’re weighing how much tool you actually need, we made that case honestly in do you need PlanRadar, or is something simpler enough?.

FAQ

What is connected field documentation? It’s site documentation where each observation is anchored to its exact place on the plan and carries its own context — what it was, who responded, when — instead of floating in a chat or email. The plan becomes a traceable record rather than a static file.

Do I need special hardware or a big rollout? No. PinMy works from the phone in your pocket — no devices to install, no deployment project. You open a plan, drop a pin, and the observation is traceable from the first second.

Does PinMy replace my design or office tools? No. It’s the field-capture layer that sits alongside them. It captures and organises what happens on site, in context, so observations survive the trip to the people who need them.

What PinMy is NOT

We’re careful about this, because honesty is part of how we want to be judged. PinMy is the field-capture layer — it isn’t here to replace the tools your office already relies on, and it doesn’t pretend to be a full design environment. It’s not a project-management suite or a common data environment. With 3D models, a pin marks a point in space — a dated snapshot — not a model element, and it doesn’t read element data. The web PDF report is useful today and still maturing, so it isn’t a full reporting suite yet. If a tool promises you everything, be a little suspicious — we’d rather do one thing well: make sure the observation from the field survives the trip to the people who need it.

Try it on your next site visit

The next time you walk a site, document one issue as a pin instead of a message — and see whether it’s still clear a week later.

• Start free: pinmy.co
• Book a 15-minute walkthrough: tidycal.com/pinmy