SOP Knowledge Pack Builder (Source Docs → Canonical SOP → Versioned Updates)
Consolidate scattered documents into a canonical SOP with versioning, change log, and open questions list.
Prompt Overview
Tips For You
Add definitions for recurring terms to avoid misinterpretation. Use consistent IDs for steps to link with automation later. Track unresolved items with owners and due dates.
From Operations TeamNexusAi TechnologyProblem It Solves
Fragmented knowledge slows onboarding and creates inconsistent execution. Centralization speeds clarity.
Canonical Structure
Standard sections to accelerate training.
Conflict Resolution
Flags and rationalizes competing inputs.
Change Log
Versioned edits for accountability.
Open Questions
Tracks blockers with owners and dates.
AI Prompt Instructions
Act as: A documentation lead and process editor.
Why this task matters: A single source of truth reduces ambiguity and training time.
Important boundaries:
- Keep sections standard: Purpose, Scope, Roles, Definitions, Preconditions, Procedure, Exceptions, Approvals, SLAs, Evidence, Change Log.
- Cite sources and flag conflicts.
User inputs:
- Multiple source docs, emails, screenshots
- Existing SOP fragments
- Stakeholder list
Objectives:
1) Merge inputs into a canonical SOP.
2) Resolve or flag conflicts with rationale.
3) Produce a versioned change log.
4) List open questions blocking publication.
Analysis workflow:
1) Extract overlapping content and normalize terminology.
2) Structure the canonical SOP with stable headings.
3) Summarize conflicts and proposed resolutions.
4) Draft change log and stakeholder review plan.
Required output format:
- Canonical SOP (sections as listed)
- Conflicts: [Section, Issue, ProposedResolution]
- Change Log: [Version, Date, Change, Author]
- Open Questions: [Area, Question, Owner, Due]
Quality controls:
- All procedures are stepwise and observable.
- SLAs and approvals stated explicitly.
Final instruction: Deliver the full SOP and tables, ready to paste into a docs repo.
Expected Outcome
Canonical SOP: Purpose: Standardize refunds with clear evidence Scope: Orders < $1,000 Procedure: 1) Verify order... 2) Validate eligibility... Conflicts: Approvals | Thresholds differ ($500 vs $750) | Adopt $750 with pilot Change Log: v0.1 | 2026-07-28 | Initial consolidation | Ops Open Questions: Evidence | Is screenshot acceptable? | Finance | 2026-08-05
Implementation Journey
Assemble sources in ChatGPT
Paste the set of source docs and fragments into ChatGPT with this prompt. Expect a canonical SOP, conflicts, change log, and open questions.
20-30 minReview in a doc tool
Paste the SOP into your docs platform (Notion, Confluence). Tag stakeholders to resolve conflicts and answer open questions with due dates.
20-40 minPublish and version
Assign a version number, publish to the docs repo, and link step IDs to the workflow mapping outputs for future automation.
10-20 min