Almost every credential a working person carries answers a question about them. Are they licensed? Are they certified? Are they current? You ask about the person, you get one answer, and the answer holds until a date printed somewhere on the document. That is how a driver's license works, how a trade license works, how nearly every other page in this library works — one row per person, one date per row.
Operator Qualification does not answer that question, and the reason it trips people up is that they keep asking it anyway. Under the pipeline safety rules, an operator has to break its own work into covered tasks — welding, valve maintenance, cathodic protection readings, line locating, excavation around the pipeline, dozens more depending on the system — and then qualify each individual on each task separately, through an evaluation that also has to establish they can recognize and react to abnormal operating conditions. "Is this technician qualified?" is not a question with an answer. Only "qualified for which task, and until when" is.
Then comes the part that has no equivalent anywhere else. The requalification interval for each covered task is not handed down as a number you look up. The rule requires the operator to identify those intervals itself and write them into its own OQ program — so the deadlines you are held to are deadlines you authored. There is no agency website that will tell you when your cathodic-protection qualifications come due, because the answer is in a document in your own office, and it is probably a different answer than the one for welding.
And it doesn't stop at your own payroll. Because the rule attaches to whoever performs a covered task on the pipeline facility rather than to whoever signs their paycheck, the contractors and vendors doing that work have to be qualified under a program too — which folds an entire outside workforce into the same grid. What you end up holding is not a list at all. It is a matrix — people down one side, covered tasks across the other, each cell carrying its own date — where a crew member can be perfectly current on three tasks and quietly lapsed on a fourth. Here is how pipeline OQ works to track, and how to keep every cell of that grid current.
General information, not pipeline-safety or legal advice — requirements are set by PHMSA and participating state agencies and change over time. Confirm what applies to your system at the official sources in section 11.
1. What is pipeline Operator Qualification?
The Operator Qualification rule requires pipeline operators to have and follow a written program ensuring that the individuals who perform covered tasks on the pipeline are qualified to do them — and that they can recognize and react to abnormal operating conditions while doing so. It applies to gas pipelines under 49 CFR Part 192, Subpart N and to hazardous liquid pipelines under 49 CFR Part 195, Subpart G, and the two subparts are close cousins rather than different regimes. An operator running both kinds of system is running one idea twice.
Four things sit inside that written program, and it is worth separating them because they behave differently once you try to track them. The program identifies the covered tasks performed on the system. It qualifies each individual who performs one, through an evaluation. It identifies the interval at which each of those qualifications has to be re-established. And it provides for re-evaluating an individual when something happens that calls their qualification into question. Only the third of those produces a date you can put in a calendar in advance. The fourth produces dates you cannot possibly know ahead of time.
Remindax helps you hold each individual's qualification and requalification dates across that whole grid, employees and contractors alike, and reminds the right people before a cell falls due. It doesn't qualify or evaluate anyone, operate your OQ program, determine which of your tasks are covered, or set your intervals — those are yours, and they are the substance of the program. Because pipeline OQ lands on the same people already holding permits, inspections, and personnel credentials across a regulated operation, it belongs in the same register as the rest of them, which is what compliance tracking is for — tracking and reminders, not a GRC suite.
1.1 Why this is a grid and not a list
The structural difference between OQ and every other personnel credential is worth stating plainly, because it is the source of nearly every tracking failure that follows:
- →Qualification attaches to a pairing, not to a person. The unit that is current or not current is one individual against one covered task. A technician who performs six covered tasks holds six qualifications with six independent statuses, and nothing about the sixth tells you anything about the first.
- →The intervals are yours to identify, and they differ. The rule does not publish one universal number for everyone. Your program names the interval for each covered task, which means two qualifications held by the same person can come due months apart because the tasks are different, not because the person did anything differently.
- →Contractors occupy the same grid as employees. The operator has to ensure that contractor and vendor personnel performing covered tasks are qualified under its program. They are not a separate list kept somewhere else; they are rows in the same matrix, sourced from organizations whose records you do not own.
- →Not every way a cell comes up is a date. The interval is only one route. Under § 192.805 the program must also evaluate an individual where the operator has reason to believe their performance of a covered task contributed to an incident, and where it has reason to believe they are no longer qualified — two triggers that arrive as events, not as anniversaries. A third event-driven duty sits alongside them: changes affecting covered tasks have to be communicated to the individuals performing them.
Covered-task determinations, evaluation methods, intervals, and record requirements are set by PHMSA and by participating state agencies, and they vary between the gas and hazardous liquid subparts. Confirm what applies to your system at the official sources in section 11. This is general information, not pipeline-safety or legal advice.
On virtually every other obligation a business carries, the deadline arrives from outside: an agency sets a renewal cycle, a certifying body sets a validity period, a statute names a date. You can look it up, and if you get it wrong the source will correct you. Pipeline OQ inverts that. Because the rule requires the operator to identify its own requalification intervals, the schedule an inspector holds you to is the schedule in your own program document — which makes it uniquely easy to be non-compliant against a number nobody outside your organization ever published, and uniquely important that the number actually lives somewhere operational rather than in a binder nobody opens between audits.
2. Does pipeline Operator Qualification expire?
There is no single expiry for a person. Qualification is held per individual, per covered task, so the same worker can be current on some tasks and due for requalification on others at the same moment.
The rule requires the operator to identify the intervals at which each covered task's qualification must be re-established, in its written program. They are not one universal number — they vary from task to task.
The program must also evaluate an individual where the operator has reason to believe their performance of a covered task contributed to an incident, and where it has reason to believe they are no longer qualified. Separately, changes affecting covered tasks must be communicated to the individuals performing them.
The operator must ensure that contractor and vendor personnel performing covered tasks are qualified under its program — so their requalification dates sit in the same grid as your employees'.
An individual who is not qualified for a covered task may perform it only under the direction and observation of a qualified individual. Performing it otherwise is a violation.
The most useful thing in that box is the second line, and it is the one people skip because it reads like an administrative detail. Consider what it actually means for a tracking system. On a page about a nursing license or a hazmat registration, the renewal cycle is a fact about the world: you can search for it, a regulator will confirm it, and every operator in the country works to the same number. Here, the number is an output of your own program, chosen when the program was written, potentially years ago, by people who were reasoning about task complexity and risk rather than about calendars. Two operators running physically identical systems can hold entirely different requalification schedules and both be correct.
Which produces a peculiar failure mode: an operator can lose track of its own deadlines not because it forgot to check somewhere, but because there is nowhere to check. The interval for a given covered task exists in a program document, the evaluation date exists in a personnel record, and the answer to "when is this due" is the sum of the two. Any organization keeping those two facts in different places has, in effect, no due date at all — only the ingredients for one.
Field organizations naturally reach for a single flag — a badge color, a column in a roster, a note in a scheduling system — that says whether someone is good to work. Every one of those constructions is wrong here, and wrong in the same direction: they all report the optimistic answer. A worker who is current on nine covered tasks and lapsed on the tenth will show as qualified under any scheme that flags people rather than pairings, and the one task they cannot legally perform is invisible right up until the moment they are dispatched to do it.
There is also a records dimension that quietly extends the tracking horizon well past the current qualification. Under § 192.807 the qualification record has to identify the qualified individual, identify the covered tasks that individual is qualified to perform, and carry the dates of current qualification and the evaluation method used — which is the grid, written down. Records supporting a current qualification are held while the individual is performing the covered task, and records of prior qualification, and of individuals no longer performing covered tasks, are retained for five years. The practical consequence is that a qualification does not stop mattering when it is superseded. The date somebody was last evaluated on a task is a fact you may need to produce long after they have been requalified twice over, or have left the company entirely.
3. Why tracking OQ requalification matters
A qualification program with a written interval schedule and a personnel file for everybody sounds well-defended. Four properties combine to make it one of the easiest compliance structures in this library to be quietly wrong about:
Qualification is per task, not per person
Someone can be current on some covered tasks and lapsed on others at the same time, so a single "qualified" flag hides exactly the tasks that have expired.
Intervals differ, and you set them
Each covered task carries its own requalification interval from your written program, so there is no one date to watch and no external source to look it up in.
Contractors are in the same matrix
The operator must ensure contractor and vendor personnel performing covered tasks are qualified too — an outside workforce whose dates you are responsible for but don't administer.
A lapse changes the staffing, silently
An individual whose qualification has lapsed may perform that task only under the direction and observation of a qualified person — and doing it alone is a violation.
The first point is arithmetic before it is anything else. An operator with sixty field personnel and thirty covered tasks is not holding sixty qualification statuses. It is holding, at most, eighteen hundred cells — fewer in practice, since nobody performs every task, but the number is in the hundreds either way. Nothing about that is unmanageable; plenty of organizations manage larger data sets casually. What makes it different is that the failure of a single cell out of hundreds has a real operational consequence, and that the cell in question is almost never the one anybody was thinking about.
The second point is where OQ separates itself from every credential this site otherwise covers. Compare it directly with something structurally similar: crane operator certification and the documented employer evaluation OSHA requires alongside it. That is also a two-part obligation, also involving an employer assessing an individual's competence, and it also fails when only half of it is tracked. But its shape is fixed: one person, a certification with a published validity from a certifying body, and an evaluation that follows a rule the employer did not write. It is a row with two columns. Pipeline OQ has no fixed width at all — the number of columns is the number of covered tasks your program identifies, and the length of each column's cycle is a number your program chose.
The third point is the one that reaches outside the building. Pipeline work is heavily contracted — construction crews, integrity service providers, locating firms, inspection contractors — and the rule does not treat that as somebody else's problem. The operator has to ensure the contractor personnel performing covered tasks on its system are qualified under its program. So the operator carries responsibility for the currency of qualifications belonging to people it did not hire, cannot schedule, and does not pay, held on evidence supplied by a company with its own turnover. This is the same structural exposure that makes vendor and subcontractor compliance worth tracking as a discipline of its own — except that there the object is usually a document belonging to the firm, like an insurance certificate, and here it is a per-task qualification belonging to a named individual who may be on your site tomorrow and someone else's next week.
The interval is the part you can put in a calendar. The two re-evaluation triggers in § 192.805 cannot be: an individual whose performance of a covered task the operator has reason to believe contributed to an incident, and an individual the operator has reason to believe is no longer qualified. Both are events. Sitting beside them is a third event-driven duty that is not a re-evaluation trigger but behaves like one operationally — the program must communicate changes affecting covered tasks to the individuals performing them, so a procedural change, a new tool, or a modification to how a task is done creates an obligation touching everyone qualified on that task at once. A tracking system that can only hold anniversaries will hold none of these. What it can do is give you somewhere to record the event the day it happens, so what follows has a date of its own instead of living in a supervisor's memory.
The fourth point deserves care, because it is often described too loosely. A lapsed qualification does not automatically stop the work. What it does is change who is legally allowed to do it alone: an individual who is not qualified for a covered task may still perform it under the direction and observation of someone who is. That is a genuine operating provision, not a loophole — it is how people are trained and how crews cover gaps. But it converts a one-person job into a two-person job, and it only works if somebody knows the qualification has lapsed before the crew is dispatched. Discovered in advance, a lapse is a scheduling adjustment. Discovered afterwards, the same lapse was a violation, and the record will show the task was performed by an individual who was not qualified to perform it unaccompanied.
4. Who needs to track pipeline OQ requalification
Large transmission operators with dedicated OQ departments generally have this instrumented. The interesting list is everyone whose share of the matrix sits at the edge of somebody's job:
Gas distribution & transmission utilities
Crews spread across many covered tasks under Part 192 Subpart N, in service territories where the same technician performs a different mix of tasks depending on which district they are working that month.
Learn More
Hazardous-liquid pipeline operators
The same structure under Part 195 Subpart G — and, for operators running both gas and liquid systems, one workforce whose qualifications sit under two subparts at once.
Pipeline contractors & vendors
Crews working across several operators' systems, each with its own program and its own intervals — so one welder's status can differ from client to client on the same calendar day.
Learn More
OQ program administrators
The people who own the whole grid — every individual against every covered task — and who are asked, during an inspection, to produce it as a coherent record rather than as a folder of evaluation forms.
Learn More
Field-operations & safety leads
The last people who can catch a lapse cheaply, at the point a crew is assigned — where a known gap is a staffing decision and an unknown one becomes a finding.
Learn More
Municipal & small operators
Systems where the OQ program is one responsibility among many, the covered-task list is short, and the whole matrix is small enough to feel memorable — which is exactly how a cell goes unnoticed for a year.
The contractor case is the one worth dwelling on, because the obligation runs in both directions and neither party can discharge it alone. The operator has to ensure the contractor's people are qualified; the contractor has to know which of its people are currently qualified under which client's program, on intervals set independently by each of them. A welder who is current for one operator may be past due for another on the same day, on the same covered task, purely because the two programs identified different intervals. Contractors who track this as a single company-wide roster discover the problem at a jobsite gate. For operators whose contracted workforce also crosses into DOT-regulated transport, the same discipline extends to logistics document tracking — tracking and reminders, not telematics.
5. What happens when an OQ qualification lapses
Because pipeline OQ is a matrix, the failure is almost always partial, and that is precisely what makes it hard to see. It is rarely a whole person going unqualified. It is one covered task's qualification quietly reaching its requalification interval while everything else about that individual stays current — a single cell changing state inside a grid that continues, in every summary view anyone looks at, to read as fine.
The immediate consequence is specific and narrow. An individual whose qualification for a covered task has lapsed can no longer perform that task on their own. They may perform it under the direction and observation of a qualified individual, and performing it any other way is a regulatory violation. Note what does not happen: nothing about their other qualifications changes, no system locks them out, and no document in their possession updates. The person is unchanged and one of their permissions has silently switched off.
The regulatory consequence is not a paperwork technicality. Covered tasks are covered because they touch the integrity of a system carrying gas or hazardous liquid. OQ programs are a standing focus of PHMSA and participating state inspections, and inspectors examine the program and the qualification records behind it rather than accepting an assurance that everyone is trained. Civil penalties follow gaps. And an inspection that finds one lapsed cell rarely stops at one cell — a record that failed to surface one due date is, on its face, a record that could be failing to surface others, which turns a single finding into a question about the program.
The contractor dimension widens the exposure without widening your control. Because the operator is responsible for ensuring contractor and vendor personnel performing covered tasks are qualified, a gap can originate entirely outside your payroll and still be your violation. The contractor's crew rotated, a replacement arrived, the paperwork said the firm was approved, and nobody checked whether that particular individual held a current qualification for that particular task under your program. From the operator's side, the failure looks like an administrative handoff. From an inspector's side, it looks like an unqualified person performing a covered task on your pipeline.
Underneath all of it sits the reason these lapses cluster rather than occur singly: the dates do not line up. Because intervals are identified per covered task, one technician's cathodic-protection qualification comes due in a different month from their welding qualification, which comes due in a different month again from their line-locating qualification. There is no natural review moment — no annual renewal season, no shared anniversary — when somebody would plausibly look at the whole grid at once. The matrix has to be watched continuously or it is not being watched, and an organization that reviews it once a year is guaranteed to spend most of the year not knowing.
A lapse found before dispatch costs a schedule change: send someone else, or send a qualified individual to direct and observe, and book the evaluation. A lapse found after the work costs something categorically different — a completed covered task on a live system performed by someone not qualified to perform it, sitting in your own records, discoverable by an inspector and by anyone reviewing the work if something later goes wrong on that segment. The gap between those two outcomes is not the severity of the lapse. It is entirely a question of whether the date surfaced before the crew went out.
6. How Remindax keeps every cell of the matrix current
The tracking problem here is not volume — it is that the unit being tracked is a pairing rather than a person, and that the people in it don't all work for you. Four pieces address that:
The whole matrix in one dashboard
Each individual's covered-task qualifications and their requalification dates, employees and contractors alike, with status at a glance — per cell, not per person.
Requalification reminders, staged
Alerts well before each person's per-task interval falls due, by Email, SMS, and WhatsApp — to the individual and to whoever administers the program, not to one inbox.
Contractor & vendor crews alongside employees
Outside personnel tracked in the same grid on the same terms, so the qualifications you are responsible for aren't split across a system you own and one you don't.
Audit-ready records, including superseded ones
Qualification and requalification dates exportable for a PHMSA or state inspection — current status, and the prior dates you may still be expected to retain.
Remindax tracks dates and status. It is not an OQ-management platform, not a learning-management or evaluation system, and not pipeline-operations software — it doesn't qualify or evaluate individuals, administer your OQ program, decide which of your tasks are covered, set your requalification intervals, or hold evaluation content. What it does is make sure every cell in the grid has a date attached to it and that the date surfaces with time to schedule an evaluation. For the wider picture, see compliance tracking or health and safety tracking — tracking and reminders, not a GRC suite.
7. Why spreadsheets fail for OQ tracking
A spreadsheet can represent a matrix perfectly well — that is arguably what a spreadsheet is for — so the failure here is not about shape. It is that a grid of dates is inert. Nothing in it knows that one of its cells crossed an interval last Tuesday, and nobody opens a hundred-column sheet to find out. The characteristic OQ spreadsheet is accurate on the day it was built and progressively less true every day afterwards, with no mechanism anywhere in it to announce the difference.
It fails second by making the wrong thing easy to read. People scan a grid by row, so the eye reports on individuals: this technician looks fine, that one looks fine. But the compliance unit is the cell, and a row of eleven current qualifications and one lapsed one reads, at a glance, as a good row. The summary a supervisor actually wants — every cell falling due in the next sixty days, across all people and all tasks, sorted by date — is precisely the view a static sheet does not offer without somebody rebuilding it by hand each time.
It fails third at the contractor boundary. The operator's responsibility extends to contractor and vendor personnel performing covered tasks, but those people are not in the operator's HR system, they arrive and leave without an onboarding event, and their qualification evidence comes from another company on that company's schedule. A file maintained by the operator's own administrator will always lag the crew that actually turned up, and a file maintained by the contractor answers a different question — their own program status, not yours.
And it has nowhere to put the obligations that are not dates. An incident that may implicate someone's performance, a reason to believe an individual is no longer qualified, a change affecting how a covered task is performed — each creates a real obligation on a day nobody could have entered in advance. A sheet of intervals has no row for an event, so it lives in an email thread or in a supervisor's recollection, which is a fragile place for something an inspector may ask about two years later.
An automated register holds every individual's per-task requalification dates, employees and contractors in the same view, raises each one well before its interval closes, and gives a triggered re-evaluation a dated item of its own the day it arises — which is the only version of this that survives a workforce that rotates and a covered-task list that changes.
- ✗Reads by row, so one lapsed cell in a good row is invisible
- ✗No warning before an individual task's interval closes
- ✗Contractor crews kept in a separate file, or not at all
- ✗Nowhere to record an incident, a concern, or a task change
- ✗Superseded qualification dates overwritten rather than retained
- ✓Every person-and-task pairing carries its own status and date
- ✓Staged alerts by Email, SMS, and WhatsApp to more than one person
- ✓Contractor and vendor personnel in the same grid as employees
- ✓A triggered re-evaluation can be opened as a dated item that day
- ✓Dates and status only — exportable for an inspection
8. Key takeaways
- ✓Pipeline Operator Qualification is a per-person, per-covered-task requirement under 49 CFR Part 192 Subpart N and Part 195 Subpart G — not a single certificate, and not a status a person can hold on their own.
- ✓Operators identify the requalification interval for each covered task in their own written OQ program, so the intervals vary from task to task and there is no external source to look your own deadlines up in.
- ✓Individuals are also evaluated on triggers rather than dates — where the operator has reason to believe their performance contributed to an incident, or that they are no longer qualified — and changes affecting covered tasks must separately be communicated to the people performing them.
- ✓Contractors and vendors performing covered tasks must be qualified under the operator's program, which puts an outside workforce in the same matrix and makes their gaps the operator's violation.
- ✓A lapsed cell doesn't stop the work — it means that individual may only perform the task under the direction and observation of a qualified person, so finding it before dispatch is a scheduling decision and finding it afterwards is a finding.
Never dispatch a crew out of qualification
Track every person, every covered task, every requalification — automatically, employees and contractors in the same grid. Remindax holds the dates, keeps the record an inspection asks for, and reminds the right people while there is still time to book an evaluation.
GDPR-ready · AWS secure cloud · Encrypted storage · Setup in under 5 minutes
9. Frequently Asked Questions
Not as a single date. Qualification is held per covered task, and each covered task has a requalification interval that the operator identifies in its own written OQ program - so an individual can be current on some tasks and due for requalification on others at the same moment. There is no one expiry for a person, and no universal number that applies across operators.
Under 49 CFR 192.801, a covered task is an activity identified by the operator that meets four criteria at once: it is performed on a pipeline facility, it is an operations or maintenance task, it is performed as a requirement of the part, and it affects the operation or integrity of the pipeline. Because the operator identifies its own covered tasks, two operators with similar systems can end up with different lists.
The operator does, in its written OQ program. The rule requires operators to identify the intervals at which an individual's qualification for each covered task must be re-established, rather than prescribing one number for everyone - which is why intervals vary from task to task and from operator to operator, and why the schedule you are inspected against is the schedule in your own program document.
Yes. The operator must ensure that contractor and vendor personnel performing covered tasks on its system are qualified under the operator's program. That places named individuals from outside your payroll into the same qualification matrix as your employees - and it means a gap can originate at a contractor and still be the operator's violation.
Only under the direction and observation of a qualified individual. Performing a covered task without current qualification and without that supervision is a violation. In practice this means a lapse doesn't halt the work outright - it converts a one-person job into a two-person one, but only if somebody knows about the lapse before the crew is dispatched.
Two things, and both arrive as events rather than dates. The program must evaluate an individual where the operator has reason to believe their performance of a covered task contributed to an incident, and where it has reason to believe the individual is no longer qualified. A related duty sits beside them without being a re-evaluation trigger: changes that affect covered tasks must be communicated to the individuals performing those tasks, which is an obligation touching everyone qualified on that task at once.
No. Remindax tracks the qualification and requalification dates and reminds you. Evaluating and qualifying individuals, administering the OQ program, determining which of your tasks are covered, and setting your requalification intervals are all handled by you. It is not an OQ-management platform, a learning-management or evaluation system, or pipeline-operations software.
Yes - the whole matrix in one place. Each individual's per-task qualifications and requalification dates, employees and contractor or vendor personnel alike, with staged reminders by Email, SMS, and WhatsApp to the individual and to whoever administers the program, and dates exportable for a PHMSA or state inspection.
Yes - a forever-free plan, no credit card required.
Operator Qualification requirements are set by PHMSA and by participating state agencies, and the specifics — covered-task determinations, evaluation methods, intervals, and record retention — depend on your own written program and on whether your system falls under Part 192 or Part 195. Remindax tracks the qualification and requalification dates and reminds you; it doesn't qualify or evaluate anyone, run your program, or determine covered tasks. Confirm current requirements at the official sources below; this is general information, not pipeline-safety or legal advice.
11. Sources & references
This page summarizes public requirements and isn't pipeline-safety or legal advice. Covered-task determinations, evaluation methods, requalification intervals, and record requirements depend on your own written OQ program and on the subpart your system falls under — confirm current rules at the official sources below.
- •PHMSA — Operator Qualification — the program overview from the regulator, including what an OQ program has to contain and how it is inspected.
- •PHMSA — Fact Sheet: Operator Qualification — a plain-language summary of covered tasks, evaluation, abnormal operating conditions, and re-evaluation.
- •49 CFR Part 192, Subpart N — Qualification of Pipeline Personnel (gas) — the regulation itself for gas pipelines, on eCFR, including the program requirements and record provisions.
- •49 CFR Part 195, Subpart G — Qualification of Pipeline Personnel (hazardous liquid) — the parallel regulation for hazardous liquid pipelines, on eCFR.