ProcessHub.
Hierarchical process documentation with mandatory four-eyes approval and full version history. Built for ISO 9001 and 27001.
Live · Demo open
Process documentation lives in one of three places in most organisations: a shared Word folder, a Confluence or SharePoint that nobody maintains, or the quality manager's hard drive. All three drift away from reality roughly from the moment the certification is signed.
ISO 9001 and 27001 don't require an expensive system — but they do require a traceable process where every published version has a reviewer, a timestamp and an unbroken history. That's what an ordinary Word document does not give you.
ProcessHub holds all process documentation in a three-level hierarchy: Process → Sub-process → Activity. Every save is a draft. Every publication requires another user's approval. The version number ticks up. The whole history stays.
What it does
- Three-level editor with drag-and-drop reordering, rich text (TipTap), live preview.
- Automatic versioning — every saved change becomes a draft, every publication gets a new version number, the whole history is queryable with diff view.
- Four-eyes approval — Draft → Review queue → Published. You cannot approve your own work. Enforced in the data layer, not the UI.
- Process templates — admins define reusable structures; template changes never quietly update already-published processes.
- Full audit trail — every create, edit, delete, reorder, attachment and approval logged with user and timestamp.
- PDF and DOCX export of every process version in ISO format with metadata and history.
- Four roles — Reader, ProcessOwner, Approver, Admin. The approver cannot approve their own work.
- TOTP MFA optional but recommended. Notifications via in-app, email and push.
What sets it apart
Only three levels. Want a fourth — split the process. An architectural principle that forces clarity. Templates do not update existing processes; a design principle that lets the template owner iterate without silently breaking what's already published. And the audit trail is not a post-hoc module but an interceptor capturing every SaveChanges at the data-layer level.
Auditable process documentation where the history can actually be trusted.