07/Governance
Documentation that holds up when someone asks who changed what.
Built into normal editing, not a separate exercise.
Versions, attribution and review are built into normal editing, so the process record stays current and stays defensible without a separate effort.
Version history · audit trail
Change history
Answer who changed this and when, without an investigation
Every edit is a version with a name and a timestamp against it, which is the question an auditor actually asks.
- Full version history with per-change attribution
- Structured change records and clear ownership
Approvals
Know which version was in force on any given date
Versions move through review before they publish, so there is an explicit answer to which version was in force on any date.
- Reviewable documentation for compliance-sensitive work
- Living documentation, refined over time
One source, many uses
One current process serves onboarding, audit and handover
The same maintained process serves onboarding, audit evidence and succession, instead of three documents quietly drifting apart.
- Reusable for training, handover and succession
- Linked knowledge across related workflows
Audit evidence without a separate exercise
The history is already there when someone asks.
Documentation your teams actually trust
A map demonstrably current gets consulted.
Handover without the guesswork
The process is already documented and attributed.
Related features
All featuresData integration
Connects to where your documents and run data already live, with exports and a REST API back out.
Capture processes
Document a process in one working session, from interviews, workshops or the files you already have.
Common questions
Can we see who changed what?
Yes. Every version carries attribution and a timestamp, and changes are recorded as structured change records against an owner rather than inferred from file metadata.
Does this satisfy compliance requirements?
Sapeum provides reviewable, versioned documentation with per-change attribution and clear ownership, which is what compliance-sensitive reviews depend on. Sapeum has completed an independent SOC 2 Type 2 examination, with the report available under NDA; see trust.sapeum.com for current details.
Can old versions be recovered?
Yes. Version history is retained, including forked and archived versions, so you can see what a process looked like at any earlier point.
What happens when the person who owned a process leaves?
The process is already documented, attributed and current, because maintaining it was part of normal work rather than a project. Nobody has to reconstruct it from scratch.
Is process data held securely?
Sapeum is designed with enterprise-grade security practices: encryption at rest and in transit, role-based access controls, and auditable change history. Sapeum has completed an independent SOC 2 Type 2 examination; trust.sapeum.com has the current position.