Revision history
Know which SOP version is current and what it replaced.
Governed execution
Automate the process without losing control.
Interactive Dox connects workflow execution with roles, approvals, signatures, revisions, and evidence, so automation remains accountable as the business changes.
Where you are set up, what needs a decision, and what to do next, the frameworks you follow and the items waiting on a person.
Governance inside the workflow, not after it.
Automated steps run where they are allowed to. Required human checkpoints wait for a person. Approvals and signatures are recorded as they happen, and the evidence and audit history build while the work runs.
- 1Start from the current access-change SOPSOP revisioncurrent revision
- 2Check the request against configured rulesSystemcompleted
- 3Prepare the change for the required checkpointSystemprepared
- 4Required human checkpoint: review the changeRequired reviewerreviewed
- 5Approve, with a signature where configuredApproverapproved
- 6Record the execution evidenceSystemrecorded
- 7Add the events to the audit historySystemadded
Records kept as the work progressesIllustrative workflow: access change request
Access change request
- procedure referenced
- rule checks recorded
- change prepared for review
- review decision recorded
- approval recorded · signature where configured
- execution evidence kept
- audit history updated
Which checkpoints, approvals, and signatures a workflow requires depends on how it is configured.
The controls behind governed execution, connected to the procedures they govern.
Know which frameworks your procedures support, hear when those frameworks change, route important revisions for approval, and keep the evidence.
Frameworks
Know which frameworks your organization follows, in one place.
Monitoring
Hear when a framework you follow changes, and be able to show it was checked, even when nothing had changed.
Controlled documents
See which procedures each framework depends on, and which framework each procedure supports.
Findings
A change or an issue becomes a clear item with the documents it affects, so the right person can act on it.
Reviews & approvals
Important revisions reach the right reviewers, with multi-step and signature-backed approval for the documents that need it.
Evidence & audit
Show what changed, who approved it, when, and that it has not been altered since.
Build the record while the work happens.
Each part of the record answers a question a reviewer or auditor will ask, without reconstructing it later.
Approvals
Retain accountable decisions.
Execution evidence
Keep supported run results connected to the process.
Signatures
Use signature-backed approval steps where configured.
Audit trail
Review who did what and when.
Changes should be reviewed, not silently absorbed.
When a procedure or environment changes, Interactive Dox can surface the difference and route the proposed update through the appropriate review process before it becomes the approved version.
01
A procedure, framework, or environment changes.
02
The difference is surfaced next to the procedure it affects.
03
An update is proposed as a draft, not applied.
04
The appropriate reviewers review it.
05
An approver makes it the approved version.
06
The previous revision stays in the history.
Controls, not a compliance guarantee.
Interactive Dox provides controls that help organizations operate controlled procedures and assemble reviewable evidence. Compliance decisions, and the independent assessments an audit requires, remain yours.
The specifics, stated plainly.
Approvals
- Approval flow builder with named approvers
- Signature-backed approval steps where configured
- Important changes reach the right reviewers
- Drafts never mix with the version in force
The record
- Every approved change keeps the one before it
- Sealed PDF exports of official versions
- Who approved, what changed, when it took effect
- Tamper-evident audit history
Compliance
- Requirements and monitoring per document
- Framework changes flagged next to the procedures they affect
- Open issues and findings near the content
- Controlled documents with formal lifecycle
Governance questions, answered.
What is governance in Interactive Dox?
The controls around SOP-driven work: who is responsible, which procedure revision is current, what was approved, what the workflow recorded, and how changes are reviewed before they become the approved version.
Can workflows require a person before they continue?
Yes. Required human checkpoints and approvals are explicit steps in a configured workflow, and the workflow waits for the person. Signature-backed approval steps are available where configured.
Does Interactive Dox make us compliant?
No. It provides controls that help you operate controlled procedures and assemble reviewable evidence: revisions, approvals, execution records, and an audit trail. Compliance decisions and audit outcomes remain yours.
What happens when a procedure or framework changes?
The change is surfaced next to the procedures it may affect, an update is proposed as a draft, and it goes through the appropriate review and approval before it becomes the approved version. The previous revision is kept.
Less audit scramble. More evidence by design.
Explore how one of your controlled procedures could run with explicit checkpoints, recorded approvals, and evidence built as the work happens.
Book a demo around one real SOP.
Leave your work email and we'll follow up to arrange a demo built around one of your procedures.