{{ORG_NAME}} Integrated Management System¶

Maintained page — not a controlled document; kept current by the {{ROLE_DOCUMENT_CONTROLLER}}.

This is the Integrated Management System (IMS) of {{ORG_NAME}}: one system, one document set, covering quality (ISO 9001:2015) and work health & safety (ISO 45001:2018) together. It is browsed right here in the repository — every page renders in GitHub.

The system at a glance¶

Every box below is a folder or view in this repository; the arrows say how each element supports the others. The map is not clickable — the links live in Start here and the table below.

flowchart TD
    accTitle: How the IMS elements fit together
    accDescr: Clause maps trace each ISO 9001 and ISO 45001 requirement to the documents that address it. Core documents and the policy are operationalised by procedures and plans; running them leaves records as evidence; Airtable registers index status and due dates but are never the evidence.

    CM["Clause maps<br/>each ISO 9001 & ISO 45001 requirement,<br/>traced to the documents that address it"]

    subgraph DOCS["Documents — the controlled set"]
        CORE["Core documents<br/>scope, context, risk, objectives, offers"]
        POL["Policy<br/>quality & OH&S commitments"]
        PROC["Procedures<br/>how each activity is run"]
        PLANS["Plans<br/>emergency preparedness & response"]
        CORE -->|"operationalised by"| PROC
        POL -->|"commitments delivered by"| PROC
        CORE -->|"identified risks planned for in"| PLANS
    end

    REC["Records<br/>append-only evidence that something ran"]
    REG["Registers — Airtable<br/>live status & due dates;<br/>an index, never the evidence"]
    GT["Guides & training<br/>how to read, run & change the system"]

    CM -->|"maps each requirement to"| DOCS
    PROC -->|"each run leaves evidence in"| REC
    PLANS -->|"drills & activations logged in"| REC
    REC -.->|"feeds audits & reviews"| PROC
    DOCS -->|"metadata mirrored into"| REG
    REC -->|"indexed by"| REG
    REG -.->|"snapshotted back into"| REC
    GT -.->|"how everyone uses this"| DOCS

How this system works — three tiers of truth¶

Tier	What it holds	Where	How it changes
Documents	Policies, procedures, plans, core documents	ims-core/, policies/, procedures/, plans/	Draft → Under Review → Approved, via pull requests — see the author guide
Records	Point-in-time evidence that something ran	records/	Append-only — never edited; a correction is a new record
Registers	Live status: who's done what, what's due	Airtable ({{ORG_NAME}} IMS Registers)	Continuously updated; an index, never the evidence

Start here¶

Everyone: the reader guide — how to read documents, acknowledge policies, log training, and report hazards.
Authors, reviewers, approvers: the author, reviewer & approver guide.
What documents exist: the document index (generated — never edit by hand).
How the system meets the standards: the clause maps — ISO 9001 and ISO 45001 (both generated).
What evidence exists: the records index (generated).
What the registers hold: the registers index — every register, what it indexes, and its fields (generated from the Airtable schema). Registers are the live index of status and due dates; they are never the evidence.

There is no Quality Manual — deliberately¶

ISO 9001:2015 does not require one. The core documents in ims-core/ plus the generated document index together do that job with less duplication and no drift. Please don't add one.

Ground rules worth knowing¶

Empty records folders are correct until the activity has actually run — this system never claims evidence it doesn't have.
Documents name roles, never people. Who currently holds each role lives in the Airtable People register.
Every index/summary page here is generated by tools/gen_views.py; CI rejects hand edits. Change the source, regenerate.
Approval happens exactly one way: the named approver merges the pull request. Nothing and no one else sets a document to Approved.
The underlying template is supplied as-is, without warranty — see the Disclaimer & terms of use.