ISO 9001 vs AS9100: which certificate goes on this RFQ

This page is a buying comparison. It is for operations and quality leads at mid-market manufacturers and machine shops who are about to send a registrar RFQ and cannot agree whether ISO 9001 or AS9100 belongs on it.

Those standards are not interchangeable quality logos. ISO 9001 is a general quality management system. AS9100 is the aviation, space, and defense quality management system published in the Americas on top of that base. Customers say "ISO" and mean either. A prime's portal often means the aerospace one and will check a different database. Salespeople will offer to quote both. The useful question is a procurement question: which certificate does this cycle have to produce, and can you staff the system behind it.

A Stage 1 versus Stage 2 page already walks the two initial visits. This page does not repeat that chapter. It decides which system those visits are allowed to sample. Whether that system is real enough to book Stage 1 is first ISO certification. After you pick the standard, you still write one outbound pack, choose a registrar, read the quote, and verify accreditation for the legal entity and the edition you will claim. For AS9100, that verification has a second door: the IAQG database, OASIS, described below. Why two replies for the same story diverge is what drives certification cost. Where the dates sit is how long ISO certification takes. This page does not invent prices, day-rate totals, or accreditation identifiers. Confirm the live approval in the quarter you would book.

The directory on this site filters ISO 9001, ISO 14001, ISO 45001, ISO/IEC 27001, and ISO/IEC 42001. It does not filter AS9100. Nothing in the registrar profiles on this site states an IAQG approval for 9100. A profile tagged for general quality is not evidence of an aerospace schedule. Do not infer one from a brand, a sector word, or a brochure.

The decision here is narrower: 9001 on this RFQ, AS9100 on this RFQ, or neither until the system exists. Then one pack.

1. What each standard is for, in plain terms

Skip the clause lecture. Buyers do not award a certificate because they memorized a table of contents.

ISO 9001 is how a customer checks that you can repeat the work and correct it when it fails. A certification body samples that quality system: how an order becomes a product or a service, how nonconforming work is caught, and who owns the process. ISO 9001 uses the shared high-level structure also used by ISO 14001, ISO 45001, ISO/IEC 27001, and ISO/IEC 42001. The certificate is not a promise that every part is perfect. It is not a product mark.

ISO published ISO 9001:2026 on 16 September 2026. Many certificates in the market, and many quotes in this quarter, are still against ISO 9001:2015. A body can certify the new edition only after its accreditation covers it. Put the edition you will claim on the pack, and ask which edition the body can issue now. A 2015 certificate did not expire because a new edition exists. The transition window belongs to the accreditation arrangement and to the certification body. It is not a date this page can assign.

On a plant the interviews sit in receiving, production, inspection, and with the people who run them. In a machine shop they sit in how a print becomes a part, how the revision on the traveler matches the revision that was ordered, and what happens when the part is wrong. The owner is the person who already runs that work and can speak without a script.

AS9100 is the quality management system for organizations that design, develop, or provide aviation, space, and defense products and services. The International Aerospace Quality Group (IAQG) writes the 9100-series. Buyers meet it under regional names: AS9100 in the Americas, EN 9100 in Europe, and JISQ 9100 in the Asia-Pacific. Use the name the customer wrote. The edition in wide use, and the one to name unless the body tells you a different edition is the one they are approved to issue, is AS9100D. That edition includes ISO 9001:2015 and then adds aviation, space, and defense requirements. It is not ISO 9001:2026 with an aerospace label. If the IAQG later publishes a 9100-series edition aligned to a newer ISO 9001, a body can issue it only after it is approved to do so. This page does not assign that date. Ask which edition the body can issue now.

A certification body samples that aerospace system. Buyers should expect the visit to care about things a general quality audit often treats lightly or not at all:

