Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  /

  / ISO 9001 Certification Requirements: What You Need to Know for Certification

ISO 9001 Certification Requirements: What You Need to Know for Certification

iso-9001-certification-requirements-checklist

Quality management is crucial for any business aiming for sustainable growth. Therefore, achieving ISO 9001 certification ensures credibility and consistency. This globally recognized standard focuses on improving operational efficiency, boosting customer satisfaction, and meeting regulatory requirements.

For businesses seeking to enhance quality assurance, understanding ISO 9001 certification requirements is essential.

This comprehensive guide explores the requirements of ISO 9001 certification. We’ll break it down into actionable steps, clarify common concerns, and provide tips for success. So, whether you’re new to ISO standards or refreshing your knowledge, this blog simplifies complex concepts. By the end, you’ll be ready to confidently navigate the ISO 9001 certification process.

Let’s embark on this journey together and uncover how ISO 9001 can transform your business practices.

What Is the ISO 9001 Certification?

The ISO 9001 certification is a global benchmark for quality management systems. It proves a company’s commitment to consistent quality. But what does that mean for your business?

Simply put, it is a way to show customers, stakeholders, and regulatory bodies that you take quality seriously. This standard is part of the ISO 9000 family and focuses on meeting customer and regulatory requirements.

Certification demonstrates a business’s ability to consistently deliver products or services that satisfy stakeholders.

And the best part? It’s universally applicable. Whether you’re a small startup or a multinational corporation.

To achieve certification, organizations must fulfill specific requirements outlined in ISO 9001. These requirements in the ISO 9001 certification process aim to create a robust framework for continuous improvement.

Imagine having a roadmap that not only improves your current processes but also positions you as an industry leader.

Why Are ISO 9001 Certification Requirements Important?

Achieving ISO 9001 certification offers numerous benefits. It enhances credibility, increases customer trust, and also improves operational efficiency. So, let’s unpack these benefits further:

  • Global Recognition: ISO 9001 is internationally recognized, helping your business stand out in competitive markets. Think of it as a badge of honor recognized by customers worldwide.
  • Customer Satisfaction: The standard ensures your processes meet customer expectations, fostering long-term loyalty. Ultimately, happy customers mean a thriving business.
  • Process Improvement: It identifies inefficiencies and encourages continuous operational enhancements. Who wouldn’t want smoother workflows?
  • Regulatory Compliance: ISO 9001 aligns your business with industry-specific and legal quality requirements. Consequently, compliance becomes less of a headache.
  • Market Opportunities: Many contracts require certification, opening doors to larger markets and partnerships. It’s like a golden ticket to new opportunities.

Therefore, by aligning your practices with ISO 9001, you build trust, reduce risks, and enhance your reputation. It could be a win-win situation.

What ISO 9001 Requires (Clause by Clause)

The requirements of ISO 9001 are structured around how an organization understands its business, leads its people, plans for risk, delivers products or services, measures performance, and improves over time. While the clauses are distinct, auditors assess them as an integrated management system rather than isolated checkboxes.

Context of the Organization (Clause 4)

ISO 9001 begins by requiring organizations to clearly understand their context. This means taking a structured view of both internal and external factors that can influence quality outcomes, such as market conditions, regulatory obligations, organizational culture, and operational complexity. Equally important is identifying interested parties. Customers, regulators, suppliers, and partners all have expectations that must be understood and reflected within the Quality Management System (QMS).

From this understanding, the organization must define the scope of its QMS and determine its core processes, including how those processes interact. Auditors typically focus here on whether the business has realistic process mapping and whether those processes clearly support strategic and quality objectives. ISO provides further guidance on this clause directly through its official overview of the standard: https://www.iso.org/standard/62085.html 

Leadership and Commitment (Clause 5)

Leadership involvement is a foundational requirement of ISO 9001. Top management must take accountability for the effectiveness of the QMS, rather than delegating responsibility solely to a quality manager or consultant. This includes establishing a quality policy, setting measurable quality objectives, assigning clear roles and responsibilities, and ensuring that customer focus is embedded across the organization.

Auditors expect to see evidence that leadership is actively engaged, particularly through decision-making, resourcing, and participation in management reviews. ISO 9001 is explicit on this point. A QMS without leadership ownership is, by design, ineffective.

Planning (Clause 6)

