Systems and interfaces change
A screen, field, permission, or path moves after the procedure was approved.
Verify the work, not just the document
Know whether the process still works.
Interactive Dox connects SOPs to execution evidence so teams can see what completed, what failed, what changed, and what needs review.
Validate supported procedures. Capture evidence. Review changes before they become the new standard.
A procedure can look current and still be wrong.
Systems change. Interfaces move. APIs evolve. Policies change. A document can remain perfectly readable while the real process behind it has already drifted.
Interactive Dox helps teams verify supported procedures against the environment they describe and retain evidence of what happened.
APIs evolve
An endpoint or integration changes underneath the documented steps.
Policies change
A rule or operating standard changes while the published procedure stays the same.
From the approved SOP to an approved update.
A supported procedure is run against the environment it describes. Each step records a result and evidence. A step that no longer matches becomes a suggested correction for a person to review.
- 1Current SOP revisionSSO setup guide · revision 6
- 2Target environmenta supported web application
- 3Step resultssteps 1 and 2 matched · step 3 did not
- 4Evidencescreenshot and page state from the run
- 5Failure / driftthe button moved to another menu
- 6Suggested correctiondrafted, not applied
- 7Reviewa named reviewer decides
- 8Approved updatebecomes the current revision after approval
validation run · SSO setup guide · revision 6Illustrative validation run● approved update
target: a supported web application
- 1Sign in as a workspace adminmatched
- 2Open Settings from the sidebarmatched
- 3Click “Security & access” on the Authentication tabdid not match
- 4Choose SAML and paste the metadata URLnot reached
- expected
- button “Security & access” on the Authentication tab
- found
- nearest match “Security” under Settings, Organization
- evidence
- screenshot and page state kept from the run
suggested correctionapproved · revision 7 current
Click “Security & access” on the Authentication tab.
Open Settings, then Organization, and click “Security”.
The published SOP stays unchanged until a person approves. Videos, training, and portal pages built from the guide keep their own review and publishing step.
Catch process drift before it becomes operational debt.
Reduce repeat failures
Find broken or outdated steps before teams repeatedly discover them manually.
Shorten investigation time
Keep the failed step, evidence, and procedure revision connected.
Improve accountability
Know which procedure ran and what occurred.
Support audits and reviews
Retain execution evidence alongside controlled revisions and approvals.
See a validation run, start to finish.
A supported guide being checked against the live product, screen by screen: each step followed, the pause where it asks a person for a value it should not store, evidence kept for every step that passes, and the result filed against the document.
The captured workflow itself: each step with the screenshot and the written explanation it was recorded with.
Validations run on a schedule. Results reach the team where they already are.
Supported guides are checked on the schedule you set, and the outcome reaches your team in Teams, Slack or email. A pass needs nothing from you; a change arrives with a suggested correction for review.
autopilot · validation schedule● on
- Nightlyevery day · 02:00
- After each releasetriggered by a deploy
- WeeklyMondays · 06:00
rotate database credentials · customer-hosted run
nightly check · 02:00in your environment
- ✓open the credentials vault
- ✓request rotation approval
- ✗rotate and update the secret
- ✓re-run the connection check
step 3 changed · correction suggested
- Microsoft Teams#ops-runbooksRotate database credentials · step 3 changed · correction suggested · review →
- Slack#docs-verificationRotate database credentials · step 3 changed · correction suggested · review →
- Emailsop-owners@Nightly validation: 3 of 4 steps matched. Step 3 changed; a suggested correction is waiting for review.
It runs without being asked
Put a supported guide on a schedule, nightly, weekly, or after each release, and it is checked without anyone having to remember.
The team hears about it where they already are
Results go to Teams, Slack or email: a pass, or a change with the exact step that no longer matched.
A person still decides
When a step changed, a correction is suggested. Nothing becomes the current version until someone on your team approves it.
For customer-hosted verification, supported checks execute in your environment, against the supported web and desktop applications and internal systems your procedures touch. Credentials stay in the operating system keychain on the machine that runs the check, and anything typed into a secure field is dropped before step data leaves it. The run result, step events and step screenshots, returns so a reviewer can see what happened.
- Verification applies to supported procedures in supported environments. Physical processes are not validated automatically.
- Not every desktop workflow can be replayed automatically.
- A failed step produces a suggested correction. It is not repaired automatically.
- A proposed change does not overwrite the published SOP; a person approves it first.
- Validating a procedure is a separate event from running a business workflow.
Verification questions, answered.
What does verification check?
Supported procedures are run against the environment they describe, on demand or on a schedule. Each step records a result and evidence, and you are told the exact step that no longer matches.
What does it mean when guidance has drifted?
The approved guidance no longer matches the real process. A button moved, a field changed, a permission differs, an API changed, or a rule changed while the published procedure stayed the same.
What happens when a step fails?
You see which step no longer matches and the evidence from the run. A correction is suggested, and someone on your team decides whether it becomes the current version. Nothing is repaired or published on its own.
Can verification run inside our environment?
Yes, for customer-hosted verification: the run executes in your environment using only the access you approve, and nothing has to be opened up to the internet. Anything typed into a secure field is dropped before step data leaves the machine, and the run result, step events and step screenshots, returns so a reviewer can see what happened.
Which procedures can be verified?
Supported procedures in supported environments, such as web and desktop applications that a validation run can follow. Not every desktop workflow can be replayed automatically, and physical processes are not validated automatically.
Is verification the same as running a workflow?
No. Running a business workflow performs the work. Verification checks whether a supported documented procedure still works against its target system. Both keep evidence, and they are separate events.
If the process changed, your SOP should know about it.
See how verification works on one of your supported procedures, with the evidence from the run and a reviewed update.
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.