Skip to main content
Verslay
All Use Cases
Operations

Notion SOP Drift Detector

Stop running the business from stale SOPs.

Keeps operational documentation aligned with reality by identifying Notion SOPs most likely to be outdated.

Best forConsultingProfessional ServicesSaaS
Agents7 required
Duration5-10 minutes

Audits SOP pages for age, owner gaps, process contradictions, and references to outdated systems or roles.

How it runs

Multi-agent orchestration — here's the flow, step by step.

01

Call verslay_recall to retrieve prior SOP audit baselines, version history, and team-process expectations from memory. Then query the configured Notion SOP database — fetching all SOPs with their full content, owner, last-edited date, version tag, and linked process tags. Also pull any recent team meeting notes that reference process changes, since these may indicate undocumented SOP updates. Store raw SOP inventory as Phase 1 output.

notion knowledge base operator
02

Consume Phase 1 SOP inventory. Detect drift signals: (a) SOPs not edited in > 180 days where the process is known to have changed (from verslay_recall); (b) SOPs referencing deprecated tools, old team members, or outdated workflows; (c) SOPs missing step-level owners; (d) process tags in meeting notes that don't have a corresponding SOP page. Produce a drift classification table with severity (critical/moderate/low) per SOP.

knowledge synthesizer
02

In parallel with knowledge-synthesizer, call verslay_web_search and verslay_news_search targeting 'SOP drift detection best practices' and 'process documentation lifecycle management'. Call verslay_scholar_search for organizational process compliance research. Identify best-practice review cadences, ownership models, and version-control approaches for SOPs. Pass recommendations to Phase 3.

web researcher
03

Consume Phase 2 drift classification table and Phase 2 best-practice recommendations. Compute SOP health metrics: total SOPs, drift rate (percentage with any drift signal), critical-drift count, average SOP age, and orphaned-process count (processes in meeting notes lacking a SOP). Call verslay_chart_create to generate a drift-severity distribution bar chart and an SOP-age histogram. Apply recommended review cadences to flag overdue reviews.

data analyst
04

Consume Phase 3 health metrics and charts, Phase 2 drift classification, and Phase 2 review-cadence recommendations. Format the SOP drift report: (a) health summary with drift rate; (b) critical-drift SOPs needing immediate update with owner and deadline; (c) moderate-drift SOPs for next review cycle; (d) missing SOPs list with suggested owners; (e) recommended review schedule by process category.

report formatter
05

Consume Phase 4 drift report and charts. Write a SOP governance brief: overall drift health, top three compliance risks, recommended ownership assignments for ownerless SOPs, and a 60-day SOP remediation sprint plan. Call verslay_memorize to store the updated SOP health state, drift classifications, and review schedule in memory.

executive briefing writer
05

Receive the SOP governance brief from executive-briefing-writer. Deliver to the configured Slack channel or email the operations owner. Confirm delivery and log send timestamp.

distributor

Required Agents

7
  • notion-knowledge-base-operator
  • knowledge-synthesizer
  • web-researcher
  • data-analyst
  • report-formatter
  • executive-briefing-writer
  • distributor

Connections

Required

notion

What it does

  • SOP age scan
  • Owner gap detection
  • Contradiction hints
  • Archive candidates
  • Update queue

Example prompt

Find Notion SOPs that look stale or contradictory. Recommend which to update, archive, or assign an owner.

Ready to deploy Notion SOP Drift Detector?

Start free. One click, full agent orchestration.

Get Started Free →