AI Workflows · Guide
Find Conflicting Instructions in a Team Playbook With AI
Use a comparison pass to surface contradictions, then let the process owner decide the rule.
A team playbook can grow into several documents that are individually clear and collectively confusing. One page says to ask an editor before scheduling; another says a producer may publish after the checklist. A new teammate does not know whether the difference reflects context or an outdated rule. AI can help find possible conflicts across a small set of pages, but it cannot decide whose instruction has authority. The useful output is a traceable list of questions for the owner. Choose one process and a bounded source set. Include the current playbook page, related checklist, and any approved exception notes. Label each document with its owner, status, and review date. Do not feed the entire shared drive to an assistant and assume a contradiction report is complete. Old drafts and meeting notes can be evidence of a proposed change, but they should not be treated as current instructions.
Ask for evidence, not a rewritten policy
A comparison prompt should request the exact passages that appear to disagree, their document titles and locations, and the condition under which each applies. It should also ask the assistant to say when the pages might be compatible. “Submit for approval” and “publish after approval” are not contradictory. “Use form A” and “use form B” may be compatible if one applies to a different project type. A good report preserves the qualifiers rather than stripping them to create an easy conflict. Check every cited passage against the original page. Models can merge nearby lines or attach a correct quote to the wrong version. Mark findings as confirmed conflict, context-dependent difference, stale copy, or false alarm. If the distinction depends on an unstated business rule, ask the process owner. Do not quietly choose the newer timestamp; a recently edited page may still describe a draft.
Resolve one source of truth
For a confirmed conflict, have the owner state the current rule, effective date, and which documents should change. Update the authoritative page first, then align the secondary checklist or template. A correction that only adds a caveat to one page may leave the other page wrong. Keep a short record of the decision so future editors know why the wording changed. Avoid building a complicated policy system for a handful of pages; clear ownership and links may solve the problem. If the owner has not decided, keep the ambiguity visible. Direct teammates to a human contact or an established holding step. An AI-generated synthesis can sound plausible enough to become de facto policy, especially when it appears in search results. Do not publish that synthesis as a resolved answer until the decision is made.
Test the correction with a user question
After editing, ask a teammate unfamiliar with the dispute to answer a realistic question using the playbook. Can they identify the right path without reading several conflicting pages? Check links and section headings. Then rerun the same comparison against the corrected source set; it should no longer flag the confirmed conflict, though it may find another issue. The test is about the reader's next action, not simply about making an AI checker quiet. Imagine the playbook says a customer complaint goes to support, while a checklist says product owners receive every complaint. The difference may reflect severity or a temporary escalation. The owner must decide which cases go where and name the trigger. The repaired documents should show an ordinary complaint and an exception with a clear handoff. A model can point to the two sentences; people must define the boundary. The exercise is complete when the current rule is easy to find and the former contradiction no longer changes a teammate's action. Save the small comparison record with the decision. Future scans can revisit the same document family after a process change, but they should remain a check on source maintenance rather than a substitute for ownership. Pay attention to the answer surfaces people actually use. A corrected policy page does little good if an old checklist is still pinned in the team channel or embedded in a form. List the common entry points and update the ones that repeat the disputed instruction. If a searchable archive must retain the older version, label it clearly as historical and link to the current rule. Then test a realistic search phrase from a new teammate. The first result should lead to the approved instruction, not another unresolved fork.
Try this next
give an assistant two current pages from one process and ask it to return only alleged conflicts with exact passage locations and possible context differences.
Sources and update note
Follow the linked official source before a product, price, plan, or policy decision.