Documents that move: co-editing, stages and signed approvals
See how the autumn 2026 release lets several people edit a document at once, tracks progress through named stages, and binds every e-signature to the exact content the approver saw.
Controlled documents are where a management system either lives or stalls. A procedure that sits at "70% complete" for three months is not controlled, it is abandoned. In the autumn 2026 release we rebuilt how a document moves from an empty page to an approved version, and who can work on it along the way.
This article is part of the series on what is new in ComplyTrain.
Several people in the same document
Until now a document had one editor at a time. Now several people can edit, review and read the same document together:
- You see each other's cursors and changes live.
- Proposals, accepted and rejected changes, comments and review panels update for everyone at once.
- There is no Save button. The server stores the document as you type.
This works in the QMS, Tender, Risk Management and Product editors.
When you need it to yourself
Some edits should not be interrupted, for example a restructuring before an audit. Anyone who can edit can lock a document. Everyone else turns read-only immediately. If the holder walks away, the lock is released after an idle period that your organisation sets (30 minutes by default), and the document owner or an administrator can take over. The previous holder is told in the app and by e-mail.
Stages instead of a percentage
A percentage tells you little. Is 80% a document waiting for one signature, or one missing its hardest section?
Documents now move through named stages: Not started, Drafting, In review, In approval, Approved, with Archived at the end. Sections have their own status, so progress reads "4 of 6 sections done", and you can see whether a section was drafted from a template or by the AI and has not yet been touched by a person.
The document page shows one next step: send for review, send for approval or approve. Stages that a document does not go through are greyed out with an explanation. When an approval is blocked, the page names the gates that block it, in your own language.
Starting a document
The first time a document is opened, you choose how to begin: Blank, Start from template, Let AI write it or Import from file. Template text no longer appears unless someone chose it, and the document history records how the document was started, by whom and when.
The people you name decide the workflow
You no longer design a workflow to get a simple review. The people on the document decide it:
- Name reviewers, and the document goes to review first. Each reviewer gets a task in their inbox.
- Name approvers, and it goes to them for approval. All of them must approve.
- Name nobody, and the owner approves.
Per document type you can require reviewers or approvers, so that a policy cannot be approved by its author alone while a work instruction can.
Approval that is bound to the content
Every document has one owner. An approval is a personal e-signature, and it is bound to a SHA-256 fingerprint of the exact content that the approver saw. Three things follow from that:
- If the document changes while approval is requested, the approvals given so far reset. The person who changed it writes a change note, and the approvers are notified.
- Approvers receive an approval copy as a PDF, watermarked as a draft for approval.
- The approved PDF prints every approver with name and date, and is signed with your organisation's own certificate authority.
Approvers can request changes with a reason, and an owner can withdraw an open request. Buttons that cannot succeed are disabled, with a tooltip that lists why.
For standards that require documented information to be reviewed and approved before use, such as the ISO management system standards, this gives you evidence of who approved exactly which text. The certificate remains yours to earn; the tool gives you the record.
Bring your existing documents with you
Most organisations do not start with empty pages. The Word and PDF import now keeps far more of the original:
- Images and figures, placed where they were, with text wrapping beside them.
- Tables and the Word table of contents.
- Label and value pairs in the page header, which become fields on the document.
- The revision of the file, which becomes the version baseline, so numbering continues from where you were.
Import runs in the background with progress shown. Afterwards you can add images from a gallery, annotate a photo in draw.io, and export to PDF or Word with the images in place.
Smaller things that matter every day
- Folders in the Document Vault. Create, rename and move folders, and generate records straight into a dated folder path.
- Process reference sections. Show a QMS process as a diagram inside a document. It is linked, not copied, and can follow the latest approved version of the process.
- One set of document types. A document type's review and approval rule now applies in every standard and every vault.
- Merge two documents. One survives, the AI rewrites the combined text, and the other stays in force until the merged version is approved.
- Related items. Link a document to other records and create a task from it.
- Minor or major. An approver chooses whether the new version is a minor or a major revision.
What changes for existing customers
Two things to plan for. A document needs an owner before it can be approved, and owners can be assigned in bulk from the document list. And underline has been removed from the editor, because it could not be stored reliably; bold and italic are unchanged.
To see the document flow with your own procedures, book a demo. More about the module is on the Documents page and the QMS page.
