
The 2-Inch Door Move That PDF Comparisons Missed
A Door Moves Two Inches. The Fire Rating, Framing and Hardware Move With It.
A 2-inch move does not change the drawing much. On a floor plan it is a door edge nudged left, still inside the corridor, still swinging the same way. Nobody flags it in a design meeting. It looks like the kind of edit that takes ten seconds and costs nothing.
Picture a healthcare project. That nudge slides a door out of a rated corridor wall into a non-rated partition. That single move pulls the fire rating with it. Then the partition assembly changes. Then the framing. Then the hardware schedule. Four trades absorb the ripple. None of them saw it coming.

The reason nobody caught it is simple and uncomfortable. The team was comparing PDFs. Somebody plotted the old set. Somebody plotted the new one. A junior coordinator flipped between them on a second monitor looking for differences. Doors look identical on two PDF sets. A 2-inch shift does not announce itself. When you are eyeing two prints, you find the things you expect to find. Moved walls. Added rooms. Deleted fixtures. You do not find a door that drifted two inches into a different wall type.

The failure was never laziness. The coordinator did the work. The problem is that PDF comparison asks a human to hold thousands of geometry relationships in their head at once, then notice the one that moved. That is not a reviewing task. It is a memory task, and memory loses. The cost lands later, in the field, as rework nobody planned and a schedule nobody padded. Found there, a clash like this costs $5,000 to $50,000.
The Cost Is Not in the Door. It Is in Everything the Door Touches.
People hear a door move and assume the door is the problem. It is not. The door is one element. The cost lives in the assemblies and disciplines the door drags along with it.
Start with the wall. A rated corridor partition is not the same build as a standard interior partition. Different studs. Different board. Different firestopping at the head. Move a door two inches and you can shift the entire wall segment into a different assembly type. Now the framing and drywall scope for that run has to be redone, not just the opening.

Then the hardware. Rated openings carry closer, latch and self-closing requirements that non-rated openings do not. Multiply that across a floor of patient rooms and the swing is real rework. A hardware set that was ordered to the old rating has to be reordered and reinstalled.

Then the sequence. The rated wall has to be inspected before it closes. That inspection has a date, and the date sits on the critical path. If the wall type changed after the schedule was set, the inspection gets squeezed. The drywall crew stacks up behind it. You are paying people to stand near a wall they cannot touch yet. That is the part that hurts most, because idle labor does not show up on any single line. An unresolved clash can burn $15K to $50K a week in idle field labor.
So when somebody says the move was small, they are measuring the wrong thing. The move was two inches. The blast radius was four trades, an inspection and a schedule. A markup never knew the door had a fire rating. The model does.
Why the Change Slipped Past Everyone Until the Field Found It
Here is the pattern that repeats on almost every job. The architect updates the model, or the design team pushes a revised set, and the update goes into a folder. Someone exports a PDF. Someone drops it in an email thread. The coordinator is already deep in another project, so the revised set sits until Friday, or until somebody remembers to compare it.

By the time the comparison happens, the answer is late. The trades may already be working to the old layout. The field may already be laying out from a print that is three revisions old. The model knew about the move the second it happened. The people did not, because nobody was reading the model against the last accepted version.

The usual defense is that documents are the source of truth. In practice, the model is the source of truth and the documents are a snapshot of it. When you compare snapshots, you are always a snapshot behind. The move happened in the model days or weeks earlier. Every hour between the move and the catch is an hour where the record is wrong and nobody knows it is wrong.
This is where people start looking for a free PDF compare tool, hoping it will close the gap. A free tool solves the visual problem and ignores the change problem. The change problem is the expensive one. A tool that overlays two prints still fails if it cannot tell you the door moved into a different wall type, because you will review the wrong picture and review it carefully.
The field is the worst place to learn about a change. It is the place where the cost has already been spent. Discovering the door in the field means you are not deciding anything anymore. You are explaining.
BidLight Diffs the Model, So the Change Is Seen When the Design Moves
BidLight keeps one live record of the project inside Revit and Navisworks. That is the whole idea. Not a PDF, not a spreadsheet somebody updates on Fridays, one record that lives where the design lives. When the door moves, the record moves with it.


You publish the model and every publish is a versioned snapshot with its own files, author and milestone. Any two revisions compare element by element, grouped by structural, MEP, envelope and interior. The door slides two inches, the wall it now sits in is listed as changed, and the change is on the screen while the architect is still in the file, not three weeks later in a subcontractor's phone call.
An issue pinned to the door carries the sheet and the revision it came from. You tag the wall trade, the hardware installer and the inspector, and the issue closes only with a screenshot, a tagged user and the model commit that fixed it. So the record is not a guess. It is the change, its owners and the proof.
This is the answer the question deserved. The coordinator should have been able to ask a simple question, what changed since the last accepted version, and get a straight answer in seconds. Then the conversation in the room becomes about whether to accept the move or push back, while the decision is still cheap. That is what model diffing gives you: the answer arrives before the work does.
The value is not the software. The value is that nobody on your team has to hold thousands of geometry relationships in their head to catch the one that moved. The diff holds them instead.


## What This Means for Your Schedule and Your Team
When your record tracks the model, you stop coordinating off stale scope. That changes two things that matter: the time you spend finding changes, and the rework you take on site. A comparison that took a 90-minute meeting can come together in about 15 minutes. That is not a productivity slogan. It is the difference between acting on Friday afternoon and telling the GC on Monday that you need more time.
You also stop losing 11 hours a week to working out which version is current. With the model as the source, the answer is in the snapshot list, with author and milestone beside each one.
The same record does something else: it makes your coordination visible. Advice backed by a model, a diff history and issues closed with proof is a service. Clients value answers they can act on. You already have the expertise. What you were missing was a defensible record of what changed and who acted.

On cost, plans run from Basics at $260 per licence per year to Max at $590, with custom Enterprise pricing and unlimited projects on every plan. Compare that to one door move that reaches the field and you can see where the math lands. And if software is not the gap, BidLight does done-for-you BIM work: execution plans, 4D sequencing, fabrication detailing and spooling.

The pitch stays plain. Stop chasing scattered updates. Close issues with proof. If you remember only one thing about BidLight, remember this: it keeps one live record of the project inside Revit and Navisworks, and every change is compared element by element. That is what makes the 2-inch move visible while it is still just a decision.