OQ Compliance Program Checklist: Documentation, Recordkeeping, and Audit Readiness

What an OQ Compliance Program Must Document

Under 49 CFR Part 192 and Part 195, operators are required to have an OQ program that ensures individuals performing covered tasks on pipeline facilities are qualified. The documentation required to demonstrate compliance goes well beyond a simple list of who has been trained.

A compliant OQ program must document: the identification and listing of all covered tasks applicable to the system, the process by which individuals are evaluated and qualified, the records for each qualified individual and each covered task they are qualified to perform, requalification intervals and due dates, and the process for handling situations where a qualification has lapsed.

The regulatory requirement is not simply that qualification happened — it is that qualification happened, was properly evaluated, and was properly documented in a way that can be demonstrated to an inspector on demand. That distinction is where many operators fall short.

OQ Recordkeeping Requirements: The Complete Data Set

For each individual and each covered task they perform, the following information should be documented and maintained in the operator's OQ records:

• Employee or contractor full legal name and unique identifier (employee ID, contractor ID, or equivalent)
• Covered task the individual is qualified to perform — identified using the operator's covered task list
• Date of qualification for each covered task
• Evaluation method used — written test, oral examination, work performance observation, simulation, or documented prior experience
• Name of evaluator who conducted the qualification evaluation
• Evaluator qualifications or credentials, if required by the operator's OQ program
• Evaluation result (pass/fail) and supporting documentation (test score, evaluation form, checklist)
• Requalification interval as defined in the operator's OQ program
• Requalification due date — the specific date by which the individual must be requalified
• Training records, if training was a component of the qualification process
• Full qualification history — not just current status but previous evaluation dates and results
• For contractors: the contractor company name, the entity that performed the OQ evaluation, and documentation of the operator's verification that the contractor is qualified

Traceability: Connecting Employee, Task, Evaluator, and Qualification Record

One of the core concepts PHMSA inspectors apply when reviewing OQ records is traceability — the ability to follow a clear, documented chain from a specific individual performing a specific covered task back through their qualification record, the evaluation method, the evaluator's identity, and the qualification date.

Traceability problems are common in OQ documentation. Records may confirm that an employee completed a training course, but not document who evaluated them, what method was used, or what covered task the qualification applies to. Records may exist in two different systems — a training platform and a spreadsheet — with no clear linkage between them.

A traceable OQ record answers five questions for every qualified individual and every covered task: Who was qualified? For what task? By what method? By whom? And when is requalification required? If any of those fields are missing or can only be partially answered, the record has a traceability gap.

Contractor OQ Documentation: The Operator's Responsibility

Many pipeline operators rely on contractors and third-party service providers to perform covered tasks. This is permitted under the OQ regulation, but it does not transfer the recordkeeping responsibility. The operator is responsible for verifying that contractors performing covered tasks are qualified and for maintaining documentation that demonstrates that verification.

Contractor OQ records must contain the same core information as employee records: the covered task, the qualification date, the evaluation method, the evaluator, and the requalification due date. In practice, this means collecting OQ documentation from contractors before work begins, verifying that the records are complete, and tracking requalification due dates for contractor personnel — not just employees.

A common weakness in contractor OQ documentation is reliance on contractor-provided certificates that state 'the individual is qualified' without including the underlying documentation (evaluation method, evaluator name, date). Those certificates alone may not satisfy the documentation standard during an audit.

OQ Record Retention: How Long Must Documentation Be Kept?

PHMSA does not specify a universal retention period for OQ records in the same way it specifies retention periods for some other record types. Operators are generally required to maintain OQ records for the duration of an individual's employment performing covered tasks, plus any additional period defined by the operator's own written program.

In practice, most OQ compliance programs establish a minimum retention period for OQ records — commonly ranging from three to five years following the last qualification or termination of employment, though this varies by operator and counsel interpretation. What matters most from a compliance standpoint is that the operator has a written retention policy, that the policy is followed, and that historical records — not just current qualification status — are accessible during an inspection.

