Missing pressure-equipment records do not automatically make an integrity assessment impossible. They do, however, change the work that must happen before an assessment can be trusted. A missing drawing, material certificate, calculation, repair record or operating history may affect the assumed equipment identity, geometry, material properties, loads, damage mechanisms or future service conditions.
The practical response is not to recreate a perfect historical dossier or fill every blank with a conservative value. It is to build a controlled integrity basis: a traceable package that states what is known, how it was verified, what remains uncertain and whether the intended inspection or engineering decision can proceed.
Key Takeaways
- Missing records should be ranked by their effect on the decision, not by the number of documents absent.
- Equipment identity must be locked before values from drawings, reports or calculations are reused.
- Field measurement can verify current geometry, while PMI and other tests may reduce material uncertainty; neither route automatically recreates the original design dossier.
- Targeted inspection should close a defined assessment gap rather than repeat every historical inspection activity.
- The final records-gap review should produce a clear decision: proceed, verify critical inputs, or pause the affected scope.
Why Missing Records Change the Assessment—not Only the Paperwork
A missing record can change the engineering input, not just the completeness of the archive. If the wrong drawing revision, material specification or operating condition is used, the assessment may describe a different component or service history from the equipment in the field.
Fitness-for-Service procedures evaluate the present integrity of damaged equipment and can support projected remaining-life decisions. They are used alongside relevant post-construction codes and depend on equipment-specific information. API 510, for example, is an in-service inspection, repair, alteration and rerating code for pressure vessels; it is not the same type of document as API 579-1/ASME FFS-1.
This distinction matters because no standard can correct an unidentified vessel, an undocumented nozzle change or an assumed material grade. The first engineering task is therefore to understand how each missing item could influence the intended decision.
Safety and Scope Note
The exact evidence required depends on the assessment method, applicable edition, jurisdiction, project specification and current equipment condition. No universal minimum record set, inspection coverage, material assumption or acceptance value should be applied without that context. The Pressure Equipment Directive 2014/68/EU covers the design, manufacture and conformity assessment of stationary pressure equipment; it should not be treated as a general in-service assessment method.
Start With the Decision, Not the Archive
The required evidence depends on the decision the team must support. An archive search should therefore begin with a short decision statement, not a request to collect every document ever produced for the asset.
The decision may be to confirm equipment identity, plan an inspection, evaluate a known flaw, rerate the vessel, define a repair, assess continued operation or establish a basis for future integrity management. Each question has a different critical-input set. For a detailed view of the data typically required for FFS, use NWE’s data-requirements guide; the purpose here is to decide what to do when those inputs are incomplete.
A useful decision statement identifies the equipment, current concern, required output, operating window, deadline and approval context. This prevents the team from spending weeks recovering low-value records while a decision-critical identity or geometry gap remains open.
Triage What Is Missing and Why It Matters
Not all missing records are equally critical. A superseded inspection summary may be recoverable later, while an unresolved tag, undocumented modification or unknown material can block or distort the affected assessment.
Classify each gap by the technical question it could change. The table below is a decision aid, not a code requirement or universal acceptance checklist.
| Gap class | Example | Potential decision impact | Typical treatment |
| Identity | Unreadable nameplate, duplicate tag or archive mismatch | Records may belong to another field item | Resolve through field identification, location hierarchy and archive cross-checks |
| Geometry / configuration | Old drawing, undocumented nozzle, lining or support | Stress, thickness or load basis may be wrong | Verify the current configuration and update controlled as-built records |
| Material / weld | Missing material certificate or weld history | Allowable basis, toughness or damage susceptibility may be uncertain | Recover records or define technically justified verification and limits |
| Design basis | Missing calculation, code edition or design conditions | MAWP, load combinations or efficiency assumptions may be unclear | Reconstruct from a controlled source hierarchy using verified inputs |
| Operating history | Missing excursions, transients or service changes | Damage mechanism or degradation rate may be underestimated | Use historian data, logs, incident review and MOC records |
| Condition evidence | Sparse, unlocated or inconsistent inspection data | Flaw size, extent or progression may not be reliable | Perform targeted inspection with repeatable location control |
| Repair / alteration | Undocumented repair, rerate or component replacement | Current configuration may not match the approved basis | Recover MOC/repair evidence and verify the field condition |
| Jurisdiction / approval | Original registration or authority path unclear | Acceptance route may remain uncertain | Seek competent jurisdiction-specific confirmation |
Each gap should receive a status such as verified, reconstructed with evidence, controlled limitation, assessment-limiting gap or not verified—do not use. A binary “document found / document missing” register is too weak for engineering decisions.
Rebuild Equipment Identity and Tag Hierarchy
Before technical values are reused, confirm that the field item and the records refer to the same equipment. Identity errors can survive for years when tags change, duplicate equipment exists, ownership changes or inspection systems use different naming conventions.
A practical identity lock may combine the current tag, serial number, manufacturer information, physical location, process service, connected nozzles or piping, photographs, P&ID references and archive cross-checks. The goal is not to invent a replacement nameplate or registration route. It is to document the evidence linking the physical asset to the controlled record set.
Where identity cannot be resolved, affected values should not be copied into an engineering model. The gap should remain assessment-limiting until the link between field item and record is reliable enough for the intended decision.
Verify As-Built Geometry and Configuration
An old drawing should not be assumed to represent the current asset when modifications, repairs or field deviations are possible. As-built verification can establish the geometry and configuration that exist today, but it does not by itself prove the original material, construction code, fabrication quality or hidden details.
The scope should be driven by the assessment question. Relevant items may include shell and head dimensions, nozzle size and orientation, attachments, supports, linings, internals, local repairs, reinforcement details and interfaces with connected systems. The required accuracy and coverage must come from the applicable engineering method and project context—not from a generic scanning tolerance.
NWE’s as-built preparation and validation service is the primary commercial route where drawings or models need to be created, updated or checked against field conditions. A separate NWE article covers deviation analysis and MOC in more detail; this article keeps geometry within the broader integrity-basis workflow.
Resolve Material and Weld Traceability Gaps
PMI can support alloy identification, but it does not automatically replace a missing material certificate. A chemical reading may narrow the alloy family while leaving mechanical properties, heat treatment, toughness, product form, weld consumables or allowable-stress basis unresolved.
The evidence route should match the property that matters to the decision. Archive recovery, material marking, PMI, hardness testing, replication, laboratory testing or engineering sensitivity analysis may be considered where technically justified. The method, competence, limitations and acceptance route are project-specific.
| Evidence route | What it may support | What it does not automatically prove |
| Original certificate / traceable record | Specified grade, heat or product information when correctly linked | That the record belongs to the current field item without identity traceability |
| PMI | Elemental composition or alloy-family identification within method limits | All mechanical properties, heat treatment, toughness or allowable stress |
| Hardness or supplementary testing | Selected property or condition information for a defined question | A complete material specification or fabrication history |
| Field geometry measurement | Current dimensions and configuration of accessible features | Original design assumptions, hidden features or material properties |
| Engineering calculation | Effect of verified or bounded inputs on the selected assessment | Truth of an unverified input or regulator acceptance |
Do not assign a familiar or “most conservative” material grade merely because the equipment was built in a certain period or facility. The assumption may alter the failure mode or hide another controlling uncertainty. Unknown materials require an explicit technical treatment and reviewer approval.
Reconstruct the Design and Operating Basis Carefully
A missing calculation or datasheet is not replaced by one value from a nameplate or historian. The reconstructed basis should separate original design information, current physical condition, actual operating history and intended future service.
Use a documented source hierarchy. Controlled drawings, manufacturer records, calculations, relief-device records, MOC files, inspection reports, historian trends, operator logs and incident records may contribute different parts of the basis. Conflicts should be recorded and resolved rather than silently averaged or selected.
Operating history deserves special attention because the current service may differ from the original design case. Changes in pressure, temperature, feed, contaminants, cycling, shutdown frequency or process chemistry can affect damage-mechanism selection and future degradation. Current relief settings or normal operating values should not be treated as proof of the complete original design basis.
Regulatory examples such as HSE plant-documentation guidance or US OSHA process-safety requirements show why design intent, materials, P&IDs and modifications matter. They are jurisdiction-specific examples, not a universal legal checklist for every NWE project.
Use Targeted Inspection to Reduce Critical Uncertainty
The answer is rarely to inspect everything again. Inspection should be designed to close the highest-impact uncertainty and produce evidence suitable for the intended engineering decision.
A targeted scope begins with a question: Is the geometry different from the drawing? Is the suspected damage local or widespread? Can a reading be tied to a repeatable location? Is an undocumented repair present? Does the available inspection cover the area that controls the assessment?
The inspection plan should define the asset, location, method, coverage, data format and traceability needed by the engineering reviewer. NWE’s in-service inspection service is a possible evidence-gathering route, while the resulting FFS or remaining-life calculation remains a separate engineering activity. Detailed inspection-data quality belongs in NWE-04.
Before a field campaign is commissioned, separate critical unknowns from records that can be recovered later. A short scope review can prevent unnecessary testing and focus access, NDT and dimensional work on the inputs that can change the decision.
Use Conservative Assumptions Transparently
The most conservative-looking value is not automatically the safest engineering choice. An assumption can move the controlling failure mode, make an assessment unrealistically restrictive or create false confidence by hiding the real uncertainty.
Each assumption should state its source, technical rationale, direction of conservatism, sensitivity to the result, owner and closure action. If the method does not permit the uncertainty to be bounded reliably, additional verification or a pause may be the correct outcome.
Conservative assumptions never convert an unknown into a verified fact. They are controlled analytical choices whose acceptability must be checked against the applicable method, edition, jurisdiction and project specification.
Build a Controlled Integrity Basis and Gap Register
The reconstructed deliverable should show what is known, how it was established and where the remaining uncertainty affects the decision. It is not a recreated original dossier and should not be presented as one.
A practical integrity-basis package can follow this eight-step ladder:
| Step | Control question | Output |
| 1. Define the decision | What inspection, assessment or operating decision must be supported? | Decision statement and scope boundary |
| 2. Lock identity | Is the field item reliably linked to the correct tag and records? | Verified identity or identity gap |
| 3. Lock configuration | What geometry and installed features exist now? | Controlled as-built configuration set |
| 4. Establish material basis | What material and weld information is verified, bounded or unresolved? | Material evidence status and limitations |
| 5. Reconstruct design and operation | What original, current and future conditions apply? | Design/operating basis with source hierarchy |
| 6. Establish condition evidence | Where is the damage, how extensive is it and how reliable are the data? | Assessment-ready inspection dataset or inspection gap |
| 7. Treat uncertainty | How could each unknown change the result? | Assumption register, sensitivity and closure actions |
| 8. Make the gate decision | Can the intended assessment proceed without hidden critical uncertainty? | Proceed, verify or pause decision |
The accompanying gap register should include the evidence source, revision or date, verification status, technical impact, responsible reviewer, required action and residual limitation. This allows future teams to understand the basis instead of repeating the same archive search or inheriting undocumented assumptions.
Decide Whether to Proceed, Verify or Pause
Assessment should proceed only when decision-critical inputs are verified or bounded in a technically accepted way. If a critical uncertainty can be closed through focused work, verify it. If the uncertainty could invalidate the affected assessment and cannot yet be controlled, pause that scope.
| Decision | When it applies | Required control |
| Proceed | Critical inputs are verified and the evidence is suitable for the intended method | Approve the controlled basis, input set and reviewers |
| Proceed with controlled limitations | An uncertainty remains but its decision impact is understood and accepted | Record the limitation, sensitivity, owner and closure trigger |
| Verify before proceeding | A focused archive search, as-built check or inspection can close a material gap | Define the question, method, deliverable and acceptance route |
| Pause the affected scope | Identity, material, geometry, load or condition uncertainty could invalidate the result | Do not use the unverified input; escalate the gap and define the next technical action |
| Seek external confirmation | Jurisdiction, registration or approval route is unclear | Consult the competent authority or responsible specialist for that context |
This gate decision should be visible to the Asset Owner and technical procurement team. A consultant’s calculation is not a substitute for a controlled decision on whether the inputs were suitable for the question being asked.
Define the Next Scope With NWE
Start with the equipment tag, available drawings or reports, current integrity concern and the decision you need to make. The archive does not need to be complete before the first discussion; the purpose of the initial review is to identify which gaps are decision-critical.
Depending on the result, the next technical scope may be records review, as-built preparation and validation, targeted in-service inspection, or a Fitness-for-Service assessment. These are connected activities, but they are not interchangeable.
NWE’s As-Built Preparation & Validation service is the primary route for configuration and documentation gaps. Where damage evidence or an operating decision already exists, the scope may also interface with In-Service Inspection or Fitness-for-Service engineering.
Frequently Asked Questions
Can a Fitness-for-Service assessment proceed without the original vessel drawings?
Sometimes. The critical geometry, material, loading and condition inputs must still be verified or bounded in a technically accepted way. The answer depends on the assessment method, applicable edition, jurisdiction and project specification.
Is field measurement enough to replace an as-built drawing?
Field measurement can verify current accessible geometry and configuration. It does not automatically prove original material, construction details, heat treatment, design assumptions or hidden features.
Can PMI replace a missing material certificate?
PMI can support alloy identification within the limits of the selected method. It does not automatically establish every mechanical property, heat-treatment condition, toughness value or allowable stress needed for assessment.
What should be checked first when pressure-equipment records are missing?
Start with equipment identity and the decision required. Do not reuse technical values until the field item is reliably linked to the correct records.
Should the most conservative material or design value always be assumed?
No. A conservative-looking assumption can change the controlling failure mode or hide another risk. It must be technically justified, sensitivity-checked and documented.
What records are most likely to block an assessment?
Identity, current geometry and configuration, material basis, design and operating loads, damage characterization and undocumented modifications are common decision-critical categories.
How should undocumented repairs or alterations be handled?
Treat them as configuration and design-basis gaps. Field verification, archive recovery, MOC review and competent engineering assessment may be required before the affected scope proceeds.
What should a records-gap review deliver?
A controlled evidence register showing sources, verification status, critical gaps, required field work, assumptions, limitations, responsible reviewers and a proceed, verify or pause decision.