Clause 6 introduces risk-based thinking as a core principle of ISO 9001. Organizations are required to identify risks and opportunities that could affect product or service quality, customer satisfaction, or the integrity of the QMS. These risks must be proportionate to the organization’s context and complexity. Formal risk registers are acceptable but not mandatory if risk is demonstrably addressed through planning and controls.

In addition to risk, organizations must define measurable quality objectives aligned with business goals. Planning also extends to how changes to the QMS are managed, ensuring that updates do not introduce unintended consequences. This approach replaced the older “preventive action” model and is explained in ISO’s official risk-based thinking guidance.

Support (Clause 7)

Support requirements focus on ensuring the organization has what it needs to operate its QMS effectively. This includes competent personnel, appropriate training, and awareness of quality responsibilities at all relevant levels. Infrastructure, work environment, and supporting resources must be adequate for the consistent delivery of products or services.

Documentation control is a critical part of this clause. While ISO 9001 no longer mandates specific documented procedures, auditors expect documentation and records to be controlled, up to date, accessible, and appropriate to the organization’s operations.

Operation (Clause 8)

Clause 8 is where planned processes are put into action. Organizations must define how they deliver products or services, from understanding customer requirements through to final acceptance. Where applicable, this includes controls over design and development, supplier management, and outsourced processes.

Auditors spend significant time in this clause assessing whether operations align with documented processes and whether customer requirements are consistently met. A recurring audit theme is simple but decisive: does the organization do what it says it does, and can it prove it with evidence?

Performance Evaluation (Clause 9)

ISO 9001 requires organizations to actively measure and evaluate how well the QMS is performing. This includes monitoring customer satisfaction, tracking process performance, and reviewing progress against quality objectives. Internal audits and management reviews are mandatory and must be conducted at planned intervals.

Auditors look closely at whether internal audits are meaningful rather than superficial, and whether management reviews result in real decisions and actions. ISO’s guidance on performance evaluation emphasizes that measurement must support improvement, not just compliance.

Improvement (Clause 10)

Continuous improvement is a non-negotiable principle of ISO 9001. Organizations must address nonconformities when they occur, take corrective action to eliminate root causes, and prevent recurrence. Beyond reactive fixes, the standard expects ongoing improvement of processes, products, and the QMS as a whole.

Auditors evaluate whether corrective actions are effective over time and whether improvement activities are embedded into normal business operations rather than treated as audit-only exercises.

Documentation Expectations in Practice

Although ISO 9001 is intentionally flexible, auditors still expect objective evidence that the system is working.

This typically includes a quality policy and objectives, a clearly defined QMS scope, process documentation, risk assessments, training and competency records, internal audit reports, management review outputs, and corrective action records.

There is no fixed list of mandatory documents, but a lack of evidence will almost always result in nonconformities.

ISO addresses this flexibility directly, noting that documented information should be “appropriate to the organization” rather than excessive or standardized.

What ISO 9001 Does Not Require

ISO 9001 does not mandate a quality manual, excessive paperwork, specific software tools, or templated processes. Organizations are free to design a QMS that reflects how they actually operate. Auditors are far more concerned with effectiveness and alignment than with the volume of documentation.

In short, ISO 9001 is not about bureaucracy. It is about running a controlled, measurable, and continuously improving business system that reliably meets customer and regulatory expectations.

At Axipro, we simplify ISO 9001 certification requirements, helping you pass audits faster and secure certification without compliance stress.

Steps to Achieve ISO 9001 Certification

iso-9001-certification-requirements-guide

The journey to certification involves several key steps. Follow this roadmap to simplify the process:

Step 1: Understand The Standard

Study the ISO 9001:2015 standard carefully. Familiarize yourself with its principles, clauses, and requirements. So, don’t worry if it seems overwhelming at first—we’re here to help.

Step 2: Conduct A Gap Analysis

Compare your current processes to ISO 9001 requirements. Identify areas needing improvement and prioritize critical gaps. Henceforth, this step acts as your starting line.

Step 3: Develop A Quality Management System

Design and document your QMS in accordance with ISO 9001 guidelines. Include policies, procedures, and processes to meet requirements.

Step 4: Train Your Team

Educate employees about ISO 9001 standards. Ensure everyone understands their roles in maintaining compliance and achieving goals. Teamwork truly makes the dream work here.

Step 5: Implement Changes

Put your documented QMS into action. Monitor progress, address challenges, and fine-tune processes for effectiveness. The ISO 9001 certification process is all about execution.

Step 6: Conduct Internal Audits

Perform regular internal audits to evaluate compliance. Identify areas for improvement and resolve non-conformities promptly.