• Configuration management. The revision the customer ordered is the revision the cell runs. Changes are approved before the floor uses them. Obsolete prints are not in the rack. A document-control procedure that only covers the quality manual is not configuration of the product.
• Product safety. The ways the product you design or make can create a hazard in service, and the controls that sit on those ways. This is product safety, not occupational health and safety. An ISO 45001 certificate does not answer it. A guarding programme on the mill does not answer it either, unless that programme is actually about the product.
• Counterfeit parts prevention. A process that keeps counterfeit and suspect counterfeit parts out of the product you deliver: purchasing, receiving, traceability back to an approved source, and what you do when a certificate of conformance looks wrong. A dimensional check at receiving, with no view of where the material came from, is not that process.
• First article inspection. Production process verification, which buyers meet as a first article. It is repeated when the part, the process, the tooling, or the source changes, not filed once in a binder from years ago. Build-to-print shops still do this on the parts they make. Many aerospace customers require the record to follow 9102. That is a record the audit will sample. It is not a second management-system certificate. Do not write 9102 on the RFQ as if you were buying a certificate to it.
• On-time delivery and supplier performance. Delivery performance against the aerospace requirement, supplier quality and delivery performance, and action when either misses. A plant-wide shipping percentage that mixes commercial jobs with aerospace jobs can hide the misses the customer will ask about. Say how you separate them if both kinds of work sit in the same building.
• The rest of the aerospace layer, in buyer language. Operational risk on the process that makes the product, not only a business-risk paragraph in a manual. Special requirements, critical items, and key characteristics where the customer or your own system named them. Control of work you move between sites, shifts, or outside processors. A management representative with the authority the aerospace system describes. Human factors considered when you investigate a nonconformity. A quality manual that states the scope and how the processes interact.

The certificate records the management system for the scope you agreed. It does not approve a part for flight. It does not issue a production approval or a parts approval. It does not mean a regulator or a prime has source-inspected you. It does not accredit a special process.

You can hold both certificates eventually. This page is about which one this RFQ is for.

2. When 9001 is the forced gate this cycle

Start with ISO 9001 when the pressure in front of you is general quality, and an aerospace mark will not lose a bid, a supplier approval, or a renewal this quarter.

That is still the usual manufacturer case, including a machine shop whose purchase orders are commercial. Portals, industrial customers, and export paperwork treat ISO 9001 as table stakes, and the shop already half-runs the work an auditor will sample. A purchase order that names ISO 9001, and does not name AS9100, EN 9100, JISQ 9100, or an OASIS-listed certificate, is a 9001 gate. Read the clause. Do not upgrade because a salesperson said aerospace always means AS9100. Facilities work, catalog hardware, ground-support work the customer has accepted under ISO 9001, and a job that has never been identified as aviation, space, or defense product can stay on the general certificate.

Put ISO 9001 on this RFQ when most of these are true:

• The customer, portal, bid, or supplier approval in front of you names ISO 9001, or names "an ISO certificate" and means general quality.
• No current contract, quality clause, or portal names AS9100, EN 9100, JISQ 9100, the 9100-series, or an OASIS-registered aerospace certificate for this work.
• You can name the legal entity, the sites that do the certified work, and a quality or operations owner who will be in the room.
• Documented processes roughly match Tuesday. Internal audit and management review can touch this system before you invite a body. That test is first-certificate readiness.
• Aerospace pressure is a forecast: a sales call, a capability line on the website, a private-equity note that "defense might be interesting," or a customer who might send a flight part next year. A forecast is not a date that kills a contract this cycle.
• You are not offering a general quality certificate as a stand-in for a flow-down that names AS9100. If the exhibit names AS9100, 9001 will not clear it.

A later AS9100 add is a normal plan when an aerospace customer is real and the aerospace system does not exist yet. One line on the pack is enough. Leave AS9100 off this RFQ while you have no aviation, space, or defense work you will defend. If the live fork is quality versus environment, occupational health and safety, information security, AI governance, or a medical-device system, use the comparison that matches that fork: ISO 9001 vs ISO 14001, ISO 9001 vs ISO 45001, ISO 9001 vs ISO 27001, ISO 9001 vs ISO 42001, or ISO 9001 vs ISO 13485. Do not add AS9100 to look specialized.

If the portal requires ISO 9001 and the quality system does not exist, build the system, then send the pack. An RFQ sent so the quote creates a deadline is how Stage 1 writes findings you already knew. Who writes the system versus who certifies it is consultant vs certification body.

Leave AS9100 off this cycle only when it is not the gate and you cannot staff both. Read the quality clause before you do that. Many aviation, space, and defense customers will not treat an ISO 9001 certificate as close enough.

3. When AS9100 is the forced gate this cycle

Start with AS9100 when a customer, a prime, a tier-1, or a supplier approval will not let you through without an aviation, space, and defense quality certificate this cycle, and you can show that system for the role you play.

