Instrumentation and Calibration Readiness for Natural-Gas Contractors
Shows what to inventory, what records to keep, and how to handle overdue or out-of-tolerance instruments without assuming universal intervals.
By Gas Contractor Connect editorial teamPublished 6 min read
Inventory first
Assign a unique identifier to every instrument. Anonymous instruments cannot be defended in an audit.
- Combustible gas indicators and leak detection instruments.
- Pressure gauges, recorders and test manifolds used for strength and leak testing.
- Fusion equipment data loggers and temperature measurement devices.
- Locating equipment, multimeters, and any instrument whose reading appears on a record you hand to an operator.
Records worth keeping
- Calibration certificate with traceability to national standards, per the instrument's applicable standard.
- Calibration date, due date, performing organization, and as-found/as-left readings.
- Bump-test or field-verification logs where the manufacturer or operator expects them.
- Assignment history: which crew or job held the instrument during each period.
Intervals are not universal
Calibration intervals come from the manufacturer's instructions, the applicable operator specification, and your own use history — not from a single industry-wide number. Document the basis for each interval you adopt so it can be explained rather than defended after the fact.
Overdue or out-of-tolerance instruments
- Remove the instrument from service immediately and tag it so it cannot be reissued.
- Identify the work performed since the last valid calibration.
- Notify the operator where readings may have affected accepted records.
- Record the impact assessment and corrective action, even when no rework is required.
Primary sources
Related resources
Natural-Gas Contractor Readiness Checklist
Scope-first readiness checklist covering operator gates, people qualifications, and practical tracking.
Read moreOperator Qualification for Contractors: What OQ Does—and Does Not—Require
Clarifies what OQ proves, what it does not prove, and where operator-specific program differences matter.
Read more