The Monday Morning Audit: Which Model Version Did Friday's Package Use?

The version gap you only see on Monday

Friday the package goes out. Monday you find out it was built from v4 and the model was already at v6. Nobody lied, nobody slacked. The architect sent a revision at 4:40 on Thursday, a PM renamed the file to keep both versions, and the coordinator reviewed the folder he had open. By Monday standup, two full rounds of design change were missing from a set of decisions the whole team is already treating as real.

This is the quiet failure mode on almost every job. The problem was not bad judgment or slow subs. The document the team worked from stopped being the document everyone else was working in. There is no alarm. The RVT file keeps moving and your notes stay frozen at whatever moment someone hit save.

Run the audit yourself. Pull last Friday's issue list and review set. Ask which model version it came from, then ask which version the architect issued latest. If those two answers differ, you are not looking at a discipline problem. You are looking at a plumbing problem. Model changes live in one place and the issues that depend on them live in another.

By the time you find the gap on Monday, the damage is done in two places. Issues were closed against geometry that has since moved, and if the work reaches the field you have bought rework on day one. The model was at v6, the scope grew, and the record never did.

A day of coordinator time also disappears into re-checking. Somebody has to open both versions, compare them, decide which issues are still valid, and rebuild the backup. That is a full day of skilled work spent proving that Friday's answer was built on Thursday's question. Teams lose about 11 hours a week to exactly this: working out which model version is current.

What project coordination software should actually do

Strip the category label away. Coordination software is the system that keeps one authoritative record of a project tied to the model it came from. When someone asks what it is, the honest answer is that it is the place where versions, issues, owners and change history stay bound together, so a decision can be defended a week later. Most tools in the space stop at the issue list, the meeting agenda and the status report.

The part that matters on a job is the record riding on the geometry. BidLight keeps one live record of the project inside Revit and Navisworks. You publish from the model and every publish becomes a versioned snapshot with its own files, author and milestone. Nobody rekeys a spreadsheet, because the spreadsheet is no longer the source of truth. The model is.

Any two revisions compare element by element, grouped by category: structural, MEP, envelope, interior. You do not read a drawing set side by side and hope your eyes catch the moved duct. You read a list of what changed, and each item points at the element.

Speed is the visible win. Finding what changed between two exports takes about 15 minutes instead of a 90-minute meeting. On the programme where this was run at scale, the case study shows 18,000+ hours saved and 8,900+ issues resolved. The cost control follows from that: a clash caught in the model costs about $50, and the same clash found in the field costs $5,000 to $50,000.

That is the difference between a tool that tracks paperwork and a tool that owns the record. One keeps a list of tasks. The other tells you the task is already out of date.

Why Friday packages go stale before the ink dries

You have probably chased updates the slow way. Someone exports a sheet set, drops the markups into a shared folder, and tags every note with the drawing revision it came from. That tagging is where the system breaks. The tag is accurate for about six hours.

Friday afternoon in an AEC office is a race. The architect issues a revision, the owner's rep sends a comment, a PM asks for an alternate, and the deadline is still running. People do what they have to do to get the package out. They grab the version they can find, note it in a comment, and promise themselves they will reconcile on Monday. Then Monday arrives with a new revision and the reconciliation never happens.

Meanwhile the model keeps accumulating changes. A duct reroute here, a ceiling height shift there, six doors added at the corridor. None of it is dramatic. All of it is scope that someone has to coordinate. A review done on v4 carries the geometry of v4, and the gap between v4 and v6 is pure exposure sitting inside a package your client thinks is final.

The uncomfortable truth is that most firms find version drift through pain rather than process. You catch it when a field crew finishes a wall that moved, or when a sub's shop drawing does not match your backup, or when a clash shows up on site and nobody can explain why it was never flagged. By then the audit is forensic, not preventive. A clash that sits 47 days can burn $28,000 in idle field labour.

One live record flips that. If every publish is a snapshot, the diff is automatic. You are not auditing a folder on Monday, you are reading what changed and telling each owner what it touches.

What a Monday audit looks like when the record is live

Imagine opening Monday with Friday's package already reconciled to the current model. Not because anyone worked the weekend, but because the record never detached from the geometry in the first place. That is the operating picture BidLight is built for, and it changes the shape of the week.

Here is the practical version. Friday you publish from Revit, the snapshot is stored with its author and milestone, and the open issues stay pinned to the elements they concern. Saturday the architect pushes v6. Monday you compare the two revisions and see a short list of what moved: three door families added, a ceiling grid relocation, one equipment layout revision. Each item is a delta on a named element, not a mystery.

The audit turns into three questions. What changed since Friday, which issues does it affect, and who needs to hear it. You know exactly how much risk you are carrying into the next coordination call, which is a very different conversation than hoping nothing moved. For issues that were already closed, you can see whether the fix still holds against the new geometry, before a crew finds out the hard way.

This is also where the 6am digest earns its place. Monday morning every owner already has the list of issues assigned to them, including the ones the weekend revision reopened. Nobody needs a Monday email chain to find out who has to act.

Auditability is the quiet benefit. Every issue traces to a model version, every closure traces to a commit, and every revision is dated. When a client asks why the plan changed, you show them the diff instead of defending your memory.

What to put in place before next Friday

Start with the version question. Before any package leaves the office, everyone involved should be able to name the model revision it was reviewed against, and that name should be automatic, not a cell comment someone types at 5pm. If it is manual, it will drop.

Next, stop letting issues live in a separate file from geometry. Every export that lands in a workbook or a markup creates a second truth, and second truths drift. The pattern is consistent across jobs: firms lose more money on coordination and rework than on any single bad decision. The fix is structural, not motivational.

Pin every issue to the element and the sheet and revision that raised it. Then closing it requires proof: a screenshot, a tagged user and the model commit that fixed it. That matters most on the issues nobody questions until the crew is on site, which is exactly where schedule and money quietly disappear.

Decide who owns the Monday read. It should be a 15-minute habit, not a two-hour excavation. If the record is live, the audit is a short list of deltas. If it is not, you are rebuilding the story from email attachments. That is how a coordinated model becomes an uncoordinated job.

Finally, watch who is behind while there is still time to recover. The project view shows every issue against its owner, so you can move work before a slip becomes a change order.

The issue list and the model should never separate

BidLight does two things. It keeps one live record of the project inside Revit and Navisworks, and it holds every issue against the element it concerns, closed only with proof. Every export is versioned and compared element by element. Plans run from Basics at $260 per licence per year to Max at $590, with a custom Enterprise plan for larger teams, and every plan includes unlimited projects.

Beyond the software, the team does done-for-you BIM work. Execution plans, 4D sequencing, fabrication detailing and spooling. If you want the tool but not the bandwidth to stand it up, that path exists.

If you remember one thing from this, remember the audit. You send Friday, you find out Monday, and the gap between v4 and v6 has a cost. The only way to close that gap is to stop keeping the record in one place and the model in another.

Run one project through the live record and check the Monday read yourself. The value is not in the software tour. It is in opening the week knowing exactly what your plan covers and what it does not.