how-to
How to Manage ISO Documentation Online: A Step-by-Step Guide
Table of Contents
- Why Managing ISO Documentation Online Matters
- Understanding ISO Document Control Fundamentals
- Setting Up Your ISO Document Register
- Choosing the Right ISO Document Management Software
- Implementing ISO Document Version Control
- Ensuring Staff Access the Latest ISO Documents
- Preparing Your Online System for ISO Certification Audit
- Migrating from Spreadsheets and Paper to Online Management
- Frequently Asked Questions
Last Updated: October 21, 2026
Managing ISO documentation online keeps documents current, accessible and audit-ready, replacing scattered files, email chains and outdated printouts. At IntegriSURE, we help Australian organisations implement document control that is straightforward and sustainable.
This guide explains how to manage ISO documentation online, from setting up registers to choosing software and preparing for certification audits.
Why Managing ISO Documentation Online Matters
Organisations that manage ISO documentation online spend less time hunting for the right version and more time on actual work.
Manual systems fail because they:
- Scatter documents across email, drives, and filing cabinets
- Make version control nearly impossible
- Leave no clear record of who approved what and when
Online management fixes these problems. Staff access one source of truth. Changes are tracked automatically.
For ISO 9001, ISO 14001, and ISO 45001, document control is not optional, it is a core requirement.
Understanding ISO Document Control Fundamentals
What document control requires
Document control means managing documents so the right people use the right version at the right time. ISO standards require organisations to control documented information describing how the management system works and what evidence proves it works.
This includes:
- Policies and procedures that explain how the organisation operates
- Work instructions that tell staff how to do specific tasks
- Forms and templates used to capture information
The standard does not prescribe how to control documents. It specifies the outcome: staff access current documents, outdated versions are removed or clearly marked obsolete, and changes are approved before use.
Common gaps in manual systems
Many organisations maintain documents in ways that make audit readiness difficult:
- Multiple versions exist simultaneously. A procedure sits on a shared drive, in email inboxes, and printed on desks. Staff do not know which is current.
- No approval trail. Changes happen without clear sign-off. Auditors cannot see who approved a document or when.
- Lost obsolete documents. Old versions remain accessible. Staff accidentally use outdated procedures.
Online systems prevent these gaps by enforcing workflow, tracking changes and controlling access.
Setting Up Your ISO Document Register
What belongs in a document register
A document register lists every document your management system uses, tracking its name, version number, approval date and status (current or obsolete).
The register serves two purposes: internal control (staff can see what documents exist and find the latest version) and audit evidence (auditors can verify your organisation knows what documents it controls and whether they are current).
A basic register includes:
- Document title
- Document code or reference number
- Version number or revision date
Automating register updates
Manual registers need updating every time a document changes; online systems can automate this. When a document is uploaded and approved, the system records the upload date, captures the approver's name and timestamp, updates the status from "draft" to "current", archives the previous version and notifies relevant staff. This removes the administrative burden and keeps the register accurate.
Choosing the Right ISO Document Management Software
The right platform depends on your team size, budget, and complexity. Start simple. Add features only when you need them.
Simple options: shared drives and basic platforms
Shared drives (Google Drive, OneDrive, SharePoint) are low-cost and familiar to most teams.
Advantages:
- No learning curve, staff already know how to use them
- Accessible from anywhere with internet
- Suitable for small teams with simple document needs
Limitations:
- Version control is manual, users must name files carefully (e.g., "Procedure_v2_final_REAL.docx")
- No approval workflow, anyone can edit anything
- Hard to demonstrate document review to auditors
Best for: Teams under 20 people with straightforward processes and strong internal discipline.
Mid-level solutions: knowledge portals and team sites
Knowledge management portals (team sites or intranet platforms) sit between shared drives and enterprise systems. They provide a central location for all documents, support basic approval workflows, track who viewed or downloaded documents, allow comments and version history, and can populate registers automatically when documents are published.
Advantages:
- Easier to demonstrate document control to auditors
- Approval workflows reduce errors
- Staff know where to find current documents
Limitations:
- Requires more setup than a shared drive
- May need training for staff
- Some platforms charge per user or per document
Best for: Teams of 20-100 people, or organisations with multiple sites needing consistent document access.
Advanced systems: automation and digital forms
Sophisticated platforms enable digital forms that populate registers, trigger approvals and archive old versions.
Advantages:
- Minimal manual administration
- Automatic version control and obsolescence management
- Digital forms capture data directly into registers
Limitations:
- Higher cost
- Longer implementation time
- May require IT support
Best for: Organisations with 100+ staff, multiple sites, complex workflows, or high audit frequency.
Implementing ISO Document Version Control
Setting up version numbering and tracking
A clear version numbering system tells staff and auditors what version is in use.
Simple approach:
- Draft: v0.1, v0.2 (document not yet approved)
- Current: v1.0, v2.0 (approved and in use)
- Obsolete: marked clearly with date withdrawn
Record the approval date alongside the version number. This creates an audit trail showing when each version was approved.
Example:
| Document | Version | Approved | Status |
|---|---|---|---|
| Quality Procedure | v2.1 | 15 Oct 2026 | Current |
| Quality Procedure | v2.0 | 3 Mar 2025 | Obsolete |
| Inspection Form | v1.0 | 20 Sep 2026 | Current |
Managing approval and review workflows
Before a document becomes "current," it must be reviewed and approved by someone with authority.
A basic workflow:
Get Your Free ISO Starter Pack →
- Author drafts the document
- Reviewer checks it against the standard
- Approver (usually a manager) signs off
- System updates status to "current"
- Staff are notified of the change
Online systems can automate this: when a document is uploaded, it routes to the reviewer automatically, then moves to "current" status once approved.
Retiring obsolete documents
When a document is superseded, it must be removed from active use but kept for record-keeping.
Actions to take:
- Mark the old version "obsolete" with the withdrawal date
- Remove it from staff access areas
- Archive it in a read-only location
Never delete old documents. Auditors need to see that your organisation controls the document lifecycle deliberately, not carelessly.
Ensuring Staff Access the Latest ISO Documents
Centralising your document repository
A single, obvious location for documents eliminates confusion. This might be a shared folder with a clear structure, a knowledge portal or intranet page, a dedicated ISO management system, or a team collaboration platform with document libraries. The key is that staff know exactly where to look; if documents are scattered, people will use outdated versions by accident.
Setting access permissions and security
Control who can view, download, edit, and approve documents.
Typical permission levels:
- View only: Staff can read documents but not edit them
- Download: Staff can save copies for reference
- Edit: Team members working on the document can make changes
Restrict editing to people who actually need to update documents. This prevents accidental changes and keeps the audit trail clean.
Communicating updates to your team
When a document changes, staff need to know. Effective communication includes an email notification with a link to the new version, a summary of what changed, the date the change takes effect, and confirmation that the old version is no longer in use. Many online systems send these notifications automatically; manual systems require someone to send the email.
Preparing Your Online System for ISO Certification Audit
Demonstrating document review and approval
Auditors will ask how you know documents are still suitable and who approves changes.
Your online system must show:
- A list of all documents currently in use
- The approval date and approver name for each
- Evidence that documents are reviewed periodically
- A record of changes made and why
If your system tracks this automatically, auditors can see it instantly. If you manage it manually, you need clear records (spreadsheets, email trails, sign-off sheets).
Audit trails and compliance evidence
An audit trail records who did what and when, proving your organisation controls documents deliberately.
Capture:
- When documents were created, edited, and approved
- Who made each change
- What changed (if the system tracks this)
- When documents were marked obsolete
Online systems generate audit trails automatically; manual systems require separate records (approval forms, email confirmations, change logs).
Auditors check that your audit trail matches reality. A clear trail speeds up the audit.
Migrating from Spreadsheets and Paper to Online Management
Planning your migration
Moving from scattered documents to a centralised system takes planning.
Steps:
- Audit what you have. List all documents currently in use across email, drives, filing cabinets, and spreadsheets.
- Decide what to keep. Not everything needs to move. Keep what is relevant; discard outdated or duplicate files.
- Organise the structure. Create a logical folder or category system so staff can find documents easily.
- Choose your platform. Select the tool that fits your budget and team size.
- Set up access. Configure who can view, edit, and approve documents.
- Load documents. Upload files to the new system and set initial versions.
- Train your team. Show staff where to find documents and how to request changes.
- Run parallel for a period. Keep the old system active while staff get comfortable with the new one.
- Switch over. Set a date when the new system becomes the single source of truth.
- Archive the old system. Keep old files for record-keeping but mark them inactive.
Consolidating fragmented documentation
Many organisations discover multiple versions of the same document during migration: a procedure exists in three places with slightly different content, staff created local versions because they could not find the official one, or old templates remain in use alongside new ones.
During consolidation:
- Compare versions and decide which is most current
- Merge the best elements if versions differ
- Assign a single owner to maintain the document
- Delete duplicates
This consolidation often reveals gaps or inconsistencies. Fixing them now, before certification, strengthens your management system.
Training your team on the new system
The best system fails if staff cannot use it.
Training should cover:
- Where to find documents
- How to download or access the latest version
- How to request changes
- How to report if a document is outdated or incorrect
Keep training brief and practical. Show examples relevant to their role.
After launch, monitor questions and confusion.
Managing ISO documentation online is not complicated, but it requires discipline.
If you are preparing for ISO 9001, ISO 14001, or ISO 45001 certification, document control is one of the first areas auditors examine.
IntegriSURE provides templates, registers and step-by-step guidance to help you set up document control that works.
Get started with your Free ISO Starter Pack to see how online document management fits into your certification journey.
Frequently Asked Questions
Can SharePoint or Google Docs be used for ISO document control?
Yes, both can work for basic ISO document control. SharePoint and Google Docs are simple and familiar to most teams, but they make it harder to demonstrate document review, approval and versioning, though not impossible. For stronger audit readiness, consider platforms with built-in version tracking, approval workflows and automated document registers. The key is ensuring your staff can access the latest versions reliably.
What should an ISO document register include?
An ISO document register records every controlled document in your management system. It typically includes: document title, document number, version number, date issued, approval status, owner, location, and current status (active or obsolete). The register serves as your master record for demonstrating document control during certification audits. Online systems can automate register updates when documents are created or revised.
How do you show that ISO documents have been reviewed and approved?
Document approval must be visible and traceable. Use approval workflows that capture who reviewed the document, when they reviewed it, and whether they approved it. Digital signatures, dated sign-off forms, or automated workflow logs all provide audit evidence. Simpler systems like shared drives require manual approval records; more sophisticated platforms create automatic audit trails that auditors can easily verify.
How can online forms update ISO registers automatically?
Advanced document management platforms and team sites can use digital forms that automatically populate your document register when new documents are created or revised. For example, when someone completes a 'New Procedure' form, the system adds an entry to your register with the title, version, owner and date. This saves time, reduces errors and ensures your register stays current without manual data entry.