Step 7: Select A Certification Body

Choose an accredited certification body to assess your QMS. Certification auditors review your system for conformity. Remember to select a trusted partner. In this regard, Axipro would be your selection.

Step 8: Achieve Certification

Once the audit is complete, receive your ISO 9001 certificate. Therefore, maintain compliance by adhering to the standard’s requirements. Congratulations—you’ve made it!

Common Challenges & Solutions

Certification isn’t without its hurdles. Here’s how to tackle common obstacles:

Challenge: Lack of leadership support.

  • Solution: Educate management on the benefits of certification for business growth and customer trust.

Challenge: Resistance to change.

  • Solution: Involve employees early, explaining how the changes improve their work environment.

Challenge: Insufficient resources.

  • Solution: Allocate a dedicated budget and team for ISO 9001 implementation.

Therefore, by addressing these challenges head-on, your organization can streamline the certification process effectively.

End Note

ISO 9001 certification is a game-changer for businesses aiming to excel. It enhances credibility, customer satisfaction, and operational excellence. Think of it as a roadmap to achieving consistent quality and trust.

To get certified to ISO 9001, an organization must implement and operate a practical Quality Management System that reflects how the business actually works, demonstrates leadership accountability, and consistently meets customer and regulatory requirements.

This includes defining the scope of the system, understanding business context and stakeholder expectations, establishing clear processes and responsibilities, applying risk-based thinking, ensuring staff competence, controlling documented information, monitoring performance through internal audits and management reviews, and taking corrective action to drive continual improvement.

Certification is achieved by providing objective evidence to an accredited external auditor that these requirements are embedded in daily operations and effectively maintained.

Hence, start your journey today, and position your organization as a leader in quality and trustworthiness. Remember, the road may be challenging, but with professional assistance from Axipro, the destination is worth it.

Frequently Asked Questions

How long does it take to achieve ISO 9001 certification?

The timeline varies depending on your organization’s readiness. It typically takes 6 to 12 months for most businesses.

No, certification is voluntary. However, many industries and clients require it for business partnerships or contracts.

Yes, ISO 9001 is scalable and applies to businesses of all sizes, industries, and locations.

ISO 9001 certification requires renewal every three years. Regular audits ensure continued compliance with the standard.

At Axipro, we turn ISO 9001 certification requirements into a clear action plan that saves time, cost, and approval delays.

Axipro Author

Picture of Thatware

Thatware

Blog Highlights

Explore More Articles

ISO 27001 for Startups

