The oilfield hose document pack: what travels with an API assembly

The oilfield hose document pack is part of the product rather than an accompaniment to it. On general industrial orders the documents follow the goods. On oilfield orders they are part of the goods: an assembly that arrives without its pack cannot be installed, and the pack cannot always be reconstructed after the fact. That inversion is the single most useful thing to understand about buying flexible connections for pressure-control and drilling service.

The right-hand column is the reason this article exists. Only the last line can be produced later. Everything above it depends on something having been recorded at the time — a batch tracked, a test carried out and logged, a tag attached to a specific item — and a supplier who did not do that cannot fix it with paperwork.

The corresponding advice for buyers is unglamorous: send the documentation clause with the request for quotation, in full, even when it is three pages of boilerplate. A supplier who reads it will price it and schedule it. A supplier who does not read it will quote lower and deliver late, and the difference will look like their fault and be nobody’s.

The API standards that govern this equipment — the rotary and vibrator hose family, choke and kill service, and control-system hose — define what an item must be, not what documents your organisation needs to file. Two assemblies can both be correct against the same standard and arrive with very different packs, because the pack follows the purchase order and the operator’s own regime.

So the specification has two halves and they are written in different places. The engineering half comes from the standard and the service conditions. The documentation half comes from your client’s contract and your own QA system. Send both to the supplier; sending only the first is how a technically perfect assembly ends up rejected on receipt.