IFC vs PDF on Site: When to Use Each One

The format war nobody is actually fighting

At conferences it sounds like a battle: the 3D model versus the good old drawing, the future versus paper. Then you walk onto any real site and the war doesn’t exist: the site manager carries PDFs on his phone, the model comes out when the questions get serious, and everyone uses whatever solves the problem in front of them.

That’s the short answer to “IFC vs PDF”: it’s not a choice, it’s a division of labour. The long version — what each does well, and how to keep the division from becoming documentation chaos — is this article.

What each format does well

PDF is the king of certainty: opens anywhere, weighs nothing, prints, and shows exactly what the designer signed — dimensions, notes, legends. Its limit: it’s flat. The section they didn’t draw doesn’t exist, and the third dimension is left to your imagination.

IFC is the king of context: the whole building, navigable, every element knowing what it is (the jargon-free explanation is here). Its limit: it asks more of the device and the user, and it doesn’t replace the contractual document — what’s signed stays signed.

The decision table

Task on site	Winning format	Why
Check a dimension or a signed detail	PDF	It’s the contractual document, with the designer’s annotation
Understand a complex multi-trade junction	IFC	Rotating the model beats imagining three sections
Quick setting-out with the trade standing there	PDF	Opens in a second, everyone reads it
Show the installer what runs through that ceiling	IFC	You see the duct, the tray, and the installation order
Mark snags room by room	PDF	The floor plan is the natural map of a snag list
Verify as-built against design intent	IFC	You compare reality with the model in front of the element
Attach to a certificate or an official record	PDF	It’s a document format, not a data format

The table’s conclusion isn’t “PDF wins” or “IFC wins” — it’s that a normal site uses both on the same day.

The real problem: two formats, two systems?

Here’s the trap people actually fall into. If plan-based issues live in one place (marked-up PDF screenshots, WhatsApp) and model-based ones in another (viewer captures, emails), you’ve turned a healthy division of labour into two parallel archives — and at Monday’s meeting nobody knows which one to check.

The fix isn’t picking a format: it’s making the documentation a single flow, wherever the background lives. In PinMy the gesture is identical: tap the point — on the PDF plan or on the IFC model — and drop a pin with a photo, an auto-transcribed voice note or text, assigned, with a status on the Kanban board. One issue flow, two backdrops. The model, by the way, converts automatically to a lightweight format for fast mobile viewing — how to open it without Revit, here.

The usual honest boundary: on the model, a pin marks a point in 3D space, not an element — PinMy doesn’t read element data and doesn’t version models. Field documentation, not BIM coordination.

Three rules for living with both

1. Contractual matters go to PDF. What gets signed, measured or certified points at the signed document. The model illustrates; the drawing binds.
2. Spatial matters go to IFC. Services crossings, odd junctions, “what’s behind this?” — to the model, that’s what it’s for (and it doesn’t end at handover).
3. Documentation goes to one place. One issue = one pin with its evidence and its owner, whether it sits on the plan or the model. One project record, not two.

FAQ

Will IFC replace PDF on site? Not soon, and not entirely: PDF is the format of the contractual document and of fast daily work. IFC adds the spatial dimension and the information. Real sites are mixed — the useful question is which task is in front of you.

Do I need the model to work well? You can work well with PDFs alone — sites always have. But if the model exists, not using it is giving away context: junction doubts, hidden services and as-built checks all resolve better in 3D.

How do I document issues without duplicating systems? With one capture flow that works the same on both backdrops: pin at the point, evidence, owner, status. The background changes (plan or model); the record is one.

What PinMy is NOT

PinMy is the field-capture layer over PDF plans, photos, videos and 3D IFC models: pins with voice, photo and text, assignment and Kanban status. It is not an authoring or BIM-coordination tool, doesn’t read element data, doesn’t version models, isn’t a CDE and doesn’t replace Revit. The web PDF report is useful today and still maturing.

Next junction doubt

When it arrives — and it arrives weekly — try it on the model instead of imagining it on the drawing. And send this table to the colleague who still thinks this is a format war.

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