ISO/IEC 27001 certificates nearly doubled in a single year, from 48,671 in 2023 to 96,709 in 2024, according to ISO’s own certification survey. A big share of that jump comes from startups, not enterprises. The reason is simple: buyers stopped taking “we take security seriously” at face value, and a certificate is the fastest way to prove it.  This guide covers when a startup should pursue ISO 27001, what it costs, how long it takes, and how a small team gets certified without a dedicated security department. What Is ISO 27001 and Why It Matters for Startups ISO/IEC 27001 is the international standard for information security management. It doesn’t hand you a checklist of firewalls to buy. Instead, it asks you to build and run an Information Security Management System (ISMS): a documented, repeatable way of finding your security risks and doing something about them. Certification means an accredited third party checked that your ISMS works and matches the standard. For a startup, that distinction matters. You’re not being graded on whether you own expensive tools. You’re being graded on whether you can show a system, which is exactly what an enterprise buyer’s procurement team wants to see before they sign. The Core Principles: Confidentiality, Integrity, and Availability Everything in ISO 27001 traces back to the CIA triad: confidentiality, integrity, and availability. Confidentiality means only the right people see the data. Integrity means the data is accurate and hasn’t been tampered with. Availability means the data is there when someone needs it. Every control you put in place, and every risk you assess, ties back to protecting one of those three properties. ISO puts it plainly: an ISMS that meets the standard preserves the confidentiality, integrity, and availability of information by running a risk management process. Keep the triad in mind, and the rest of the framework stops feeling abstract. How ISO 27001 Differs from Other Security Frameworks for Early-Stage Companies SOC 2 is the framework startups usually bump into first, especially when selling into the US. It results in an attestation report from a CPA firm, scoped to specific systems. ISO 27001 is a certification, recognized in over 150 countries, and it covers your whole organization through a formal ISMS with management reviews and company-wide risk assessment. The two overlap heavily. Roughly 70 to 80 percent of the controls line up, so if you do one, the second gets much cheaper. The real difference is structure. SOC 2 checks whether specific controls work. ISO 27001 checks whether you’ve built a management system that keeps those controls working over time. It also aligns closely with GDPR, which is why it travels well in Europe. Insider Note: Auditors can usually tell within an hour whether your ISMS is real or was assembled the week before the audit. A management review meeting with actual notes, decisions, and follow-ups from three months ago is worth more than a perfect-looking policy binder with no evidence anyone ever used it. When Should a Startup Pursue ISO 27001 Certification? The honest answer: when a deal, a market, or an investor is asking for it, or is about to. Certifying purely because it feels responsible is a good way to burn cash and calendar time you don’t have yet. Early-Stage vs. Growth-Stage: Timing the Certification At pre-seed and seed, ISO 27001 is usually early unless you’re selling into regulated industries or the EU from day one. Your product and processes are still shifting, and certifying a moving target means re-documenting everything a quarter later. At Series A and beyond, the math changes. Deals get bigger, buyers get more careful, and investor due diligence starts probing your security posture. Certifying while you’re 15 to 40 people is often the sweet spot: mature enough to have stable processes, small enough that scoping the ISMS is still manageable. When ISO 27001 Might Be Overkill for Your Startup If your customers are US SMBs who only ever ask for SOC 2, leading with ISO 27001 may be solving a problem you don’t have. If you’re pre-revenue and still hunting for product-market fit, your time is better spent shipping. And if no one in your sales pipeline has ever mentioned a certificate, that silence is data. Pro Tip: Pull your Last 20 Security Questionnaires Before you commit, pull your last 20 security questionnaires or RFPs and count how many explicitly asked for ISO 27001 versus SOC 2 versus nothing. That single tally answers the “which framework, and when” question faster than any consultant’s discovery call. Key Benefits of ISO 27001 for Startups Unlocking Enterprise Sales and Bigger Deals The clearest return is revenue you couldn’t touch before. Large buyers often won’t even start a security review without a recognized certificate on file. ISO 27001 gets you past the first gate of enterprise sales, and it shortens the review itself because a big chunk of the questionnaire is already answered by your certification. Building Investor and Board Confidence Certification signals operational maturity. When an investor sees a functioning ISMS, they see a founder who can build systems, not only ship features. That plays well in investor due diligence, where a security gap can stall a term sheet, and it gives your board something concrete to point to on risk. Establishing Customer Trust from Day One A certificate is third-party proof, and third-party proof beats self-assurance every time. For a young company with no brand equity yet, it’s a shortcut to being taken seriously by customers who’ve never heard of you. Creating a Scalable Security Foundation Because ISO 27001 makes you build a system rather than a one-off fix, it scales as you grow. New hires, new products, and new data types slot into an ISMS you already run. You’re not rebuilding security from scratch at every stage. Reducing Long-Term Compliance Costs Adding SOC 2, HIPAA, or ISO 42001 later is far cheaper once an ISMS exists, thanks to that 70 to 80 percent control overlap. The first framework is the expensive one.