That is the usual case for a machine shop or a manufacturer building aerospace or defense product to a customer's print, and for a firm that designs that product as well as makes it. It is not the case for a shop whose brochure says "aerospace capable" and whose purchase orders do not. It is not the case for a company that only stocks and resells parts, and it is not the case for a maintenance organization. Those roles have their own standards in the same series, described below.

The certificate does not authorize the part. Quoting AS9100 does not finish a first article you have never run, and it does not answer a source inspector.

Put AS9100 on this RFQ when most of these are true:

• The agreement, portal, or supplier approval names AS9100, EN 9100, JISQ 9100, or an OASIS-registered 9100 certificate, on a date you can point at. Use their words.
• You design, develop, or manufacture aviation, space, or defense product, or you provide a related service that 9100 actually covers, and the sentence matches the contracts. A build-to-print machine shop is a normal 9100 scope when design stays with the customer and you can defend that exclusion.
• The aerospace system exists. Configuration control people use. A product-safety view of the work you actually do. Counterfeit controls at purchasing and receiving. First article records where you have already produced the part, and a defined process where you have not yet. Delivery and supplier performance someone reviews. Internal audit and management review that touched this system. A management representative who can walk it without a consultant in the room.
• Design is an explicit decision. In, with records you can show. Or out, with the contract fact that the customer owns the design and you do not change it. "The website says engineering" is not a design scope. "The customer owns the print and we do not change it" is a start, and Stage 1 will still ask who approves a deviation.
• You know which sites touch the aerospace product, including a cell, a second shift, an outside processor you will claim, and a warehouse that holds that product. More than one address is multi-site certification scope.
• You are not asking the certificate to stand in for a regulatory approval, a customer source inspection, or a special-process accreditation.

If the agreement requires AS9100 and the aerospace system does not exist, build the system, then send the pack. A general quality manual with "aerospace" typed into the scope will not survive Stage 1. Readiness still has the first-certificate shape. The content is the aerospace system. What that first visit is for sits in Stage 1 versus Stage 2.

Three neighboring products get confused with this certificate. Keep them off the pack unless you are buying them on purpose.

9110 and 9120 are the other standards in the same series. 9100 is for organizations that design, develop, or provide aviation, space, and defense products and services, which is the manufacturer and the machine shop that makes parts. 9110 is for maintenance, repair, and overhaul organizations. 9120 is for distributors and stockists. A shop that machines a part belongs on 9100 if the customer requires the series at all. A company that buys a finished part and resells it, without the manufacturing role 9100 describes, belongs on a 9120 conversation. A repair station belongs on a 9110 conversation. Putting 9100 on the pack to "cover distribution" or "cover the hangar" asks a body to quote the wrong object. If you truly do more than one of those roles, say so as separate rows. Do not average them into one scope sentence.

Nadcap is a different accreditation. It is aimed at special processes such as heat treat, non-destructive testing, welding, chemical processing, and coatings. A customer can require Nadcap of the processor and AS9100 of the manufacturer in the same breath. An AS9100 proposal does not include Nadcap unless the quote says so, and even then it is a separate approval with its own body and its own rules. If you outsource the special process, your aerospace system still has to control that external provider. The processor's Nadcap accreditation, if the customer requires it, is their accreditation. Write "9100 management-system certification only" unless you are running that other procurement on purpose.

Regulatory and export approvals are different products. A production approval, a parts approval, an airworthiness decision, and a registration such as ITAR are not delivered by an AS9100 certificate. If the customer wants one of those, that is a question for the approval holder and for counsel. It is not a stamp a registrar adds to a quote. Do not write "FAA approved" or "flight ready" on the RFQ.

Leave ISO 9001 off this cycle only when general quality is not the gate and you cannot staff both. Read the other portals before you do that. An industrial customer can still require ISO 9001 for the non-aerospace work in the same legal entity. An aerospace certificate does not automatically clear that field. Ask, in the same pack, whether you also need a separate ISO 9001 certificate issued for the commercial scope.

4. What buyers get wrong

Five patterns show up in mid-market rooms. Each one produces unlike quotes, or a Stage 1 whose job is to discover fiction.

