Manage and update standard operating procedures

Manage and update Shaw's standard operating procedures

Repeatable processes Shaw executes regularly—when you extract the core procedure (not transcribe conversation) and save it as a tight reference checklist.

• · process Shaw describes or repeats
• · process name and target audience (who executes)
• · steps, decision points, and edge cases
• · email/message templates for the process

• · Notion SOP page under correct category
• · checklist-style steps (short, imperative bullets)
• · email/message templates separated by --- dividers
• · links to related Notion pages

• · Notion MCP (notion-update-page, notion-search, notion-create-pages)
• · Notion SOP parent page structure (categories and child pages)

• · Shaw's SOP library in Notion (ABA Master workspace)
• · Process is repeatable (not one-time)
• · SOP category fits under existing structure (Acquisition, Delivery, etc.)

• · Creating duplicate SOP without searching first → shelf of near-duplicates
• · Over-engineering template → bloat (Purpose, Scope, Version, etc.)
• · Missing reference links to related pages → disconnected SOP
• · Nesting > 2 levels deep → unclear hierarchy
• · Using Markdown [links] instead of Notion <mention-page> → breaks live references

• · Format conventions documented (two sections: checklist + templates)
• · Style rules explicit (short imperative bullets, preserve shorthand like FU/ID, 2-level nesting max)
• · Search-before-create protocol to avoid duplicates
• · Notion-specific markup guidance (<mention-page> vs. Markdown links)