Most organizations think their AI governance is further along than it is. McKinsey’s 2026 AI Trust Maturity Survey of roughly 500 organizations found an average maturity score of 2.3 out of 4, and only about a third reported level three or higher in strategy, governance, and agentic AI oversight. Adoption is outpacing control, and regulators have noticed. An AI governance maturity model gives you a way to measure that gap honestly. This guide covers what a maturity model is, the six dimensions it should measure, the five levels most models use, and how to assess your own organization and build a roadmap to the next level. What Is an AI Governance Maturity Model? An AI governance maturity model is a structured framework that describes how capable an organization is at governing its AI systems, usually across five progressive levels. The concept borrows directly from the Capability Maturity Model (CMM) that software engineering has used since the early 1990s: define the capability, describe what it looks like at each stage of development, and score yourself against it. The purpose is diagnosis. A maturity model tells you where governance is strong, where it’s theater, and where it doesn’t exist at all. How It Differs from General AI Governance Frameworks Frameworks like the NIST AI Risk Management Framework or ISO/IEC 42001 tell you what good governance contains: policies, risk assessments, accountability structures, monitoring. A maturity model tells you how well you’re doing those things today. The framework is the destination. The maturity model is the odometer. That distinction matters in practice. Plenty of companies can point to an AI policy document. Far fewer can show that the policy changes what teams actually ship. Why Enterprises Need a Maturity Model Three reasons. First, budget: you can’t prioritize governance investment without knowing which dimension lags. Second, accountability: a maturity score gives boards something concrete to track quarter over quarter. Third, regulation: the EU AI Act and frameworks like ISO 42001 assume a functioning management system, and a maturity assessment is the fastest way to find out whether yours would survive scrutiny. Core Dimensions of an AI Governance Maturity Model A useful model measures more than policy coverage. Six dimensions show up consistently across the credible models, including the IEEE-USA flexible maturity model built on the NIST AI RMF. Strategy and leadership. Does the organization have a stated position on AI risk, an executive owner (increasingly a Chief AI Officer), and board visibility? Gartner’s 2025 polling found 55% of organizations now have an AI board or dedicated oversight committee, which means nearly half still govern by improvisation. Policies, standards, and accountability. Written policies mapped to regulations, a RACI matrix for AI decisions, and clear escalation paths. Many organizations adapt the three lines of defense model from financial risk: the teams building AI, the risk function overseeing them, and internal audit checking both. Data governance and model lifecycle. Training data lineage, quality controls, and lifecycle management from development through deployment, monitoring, and retirement. This is where AI governance meets MLOps, and where mature organizations maintain an AI register, a live inventory of every model and system in production. Risk, compliance, and ethics. Risk classification of AI systems, impact assessments, bias and fairness testing, and explainability requirements. Banks will recognize the DNA of model risk management under SR 11-7 here. People, skills, and culture. Training, role clarity, and whether people outside the governance team actually understand their obligations. Tools, automation, and monitoring. Drift detection, automated policy checks, audit logging, and dashboards. Governance that lives in spreadsheets caps out around level three. The 5 Levels of AI Governance Maturity Level 1: Ad Hoc / Initial AI use happens without oversight. There’s no inventory, no policy, or a policy nobody follows. Shadow AI is common, and risk surfaces only when something breaks publicly. Level 2: Developing / Repeatable Someone has been assigned responsibility. A draft policy exists, a partial inventory exists, and reviews happen for high-profile projects. The practices are repeatable but depend on specific people rather than defined processes. Level 3: Defined / Structured Governance is documented, standardized, and applied across the organization. There’s a governance committee, a risk classification scheme, defined lifecycle gates, and mandatory training. Most organizations pursuing ISO 42001 certification are working to reach and formalize this level. Level 4: Managed / Metrics-Driven Governance produces numbers. Coverage rates, review cycle times, incident counts, and risk reduction are measured and reported to leadership. Controls are enforced by tooling rather than goodwill, and audits confirm the system works as described. Level 5: Optimized / Adaptive Governance improves itself. Monitoring feeds back into policy, controls adapt to new model types (agentic systems being the current test), and the organization anticipates regulatory change rather than reacting to it. Almost nobody is here yet, and that’s fine. Level 5 is a direction, not a deadline. Insider Note: In assessments, the most common self-scoring error is claiming level 3 on the strength of documents alone. If your policy says every model gets a pre-deployment review and your inventory shows 40 models but your review log shows 6, you’re at level 2. Evidence beats paperwork every time, and auditors check the logs first. AI Governance Maturity Matrix The matrix crosses dimensions with levels so you can score each one independently. Organizations are rarely uniform: it’s normal to sit at level 3 on policy and level 1 on monitoring. For scoring, keep the rubric simple: 1 to 5 per dimension, scored on evidence you could show an auditor, not on intentions. Board-level indicators (does the board see AI risk reporting?) and operational indicators (does every production model have a completed impact assessment?) should be scored separately, because they fail independently. How to Assess Your Current AI Governance Maturity Start with a baseline self-assessment. Pull together a cross-functional group covering engineering, legal, risk, security, and the business owners of major AI use cases, and score each dimension against the matrix. Half a day is usually enough for a first pass. For each dimension, the