Treating AS9100 as ISO 9001 plus the word aerospace. Same sites, same day count, same auditor bench, same exclusion list, with "including aerospace" added to the scope sentence. The aerospace requirements are additional work: configuration, product safety, counterfeit parts, first article, delivery and supplier performance. The approval path for the certification body is additional too. A 9001 lead who has never audited a first article or a counterfeit control is not an aerospace team. If you want both certificates eventually, name which one is this cycle. "Both, we're integrated" is a sentence, not a programme. Integration is real when shared processes already run (document control, internal audit, management review, corrective action) and the aerospace work exists: a configuration a machinist would recognise, a first article someone can open, and a delivery miss someone has already acted on.

Sending ISO 9001 to a customer who named AS9100. The field on the supplier portal is not a suggestion. A certificate you already hold for general quality does not put aerospace controls into scope, and it does not create an OASIS record. Customers who flow down 9100 check OASIS. If the revenue is blocked on that approval, the general quality certificate is the wrong product this cycle.

Picking 9100 for a role the series puts somewhere else, or hiding the role you have. Quoting AS9100 for a stockist, or for a maintenance organization, buys the wrong standard. Quoting AS9100 because a logo might win industrial bids, when you do not design or make aviation, space, or defense product, buys a system you will fail to show. Hiding an aerospace contract inside an ISO 9001 scope because finding an approved body is annoying is under-scoping. The same honesty applies to design. Putting design in the scope because the brochure says "engineering," when every aerospace job is build-to-print, asks the auditor to sample a design process you do not run. Excluding design while your people still change the print, accept a verbal deviation, or release a specification the customer files, asks the auditor to ignore work you do.

Assuming any registrar on a general directory can quote it. ISO/IEC 17021-1 is the general competence standard for bodies that audit and certify management systems. AS9100 sits on a further scheme, described in the next section. A body can be accredited for ISO 9001 and still have no approval to issue 9100, no listing in OASIS, and no authenticated aerospace auditors. This site's directory does not tag that approval. One profile that publishes an ANAB aerospace line for Amtivo (USA), Inc. in Arvada, including AS9100:2016, AS9110:2016, and AS9120:2016, is Amtivo (USA). That page is not an OASIS record. Verify the live schedule and the IAQG listing the way the scheme requires, in the quarter you would book.

Confusing a customer visit, a special process, or a safety certificate with this buy. A source inspection, a first-article witness, and a prime's process audit are the customer's own activity. Nadcap is a special-process accreditation. ISO 45001 is occupational health and safety. None of those is an AS9100 certificate, and none of them clears an OASIS field. Adding ISO 14001, ISO 45001, or ISO/IEC 27001 because someone mentioned a stack belongs on the IMS buying guide or the matching comparison, and only when that system exists. A first aerospace certificate is not the moment to look thorough.

"Quote whichever is easier" means the bodies are not quoting the same object.

5. How the scheme, the scope, and the quote differ

A quote is a designed audit programme. It starts from your facts. ISO 9001 facts and AS9100 facts are not the same list with a different title. The approval behind the body is not the same approval either.

Who is allowed to issue AS9100. The IAQG runs the certification scheme for the 9100-series. Buyers meet it as the Industry Controlled Other Party scheme, usually shortened to ICOP. The rules live in the 9104-series. 9104/1 is the requirements for the certification programme. 9104/2 is how that programme is overseen. 9104/3 is auditor competency and training. 9101 is how the audit itself is conducted. You do not need to buy those documents to send an RFQ. You do need the body to be inside the scheme.

In plain terms, a certification body that wants to issue 9100 has to clear a stack a general ISO 9001 schedule does not imply:

• It is accredited to audit and certify ISO 9001 by an accreditation body that is an IAF MLA signatory for quality management systems and that the IAQG has approved for this scheme. The accreditation walkthrough is still how you read an accreditation-body schedule. It is not the whole check.
• That accreditation body has assessed the certification body against 9104/1. The body has to be able to audit to ISO/IEC 17021-1, 9104/1, and 9101 for the aerospace standards on its scope.
• The scope of that approval includes 9100. An approval that lists only 9110, or only 9120, is not a 9100 approval. An ISO 9001 line on the same schedule is not a 9100 approval.
• The certification body is registered in OASIS and enters its aerospace audits there.

Auditors who perform these audits are authenticated under the IAQG scheme. OASIS is also where those authenticated auditors are listed. A lead auditor who is competent for commercial ISO 9001 is not, by that fact, an authenticated aerospace auditor. Ask for the authentication, not for a training slide.

