What is API Spec Q1?
API Specification Q1 sets the requirements for a quality management system at an organisation that makes products for the petroleum and natural gas industry. It says what the system must control: how orders are reviewed, how design is managed, how suppliers are chosen and checked, how production and inspection are run, how non-conforming product is handled, and what records are kept. It does not say how to build any particular product. That is the job of product specifications such as API 6A or API 6D.
The current edition is the 10th. API published it on 18 September 2023 and it took effect a year later. The 9th edition was titled for manufacturing organisations. The 10th is titled Quality Management System Requirements for Organizations Providing Products for the Petroleum and Natural Gas Industry, and API describes its reach as wider: engineering and design, activities such as welding, heat treatment and inspection, and product-related activities such as distribution. API has issued errata and addenda to it, so name the edition and its amendments when you state conformance.
How does API Q1 relate to ISO 9001?
API describes Q1 as meeting most ISO 9001 requirements and adding elements the oil and gas industry considers valuable. The 10th edition is aligned with ISO 9001:2015. The 9th was aligned with the 2008 version. The two standards are separate documents with separate certificates.
| Point | ISO 9001 | API Spec Q1 |
|---|---|---|
| Who it is for | Any organisation in any sector | Organisations that supply products to the petroleum and natural gas industry |
| Style | States what must be achieved and leaves more of the method to the organisation | More prescriptive about the procedures and records that must exist |
| Topics public summaries say Q1 treats in more depth | Covered in general terms | Risk assessment, contingency planning, management of change, and the evaluation and control of suppliers, including critical purchases |
| Exclusions | Requirements may be judged not applicable with a justification | API says Q1 limits which sections may be excluded, and each exclusion needs a written justification |
| Who certifies | Any accredited certification body | API's own registrar, APIQR, registers organisations to Q1 |
| Link to a product mark | None | A Q1 system is required for an API Monogram licence |
The practical point for a supplier: an ISO 9001 certificate does not answer a requirement for API Q1. A working ISO 9001 system is a sound base, and the closer alignment of the 10th edition makes it easier to run one system for both. But the customer who writes Q1 into a quality specification expects Q1 evidence.
How does API Q1 relate to the API Monogram Program?
There are two routes, and customers sometimes mix them up. An organisation can have its quality system registered to API Q1 through APIQR. That is a statement about the system. Or it can hold a licence under the API Monogram Program for a named product specification. That allows it to apply the mark to conforming new products made at the licensed facility.
The Monogram route includes the quality system. API says a licensee must run a system that meets Q1 and has been in operation for at least four months, describe it in a quality manual, carry out a documented internal audit and management review, and hold the technical capability to make the product. Q1 registration without a Monogram licence does not allow the mark on anything.
A third document, API Spec Q2, is the equivalent for organisations that supply services to the industry, such as well servicing. A requisition for equipment that names Q2 has probably named the wrong one. Ask.
What do customers ask suppliers to show?
Operators and engineering contractors name API Q1 in the quality section of a requisition or in a supplier quality specification. The wording varies from a single line to several pages. It tends to ask for evidence at three levels: that the system exists and is certified, that it will be applied to this order, and that it reaches the sub-suppliers who make the critical parts.
For a package builder the third level is the hard one. The customer may accept the builder's own certificate and still ask for Q1 or equivalent evidence from the makers of pressure-containing items, or ask how the builder evaluates and re-evaluates its suppliers. Public summaries of the 10th edition say supplier evaluation was revised and now covers initial evaluation and re-evaluation. Read the customer's clause for what it requires of sub-vendors, and pass it down in the purchase order.
What a customer's quality requirements usually ask for under API Q1
| What the customer asks for | What to check before you accept it |
|---|---|
| A current API Q1 certificate or registration | The edition, the expiry date, and that the certificate names the site where the work will be done |
| A scope that covers the product | Whether the scope statement on the certificate includes the product or activity ordered, including design if you design it |
| ISO 9001 as an alternative | Whether the clause says 'API Q1 or ISO 9001', or Q1 only. If Q1 only and you hold ISO 9001, that is a deviation to declare |
| An API Monogram licence for the product specification | Whether the order asks for monogrammed product, and whether your licence covers that specification and facility |
| A quality plan for the order | When it is due, whether it needs approval before manufacture starts, and how it relates to the ITP |
| Control of sub-suppliers | Whether sub-suppliers of critical items need their own certification, the customer's approval, or both |
| Flow-down of requirements | Which customer clauses must be copied into your purchase orders, and whether the customer may see them |
| Notification of change | Which changes need the customer's agreement first: design, material source, manufacturing site, sub-supplier, or a special process |
| Non-conformance and concession handling | Which non-conformances must be reported, how quickly, and who may accept use-as-is or repair |
| Access for audit and inspection | Rights of access for the customer, its inspector and the end user, at your site and at sub-suppliers |
| Record retention | The period asked for, against your own. Public summaries say the 10th edition lengthened the minimum retention period, and customers may ask for longer still |
| Personnel competence and special processes | Evidence of qualification for welding, NDE, heat treatment and coating, in house or subcontracted |
These points are spread across the requisition, the general conditions and the supplier quality specification, and they are easy to accept without reading. OdysseyGPT's Customer Specification Review (beta) lists the quality and documentation requirements in a specification package with the clause behind each. Document Review compares the package with your own quality plan or quality manual extract and gives each requirement a status such as complies, deviates, clarification or not addressed, quoting both documents. After award, the ITP Validator (beta) checks your inspection and test plan against the customer's quality specification.
What OdysseyGPT does not do here
It does not audit a quality system, judge conformance to API Q1, or confirm that a certificate or licence is valid. It reads the customer's documents and yours and reports the differences, each with a quote. Certification is between you and API.
Talk through your tender review
See how OdysseyGPT reviews a tender
Tell us how your team reviews tenders today. We can walk through an example together.
