The 2% Rule: Why Small Changes Matter

A small tweak to a curtain wall detail looks like nothing. A few elements move, a mullion spacing shifts, and the revision goes out with a one-line note. Then a trade fabricates to the old geometry, and nobody notices until the panels show up on site. The model changed. Did the people who depend on it find out?

The 2% Rule is about paying attention to the changes that look small. It is not about watching every nut and bolt. It is about knowing which changes touch other work and catching them while they are still cheap. A clash caught in the model costs about $50. The same clash found in the field costs $5,000 to $50,000.

The rule works because model changes are rarely isolated. Move a wall, and the curtain wall adjusts. Adjust the curtain wall, and the mullion spacing changes. Change the mullion spacing, and the embeds, the anchors and the ceiling layout above it all have to follow. Each tweak is small. Together they add up to rework that nobody planned for.

The problem is that most teams discover these changes too late. They find out at the weekly coordination meeting, or worse, during construction. By then the trade has built to the old version, and the fix is a change order and an argument. The 2% Rule flips that. You see the shift when the export lands, you see exactly what it touches, and you walk into the meeting with a list of owners instead of a surprise.

How to Spot Model Changes Before They Spread

Spotting a change before it spreads is a real edge. You do not need a crystal ball. You need the right signals, and they are already in your project.

The first signal is the diff. Every export in BidLight is a versioned snapshot with its own files, author and milestone. Compare any two revisions and the changed elements show up one by one, grouped by category: structural, MEP, envelope, interior. A curtain wall edit that quietly moved forty elements is no longer a surprise buried in a file.

The second signal is the pattern. When the designer swaps standard glazing for something heavier, that is not just one change. It tells you what the team is heading toward: different support loads, different lead times, different reveals. The diff shows you which elements moved, so you can ask the right question before anyone builds.

The third signal is the issue history. Issues in BidLight are pinned to the elements they concern and carry the sheet and revision that raised them. When the same curtain wall zone keeps collecting issues across revisions, that is a coordination hot spot. You know where to put your attention first.

The key is to see these signals the same day the model changes. You cannot catch a drift if you only learn about it a week later. You need every publish versioned and compared, right inside Revit or Navisworks, so the answer to "what changed" takes about 15 minutes instead of a 90-minute meeting.

The Cost of Missing the 2%

Miss the small change and it travels. A trade drawing from the old revision keeps fabricating. A crew shows up to a wall that is not where the model says it is. Now you have an idle crew, an RFI, and a clash in the field that cost $5,000 to $50,000 instead of the $50 it would have cost in the model.

It gets worse when it sits. An unresolved clash can burn $15K to $50K a week in idle field labour. One that sat 47 days burned $28,000. None of that was caused by a big mistake. It started as a change that nobody flagged.

The cost is not just money. It is trust. When the GC hears about a model change from a foreman instead of from you, they question the whole process. They wonder what else slipped. In a coordination role, that costs you credibility, not just a fix.

The 2% Rule is about protecting your credibility. You want to be the coordinator who answers the question before anyone asks it. When the architect moves that curtain wall, you already know which trades it touches. You walk into the meeting with a clear message: "We saw the change, here is what it hits, here is who owns each item."

Turning Small Changes into Closed Issues

Seeing the change is half the job. The other half is making sure somebody acts on it. That is where issues come in.

Pin the issue to the element that changed. It carries the sheet and the revision that raised it, so nobody has to ask which drawing you meant. Assign it to an owner. The 6am digest puts it in front of that person every morning until it is dealt with, so you stop chasing by email.

Closing it is gated. The owner needs a screenshot, a tagged user and the model commit that fixed it. A closed issue means something, and the same problem does not come back on site. The median issue closes in 7 days, and the project view shows who is behind while there is still schedule to recover.

That is a different way to run a coordination week. You are not rebuilding the history from email threads and 47 versions of the same markup. You have one record, kept as the work happens.

The 2% Rule turns model drift from a reactive chore into a routine. You stop chasing scattered updates and start leading the conversation.