OASIS is where the certificate has to be visible. OASIS, the Online Aerospace Supplier Information System, is the IAQG database of aerospace quality management system certifications, of the certification bodies in the scheme, and of audit results. The IAQG describes it, and links the entry point, on the IAQG certification pages and the OASIS overview. A customer that flows down 9100 uses that record to see whether a supplier's certificate is current and which body issued it. A PDF on the wall, a logo on a quote, and an ISO 9001 hit in IAF CertSearch are not that record. IAF CertSearch remains the right lookup for a general accredited certificate, which is why the verify guide sends you there. It does not replace OASIS for AS9100.

After issue, the certification body enters the certificate. Your organization needs its own OASIS access to manage contacts, feedback, and who can see audit information. Ask the body which record you should expect to see, and open it before you tell a customer the certificate is live. Some views of audit results require an account. The status a prime uses for supplier approval is the OASIS record.

Scope. For ISO 9001, name the legal entity, the products or services, the processes, and the exclusions you will defend. For AS9100, name the aviation, space, and defense products or services, the activities (design, manufacture, and the processes you actually run), and what is out. The scope sentence is what a customer reads in OASIS. "General machining" is a weak aerospace scope if the aerospace work is why you are buying the certificate, and it is a false scope if that work does not exist. "The whole company" pulls a commercial cell or a sales office into a record the customer will read, or it drops the cell that actually runs the aerospace job because that cell was not on the quality tour.

Sites. ISO 9001 follows the work: plants, job shops, warehouses, and the offices where the certified service is run, including the second shift. AS9100 follows where the aerospace product is designed, made, inspected, stored, or released, and where you control work you transfer out. A design office can be in or out depending on the design decision. An outside heat-treat or plating source can be central to the process control and missing from a factory list that says "the shop." A second shift that runs the aerospace job still counts. This cycle names one standard's sites. If you are honestly quoting both, the pack carries a site-by-standard matrix. The later add stays off the pack, with one line that says so.

People. ISO 9001 interviews a quality or operations owner, process owners, and someone who does the work. AS9100 interviews a management representative and the people who can show configuration, purchasing and counterfeit controls, first article and production, delivery performance, and design or the justified exclusion. "We'll bring the aerospace lead in at Stage 2" means the pack is early. "The ISO 9001 manager will cover AS9100" means the aerospace system has no owner. If one person owns both, say so only when that person can walk both.

What you already hold. If an ISO 9001 certificate exists, name the issuing body, the scope, and the expiry. Say whether you want the same body to add AS9100 or a different body to certify it. An existing certificate can change how a body plans the file. It does not convert one standard into the other, and it does not put the current body into OASIS.

Who implemented. Internal, a named consultant, or nobody yet. ISO/IEC 17021-1 restricts a certification body from certifying a management system it consulted on. If the same firm wrote the aerospace procedures, they should not be the certifier. Disclose the implementer on the pack. That split is consultant vs certification body.

One page, the same pack to every body. The full checklist is how to build a registrar RFQ / scope pack. For this decision, these rows have to be explicit:

Fact	If ISO 9001 is this cycle	If AS9100 is this cycle
Standard and edition	The 9001 edition you will claim. Ask which edition the body is accredited to certify now	AS9100D, EN 9100, or JISQ 9100, using the customer's words, unless the body tells you a different edition is the one they are approved to issue
What is in scope	Products, services, processes, exclusions you will defend	Aviation, space, and defense products or services, activities, design in or out
Document the owner can show	Processes that match the work, plus internal audit and management review of this system	Configuration, product safety, counterfeit controls, first article records, delivery and supplier performance, plus internal audit and management review of this system
Sites	Where that work happens, with headcount bands and shifts	Where the aerospace product is designed, made, inspected, stored, or released
Owner	Named quality or operations owner	Named management representative who can walk the aerospace system
The other standard	Later add, or not this cycle	Later add, or not this cycle. Say if a separate ISO 9001 certificate is also required
Neighboring product	Not this quote	Write "9100 only" unless you also need 9110, 9120, or Nadcap as its own row
Who implemented	Internal, named consultant, or none	The same disclosure. The implementer is not the certifier
Where the certificate must show up	The accreditation path in the verify guide	OASIS, entered by the issuing body, plus the accreditation path

