What the Industry's CDE Debate Misses About Field Teams

Reading the industry’s homework with muddy boots

We build a field tool, so we read the industry’s platform conversations the way a plumber watches a cooking show about kitchens: with interest, and with one recurring question — who’s going to wash up?

Lately we’ve been reading the working-group conclusions that buildingSMART Spain’s round tables have published on common data environments — how CDEs are actually being used, where the approval flows break, what contractors complain about (their analyses are public, in Spanish, and worth your time: buildingsmart.es; the international context lives at buildingsmart.org). Four takeaways stuck with us. Each one is correct. And each one looks different when you read it from the workface.

Takeaway 1: a CDE is an ecosystem, not a folder

The working groups are blunt about this: teams that treat the CDE as “the folder where deliverables go” get disorder, duplicates and broken approval chains. A real CDE is an ecosystem of rules — who publishes what, in which state, approved by whom.

The field-side view: the people in boots never see the ecosystem. They see a login they were given in week one and forgot by week three. If using the official environment takes more taps than WhatsApp, WhatsApp wins — and the beautifully governed ecosystem curates documents while the decisions happen somewhere else. Adoption isn’t a rollout problem; it’s a friction problem.

Takeaway 2: files move, context dies

Another recurring finding: even with a CDE in place, information travels between design and site as files — and the context around them (why this version, what changed, what was answered) evaporates in the transfer. Traceability is the whole point, and it keeps leaking.

The field-side view: on site the unit of information was never the file — it’s the finding. This crack, this instruction, this photo of what’s behind the partition. A finding without its place and its thread is trivia. That’s why we anchor everything to a pin: the photo, the voice note (auto-transcribed), the reply thread, the owner, the status — welded to the point on the plan or the 3D model where it happened. Context doesn’t die when it’s structurally attached to the place — the case we made in why your site has no memory.

Takeaway 3: the barrier is cultural, not technical

Every working group lands here eventually: the technology exists; what’s missing is habits, roles, and people willing to change how they record work.

The field-side view: agreed — but culture doesn’t change by mandate, it changes by gradient. Nobody on a scaffold adopts a governance model; they adopt a gesture that’s easier than the current one. Tap the plan, speak, done. If the compliant path is also the lazy path, culture follows. If it isn’t, no amount of training budget saves the rollout.

Takeaway 4: open standards and structured data are the direction

The long-term vision the industry converges on: information as structured, standards-based data — IFC and its siblings — not as PDFs in folders with clever names.

The field-side view: we’re believers — it’s why PinMy opens IFC models on a phone and why our pins are structured records (place, evidence, owner, state) rather than loose messages. But the structured future only materialises if capture starts structured. You can’t retrofit structure onto a camera roll and a chat export at project’s end. The pipeline begins in the pocket.

The CDE of the future “knows, checks and remembers”

One phrase from the industry conversation stayed with us: tomorrow’s environments won’t be passive repositories — they’ll know things, check things, remember things. We’d sign that. With one amendment from the boots: a system can only remember what someone actually captured. However smart the environment, its memory is bounded by what reaches it — and today, on most sites, the richest layer of project information dies in chat threads before any environment gets a chance to remember it.

That’s the corner of the problem we chose. Not a CDE — we say so explicitly in what is a common data environment — but the capture layer that makes any future environment worth its name, because decisions and evidence are born structured, located and owned.

FAQ

What is a CDE, briefly? A common data environment: the agreed single source of project information, with rules for states, approvals and responsibilities (the ISO 19650 family describes the management side). Our plain-words guide: what is a common data environment.

Is PinMy a lightweight CDE? No — and we’re strict about saying so. PinMy is field capture: located findings with evidence, owners and statuses. It doesn’t run document approval workflows or contractual information management. It sits before a CDE, and alongside one when you have it.

Where should a small team start? Where it bleeds: stop losing decisions and evidence. Structured capture on the plan costs a gesture and pays immediately — and it’s the cultural half of any future platform adoption, done early.

What PinMy is NOT

PinMy is the field-capture layer: pins with voice, photo, video and text on PDF plans, site photos and 3D IFC models, with assignment and Kanban status. It is not a CDE, doesn’t replace one, doesn’t manage document approval or claim any standards compliance — and a pin on a 3D model marks a point in space, not a model element. The web PDF report is useful today and still maturing.

If you sit in those working groups

We mean this warmly: invite more people in boots. And if you are the person in boots — try capturing tomorrow’s first finding as a pin instead of a message, and see which one your project remembers in March.

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