Home / Features / Modification tracking
Modification trackingEvery modification
keeps its own record
MOD 01 and MOD 02 are separate pieces of work with separate paperwork and separate money. Folding them into the parent is how teams lose track of which document supports which change.
Why one percentage tells you nothing
A subcontract showing 42 percent complete sounds informative. It is not, because two very different situations produce the same figure.
How modifications are usually handled
Most contractors track modifications somewhere. The question is whether that somewhere is connected to the award record.
A separate spreadsheet
Modifications listed in their own file, maintained by whoever remembers, with no link to the documents that support each one.
On the award record itself
Each modification lives on the award it changes, carrying its own amounts, documents, progress and activity.
One number, usually the award
Award and funded amounts get recorded as a single figure, which works until incremental funding means the two differ and nobody can say by how much.
Two figures, held separately
Award and funded amounts are tracked as distinct numbers per modification, so the gap under incremental funding is visible rather than found during a review.
Everything in the parent folder
Documents for all modifications sit together, so working out which change a particular file supports means opening it and inferring.
Filed against the change
Evidence attaches to the modification it supports, and the parent record links through to each one.
Harder every year
After the third or fourth modification the record becomes something only the original buyer can navigate confidently.
The same at any number
Each modification reads identically whether it is the first or the eighth, so the record does not degrade as a program runs.
Three outcomes that follow from separation
Three outcomes that follow from separation
The question that arrives is which change a document supports. When evidence is filed against the modification, that is a lookup rather than an exercise in reading and deducing.
- Retrieval stops being inference
- Funding gaps stay visible
- Long programs stay legible
Retrieval stops being inference
The question that arrives is which change a document supports. When evidence is filed against the modification, that is a lookup rather than an exercise in reading and deducing.
Funding gaps stay visible
Incremental funding is normal in government contracting and rarely tracked well. Holding award and funded amounts separately makes the difference something you can see.
Long programs stay legible
A record that gets harder to read with each modification eventually depends on one person. One that reads the same at any number does not.
Four moments teams describe
Four moments teams describe when separation matters.
Funding changes, document packs and review questions hit modifications hard. Keeping each one distinct is what stops the parent record from lying.
- When funding changes mid-award
- When a review asks about one modification only
- When progress on MOD 02 must not hide MOD 01
A modification arrives in year three
Recorded with its own amounts and evidence rather than appended to a record that is already hard to read.
Learn moreSomebody asks what supports a change
Answered from the modification the document was filed against, without opening anything to infer it.
Learn moreA review looks at one modification
The reviewer sees that change and its evidence rather than the whole award history.
Learn moreThe buyer moves on
The next person reads MOD 04 the same way they read MOD 01, because both were recorded identically.
Learn moreMoney and evidence, in that order
Almost every modification problem we see is one of these. Click through both.
Award and funded amounts get recorded as one figure, which works until incremental funding means the two differ and nobody can say by how much or since when.
- Award amount and funded amount held as distinct numbers
- The gap visible on the modification rather than inferred
- Recorded as funding arrives rather than reconciled later
- No surprise at the point remaining funding becomes urgent
Documents for every modification sit in one place, so working out which change a particular file supports means opening it and deducing from the contents.
- Evidence attached to the modification it supports
- The parent award links through to each one
- Activity logged per modification rather than per award
- Which change a document belongs to is explicit
Six fields that let it stand alone
Award amount
What was agreed for this change, held separately from the parent award.
Funded amount
What money is actually behind it, which under incremental funding is frequently less.
Its own progress
Completion measured against this modification rather than blended upward.
Its own documents
Evidence filed against the change it supports rather than the parent.
Its own reviewer
Sign off assigned per modification where the phases call for it.
Its own activity
A timeline showing what changed on this modification and when.
Questions about modification tracking
Why not just track the total?
What is the difference between award and funded amounts?
Where do documents for a modification live?
Is there a limit on how many modifications an award can carry?
Can a modification have its own reviewer?
How does progress work across modifications?
What happens to a modification once the award closes?
Other parts of the same workspace
Bring a subcontract with modifications
Ideally one where the paperwork is spread across folders and nobody is certain which change a document supports.
Book a demo