API SIFE common mistakes
API SIFE · Understand the traps and how to avoid them.
Building the inspection and surveillance plan by copying the previous project's plan and deleting line items that no longer seem to apply, without recording any risk basis for what was kept or removed.
Under bid and mobilisation deadlines the plan is treated as an administrative deliverable rather than a risk document, so the nearest prior plan becomes the fastest template and nobody challenges the deletions.
What to do instead
Start from the purchase order scope, equipment criticality, fluid/service, vendor history and any open nonconformances; give each surveillance activity a written risk justification, keep it in the plan, and require a documented engineering review before the plan is issued.
Arriving at the shop only after a hold point has already been cleared, or accepting a verbal or emailed description of the activity in place of the notification the specification requires.
Travel and review schedules follow the vendor's production calendar, inspectors assume the shop will call them, and notification obligations are rarely tracked as a formal log with dates.
What to do instead
Maintain a hold and witness point log stating the required notice period and the responsible contact for each point; confirm each notification in writing before travelling, and treat a bypassed or unnoticed hold point as a nonconformance requiring documented disposition.
Accepting mill certificates as proof of material conformance without matching heat numbers to the physical marking, to the purchase order grade and specification, and to the product form actually delivered.
Certificates arrive as a thick, complete-looking package and commercial pressure pushes toward filing them, while heat numbers are small, often in awkward locations or covered by coating.
What to do instead
Do a three-way match of purchase order, mill certificate and physical heat marking; confirm grade, specification, product form and any impact or hardness requirements; record the result, and specify product analysis or PMI where the material specification or service demands it.
Approving a welding procedure after checking only that a supporting procedure qualification record exists, without comparing position, thickness range, backing, preheat, post-weld heat treatment condition and filler classification against the actual production joint.
The reviewer sees a qualified procedure and an attached test record and assumes the coverage question is answered, not recognising that qualification is bounded by ranges rather than by the process name alone.
What to do instead
Use a variable-by-variable comparison sheet covering essential and supplementary essential variables against the production joint, and confirm the welder's qualification range (process, position, thickness, backing) covers the same joint before welding starts.
Accepting a non-destructive examination report without confirming that the method, technique, examination extent, acceptance level and code edition actually used match the governing specification, such as accepting a radiograph where volumetric examination by ultrasonics was specified.
Reports look official and the terminology overlaps across standards; a reviewer recognises the method name but not the acceptance class, technique limitations or the edition cited in the header.
What to do instead
List the required method, extent, technique, acceptance criteria and code edition in the surveillance plan, then verify each against the report header, the technician's certification scope and the equipment identification before accepting the result.
Witnessing a hydrostatic or pneumatic test and signing the record without first checking gauge calibration status, gauge range relative to the intended test pressure, the number and location of gauges, the test medium temperature and the specified hold time.
The test is treated as a single pass-or-fail event at the end of the job, the crew has already rigged the equipment, and the paperwork is completed in one sitting after the pressure is released.
What to do instead
Use a written pre-test checklist and verify it before pressurisation: current calibration records, gauge range and readability against the target pressure, gauge quantity and location, test medium and metal temperature against minimum design metal temperature, air venting, and a recorded hold time.
Verifying shell and head welds but leaving internals and assembly geometry unchecked, including tube-to-tubesheet expansion or seal welds, baffle spacing and orientation, impingement protection, nozzle orientation and elevation, and bolted joint assembly.
Attention gravitates to the pressure-boundary welds that carry the most visible code requirements, while internals are seen as vendor detail and are often covered up or boxed in by the time the inspector returns.
What to do instead
Build a dimensional and internals checklist directly from the drawings and datasheet, schedule its verification before internals are closed in or the bundle is inserted, and record measurements rather than a simple pass mark.
Releasing a vessel, heat exchanger or valve after matching only the tag number, without comparing the nameplate or data report against the datasheet, including design pressure and temperature, material, minimum design metal temperature, and for valves the set pressure, trim, seat, end connections and flow coefficient.
Tag matching feels like a complete identity check, the nameplate is small and often repainted, and valve internals are treated as a procurement detail rather than a release condition.
What to do instead
Compare nameplate and data report field by field against the approved datasheet, verify valve set pressure and trim against the tag sheet, and record any deviation as a nonconformance rather than a note on the release document.
Issuing the release certificate while nonconformances remain open or while the manufacturing record book still lacks mill certificates, heat treatment charts, examination reports or final dimensional records, on the promise that the missing items will follow.
Shipping windows and liquidated damages create pressure to release, and missing documents are scattered across departments so nobody sees the full gap at the moment of signature.
What to do instead
Maintain a documentation completeness matrix by equipment tag, require every cell to be closed or formally deferred with an approved concession, and confirm the nonconformance log is closed before the release certificate is signed.
Reviewing fabrication against a remembered or superseded edition of a code, or against a different standard family than the contract invokes, because the reference was carried over from earlier work.
Code editions and project specifications change between jobs, and inspectors rely on habit and experience rather than re-reading the contract's cited edition, addenda and any project amendments.
What to do instead
Confirm the governing code, edition, addenda and contract-specified standards at kickoff, print them on the surveillance plan and on every checklist header, and verify at each document review that the reference cited by the vendor matches that baseline.