VERSION CONTROL

Purpose of This Section

The Version Control section defines how NWAF™ tracks, updates, records and communicates changes to governance documents. It ensures that versions are:

accurate
traceable
transparent
accessible
legally aligned
approved at the correct governance level

Version Control protects the integrity of NWAF™ and ensures that all users and organisations are working from the correct, up‑to‑date information.

1. Version Control Principles

1.1 Accuracy

Version numbers must reflect the true status of the document.

1.2 Transparency

All changes must be visible, documented and traceable.

1.3 Consistency

The same versioning method must be applied across all governance documents.

1.4 Accessibility

Version information must be easy to find and accessible to all users.

1.5 Legal Alignment

Versioning must support legal compliance and tribunal expectations.

1.6 Stability

Version changes must not introduce confusion or inconsistency.

1.7 Founder Authority

Major version changes require Founder approval.

2. Version Types

NWAF™ uses three version types:

2.1 Major Versions (e.g., 1.0 → 2.0)

Used when:

structure changes
roles change
legal alignment changes
accessibility standards change
governance processes change

Approved by: Founder

2.2 Minor Versions (e.g., 1.1 → 1.2)

Used when:

content is clarified
examples are updated
small improvements are made
accessibility fixes are applied

Approved by: Oversight

2.3 Micro Versions (e.g., 1.1.1 → 1.1.2)

Used when:

spelling is corrected
formatting is adjusted
layout is improved

Approved by: Leads

3. Version Control Activities

Version Control includes:

assigning version numbers
documenting changes
updating version blocks
archiving previous versions
publishing new versions
communicating updates
maintaining version history

All activities must follow NWAF™ governance standards.

4. Version Control Process

All documents must follow this structured process:

Identify change type (major, minor, micro)
Apply correct version number
Document change summary
Seek required approval level
Update version block
Publish updated version
Archive previous version
Communicate update to organisations
Record version change in governance logs

This ensures versions are controlled, stable and transparent.

5. Version Block Requirements

Every governance document must include a version block containing:

version number
status (draft, approved, published)
approval record
last updated date
summary of changes
responsible role

This block must appear at the bottom of every page.

6. Version History Requirements

Version history must:

be stored securely
be accessible to authorised roles
include all previous versions
include change summaries
support audit and tribunal evidence

Version history is part of NWAF™’s legal and governance record.

7. Roles & Responsibilities

7.1 Founder

Approves major versions
Sets version control expectations
Ensures alignment with NWAF™ vision

7.2 Oversight

Leads version control
Approves minor versions
Monitors consistency and accuracy
Escalates issues

7.3 Leads

Apply micro versions
Support version updates
Ensure accuracy and compliance

7.4 Organisations

Use the latest versions
Apply updates promptly
Report outdated content

7.5 Users

Engage with updated documents
Report errors or concerns
Provide feedback

8. Why Version Control Matters

Version Control:

protects governance integrity
ensures legal and accessibility compliance
prevents outdated or incorrect information
strengthens governance maturity
supports transparency and accountability
reinforces Founder‑led authority
safeguards the long‑term stability of NWAF™

Versioning is the heartbeat of a national‑grade governance system.

Version Information

Version: 1.0
Status: Published
Approved by: Founder
Last Updated: 19 February 2026

← Back to Governance Hub Overview