The Half Life of Project Information: When Yesterday's Data Becomes Today's Risk

A project can fail with the correct document in hand.

The drawing may be approved. The cost estimate may sit in the right folder. The vendor quote may carry a valid reference number. The survey may have passed every document control gate. Yet the information inside may no longer describe the project the team is building now.

That is the quiet problem behind many cost overruns, procurement delays, field clashes, safety exposures, and late-stage redesigns. Project information ages. It usually doesn't become wrong in a single event. It loses reliability as assumptions shift, interfaces move, markets change, permits evolve, vendors revise lead times, and site conditions reveal more than early studies could know.

This is the idea of an information half-life in project management. Information that was once good can decay in value over time, even when no one has formally superseded it. The risk is highest in complex capital projects where long timeframes, multiple contractors, technical uncertainty, global supply chains, and regulatory approvals all move at different speeds.

Oil and gas, EPC, construction, energy, infrastructure, mining, utilities, and marine projects all depend on a chain of evidence. If one link in that chain has aged beyond its useful life, decisions built on it can become fragile.

Project Information Decays Long Before It Looks Obsolete

“Out of date” is easy to recognize when a document has been replaced by a newer revision. Information decay is harder. It starts while the document still looks current.

A geotechnical report may remain the latest approved version, but the facility's footprint has shifted. A constructability review may still sit in the project record, but the construction sequence has changed because module deliveries moved. A vendor quotation may still be within its formal validity period, but the supplier’s factory slots have been taken by other customers. A risk register may show the latest revision, but it may not reflect a new interface with a utility corridor, port restriction, or third-party crossing.

The information has not vanished. It has lost fitness for use.

The half-life analogy helps because information rarely expires at the same rate. Some data may remain valid for years. Other data can weaken in weeks.

A concrete design code reference may stay stable across a project phase. A shipping route assumption during a period of port congestion may decay quickly. A topo survey in an undeveloped site may remain useful until major earthworks begin. A stakeholder assumption about local approvals may weaken the moment a new authority, landowner, operator, or community interest enters the project.

Information age matters, but age alone is not the main issue. The main issue is whether the conditions that made the information valid still exist.

Several forces drive project information decay.

Time

The longer the gap between study and decision, the greater the chance that something material has changed. Long-cycle projects often carry concept-phase assumptions into FEED, engineering, procurement, and construction because they are familiar, not because they have been retested.

Change in scope

A small design movement can invalidate large parts of earlier work. A minor relocation of equipment can affect underground services, access, lifting studies, hazardous area classification, firewater coverage, and maintenance clearances.

Market movement

Steel prices, cable availability, module yard capacity, vessel rates, specialist labor, and long-lead equipment can shift within a project cycle. A cost estimate or procurement plan based on old market soundings can create false confidence.

Interface movement

Interfaces decay faster than standalone data because they depend on more than one party. Tie-ins, battery limits, utility connections, marine berths, brownfield shutdown windows, and third-party permits can change outside the project team's direct control.

Technical learning

Projects learn as they progress. Soil data improves. Process loads become clearer. Vendor data replaces preliminary datasheets. Operating philosophies mature. Each new piece of knowledge can undermine earlier assumptions.

Stakeholder movement

Authorities, operators, neighbors, lenders, insurers, and local communities may change expectations. A consultation outcome from early concept may not hold after land use changes, environmental findings, or updates to national requirements.

A mature project team does not ask only, “Do we have the latest version?” It asks, “Is this information still valid for the decision we are about to make?”

Different Information Types Age At Different Speeds

Not all project information decays at the same rate. Experienced teams often know this intuitively, but they may not manage it explicitly.

The table below gives a practical way to think about common information types and how they lose reliability.

Information type	How decay usually appears	Typical consequence
Surveys and site investigations	Site access changes, additional excavation, new utilities, seasonal effects, limited early sampling	Rework, foundation redesign, claims, unsafe excavation assumptions
Cost estimates	Scope growth, market movement, productivity changes, exchange rate shifts, escalation gaps	Budget shortfall, approval delay, weakened business case
Vendor quotations	Expired validity, changed capacity, updated technical requirements, altered delivery terms	Procurement delays, price growth, non-compliant equipment selection
Technical studies	New loads, new regulations, changed layouts, updated operating cases	Wrong design basis, late redesign, performance shortfall
Schedules	Productivity assumptions age, access windows change, supplier dates slip, approvals move	Unrealistic milestones, poor sequencing, late recovery plans
Risk assessments	Risks close without evidence, new interfaces missed, controls assumed but not implemented	False sense of control, unmanaged exposure
Stakeholder assumptions	Authority expectations change, land access shifts, owner priorities alter	Permit delays, redesign, reputational damage
Logistics plans	Port rules, road restrictions, laydown areas, transport permits, route condition changes	Delivery delays, demurrage, lifting and handling risk
Constructability reviews	Construction method changes, contractor input arrives late, temporary works evolve	Field clashes, unsafe workarounds, low productivity
Operational data	Actual operating patterns differ from design assumptions, maintenance history changes	Poor handover, reliability issues, start-up instability

This does not mean every document needs constant review. That would bury the project in administration. It means high-impact information needs a validity logic. Each critical data set should have an owner, a review trigger, a known assumption set, and a clear use boundary.

A vendor quote for a standard valve may need only commercial refresh before award. A compressor package quotation tied to power availability, plot space, cooling duty, noise limits, and factory acceptance testing windows needs far more attention. A marine survey for a nearshore pipeline route may serve one decision but not another if dredging, seabed movement, or new navigation constraints arise.

The question is not whether the information is old. The question is whether it is being used beyond its evidence base.

Decay Follows The Project Lifecycle

Information decay looks different at each phase. The pattern is usually cumulative. Early assumptions become embedded, then each phase adds detail, pressure, and contractual commitment.

Concept Phase Creates The First Generation Of Assumptions

Concept studies often work with limited data by design. The aim is to test options, screen feasibility, compare locations, and frame the business case. This phase openly carries uncertainty, at least in theory.

The difficulty comes later, when concept assumptions gain authority because they appear in approved papers. A screening estimate becomes the number people remember. A preferred plot plan becomes the base for stakeholder messaging. A production profile, throughput case, or demand forecast becomes the anchor for design choices.

Concept information decays when the project changes from “Should we do this?” to “How exactly will we do this?” The questions become more precise, but the source data may still be broad. If no one marks the boundary, early information quietly becomes overused.