The records that tend to be most important during an audit are not just current qualification records but historical ones: prior qualification dates, prior evaluation methods, and the full qualification history for individuals who have been requalified multiple times. Operators who delete historical records when new qualifications are issued often discover during audits that inspectors want to see the longitudinal record.

Common OQ Documentation Findings During PHMSA Audits

The following are among the most frequently cited OQ documentation deficiencies during PHMSA compliance inspections:

• Missing evaluation method documentation — records show a qualification date but do not identify how the individual was evaluated
• Missing or incomplete evaluator identification — qualification records do not name the evaluator who conducted the evaluation
• Expired qualifications — requalification due dates have passed without the individual being requalified, and without the operator having a system to detect and respond to expirations
• Scattered or fragmented records — OQ documentation exists in multiple locations (training platform, spreadsheets, paper files, email) with no centralized inventory or retrieval capability
• Contractor OQ records not collected or verified — the operator relied on a contractor's word rather than collecting and retaining documentation
• Training certificates used in place of evaluation records — completing a course satisfies a training requirement but does not, on its own, constitute an OQ evaluation under the regulation
• Covered task list not current — the operator's list of covered tasks has not been reviewed and updated when operations changed, leaving some performed tasks without a corresponding OQ program element
• No qualification history maintained — only current qualification status is recorded, with no historical data on prior evaluations
• Records not retrievable on demand — records exist but cannot be located within a reasonable time during an inspection

Organizing OQ Records for Rapid Retrieval During an Inspection

PHMSA inspectors may ask for OQ documentation for specific individuals, specific covered tasks, or specific time periods — and expect to receive it quickly. The ability to retrieve requested records promptly is itself part of demonstrating a functional OQ program.

An OQ documentation system that supports rapid retrieval should be organized around two primary indexes: by individual (the ability to pull all covered tasks for which a specific person is qualified) and by covered task (the ability to pull all individuals qualified for a specific task). Both retrieval paths will be used during an audit.

Many operators find that their records are retrievable by individual in theory, but not by covered task — because the records are organized by person, not cross-indexed by task. Building a cross-index at the start of a program, or maintaining a master qualification matrix, resolves this structural gap.

OQ Documentation Checklist: 25 Items to Review Before Your Next Audit

Use the following checklist to evaluate your organization's OQ compliance documentation readiness. Each item reflects a documentation standard that PHMSA inspectors commonly examine during an audit or inspection.

• Written OQ program documentation exists, is current, and has been reviewed within the past program cycle
• All covered tasks applicable to the system have been identified and listed in writing within the OQ program
• The covered task list has been reviewed and updated when operations, maintenance activities, or personnel roles changed
• OQ program procedures are accessible to the personnel responsible for managing and maintaining OQ records
• Each qualified individual has a current OQ record on file for every covered task they perform
• Each record identifies the individual by full name and unique identifier (employee ID or equivalent)
• Qualification date is recorded for each covered task for each qualified individual
• Evaluation method is documented (observation, written test, oral exam, work performance, simulation, or prior documented experience)
• Evaluator name is recorded for every qualification evaluation
• Evaluation result (pass/fail) is recorded with supporting documentation (test, evaluation form, or checklist)
• Requalification intervals are defined in the written OQ program for all covered tasks
• Requalification due date is tracked for every qualification record for every individual
• A system exists to alert program administrators before qualifications expire
• Lapsed qualifications are identified and individuals are removed from covered task work until requalification is complete
• A traceable path exists between each employee, covered task, evaluator, evaluation method, and qualification date
• Historical qualification records are maintained — not just current qualification status
• Contractor OQ documentation is collected and verified before contractors begin covered task work
• Contractor records include all required fields: task, evaluation method, evaluator, qualification date, and requalification due date
• A tracking system exists for contractor qualification expiration dates
• OQ records are centralized in a single system or location — not distributed across spreadsheets, email, and filing cabinets
• Any individual's complete OQ record can be retrieved within 30 minutes of a request
• OQ records can be retrieved by both individual and by covered task
• A written retention schedule specifies how long OQ records must be kept
• Historical records (prior qualifications) are maintained and not deleted when new qualifications are issued
• A pre-audit OQ documentation review has been performed within the past 12 months to identify and close documentation gaps