Clause map - ISO 9001:2015¶
One row per distinct obligation of ISO 9001:2015: what the duty concerns,
the document that implements it, how the system complies, where the
evidence lands, and its status. The standards themselves are not
reproduced here. Source of truth: docs/clause-map-9001.csv.
Clause 4¶
| Req ID | Clause | Obligation | Implementing document | Statement of compliance | Section | Evidencing register | Records folder | Status | Integrated with |
|---|---|---|---|---|---|---|---|---|---|
| Q4.1-1 | 4.1 | Organisational context and keeping it under review | context-interested-parties-compliance-obligations | Handled by the Context Review Method (section 3.1) of Context, Interested Parties & Compliance Obligations, which maintains the issues table as part of the controlled document so every change is a revision through the PR lifecycle. Context is worked as a standing slice of the rolling management review, with out-of-cycle sessions on trigger events; sessions are logged in the Management Review Log register and their records committed to docs/records/management-reviews/. | Context review method | Documented | OHS4.1-1 | ||
| Q4.2-1 | 4.2 | Interested parties and their needs and expectations | context-interested-parties-compliance-obligations | Answered by the Interested Parties section (3.2) of Context, Interested Parties & Compliance Obligations, whose analysis table at 3.2.3 is maintained as part of the controlled document on the same management review cadence and trigger events as the context issues, evidenced in docs/records/management-reviews/. Obligations arising from that analysis are actioned in the compliance registers per the Compliance Obligations Procedure. | Interested parties | Documented | OHS4.2-1 | ||
| Q4.3-1 | 4.3 | Scope of the integrated management system | ims-scope-statement | Carried entirely by the IMS Scope Statement: section 3.1 draws the system boundary and records how it was determined, and section 3.4 holds any exclusion justifications, which the template currently records as none and instantiate.py regenerates from the clause map rather than hand-editing. The document is itself the maintained documented information for scope, controlled under the Document & Record Control Procedure, indexed in the Document Register, and available through the published IMS site and on request. | Scope | Document Register | Documented | OHS4.3-1 | |
| Q4.4.1-1 | 4.4.1 | The management system as interacting processes | ims-scope-statement | Handled by the System processes section (3.2) of the IMS Scope Statement, whose process map defines the sixteen core processes and how they interact as one plan-do-check-act loop, with working-level detail held in each process's slug-matched procedure or plan. Supporting machinery is divided across risk-opportunity-hazard-methodology with the Risk & Opportunity Register for process risks and opportunities, monitoring, internal audit and management review for evaluation, and management-of-change-procedure plus ims-objectives-improvement-plan for change and improvement. | System processes | Documented | OHS4.4-1 | ||
| Q4.4.2-1 | 4.4.2 | Documented information supporting the system processes | ims-scope-statement | Governed by the documented-information passage of the System processes section (3.2) in the IMS Scope Statement, following the system's standing split between documents and records. Controlled documents live under docs/ and are indexed in the Document Register, while evidence of how each process actually ran accumulates append-only in the docs/records/ subfolders and per-job operational files, where a correction is always a new record. | System processes | Document Register | operational | Documented |
Clause 5¶
| Req ID | Clause | Obligation | Implementing document | Statement of compliance | Section | Evidencing register | Records folder | Status | Integrated with |
|---|---|---|---|---|---|---|---|---|---|
| Q5.1.1-1 | 5.1.1 | Active top-management leadership of the system | quality-ohs-policy | Carried by Section 4.1 (Leadership commitments) of the Quality & OH&S Policy, where {{ROLE_TOP_MANAGEMENT}} takes personal accountability for the IMS delivering its intended results. Demonstration lands in management review records, resourcing decisions and day-to-day conduct rather than in a dedicated register. | Leadership commitments | Documented | OHS5.1-1 | ||
| Q5.1.2-1 | 5.1.2 | Customer focus commitments from top management | quality-ohs-policy | Expressed through the customer-focus commitments in Section 3.1 (Quality commitments, customer focus) of the Quality & OH&S Policy, issued by {{ROLE_TOP_MANAGEMENT}}. The machinery behind those commitments is the IMS assessment method and routine delivery and feedback monitoring, with customer satisfaction a standing agenda item at management review, where the evidence accrues. | Quality commitments (customer focus) | Documented | |||
| Q5.2.1-1 | 5.2.1 | Establishing the quality policy | quality-ohs-policy | The Quality & OH&S Policy is itself the implementing document: {{ROLE_TOP_MANAGEMENT}} issues it, and its Section 3 policy statements carry the policy commitments, with every objective in the IMS Objectives & Improvement Plan and the Objectives & Targets register tracing back to a Section 3 commitment. The policy is kept fit through the review cadence in its frontmatter and re-examination at management review whenever context materially changes. | Policy statements | Documented | OHS5.2-1 | ||
| Q5.2.2-1 | 5.2.2 | Communication and control of the policy | quality-ohs-policy | Section 3.4 (Communication of the policy) of the Quality & OH&S Policy sets the policy's handling arrangements, working with the Document & Record Control Procedure. The policy lives as a controlled document indexed in the Document Register; workforce acknowledgement campaigns land in the Policy Acknowledgements register with snapshot records in docs/records/acknowledgements/; and the channel for external interested parties is settled as an [ORG-DECISION] at instantiation. | Communication of the policy | Document Register; Policy Acknowledgements | acknowledgements | Documented | OHS5.2-1 |
| Q5.3-1 | 5.3 | Assigning and communicating IMS roles and authorities | ims-scope-statement | Section 3.3 (Roles, responsibilities and authorities) of the IMS Scope Statement carries the role assignments for the IMS, with process-level ownership shown on the Section 3.2 process map and the People register indexing who currently holds each role. Assignments are communicated through induction, the scope statement itself and the published IMS site. | Roles, responsibilities and authorities | People | Documented | OHS5.3-1 |
Clause 6¶
| Req ID | Clause | Obligation | Implementing document | Statement of compliance | Section | Evidencing register | Records folder | Status | Integrated with |
|---|---|---|---|---|---|---|---|---|---|
| Q6.1.1-1 | 6.1.1 | Determining the risks and opportunities requiring attention | risk-opportunity-hazard-methodology | Risks and opportunities are determined through the Assessment flow (section 3.3) of risk-opportunity-hazard-methodology, which runs proactively: on first identification, before any planned change proceeds via management-of-change-procedure, and on the band review cadence, never only after something has gone wrong. Every confirmed item becomes a row in the Risk & Opportunity Register, the live index of what the system is acting on. | Assessment flow | Risk & Opportunity Register | Documented | OHS6.1.1-1 | |
| Q6.1.2-1 | 6.1.2 | Planning proportionate actions on risks and opportunities | risk-opportunity-hazard-methodology | Actions arising from assessment are planned under the Action planning section (3.7) of risk-opportunity-hazard-methodology, which builds each owned, dated action into the everyday IMS process where the work actually happens and sizes it under the section's proportionality and constraints rules, with any limiting constraints recorded honestly in the register row's Treatment narrative. The Risk & Opportunity Register indexes every action through its Treatment and Status fields. | Action planning | Risk & Opportunity Register | Documented | OHS6.1.4-1 | |
| Q6.2.1-1 | 6.2.1 | Setting and maintaining documented quality objectives | ims-objectives-improvement-plan | Quality objectives are set, qualified and documented through the two-level model in ims-objectives-improvement-plan: the Company-wide objectives table (section 3.2) is the authoritative statement of each objective, section 3.2.1 sets the qualities every objective must satisfy, and section 3.2.3 covers communication. The Objectives & Targets register is the live index of current result, last-measured date and status; changes are always made to the document through the PR lifecycle and mirrored to the register, and retained evidence of results accumulates in docs/records/management-reviews/ via the review-slice snapshots. | Company-wide objectives | Objectives & Targets | Documented | OHS6.2.1-1; OHS6.2.2-1 | |
| Q6.2.2-1 | 6.2.2 | A delivery plan behind every objective | ims-objectives-improvement-plan | Each objective, company-wide and sleeve, is planned through the Objective planning section (3.2.2) of ims-objectives-improvement-plan, whose planning table is completed before an objective is set to Active. The plan is summarised in the objective's Objectives & Targets register row, and an objective needing resources not yet provided stays Proposed until {{ROLE_TOP_MANAGEMENT}} commits them. | Objective planning | Objectives & Targets | Documented | OHS6.2.2-1 | |
| Q6.3-1 | 6.3 | Planning changes to the management system | management-of-change-procedure | Changes to the system run through the Change assessment steps (section 3.1) of management-of-change-procedure: a fixed sequence in which the assessing role and the proposer weigh the proposed change against the procedure's checklist before implementation, a decision to proceed is recorded, execution is planned, and a post-implementation review confirms what the change actually caused. Assessment evidence is retained with the thing changed, in the job file or the PR description. | Change assessment | Documented | OHS8.1.3-1 |
Clause 7¶
| Req ID | Clause | Obligation | Implementing document | Statement of compliance | Section | Evidencing register | Records folder | Status | Integrated with |
|---|---|---|---|---|---|---|---|---|---|
| Q7.1.1-1 | 7.1.1 | Resources for the management system | ims-scope-statement | {{ROLE_TOP_MANAGEMENT}} determines and provides what the IMS needs through the Resources section of ims-scope-statement, with needs surfacing through the defined channels (objective plans in ims-objectives-improvement-plan, management review as a standing input, corrective actions and change assessments, and worker consultation) and resourcing decisions recorded in the Management Review Log. Resources sourced from outside the organisation are controlled under procurement-contractor-management-procedure. | Resources | Documented | OHS7.1-1 | ||
| Q7.1.2-1 | 7.1.2 | People resourcing for the management system | competence-training-awareness-procedure | Carried by the Competence determination section of competence-training-awareness-procedure: role coverage is indexed through the IMS Roles field on People register rows, and {{ROLE_TOP_MANAGEMENT}} assesses adequacy at least at each management review, with the outcome evidenced in docs/records/management-reviews/. | Competence determination | Documented | |||
| Q7.1.3-1 | 7.1.3 | Infrastructure provision and upkeep for delivery work | operational-control-service-delivery-procedure | The Infrastructure and environment section of operational-control-service-delivery-procedure sets the provision and maintenance arrangements for the infrastructure delivery depends on. Recurring maintenance surfaces when due through the Schedule register, completed-maintenance evidence stays with the asset or job records, and equipment used for measurement is additionally controlled under monitoring-measurement-calibration-procedure and the Equipment & Calibration Register where that capability applies. | Infrastructure and environment | Documented | |||
| Q7.1.4-1 | 7.1.4 | Working conditions needed for service delivery | operational-control-service-delivery-procedure | Also carried by the Infrastructure and environment section of operational-control-service-delivery-procedure, which defines the working conditions delivery needs. Concerns are raised through the consultation channels or the {{ROLE_WORKER_REP}}, and an environment issue that is also a hazard is logged in the Hazard Register. | Infrastructure and environment | Documented | |||
| Q7.1.5.1-1 | 7.1.5.1 | Dependable resources for monitoring and measurement | monitoring-measurement-calibration-procedure | The Calibration and measuring equipment section of monitoring-measurement-calibration-procedure carries this leaf: instruments underpinning valid quality or OH&S results are registered and controlled through the Equipment & Calibration Register, and fitness-for-purpose evidence is committed append-only to docs/records/calibration/, linked from each instrument's register row. Where no such equipment is used, conformity is verified through competent people and defined methods and the absence is recorded in ims-scope-statement; the equipment-control steps are gated by the calibration capability flag. | Calibration | Equipment & Calibration Register | calibration | Documented | |
| Q7.1.5.2-1 | 7.1.5.2 | Calibration, traceability and care of measuring equipment | monitoring-measurement-calibration-procedure | Also handled in the Calibration and measuring equipment section of monitoring-measurement-calibration-procedure: each registered instrument is tracked through its Equipment & Calibration Register row, calibration evidence lands append-only in docs/records/calibration/, and schedule visibility rides the Schedule register, whose status formula surfaces overdue calibration. Where a delivered result is affected by an instrument problem, the matter routes through the nonconformity process via the Nonconformity & CAPA Register; the machinery is gated by the calibration capability flag settled at instantiation. | Calibration | Equipment & Calibration Register | calibration | Documented | |
| Q7.1.6-1 | 7.1.6 | Organisational knowledge and where it lives | competence-training-awareness-procedure | The Organisational knowledge section of competence-training-awareness-procedure gives operational knowledge a known home: the controlled documents, templates, guides and training pages for how the system is run, the project and delivery knowledge locations named at instantiation for how the work is done, and the People, Training Curriculum and Training Log registers for who knows what. Upkeep rides the access arrangements in document-record-control-procedure and the departure handover steps, and acquisition of further knowledge is routed by the {{ROLE_QUALITY_MANAGER}} through the training matrix. | Organisational knowledge | Documented | |||
| Q7.2-1 | 7.2 | Competence defined, delivered and evidenced per role | competence-training-awareness-procedure | The Training matrix section of competence-training-awareness-procedure is the machinery: Training Curriculum items crossed with each person's IMS Roles in the People register form the competence and training matrix, operated by the {{ROLE_QUALITY_MANAGER}} with the {{ROLE_OHS_COORDINATOR}} for anything affecting OH&S performance. The Training Log indexes outcomes live, and the retained evidence is the append-only snapshots committed to docs/records/training/ by tools/snapshot_register.py, with external certificates attached to the relevant Training Log rows. | Training matrix | Training Curriculum; Training Log | training | Documented | OHS7.2-1 |
| Q7.3-1 | 7.3 | Worker awareness of the system and their part in it | competence-training-awareness-procedure | The Awareness section of competence-training-awareness-procedure delivers the awareness topics as curriculum items through induction and toolbox talks, chased for currency by the monthly reminder automation. Evidence lands in Training Log rows and docs/records/training/ snapshots, with policy awareness additionally evidenced through the Policy Acknowledgements register and the campaign snapshots under docs/records/acknowledgements/. | Awareness | Documented | OHS7.3-1 | ||
| Q7.4-1 | 7.4 | Internal and external communications of the management system | communication-consultation-participation-procedure | The Communication matrix section of communication-consultation-participation-procedure holds internal and external matrix tables covering every communication the IMS needs. Matrix changes are revisions to the document through the PR lifecycle, with worker consultation where a change affects workers; audiences, roles and contact points resolve from the People register, and each row's aim is evaluated annually as an input to management review. | Communication matrix | Documented | OHS7.4.1-1 | ||
| Q7.5.1-1 | 7.5.1 | Composition and extent of the IMS documentation | document-record-control-procedure | The Document control framework section of document-record-control-procedure defines what the IMS documentation comprises, all of it indexed in the Document Register and held in the three-tier documents, records and registers model. The extent is deliberately scaled to the organisation's size and complexity, with a document that adds no operational value challenged through the procedure rather than padded. | Document control framework | Document Register | Documented | OHS7.5.1-1 | |
| Q7.5.2-1 | 7.5.2 | Controls when creating and updating documents | document-record-control-procedure | The Creating and updating section of document-record-control-procedure is the machinery: every controlled document carries YAML frontmatter with fields defined solely in schemas/document-types.yml, lives as plain-text Markdown in the Git repository, and moves through the branch, PR review and merge lifecycle, where the merge is the approval event. The Document Register row is synced in the same change, and tools/check_docs.py enforces conformance and separation of duties in CI. | Creating and updating | Document Register | Documented | OHS7.5.2-1 | |
| Q7.5.3-1 | 7.5.3 | Lifecycle control and protection of documented information | document-record-control-procedure | The Control of documents section of document-record-control-procedure governs controlled documentation across its in-service life, anchored on the single source on main, the Document Register and generated index as retrieval aids, and the Git repository's access control, branch protection and full history as the safeguards, with retention settings fixed at instantiation. External documents the system relies on are indexed as external-origin Document Register entries kept current by the {{ROLE_DOCUMENT_CONTROLLER}}. Evidence under docs/records/ is protected structurally by the append-only rule, with a wrong record corrected by a new record rather than an edit. | Control of documents | Document Register | Documented | OHS7.5.3-1 |
Clause 8¶
| Req ID | Clause | Obligation | Implementing document | Statement of compliance | Section | Evidencing register | Records folder | Status | Integrated with |
|---|---|---|---|---|---|---|---|---|---|
| Q8.1-1 | 8.1 | Operational planning and control of service delivery | operational-control-service-delivery-procedure | Operational planning and control run through the Operational planning section of operational-control-service-delivery-procedure, which opens a job file for every job as the single home of the delivery plan and the evidence that work ran to it. Changes to the system route through the Change assessment steps of management-of-change-procedure, and outsourced processes stay controlled through the Controls on providers section of procurement-contractor-management-procedure with live status on the Supplier & Contractor Register. Per-job evidence is marked operational in the clause maps and lives in job files rather than docs/records/. | Operational planning | Supplier & Contractor Register | operational | Documented | OHS8.1.1-1; OHS8.1.3-1; OHS8.1.4.3-1 |
| Q8.2.1-1 | 8.2.1 | Customer communication channels and responsible roles | customer-requirements-contract-review-procedure | Customer communication is handled through the Customer communication section of customer-requirements-contract-review-procedure, which fixes a channel, practice and responsible role for each subject, drawing service information from product-market-offer-definitions. Feedback and complaints are indexed in the Customer Feedback & Complaints register and job correspondence is filed in the job file. | Customer communication | Customer Feedback & Complaints | Documented | ||
| Q8.2.2-1 | 8.2.2 | Product and market offer requirement definitions | product-market-offer-definitions | product-market-offer-definitions holds the generic definition of every product and market offer within IMS scope, with the Product & Market Offers register as the live index. Requirements enter each definition through the requirements-determination step of customer-requirements-contract-review-procedure, and the document changes only when an offer itself changes. | Offer definitions | Product & Market Offers | Documented | ||
| Q8.2.3.1-1 | 8.2.3.1 | Review of requirements before commitment to work | customer-requirements-contract-review-procedure | No quote, proposal, tender or contract is committed to until the Review before commitment section of customer-requirements-contract-review-procedure has run, scaled from a short checklist pass for routine work matching a defined offer to a deliberate review meeting for novel or unusual-terms work; the thresholds and commitment authority are an [ORG-DECISION]. The completed review and its correspondence are evidenced in the job file. | Review before commitment | operational | Documented | ||
| Q8.2.3.2-1 | 8.2.3.2 | Contract review evidence in the job file | customer-requirements-contract-review-procedure | Review evidence is retained in the job file under the Review before commitment section of customer-requirements-contract-review-procedure, with retention scaled to the job. Anything new surfacing during review feeds back into the requirements-determination step and the Product & Market Offers register. | Review before commitment | operational | Documented | ||
| Q8.2.4-1 | 8.2.4 | Changes to requirements after job commitment | customer-requirements-contract-review-procedure | Variations to a committed job are handled through the Changes to requirements section of customer-requirements-contract-review-procedure, with the amended documents and notifications in the job file as the evidence of the update. | Changes to requirements | operational | Documented | ||
| Q8.3.1-1 | 8.3.1 | The standing design and development process | design-development-procedure | The Design planning section of design-development-procedure operates the standing five-stage design and development process, maintained by the {{ROLE_QUALITY_MANAGER}}, with a design plan record opened in docs/records/design-reviews/ before work starts. The whole capability is gated by the design_and_development feature flag, with any exclusion justified in the IMS Scope Statement. | Design planning | Documented | |||
| Q8.3.2-1 | 8.3.2 | Stage planning for each design project | design-development-procedure | Each project's stage plan is shaped through the Design planning steps of design-development-procedure, scaled to the nature and complexity of the work, and lands in the design plan record in docs/records/design-reviews/; the plan is a living record, updated by appending rather than editing. | Design planning | Documented | |||
| Q8.3.3-1 | 8.3.3 | Design inputs and the design brief | design-development-procedure | Design inputs are governed by the Inputs section of design-development-procedure and worked through the design brief, which the design lead assembles and clears with the {{ROLE_QUALITY_MANAGER}} before development starts. The brief committed to docs/records/design-reviews/ is the retained evidence. | Inputs | design-reviews | Documented | ||
| Q8.3.4-1 | 8.3.4 | Design and development stage controls | design-development-procedure | Design control runs through the Controls section of design-development-procedure, which works each project through the checking stages set in its design plan with the people performing them named in the plan. Every control activity, and any problem it surfaces, lands as an append-only record in docs/records/design-reviews/. | Controls | design-reviews | Documented | ||
| Q8.3.5-1 | 8.3.5 | Design and development outputs and their records | design-development-procedure | Design outputs are governed by the Outputs section of design-development-procedure, which has the design lead produce outputs the delivery process can work from under operational-control-service-delivery-procedure. A design outputs record is committed to docs/records/design-reviews/, summarising outputs that live in delivery systems. | Outputs | design-reviews | Documented | ||
| Q8.3.6-1 | 8.3.6 | Design and development change control | design-development-procedure | Changes arising during or after design and development route through the Changes section of design-development-procedure, which reviews and authorises each change before action is taken, with the change record committed to docs/records/design-reviews/. | Changes | design-reviews | Documented | ||
| Q8.4.1-1 | 8.4.1 | Approval and oversight of external providers | procurement-contractor-management-procedure | External provision is governed through the Evaluation and selection section of procurement-contractor-management-procedure: providers are evaluated and approved before engagement and kept under monitoring and scheduled re-evaluation, with status and criticality carried on each Supplier & Contractor Register row. Retained evidence is the register snapshots committed to docs/records/procurement-evaluations/ via tools/snapshot_register.py. | Evaluation and selection | Supplier & Contractor Register | procurement-evaluations | Documented | OHS8.1.4.1-1; OHS8.1.4.2-1 |
| Q8.4.2-1 | 8.4.2 | Control of externally provided processes, products and services | procurement-contractor-management-procedure | The Controls on providers section of procurement-contractor-management-procedure defines, per provider and provision, the controls and verification applied, sized to criticality and the provider's demonstrated capability and recorded on the Supplier & Contractor Register row. Verification of what arrives is executed within the acceptance and release controls of operational-control-service-delivery-procedure before anything reaches a customer. | Controls on providers | Documented | OHS8.1.4.3-1 | ||
| Q8.4.3-1 | 8.4.3 | Information issued to external providers | procurement-contractor-management-procedure | Requirements reaching providers are governed by the Information to providers section of procurement-contractor-management-procedure: adequacy is confirmed before anything is issued, with the {{ROLE_QUALITY_MANAGER}} releasing High-criticality requirements, and the requirements travel in the purchase order, subcontract or engagement letter referenced from the provider's Supplier & Contractor Register row. | Information to providers | Documented | |||
| Q8.5.1-1 | 8.5.1 | Controlled conditions for service delivery | operational-control-service-delivery-procedure | All service delivery runs under the Controlled conditions section of operational-control-service-delivery-procedure, whose table states each condition and how {{ORG_NAME}} implements it, applied as far as the conditions are relevant to the job at hand, with supporting machinery drawn from the linked procedures the table cites. | Controlled conditions | Documented | |||
| Q8.5.2-1 | 8.5.2 | Identification and traceability of deliverables | operational-control-service-delivery-procedure | Output identification and traceability ride the Identification and traceability section of operational-control-service-delivery-procedure, built on the unique job identifier and the deliverable status scheme that governs what may leave the organisation. Where traceability applies, the linkage records are kept in the job file for as long as the applicable retention obligation requires. | Identification and traceability | operational | Documented | ||
| Q8.5.3-1 | 8.5.3 | Property belonging to customers or external providers | operational-control-service-delivery-procedure | Property held or used for a job is governed by the Customer and external provider property section of operational-control-service-delivery-procedure, from receipt through protection to end-of-job handling, with the property log and any event records kept in the job file. Events that also engage harm, data or security are raised in the Incident Register. | Customer and external provider property | operational | Documented | ||
| Q8.5.4-1 | 8.5.4 | Preservation of outputs through to handover | operational-control-service-delivery-procedure | Preservation is carried by the Preservation section of operational-control-service-delivery-procedure, resting chiefly on integrity: the job file as the single authoritative copy, the backup regime with periodically proven restoration, and the identification and status rules, with restore tests entered in the Schedule register so they actually happen. | Preservation | Documented | |||
| Q8.5.5-1 | 8.5.5 | Post-delivery obligations and their fulfilment | operational-control-service-delivery-procedure | Each job's post-delivery obligations are identified at contract review, re-checked at release and scaled under the Post-delivery section of operational-control-service-delivery-procedure. The obligations and the evidence of fulfilling them live in the job file, with obligations falling due after close-out entered in the Schedule register so they surface when due. | Post-delivery | Documented | |||
| Q8.5.6-1 | 8.5.6 | Control of changes arising during delivery | operational-control-service-delivery-procedure | In-flight changes to a job are reviewed and authorised under the Change control in delivery section of operational-control-service-delivery-procedure, with each change record kept in the job file. Changes altering what the customer will receive route through the requirements-change step of customer-requirements-contract-review-procedure, and system-level change belongs to management-of-change-procedure instead. | Change control in delivery | operational | Documented | ||
| Q8.6-1 | 8.6 | Verification and release of deliverables | operational-control-service-delivery-procedure | The Release section of operational-control-service-delivery-procedure holds every deliverable to the verification set in its delivery plan before it leaves {{ORG_NAME}}, with any early release carrying documented approval. Verification and release evidence, including any concession, is filed in the job file. | Release | operational | Documented | ||
| Q8.7.1-1 | 8.7.1 | Handling and disposition of nonconforming outputs | nonconformity-corrective-action-improvement-procedure | Nonconforming outputs are handled through the Reaction and correction section of nonconformity-corrective-action-improvement-procedure, which controls each one from identification through proportionate disposition by the applicable authority. Every case is indexed as a Nonconformity & CAPA Register row, with re-verification evidence in the job file where correction applies. | Reaction and correction | Nonconformity & CAPA Register | Documented | ||
| Q8.7.2-1 | 8.7.2 | Records of nonconformity handling | nonconformity-corrective-action-improvement-procedure | Evidence is retained per Reaction and correction step 5 of nonconformity-corrective-action-improvement-procedure: the Nonconformity & CAPA Register row is the index, and the committed record in docs/records/nonconformities/, named YYYY-MM- |
Reaction and correction | Nonconformity & CAPA Register | nonconformities | Documented |
Clause 9¶
| Req ID | Clause | Obligation | Implementing document | Statement of compliance | Section | Evidencing register | Records folder | Status | Integrated with |
|---|---|---|---|---|---|---|---|---|---|
| Q9.1.1-1 | 9.1.1 | Monitoring and measurement planning, evaluation and evidence | monitoring-measurement-calibration-procedure | The Monitoring plan (section 3.1) of the Monitoring, Measurement & Calibration Procedure is the machinery for this clause: its single table governs every monitoring and measurement stream {{ORG_NAME}} runs, and the procedure's Analysis and evaluation step exercises the judgement side at each management-review slice. Results land in the registers and per-job files the table names for each stream, with periodic register snapshots and the management-review records in docs/records/management-reviews/ as the retained evidence. | Monitoring plan | operational | Documented | OHS9.1.1-1 | |
| Q9.1.2-1 | 9.1.2 | Customer satisfaction monitoring and feedback review | monitoring-measurement-calibration-procedure | Customer perception is handled by the Customer satisfaction section (3.2) of the Monitoring, Measurement & Calibration Procedure, working through the Customer Feedback & Complaints register: continuous capture of feedback and complaints, a post-project follow-up with the client contact, and a monthly register review by the {{ROLE_QUALITY_MANAGER}}. The review feeds the customer-satisfaction objective's current result and the customer slice of management review, where the outcomes are recorded. | Customer satisfaction | Customer Feedback & Complaints | Documented | ||
| Q9.1.3-1 | 9.1.3 | Analysis and evaluation of performance data | monitoring-measurement-calibration-procedure | Analysis and evaluation runs under section 3.3 of the Monitoring, Measurement & Calibration Procedure: the accountable roles work the relevant data at each management-review slice and ahead of audits touching the area, with the section mapping each evaluation to its data source. Outputs are recorded in the management-review record for the consuming slice in docs/records/management-reviews/ and feed the improvement pipeline in the IMS Objectives & Improvement Plan. | Analysis and evaluation | Documented | OHS9.1.1-1 | ||
| Q9.2.1-1 | 9.2.1 | The rolling internal audit programme | internal-audit-procedure | Internal auditing runs as the rolling programme in the Audit programme section (3.1) of the Internal Audit Procedure: twelve short monthly slices whose full cycle spans every requirement area of both standards. Sessions are indexed in the Internal Audit Log, and each performed slice leaves its committed record in docs/records/internal-audits/. | Audit programme | Internal Audit Log | Documented | OHS9.2.1-1 | |
| Q9.2.2-1 | 9.2.2 | Audit programme, auditor independence and audit execution | internal-audit-procedure | The Internal Audit Procedure carries this clause across three sections that divide the labour: the Audit programme (3.1) with its twelve-slice programme table, seeded as Schedule register rows and Scheduled rows in the Internal Audit Log and machine-checked for clause coverage; Auditor independence (3.2), which governs who may audit what; and Audit execution (3.3), which takes each session from scoping through to follow-up. Findings needing action become Nonconformity & CAPA Register rows, session records are committed to docs/records/internal-audits/, and the Internal Audit Log indexes every session. | Audit programme | Internal Audit Log; Schedule; Nonconformity & CAPA Register | internal-audits | Documented | OHS9.2.2-1 |
| Q9.3.1-1 | 9.3.1 | Management review programme and cadence | management-review-procedure | Management review runs as the rolling programme in the Review programme section (3.1) of the Management Review Procedure: twelve short monthly slices chaired by {{ROLE_TOP_MANAGEMENT}} with the {{ROLE_QUALITY_MANAGER}} and {{ROLE_OHS_COORDINATOR}} as standing attendees, keeping the whole system under top-management scrutiny across each cycle. Sessions are indexed in the Management Review Log, with cadence and due dates tracked in the Schedule register. | Review programme | Management Review Log; Schedule | Documented | OHS9.3-1 | |
| Q9.3.2-1 | 9.3.2 | Feeding each management review from the registers and records | management-review-procedure | Review inputs are handled by section 3.2 of the Management Review Procedure working with the slice table in section 3.1, which spreads the standing input set across the twelve-month cycle; the accountable role for each slice prepares its material from the live registers and committed records. Each session record lists what was actually tabled, so input coverage is auditable from docs/records/management-reviews/. | Review inputs | Documented | OHS9.3-1 | ||
| Q9.3.3-1 | 9.3.3 | Management review decisions, actions and retained records | management-review-procedure | The Review outputs section (3.3) of the Management Review Procedure closes every session with explicit decisions and actions, commits the full session record to docs/records/management-reviews/YYYY-MM- |
Review outputs | Management Review Log | management-reviews | Documented | OHS9.3-1 |
Clause 10¶
| Req ID | Clause | Obligation | Implementing document | Statement of compliance | Section | Evidencing register | Records folder | Status | Integrated with |
|---|---|---|---|---|---|---|---|---|---|
| Q10.1-1 | 10.1 | Improvement opportunities and the pipeline behind them | nonconformity-corrective-action-improvement-procedure | Section 3.3 (Improvement) of the Nonconformity, Corrective Action & Improvement Procedure sets out how {{ORG_NAME}} identifies, selects and implements improvement opportunities, feeding the improvement pipeline in the IMS Objectives & Improvement Plan. Each selected improvement is tracked to completion as an Objectives & Targets register row, a Nonconformity & CAPA Register row, or a change run through the Management of Change Procedure. | Improvement | Documented | OHS10.1-1 | ||
| Q10.2.1-1 | 10.2.1 | Nonconformity handling and corrective action to closure | nonconformity-corrective-action-improvement-procedure | Sections 3.1 (Reaction and correction) and 3.2 (Root cause and corrective action) of the Nonconformity, Corrective Action & Improvement Procedure carry the end-to-end handling of nonconformities from any source, including customer complaints. Every nonconformity lives as a Nonconformity & CAPA Register row that the Row Owner Role works through the procedure's steps, with closure confirmed by the {{ROLE_QUALITY_MANAGER}}. Where the work shows planning or the system itself needs adjusting, changes land via the Risk, Opportunity & Hazard Methodology, the PR lifecycle and the Management of Change Procedure, reflected in the Risk & Opportunity Register and the controlled documents. | Reaction and correction | Nonconformity & CAPA Register; Risk & Opportunity Register | Documented | OHS10.2-1 | |
| Q10.2.2-1 | 10.2.2 | Evidence records for nonconformities and corrective action | nonconformity-corrective-action-improvement-procedure | Step 7 of section 3.2 (Root cause and corrective action) in the Nonconformity, Corrective Action & Improvement Procedure keeps the evidence chain for nonconformity handling: the Nonconformity & CAPA Register row is the live index, and the committed record in docs/records/nonconformities/ is the append-only evidence. | Root cause and corrective action | Nonconformity & CAPA Register | nonconformities | Documented | OHS10.2-1 |
| Q10.3-1 | 10.3 | Continual improvement of the integrated management system | ims-objectives-improvement-plan | Section 3.6 (Improvement pipeline) of the IMS Objectives & Improvement Plan carries continual improvement of the IMS: candidate improvements drawn from the system's own outputs are weighed and selected at management review, then tracked as Objectives & Targets register rows or Nonconformity & CAPA Register rows, with no third, untracked place for improvement work to live. Evidence lands in the review minutes and objective snapshots committed to docs/records/management-reviews/. | Improvement pipeline | Objectives & Targets | Documented | OHS10.3-1 |