Headcount is a band per site, not the about-page total. A night shift still counts when the aerospace job runs at night. A thinner story for one logo ends the comparison. What comes back (programme structure, days, travel, exclusions, aerospace competence) is what CB quotes include.

Audit time is part of that return, and it is where unlike quotes start. Duration for an aerospace quality system is set under the 9104-series rules for that scheme. It is not produced by copying an ISO 9001 day count, and it is not a number this page can assign. Complexity, sites, shifts, design responsibility, and special processes you perform are the kinds of facts that move the calculation. A reduction counts only when the body writes the reason. Ask them to show the aerospace time, any addition, and any reduction. Do not import a day count or a percentage from a blog, and do not accept "same days as your 9001" as the answer. How to lay those rows beside another quote is what drives certification cost.

Ask these in writing, of every body, against the same pack:

• The issuing legal entity, the accreditation body, and whether that entity is approved for 9100 under the IAQG scheme and listed in OASIS. Confirm 9100 specifically. A 9110 or 9120 line is a different scope.
• The edition they will certify, and the regional name the customer used.
• Whether their reading of your pack includes design or excludes it, and what evidence they will expect at Stage 1 for that sentence.
• Days by stage for the initial audit, then surveillance and recertification, calculated for the aerospace scheme. A quote that prices Stage 2 and leaves the rest blank is not comparable. The calendar around those days is how long ISO certification takes. The two initial visits are Stage 1 versus Stage 2.
• What an existing ISO 9001 certificate changes. Ask whether Stage 1 still happens, what it will sample, and how long they typically leave between Stage 1 and Stage 2 for a file like yours. That gap is a range the body will accept. It is not a number this page can assign. Findings that say the aerospace system is not ready should move Stage 2. What a major or a minor then does to certificate issue is closing ISO nonconformities.
• If both standards are on this pack, the calculation. Ask them to show the aerospace time, any time for a separate ISO 9001 certificate, and any reduction and the reason. Shared processes that already run can be sampled once. A commercial quality manual is not an aerospace system, so it is not a discount.
• Who will audit. An authenticated aerospace auditor for your kind of work, not a general quality team with a slide. Ask what happens if the named auditor is unavailable.
• Whether any of the audit is proposed as remote, and for which stage. A document review and a machine-shop floor are not the same method. The 9104-series and the customer's own rules constrain what an aerospace audit can do remotely. Ask the body what their procedure allows for a scope like yours. Do not demand a remote Stage 2 to save a trip. The method page is remote vs on-site ISO audits.
• Whether the proposal also issues a separate ISO 9001 certificate, and for which scope. Do not assume the aerospace certificate clears every portal that still says ISO 9001.
• Whether any line is 9110, 9120, or Nadcap. If you did not ask for those, the page should say 9100 management-system certification only.
• Who enters the OASIS record, and what you have to do in your own OASIS account before a customer can rely on it.

6. One CB programme this cycle, a transition from 9001, or a different product

Sometimes one certification body should quote ISO 9001 and AS9100 together. Often that request is a hope that the aerospace work is a logo on a system you already run. The path from a certificate you already hold is a transition of the system, not a reprint of the old certificate.

One programme this cycle is honest when both systems already run under one legal entity, shared processes are real, the aerospace owner can sit the audit, and each standard has its own scope story or an honest matrix. You may still receive two certificates. Say which processes are shared and which work is aerospace-specific. Configuration, product safety, counterfeit controls, first article, and aerospace delivery performance are aerospace work, not quality clauses with a new label. Let the certification body restate the method. Do not ask them to invent integration you do not operate. The body's approval has to cover 9100, not only ISO 9001, and the body has to be in OASIS. Ask how they staff an authenticated aerospace auditor.

A transition from ISO 9001 to AS9100 is the better buy when the general system is real and the aerospace system is not, or when the aerospace system is real and you do not yet have a body that can certify it. The sequence is a procurement sequence:

