It passed inspection. Why did it fail in the field?
In early 2024, a maintenance supervisor called me from an offshore platform in Norway. A wellhead component had just arrived with a certificate of conformance, a pressure test record, and a clean inspection report. It still would not mate with the equipment already in the wellhead stack. He asked how Baker Hughes could release something like that.
I work in quality assurance at Baker Hughes in Tomball, TX. My job is to review equipment before it goes to the field—not just the hardware, but the documentation that says what it should be. When that supervisor called, I didn't start with a defense. I asked to see the purchase order. After the second paragraph, I knew where the problem had started.
The part, honestly, was fine. The specification was not.
A vague specification is the only quality defect that ships before the part gets made.
The surface problem: “Certified” does not mean “Correct”
If you've worked in oilfield procurement, you've seen this pattern. The crate arrives with an Inspection and Test Plan, material certificates, and a signed release from the factory. Then the crew opens the crate and finds the thread form is wrong, the trim is wrong for the service, or the pressure rating is a class lower than the completion plan requires.
The manufacturer says it built exactly what the PO described. The site team says it is not what the job requires. Both are telling the truth.
That is not because the supplier is incompetent. It happens because “certified” means certified against a written requirement. If the written requirement is too thin, the certificate is thin too.
The deeper problem: what I call a white contract
I keep a category for this failure mode. I call it a white contract. It's not a legal term; it's a description. The purchase order is filled with words, but the meaning is hiding in the white space. Every supplier fills that white space differently.
Take a line like this: “Valve, gate, 5 1/8 in, 5,000 psi, API 6A.” That looks exact. But API 6A is a family, not a single specification. It includes multiple material classes, temperature classes, product specification levels, and performance requirements. Two different API 6A valves can be excellent products and still not be interchangeable. The phrase describes the general category, not the exact requirement.
The same thing happens with “stainless steel,” “sour service,” “as per drawing,” or “same as previous order.” They are placeholders for decisions that haven't been written down.
I learned never to assume “same as previous order” means the same result. In 2023, I caught a repeat part where the supplier had moved from an obsolete coating specification to a newer one. The new coating met the material standard. It did not meet the original field performance requirement. Nobody was cutting corners; they were working from a contract that had been too vague for years.
There is also the gap between words that sound the same. I said “material traceability.” The supplier heard “certificate package.” Those are not the same. Traceability follows a heat number through fabrication and into the final assembly. A certificate package can be a neatly collected folder without a clear chain. That mismatch usually appears after a problem, when someone tries to trace the actual heat.
What a white contract costs you
A white contract rarely shows its price at order time. It shows up when the equipment is at the platform, the schedule is tight, and someone has to make a decision with incomplete information.
I remember a batch of gate valves in 2023. The contract said “API 6A” and did not say the trim class or temperature rating. The valves met the PO. The completion plan needed different trim. Engineering caught it before the valves went to the field, but the corrective work cost six weeks. The supplier redid the order at their own cost, because the ambiguity was not theirs to interpret.
If the mistake had reached the wellsite, the six-week delay would not have been the expensive part. The interruption would have been. A waiting rig costs far more per hour than the components sitting next to it. A small specification gap can easily cost more than the entire valve.
The surprise, honestly, was not the rejection. It was how easy the fix was once the missing requirements were written down. A few sentences changed the trim class, the temperature class, and the product specification level. The supplier knew exactly what to build. The interpretation was gone.
The fix is not a bigger inspection department
The fix is a contract that reads like a technical document, not a shopping list. That doesn't mean every purchase order needs a binder full of QA instructions. It means the white space needs to be closed before the order is released.
- Name the exact product and revision. “Baker Hughes gate valve” is a starting point, not a specification. Add the product datasheet revision, the drawing, or the manufacturer-specific code.
- Write acceptance criteria into the PO. Include the standard and the limit: API 6A plus PSL, material class, temperature class, trim, and test pressure. If you are accepting “vendor standard,” say which standard and which date.
- Require an Inspection and Test Plan with hold points. Choose raw material, machining, pressure test, and final release at a minimum. If you do not choose them, you may find out that someone else approved the wrong milestones.
- Specify the destination and its requirements. Equipment for Norway or the Norwegian Continental Shelf can trigger NORSOK or Equinor requirements. Electrical products in hazardous areas may need ATEX or IECEx. The same logic applies to simpler items: an order described as “Baker Hughes shirt, Norway” could be promotional merchandise or flame-resistant workwear. Those are two different products with the same logo. Write down the standard, whether EN ISO 11612 or just “promotional fabric.”
- Name the document reviewer. Who approves the material test certificate, pressure test report, and coating certificate before shipment? If nobody owns that review, the paperwork is just paperwork.
I don't mind spending time explaining this. I'd rather spend ten minutes on the phone while the PO is still editable than sit in a disagreement after the equipment ships. An informed customer asks better questions. Better questions produce clearer requirements. Clearer requirements mean less interpretation.
So if you remember one thing from this article, remember this: a clean certificate means the part matched the document. If the document has white space, the part's real-world performance is a guess.