- QuickstartGet from a new account to your first AI conformance assessment.
- Uploading your documentsAdd your documented information so the AI can assess it against your standards.
- Inviting your teamAdd colleagues to your organisation and give them the right role.
- Choosing standardsAdopt the ISO standards you're pursuing and run them as one integrated management system.
- Clauses, controls & scopeHow StayEvident models a standard's clauses and controls, and how scope and exclusions work.
- AI assessmentsHow the AI assesses each clause against your documents, and how you review its findings.
- Evidence linkingConnect documents and register records to the clauses they evidence.
- Statement of ApplicabilityGenerate an SoA from your scope decisions — always in sync with what you've assessed.
- Audit-day mode & audit packWalk your auditor through each clause with its confirmed evidence, or hand over a PDF pack.
- Registers & modulesThe operational registers StayEvident provides, and how they switch on for your standards.
- Roles & permissionsThe four built-in roles and what each can do.
- Security & sign-inSign-in options, two-factor authentication, data isolation and the audit trail.
- Billing & plansHow plans, limits and AI clause assessments work.
- FAQ & troubleshootingAnswers to common questions, and what to check when something doesn't look right.
- GlossaryThe terms used throughout StayEvident and the ISO standards it supports.
- No matching pages.
Documentation menu▾
Core Concepts/Clauses, controls & scope
Clauses, controls & scope
How StayEvident models a standard's clauses and controls, and how scope and exclusions work.
Clauses and controls
Every standard is a tree of numbered requirements. ISO 9001 and ISO/IEC 27001 share the harmonised structure of clauses 4–10, and ISO/IEC 27001 adds the Annex A controls in four themes (A.5–A.8). Assessments and evidence work at the leaf level — the most specific requirement — so “9.2” is assessed through its sub-clauses, and each Annex A control is assessed on its own.
Scope statement
Each adopted standard has a scope statement: the boundaries of your management system. Record it on the standard’s applicability page. It’s printed on your Statement of Applicability and audit pack.
Exclusions
You can declare a requirement not applicable at any level the standard allows, each with a justification:
- Excluding ISO 9001’s 8.3 Design and development is one decision with one justification — and it applies to every sub-clause beneath it.
- In ISO/IEC 27001 you can exclude an individual Annex A control or a whole theme.
Exclusions take effect everywhere. Excluded clauses aren’t assessed (so they don’t use your AI allowance), don’t count as gaps, and are shown as excluded with their justification on your Statement of Applicability. Modules governed only by excluded clauses switch off too.
For ISO/IEC 27001 Annex A controls you can also record why a control is included — for example, a risk treatment, a legal requirement or a contractual obligation.
Coverage
The Conformance overview shows readiness for each adopted standard: how many in-scope clauses are conformant, partial, gaps or not yet addressed. Open a standard to see clause-by-clause verdicts and its gap register.