1. Read the flow-down and name the standard. 9100, 9110, or 9120. This page assumes 9100 because that is the manufacturer and machine-shop case. If the clause says 9110 or 9120, stop and scope that standard. Do not rename it AS9100 to keep the shortlist comfortable.
2. Treat the existing ISO 9001 system as a head start only where it is real. The shared clauses (how an order becomes a part, how nonconforming work is stopped, internal audit, management review, corrective action) transfer as evidence if people already run them. They do not transfer the aerospace layer.
3. Build the layer the visit will sample before you send the pack. Configuration that matches the print on the machine. Product safety for the product you make. Counterfeit controls at the point parts and material enter. A first-article process, and records if you have already shipped the part. On-time delivery and supplier performance for the aerospace work, separated from a blended plant metric if commercial work shares the building. A management representative who can walk those without a script.
4. Run internal audit and management review on that aerospace system. A review of the commercial quality system, with an aerospace sentence in the minutes, is not that review.
5. Then send one pack. Tell every body you already hold ISO 9001: who issued it, the scope, and the expiry. Ask what that file changes, including whether Stage 1 of the aerospace scheme still happens. Expect it to happen. The new scheme is what Stage 1 is there to read.
6. If the body that holds your ISO 9001 certificate is not approved for 9100 and is not in OASIS, they cannot issue this certificate. The honest options are a body that is approved, or two certification bodies on purpose: one for the general certificate you already have, one for AS9100. Two bodies is a legitimate design when you write it down. It is not a way to hide the aerospace work inside a friendlier general-quality quote. If you later want one name on both certificates, that move is a transfer of the certificate that already exists, plus an aerospace scope the receiving body is actually approved to issue. A transfer does not create an IAQG approval the receiving body does not have.

A later add, even on top of an ISO 9001 certificate you already hold with a body that is approved for 9100, is still an RFQ. Ask what Stage 1 they will still perform. Tell the shortlist which standard comes later.

A different product is a different procurement. 9110, 9120, and Nadcap are not delivered by ticking AS9100 on a management-system proposal. A regulatory approval is not either. If the customer requires one of those, stop and scope that procurement separately. You may still want AS9100 from a body in the IAQG scheme. Say so. Do not let one quote pretend to be all of them.

Keep ISO 14001, ISO 45001, and ISO/IEC 27001 off this pack unless that system is the gate this cycle and you can staff it. The plant stack is the IMS buying guide. The quality-to-security sequence is the path guide. One body for aerospace quality and another for the operations standards is a legitimate design when you write it on purpose. Confirm the legal entity in how to choose a registrar and how to verify accreditation, and confirm the aerospace approval in OASIS.

7. Choose what goes on this RFQ, then send one pack

Make the call in one sitting. The output is a sentence at the top of the scope pack.

1. Write the actual requirement. Portal, quality clause, supplier approval, purchase order. Use their words. If one field says ISO 9001 and another says AS9100, note which revenue is blocked this cycle. If a field says 9110, 9120, Nadcap, or a regulatory approval, mark it as a different product.
2. Match it to a system you can show. ISO 9001 needs processes that match the work. AS9100 needs configuration, product safety, counterfeit controls, a first-article process, delivery and supplier performance, and a management representative who can walk them. If that system does not exist, do not send. Build it, or hire an implementer who will not certify you, and disclose them on the pack.
3. Name one primary standard. Mark the other "later add" or "not this cycle," unless both systems and both owners are real enough to defend at Stage 1.
4. Name the role, the owner, the design decision, and the sites for that standard. General quality owner and the locations where the work happens, or management representative, aerospace role, design in or out, and the locations where the aerospace product is handled.
5. Write one pack and send it to every body you might award. How to choose them is how to choose a registrar. For AS9100, confirm the legal entity is approved for 9100 under the IAQG scheme and listed in OASIS before you invite a body you cannot award. The general lookup is how to verify accreditation. The aerospace lookup is OASIS. If you already hold the other certificate, name it on the pack so the add is comparable.

If the room is still split after step 3, you have two procurements. Run the one that unblocks revenue and park the other until its system exists.

When that sentence is true, send one registrar RFQ / scope pack. The Get quotes form on this site lists the standards on the directory desk. AS9100 is not one of those checkboxes. In Scope notes, name AS9100 if it is this cycle, say whether ISO 9001 is also this cycle or a later add, and state the role and the design decision in one or two lines. If the form will not send without a ticked standard, do not let a ticked ISO 9001 box stand in for an aerospace request. The notes sentence is the scope. Put any certificate you already hold in Existing certificates. Submit the same page once, including to the logo you already like. The standard on the page has to be the standard you can staff.