Most organizations get ISO 42001 certified in 2 to 9 months. Companies that already hold ISO 27001 regularly land in the 2 to 5 month range, while enterprises with sprawling AI portfolios and no existing management system can take 12 months or more. The audit itself only takes days. Almost the entire calendar goes into building and operating your AI Management System (AIMS) long enough to produce evidence an auditor can actually check. That is the short answer. The longer answer depends on your starting point, your scope, and how quickly you can get a certification body on the schedule. This article breaks down the full timeline phase by phase, the factors that stretch or compress it, and what the recertification cycle looks like once you hold the certificate. Typical ISO 42001 Certification Timeline at a Glance ISO/IEC 42001:2023 is the first international standard for AI management systems, published in December 2023. Because it follows the same harmonized structure as ISO 27001 and ISO 9001, the certification process will feel familiar to anyone who has been through a management system audit: build the system, run it, pass a Stage 1 and Stage 2 audit, then maintain it through annual surveillance. Here is how timelines typically break down by company size. Average Timeline for Small Businesses Small companies move fastest because scope stays contained. A startup with two or three AI systems, a handful of decision makers, and short approval chains can finish scoping in a week and get policies signed off in days rather than weeks. The realistic floor for a small business starting from scratch is around 3 months. With an existing ISO 27001 program and a compliance platform already collecting evidence, 2 months is achievable. Average Timeline for Mid-Sized Companies Mid-sized companies usually take 6 to 9 months. The AI inventory is growing, more departments are touching AI systems, and risk assessments have to cover more use cases. Coordination becomes the hidden cost: getting engineering, legal, and product to agree on an AI policy takes longer than writing the policy itself. Average Timeline for Enterprises Enterprises should plan for 9 to 12 months, sometimes longer. The main drivers are AI system sprawl across business units, longer procurement cycles for certification bodies, and audits that take more days. The Stage 2 audit for a large multinational can run two weeks or more on its own, and internal alignment before the audit takes far longer than the audit itself. Breakdown of the ISO 42001 Certification Timeline by Phase The phases below overlap in practice. Treat the durations as effort estimates for a reasonably resourced program, not a strict sequence. Phase 1: Scoping and Gap Analysis (2–4 Weeks) Everything starts with two questions: which AI systems are in scope, and how far is your current governance from what the standard requires? The gap analysis maps your existing policies and controls against the standard’s clauses and Annex A controls, and produces the project plan for everything that follows. Get the scope wrong here and every later phase inherits the mistake. Phase 2: AIMS Design, Leadership, and AI Policy Development (2–4 Weeks) This phase establishes the skeleton of the management system: the AI policy, governance roles, objectives, and the leadership commitments the standard requires. Executive sign-off is the gating item. The documents are not hard to write. Getting senior leadership to formally own AI governance is where programs stall. Phase 3: AI Risk and Impact Assessments (2–6 Weeks) ISO 42001 requires both AI risk assessments and AI impact assessments, and the distinction matters. Risk assessments look at what could go wrong for the organization. Impact assessments look at consequences for individuals and society, which is a newer discipline for most teams. This phase takes longer when you have many AI systems, high-risk use cases, or no prior methodology to adapt. The output feeds directly into your Statement of Applicability (SoA), the document that maps which Annex A controls you have selected and why. Insider Note: Impact assessments are where auditors probe hardest, because they are the most distinctive part of ISO 42001 compared with ISO 27001. A recycled security risk register with “AI” pasted into it will get picked apart in Stage 2. Build the impact assessment methodology properly the first time. Phase 4: Controls Implementation (2–10 Weeks) The longest phase. Here you implement the Annex A controls selected in your SoA: AI system lifecycle documentation, data governance for training data, human oversight mechanisms, transparency measures, supplier management for third-party AI, and so on. Duration depends almost entirely on the gap analysis results. Organizations with mature engineering practices often find they already do much of this and just need to document it. Organizations without formal AI development processes are building from zero. Phase 5: Documentation, Training, and Evidence Collection (2–8 Weeks) Certification requires proof that the system operates, not just that it exists on paper. That means records: training completion logs, risk assessment outputs, review meeting minutes, monitoring reports. This phase runs partly in parallel with implementation, but it cannot be compressed below a certain floor because auditors want to see evidence generated over time, not a folder of documents all created the week before Stage 1. Phase 6: Internal Audit and Management Review (2–4 Weeks) The standard requires an internal audit of the AIMS and a formal management review before the certification audit. This is your dress rehearsal. A good internal audit surfaces nonconformities while they are still cheap to fix. Skipping or rushing it is a false economy that shows up later as Stage 2 findings. Phase 7: Stage 1 Certification Audit (1–2 Weeks) The certification body reviews your documentation and assesses readiness for Stage 2. The audit itself takes 1 to 3 days for most organizations. The auditor examines your scope statement, AI policy, risk and impact assessment methodology, SoA, and internal audit results, then issues findings. The 1–2 week window covers the audit plus the report. Phase 8: Closing Nonconformities (2–4 Weeks) Almost every Stage 1 produces findings.