Golden Example — SOP (Human)
The Benchmark
The golden example for a Human SOP is the Month-End Close SOP built for Crulliance.
File location: aos-client-rc/projects/accounting-manager-os/builds/ruben-sop-month-end-close-v4-feb-2026.html
Open this file in a browser before building any Human SOP. Study it. Then extract the specific values documented below.
What This Example Demonstrates
Why It's the Benchmark
The Month-End Close SOP is the reference standard because it was built from a complete extraction interview with full team involvement. Every element — team roster, step ownership, phase boundaries, status tag system, escalation protocol — came from the extraction process, not from assumption. Nothing was invented. Every gap was identified and resolved before the build started.
It demonstrates what a Human SOP looks like when the source material is complete. Use it as the target quality standard, not as a content source.
What to Study
Team roster: Notice the specificity. Each person's responsibilities in the roster section are written from the perspective of this process specifically — not their general job description. Pooja's roster entry explains her role in the close cycle. The bookkeepers' entry explains how workload is distributed between them. This level of detail comes from the extraction interview, not from reference data.
Step ownership: Every step has explicit owner tags. No step is owned by a generic role. Ruben and Kevin appear in steps only where CPA judgment is required. The process owner (Pooja) appears in steps she executes — not in every step just because she owns the process.
Phase boundaries: The three phases (Active Close, Review & Delivery, Set Up Next Month) are named for what happens during them, not for generic framework categories. The time windows (Day 1→8, Day 8→15th, 15th→EOM) are specific to how this firm actually runs its close cycle.
Step detail density: Each step's What/When/Who section is specific enough that a new bookkeeper could follow it on day one. The reconciliation step names account types, explains the running-balance shortcut, and addresses the specific exception (loan statements). This density comes from the extraction interview, not from general accounting knowledge.
Gates and flags: The Gate notes identify real hard stops that surfaced during extraction — not generic best practices. The self-review gate exists because the extraction revealed that manager review was catching issues that a 10-minute bookkeeper review would have caught first.
Status tag system: The four tags (Expected On Time, In Review, Push — Waiting on Client, Push — Info Received Late) reflect how this firm actually tracks client status. The names and definitions came from the extraction interview, not from a generic project management framework.
Parking lot: Five specific items, each with real context. The ask-client item standardization entry names the actual tools in play (Uncat, Financial Cents, QuickBooks) and the real tension (three platforms doing the same thing). This came from the extraction, not from invention.
Values to Extract Before Building
When building a Human SOP, open the Month-End Close file and extract these exact values. Do not work from memory.
Colors
Brand navy: #122640
Brand green: #3d7a5f
Brand gold: #C4A44D
Brand copper: #c4785e
Brand stone: #8a8680
Cream text: #f8f7f4
Body text: #0a0a0a
Secondary text: #6a6a6a
Gate red: #dc2626
Gate background: #fef2f2
Flag amber: #ca8a04
Flag background: #fefce8
Pending background: #f0f4ffTypography
Heading font: Cormorant Garamond (loaded from Google Fonts)
Body font: Inter (loaded from Google Fonts)
Code font: JetBrains Mono (only if workflow block present)
Description: 1.15rem, line-height 1.8
Container: max-width 920pxStep Card
Step number: Cormorant Garamond, 1.75rem, weight 400, color #122640, opacity 0.45
NO border-radius. NO background. NO circle.
Step title: 1.2rem
Step summary: 13px
Step header: padding 20px 28px
Step card margin: 12px
Step numbers: 1, 2, 3 (NOT 01, 02, 03)Phase Dividers
Active (Phase 1): rgba(61, 122, 95, 0.04) — green tint
Review (Phase 2): rgba(18, 38, 64, 0.04) — navy tint
Setup (Phase 3): rgba(196, 164, 77, 0.06) — gold tint (0.06, not 0.04)Dark Background (Monthly Rhythm)
Column titles: rgba(248, 247, 244, 0.7)
Day markers: rgba(248, 247, 244, 0.85)
Checkpoint labels: rgba(248, 247, 244, 0.35)
Body text: rgba(248, 247, 244, 0.85)
De-emphasized: rgba(248, 247, 244, 0.5)Rule: All text inside navy dark backgrounds uses cream at varying opacities. Never gold. Never green. Never white. Never phase colors.
Version Badge
Active status: navy background (#122640), dot color #3d7a5f (brand green, NOT #22c55e)
Draft status: amber background (#ca8a04), dot color #f8f7f4 (cream)CSS Classes
Readiness bars: .context-bar (NOT .context-checkbox)
Step numbers: .step-number
Step owner tags: .step-owner-tag.[role]What the Golden Example Does NOT Provide
Team roster for your SOP. The Month-End Close roster (Pooja, Ruben, Kevin, Sarah, Anas, Jheanifer, Patty, Sariah, Krisha) is specific to that process. Your SOP may involve a completely different set of people in completely different roles. Pull from the extraction interview and reference data.
Process owner for your SOP. Pooja owns the Month-End Close. That tells you nothing about who owns the SOP you're building.
Phase structure for your SOP. The three-phase model is a pattern that works well for cyclical processes. Your process may have two phases, four phases, or no phases at all. The phase structure comes from how the client experiences the process — not from matching the golden example.
Step content for your SOP. The close steps are specific to a CAS accounting practice's month-end workflow. Do not draw on them as a source for steps in a different process.
Parking lot items for your SOP. Every parking lot item in the golden example surfaced during extraction for that specific process. If parking lot items don't come from the extraction, they don't exist.