For MSPs and small IT teams
Catch the SOP that just went out of date, before a tech follows the wrong step.
ProcedurePulse watches the Microsoft 365, Google Workspace, and vendor admin consoles your runbooks depend on, and sends one weekly report naming each procedure that has become inaccurate.
Early access for the first teams. No card required.
Reset a user's MFA in Microsoft 365
Step 4 points to "Azure Active Directory." Microsoft renamed this to "Microsoft Entra ID."
Proposed fix: update the menu path and the two screenshots that follow.
Offboard a Google Workspace account
The "Delete user" confirmation flow added a required data-transfer step before deletion.
Proposed fix: insert step 6 covering the transfer prompt.
The problem
Your SOPs don't fail loudly. They just quietly go wrong.
You document how to reset MFA, offboard a user, or configure a mailbox. Then Microsoft renames a blade, Google reorders a menu, or a vendor changes a policy, and your written steps no longer match the screen. Nobody gets an alert. The doc still looks finished.
Where it bites
- A new technician follows a runbook step-by-step and hits a screen that isn't there.
- A client-facing procedure sends the wrong instructions and generates a ticket.
- An audit finds documentation that no longer reflects how the system actually works.
Why it keeps happening
- The software behind your SOPs changes constantly, on a schedule you don't control.
- Nobody owns re-reading twenty procedures every week to check them against live consoles.
- The tools you already use store documents; they don't watch the world your documents describe.
How it works
Point it at your procedures. Read one report a week.
Upload an SOP or connect a docs folder, then name the software and source pages each procedure depends on. The agent monitors those sources and, when something changes, its weekly report gives you four things for every affected procedure.
Affected SOP
The specific procedure that the change touches, named, not a list of "pages that changed."
Exact outdated step
The line, menu path, or screenshot inside that SOP that no longer matches the live product.
Evidence
What changed at the source, quoted, so a technician can confirm it in seconds.
Proposed revision
A suggested edit to the step, ready for a human to approve or adjust before it lands.
Why it's different
SOP tools store your docs. Change monitors watch pages. Neither closes the gap.
Compared with SOP and knowledge-base tools
Hudu, IT Glue, Notion, and Google Docs hold your procedures well, but they assume the words stay true. They have no idea when the software you wrote about moved on.
ProcedurePulse watches the products your SOPs describe and tells you which stored procedure is now wrong.
Compared with generic page-change monitors
A page-diff tool tells you "this URL changed." You still have to figure out whether it matters and which of your twenty runbooks it breaks.
ProcedurePulse maps the change back to the exact procedure and step, so you get a fix to review, not a diff to investigate.
Pricing
One flat price per workspace.
- Monitor the procedures for one workspace
- Weekly report: affected SOP, exact step, evidence, proposed fix
- Microsoft 365 and Google Workspace admin sources supported
- Connect uploads, a docs folder, or paste procedures directly
- Human approval on every proposed revision
Early access
Be one of the first teams to try it.
Leave your work email and we'll reach out as we bring teams on. We build the initial monitoring around what early users actually document.
Prefer email? Write to [email protected].