How to Resolve Conflicting SOPs Before AI Repeats the Wrong Instructions

The problem is authority, not just search

A teammate asks how to onboard a customer. The wiki says to use Checklist A. A newer project note links Checklist B. A Slack message says to skip one step for a specific account. An AI answer can retrieve all three and still give bad guidance if it merges them into a single procedure.

The right first output is a short conflict record. It should show exactly where the sources disagree, which situation each source covers and who can resolve the difference. More confident phrasing will not repair an unclear source hierarchy.

Classify the conflict before rewriting anything

The review action is not a verdict. A step that looks outdated may reflect a requirement the reader does not know about. Record the question and evidence instead of deleting the instruction because it seems inconvenient.

Use ownership and verification without confusing them with truth

Notion's verified pages support page owners and verification periods, with notifications when verification expires. Those signals can help route a review. Check their availability in your actual workspace before making them part of your process.

A verification badge tells the team something about a review process; it does not resolve every new contradiction. Similarly, a last-edited date could reflect a spelling fix. Ask which substantive version the owner approved, for which audience and from which effective date.

Build a six-part conflict record

• Question: the exact operational step a teammate is trying to perform.
• Applicable scope: team, product, audience and conditions relevant to this case.
• Conflicting instructions: short accurate excerpts or paraphrases with source links.
• Version evidence: current owner, substantive revision and effective date when known.
• Decision needed: the narrow question that would resolve the contradiction.
• Affected references: templates, onboarding guides or recurring jobs that may repeat the old instruction.

Keep unknown fields visibly unknown. Do not infer ownership from the person who most recently edited a page, and do not infer approval from a reaction to an older draft. The owner of the process may differ from the owner of the document.

Work the onboarding example through

In a fictional team, Checklist A includes an internal readiness review. Checklist B was drafted for a new self-serve segment and omits that review. The Slack exception applies to one long-standing customer. A generic answer saying 'use the newest checklist and skip review' would combine three different scopes incorrectly.

The conflict packet should ask whether the current customer belongs to the self-serve segment, whether Checklist B was approved for that segment and whether the exception applies here. Until those facts are established, it should not invent a universal replacement procedure.

The owner might confirm that both checklists are valid for different groups. In that case the useful correction is an explicit entry condition and cross-link, not deleting one checklist. Or the owner may approve B as a full replacement and identify A as superseded. Preserve that actual decision.

Ask Mio to compare sources, not arbitrate authority

Mio's Notion workflow describes reading company documents from Slack and proposing edits. Its product-operations case includes identifying conflicting internal framing and suggesting clearer wording. Neither establishes that AI should decide which company rule has authority.

Try: 'Compare these procedures for this specific task. Show conflicting steps, scope differences, known owners and version evidence. Separate proposals and exceptions from accepted guidance. Draft questions for the process owner and a minimal correction after their decision. Do not change documents, mark pages verified or execute the disputed step.'

Review the output in a channel whose audience is authorized to see the supporting material. Use source links instead of copying restricted procedures into a wider discussion. Keep any sensitive approval with the existing responsible function.

Verify the correction where people will use it

After the owner approves a correction, update the canonical procedure through the normal process and mark the old guidance appropriately. Test the original question again. Does a teammate find the right scope, identify the current version and understand when to ask for an exception?

Check dependent instructions too. If a recurring job cites the old procedure, its workflow runbook needs a reviewed source update. Fixing one page does not prove every downstream answer is current.

Start with one frequently used procedure. Track unresolved contradictions, incorrect answers and references still pointing to superseded guidance. The goal is a correct next step, not a larger wiki. Review company context with Mio.