On Track 6 – Version Control

On Track
Issue 6  ·  August 2026  ·  IPM Team
Which version are you actually working from?
Why version control matters just as much on consultant service contracts as it does on construction — and what happens when the wrong version slips through.

On a compact program, documents are not just paperwork. They are the evidence behind claims, variations, payments, and decisions. And the risk is the same whether the contract is for construction works or for consultant services: when people act on the wrong version of a document, the cost shows up later — in rework, disputes, and delay. Good document management is not about filing more neatly. It is about knowing, at any moment, which version is current and who can reach it. This issue looks at why version control matters across every contract on your program.

Why It Matters
Version Control
The same risk, on both sides of the program.

Document control is often seen as a construction concern, and on a works contract the stakes are clear. Build from a superseded drawing, or price a variation against the wrong specification, and the error is expensive to unwind. But the same risk runs through every consultant service contract. Reports, terms of reference, and design deliverables move through rounds of review, and the question “which version was approved?” decides what gets paid and what the next stage is built on. On both sides, the failure looks the same: someone acts on information that has already been superseded — and no one notices until the consequences appear.


Tool in Focus
Document Management in the PPMM: Version Control at the Core

The Practical Project Management Methodology (PPMM) treats document management as a live system that connects the people producing information to the people acting on it. At its core is version control — the discipline of knowing which document is current, and which ones have been replaced. Without it, even carefully recorded information cannot be trusted.

This applies equally to construction contracts and consultant service contracts. Drawings, specifications, and variations need the same control as reports, deliverables, and review comments. The PPMM helps MCA teams set up a system that is proportional to the program — clear naming, controlled revisions, and defined access — so the version you open is the version you can act on.

Three things to get right on version control
1
Mark every revision — and retire the old ones. A clear status of current versus superseded is the single most important control. If two versions can both look final, neither one is.
2
Apply the same discipline to services, not just works. A consultant deliverable goes through as many revisions as a drawing set. Track which version was submitted, reviewed, and formally accepted.
3
Tie the version to the decision. Payments, approvals, and instructions should point to one identifiable version — so everyone can see exactly what was agreed, and on what basis.
Coming next month  ·  September 2026
Good project management, recognized. The IPM recognition program for teams putting a methodology to work — and delivering because of it — launches next month. If that sounds like your team, watch this space.
Read the full PPMM — and put it to work.

The PPMM covers document management and nine other project management areas designed for MCC programs. Download it and see what your team could be doing differently — or reach out to IPM to talk through how to apply it to your program.

Download the PPMM →
Questions or ideas for a future issue? Contact the IPM Team:
tkachm@mcc.gov
Next issue: Scope & Earned Value — early warning signals your decision makers can trust.

Leave a Reply

Discover more from IPM

Subscribe now to keep reading and get access to the full archive.

Continue reading