The Specification Drift

Before a single contractor sets foot on the pier, before the dry dock floods, before the first cable is pulled or the first panel is mounted, the availability has already been compromised.

It was compromised the moment someone opened a work specification from a previous availability, changed the hull number, updated a few line items, and sent it out for bid.

This is Specification Drift: the accumulated degradation of work documentation that occurs when copy-paste replaces deliberate review, and when lessons learned from previous availabilities never make it back into the source material. The specification that arrives at the yard is not a current, accurate description of the work required on this hull. It is a historical document dressed as a technical requirement, carrying forward the errors, the outdated assumptions, and the unresolved ambiguities of every availability that used the same template before it.

The cruiser modernization program produced 9,000 contract changes.¹ That number is not a project management failure. It is the arithmetic of Specification Drift applied across seven hulls over fifteen years.

How the Drift Accumulates

A work specification is written once, with care, for a specific condition on a specific vessel. It gets used. The work gets done. Some of it goes well. Some of it surfaces problems the spec did not anticipate. The problems get resolved through condition found reports, change orders, and field engineering decisions, none of which feed back into the original specification.

The next availability opens. Someone pulls the previous work package. They update the easy fields. Hull number, dates, contract references. The technical content, the actual description of what is required, how it is to be accomplished, and what the acceptance criteria are, stays largely intact. The errors stay with it. The outdated references stay with it. The compartment descriptions that apply to a different class of ship stay with it.

Robert du Mont, a former nuclear surface warfare officer with direct experience in this environment, described it precisely in a comment on this series. Too often new work specs are copied and pasted from previous specs without improvement using lessons learned from previous overhauls or modification to meet different requirements. Even the most basic review of the work specification by a knowledgeable person prior to putting it out for bid would have caught some of the egregious errors.

The GAO found exactly this pattern in the cruiser modernization effort. Poor planning produced 9,000 contract changes across seven hulls, and the Navy had not codified root cause mitigation strategies for the unplanned work problem.¹

What the Drift Produces Inside the Hull

MIL-STD-2003 governs electrical installation requirements for surface ships. NAVSEA Standard Item 009-73 governs cable work qualification and documentation requirements. Neither standard can be applied accurately to a work package written from a previous availability's template without someone physically checking that the current hull's electrical infrastructure matches what the spec assumes it to be.

Twenty-year-old Arleigh Burke-class destroyers have been modified repeatedly since commissioning. Cable routes that the spec assumes are clear have been compromised by subsequent installations. Penetration locations that the spec references may have been sealed and rerouted. Grounding connections that the spec treats as established baselines may have been altered by a previous modernization contractor operating under a separate contract, exactly the dynamic this series documented in The Segregation Tax and The Modernization Seam.

A spec written without a hull-specific inspection is a spec written for a theoretical vessel. The actual vessel will disagree with it, and the disagreement will arrive as a condition found report, and the condition found report will become a change order, and the change order will become a schedule overrun.

What the Drift Costs

Every change order generated by Specification Drift is priced at the point of maximum leverage for the contractor. The ship is in the dry dock. The undocking date is fixed. The scope growth is urgent. The government is negotiating from a position of compressed time and constrained alternatives. The GAO documented that the Navy must negotiate the price of growth work under significant schedule pressure, and that speed matters more than getting the best price when the ship is already in the dock.¹

A specification that is 85 percent accurate produces 15 percent growth work. A specification that is 70 percent accurate produces 30 percent growth work. A specification that is 50 percent accurate produces the cruiser program, where 9,000 contract changes drove $1.84 billion in wasted investment on four hulls that were divested before they could deploy.

The cost of fixing a specification error during planning is the cost of one qualified reviewer walking the hull. The cost of fixing that same error during execution is the cost of stopping work, negotiating the change, waiting for parts, and correcting the error in a schedule that did not budget for it. The ratio is not linear. It is exponential. And the exponent compounds every availability the uncorrected specification is used.

The Fix Is Pre-Bid Inspection and Living Documentation

The Specification Drift problem has two structural solutions, both of which are known and neither of which is consistently implemented.

The first is mandatory pre-bid inspection by technically qualified personnel before the work package is finalized. Not a review of the previous spec. A physical walk of the actual hull, with someone who understands MIL-STD-1399 interface requirements and MIL-STD-1310G bonding standards, comparing the vessel's actual condition to the draft specification's assumptions. The discrepancies found in that walk are the change orders that will otherwise be written during the availability, at a fraction of the cost and with none of the schedule pressure.

The second is living documentation. A specification that is updated after every availability with the lessons learned, the conditions found, and the modifications made. Not filed in a project closeout report that nobody reads. Updated in the source document that becomes the basis for the next work package. The specification should get more accurate with every availability, not stay equally wrong for fifteen years.

The Navy has yet to codify root cause mitigation strategies for the unplanned work problem the GAO documented in the cruiser program.¹ The root cause is Specification Drift. The mitigation is not a new project management software tool or an additional oversight layer. It is a qualified person reading the spec against the actual hull before the contract is signed.

NAVSEA contracting officers and specification writers: when did someone last walk the hull before finalizing the work package? If the answer is nobody, you already know where the 9,000 contract changes came from.