Oilfield equipment pre-dispatch checklist

"Available in the yard" answers a location question. Dispatch planning needs more information: is this the requested unit and configuration, are the required records present, is any work outstanding and who is responsible for the next decision?

A pre-dispatch checklist gives the yard, operations and workshop teams a shared way to review those questions. It should identify missing evidence and unresolved actions early enough to address them before the planned collection.

Hafrix editorial · Initial edition: 5 November 2026. This guide covers operational records. It does not prescribe technical inspection steps or establish that equipment is safe for service. The applicable OEM instructions, customer requirements and approved procedures determine the technical checks and authorized release.

Establish what the job requires

Start with the requested job and the customer-approved requirement. Record the job reference, destination, planned dispatch date, equipment type and configuration, quantity, accessories and any specified documents. Identify the version of the request being used.

A changed request needs an explicit review. If the customer asks for a different configuration after the first preparation, the earlier check should not silently stand in for a check of the revised requirement. Keep the change and the resulting action connected to the job.

Distinguish planned times from actual events. The plan helps coordinate preparation; the dispatch record establishes what left and when. Neither should be overwritten to make the other appear correct.

Match the records to the physical equipment

The equipment ID, serial number and recorded configuration need to refer to the unit being prepared. A suitable description in a booking is not enough if the physical identification is unclear or the configuration record belongs to another assembly.

For kits, compare the requested contents with the units or quantities being supplied. Record substitutions and shortages. A counted quantity and an identified serialized item are different forms of evidence; the checklist should preserve whichever is required for each line.

Review the supporting evidence

Gather the documents required by the applicable process. Depending on the equipment and job, the set may include inspection evidence, certificates, maintenance records or other controlled documents. The checklist should identify the actual requirements rather than assume that every document applies to every asset.

For each document, establish which equipment and scope it covers, the relevant dates, the source and the review outcome. A filename containing a serial number does not establish that the content matches the unit. A document may also be present while a question about its scope remains unresolved.

Where a date or validity period matters to the planned assignment, the responsible reviewer needs the applicable requirement and job context. This article does not provide universal inspection intervals or certification periods.

Resolve open work and contradictions

Check for maintenance or inspection work connected to the unit, a reported concern from its previous job and any unresolved discrepancy in the records. Record who will resolve each exception and what evidence is needed.

Some exceptions are administrative; others require a technical decision. A missing customer reference should not be treated as equivalent to an unresolved inspection finding. Both need an owner, but the competent person, decision and permitted next step may differ.

Consider illustrative unit EQ-118. Its warehouse location is correct and a certificate is attached, but the returned configuration differs from the job request. The useful action is to identify that difference and obtain the required review. Changing the label to "ready" would only hide the reason the unit needs attention.

Record the handover itself

At dispatch, preserve the actual event: units and quantities supplied, destination, date and time where required, dispatch-document reference, the parties involved and any acknowledged discrepancy. Link the evidence of receipt or acceptance according to the process in use.

Photographs can help explain condition or contents, but the record should say what they depict and which handover they concern. A folder of images without an equipment or document reference is difficult to use in a later return review.

The commercial meaning of dispatch and receipt dates depends on the agreement. Preserve the physical events even when billing starts from another agreed event. The rental-date guide explains that distinction.

A reusable preparation record

Use one record for the dispatch being reviewed, with the following sections:

1. Request: job, destination, requirement version and planned date.
2. Supply: equipment IDs, serials, configuration references, quantities and kit contents.
3. Evidence: required documents, sources, relevant dates and review outcome.
4. Exceptions: each unresolved issue, responsible person, next action and status.
5. Decision: authorized review outcome, person and date, with any conditions recorded.
6. Handover: actual dispatch and receiving evidence, document references and discrepancies.

Keep the exception list attached to the same job. A second spreadsheet containing the "real" blockers makes the main checklist less reliable precisely when several teams are preparing the equipment together.

Where Hafrix helps

Hafrix brings equipment identity, stock and kit records, documents, maintenance work and dispatch activity into connected workflows. Readiness indicators use the records and configured rules available to the system. They help teams identify work and evidence to review; they do not replace an authorized technical assessment.

For an initial rollout, choose one equipment group and agree the meaning of its statuses and required records. Test a complete example and an example with a missing document or open work order. The exception path shows whether the team can find the owner and resolve the issue without losing the evidence.

Explore Inventory, Maintenance and Rental. For the return journey, use the field-to-workshop handover guide.

Sources and further reading

This checklist is an original administrative framework. The IADC Manufacturing Record Book Guidance provides an industry example of organizing an equipment documentation package. It is a reference for documentation, not a universal dispatch checklist or a claim of Hafrix certification.

The Hafrix equipment documentation, dispatch documentation and maintenance documentation describe the related product records. Set the technical requirements from the controlled documents applicable to the actual equipment and assignment.

Browse all articles and guides.