Software module · Foundation for every standard

Documents

Controlled documents move through Draft, In review, Approved, Published and Obsolete. Approved copies are frozen and hash-verified, so the revision an auditor opens is the one you approved.

One current revision, and proof of which one it is

The problem

Nobody knows which revision is current. The procedure on the floor is two versions behind the one on the server, approvals happen by email, and the week before the audit someone has to reconstruct who approved what, and when.

How the software handles it

Every document follows one lifecycle: Draft, In review, Approved, Published, Obsolete.

Approvers are set in sequence or in parallel. An owner cannot approve their own document.

Word and Excel files are edited in the browser. PDF and PowerPoint files are previewed. Legacy .doc and .xls files are converted to an editable copy.

Versions are compared with the changes marked, and reviewers leave comments on the document.

Approved copies are frozen and hash-verified. Branded letterheads, translations and bulk upload are built in.

Deleted documents sit in a trash with a 30-day recovery window.

AI drafting is optional and off until the organization turns it on. Every draft is reviewed by a person before it enters the lifecycle.

What the auditor sees

  • The published revision, frozen at approval, with its hash.
  • The approval chain: who approved, in what order, and when.
  • A version comparison showing what changed between revisions.
  • Obsolete revisions kept for the record and clearly marked.

Related standard clauses

StandardClauseWhat it asks for
ISO 9001:20157.5Documented information
ISO 13485:20164.2.4Control of documents
ISO 13485:20164.2.5Control of records
ISO/IEC 17025:20178.3Control of management system documents
AS9100D8.1.2Configuration management

How we configure it with you

01

Map your process

Your processes are mapped in Processes as they run, with named owners and the forms and approvals your team already uses, instead of starting from a generic template.

02

Configure the modules

Fields, checklists, terminology and routing are configured to match your operation. The software speaks your language, not software jargon.

03

Onboard your standards

Catalogue standards are switched on. Customer-specific or internal standards are imported from a workbook as custom standards. Every clause links to the modules and evidence that satisfy it.

04

Deploy to the floor

Roll out with training campaigns, competency records and evidence capture, with a certified consultant reviewing the configuration through to your audit.

Talk about document control with a certified consultant

Tell us how this part of your operation runs today. You will get a clear read on what the module changes on Monday morning, and what the auditor will see.

We reply within one business day

ISO ConsultantCall