Evergreen SOP Building Method
Document complete processes so others can execute them without assistance
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 7
- Confidence
- 99%
The Evergreen SOP Building Method turns a recurring business activity into a complete, maintainable reference document. It begins with a concise name and summary, then establishes the process objective, participating roles, KPIs, and frequency. The author divides the detailed process into navigable sections and documents the work from its actual starting point, including logins, URLs, buttons, dependencies, and standards that experienced employees may take for granted. Written instructions form the durable core because they are easier to update than long videos. Screenshots, short videos, and explanatory callouts support the text where they add clarity. Large subprocesses receive separate linked SOPs, preventing one document from becoming unwieldy. The final output should let a new employee understand both how the work is completed and why each important action exists.
Origin
Extracted from The Jasmine Star Show. Jasmine Star Brands created a standardized Notion template after struggling to build SOPs and continued using the resulting method four years later across multiple businesses.
Core principles
- 01Write for a capable newcomer with no hidden context
- 02Explain why the process matters as well as what to do
- 03Use roles rather than employee names to keep documentation evergreen
- 04Prefer editable written steps over videos that become stale
- 05Separate reference documentation from task execution
- 06Link substantial subprocesses instead of duplicating them
How to run it
- 1
Define the Process
Give the SOP a specific action-oriented name and a one-sentence summary of what the reader will know how to do. Add the objective or intended outcome in a short contextual paragraph.
Pro tip A reader should be able to confirm they opened the correct SOP from the first sentence.
Watch out Do not begin with steps before defining what successful completion means.
- 2
Record Ownership and Measures
Identify responsible, accountable, consulted, and informed roles using role names rather than personal names. Add relevant KPIs and state how frequently the process occurs.
Pro tip Mark a role as not applicable rather than leaving an ownership field blank.
Watch out Using employee names forces unnecessary updates whenever staffing changes.
- 3
Create Navigable Sections
Divide the work into logical milestones or subprocesses and expose them through quick links or a table of contents. Use consistent heading levels and formatting across the company.
Pro tip Existing project milestones often provide a useful first draft of the section structure.
Watch out Do not create a wall of instructions with no way to locate a specific phase.
- 4
Write Granular Instructions
Document the process from the true beginning, including where to log in, which URL to use, what to click, and what deliverable to produce. Reuse accurate instructions from existing task templates before adding missing detail.
Pro tip Write as though the reader has joined the company today and cannot ask you a question.
Watch out Do not omit actions merely because they feel obvious to an experienced team member.
- 5
Explain the Why
Add contextual callouts that explain why consequential steps, standards, or constraints exist. This helps employees make better decisions when circumstances vary.
Pro tip Prioritize explanations for steps that commonly attract questions or shortcuts.
Watch out Purely robotic instructions can produce compliance without understanding.
- 6
Add Supporting Media Selectively
Use screenshots or videos when they clarify interfaces or complex actions, but keep written steps as the primary source of truth. Place any overview video near the top.
Pro tip Use small visual aids that can be replaced independently when a screen changes.
Watch out A long video-only SOP becomes expensive to maintain after minor process changes.
- 7
Link Independent Subprocesses
When one portion is substantial enough to stand alone, create a separate SOP and link it at the appropriate point. Keep the parent SOP focused on the end-to-end flow.
Pro tip Split a subprocess when it is reused elsewhere or has its own detailed sequence.
Watch out Do not duplicate the same detailed subprocess across several documents.
In the wild
Jade uses creation of an opt-in to illustrate a parent SOP involving copywriting, graphic design, marketing strategy, testing, and publication. The technically detailed landing-page and campaign setup can exist as a separate SOP linked from the broader opt-in process.
→ The team receives one comprehensible end-to-end process without duplicating a complex reusable subprocess.
Social Curator's project-management SOP includes an objective, intended audience, quick links, detailed sections, screenshots, videos, templates, contextual explanations, task requirements, due-date rules, lead times, and KPIs.
→ Managers can assign work consistently while team members receive enough information to proceed without repeated clarification.
Common mistakes
Making Video the Source of Truth
Long recordings become stale and cumbersome to replace when only a few steps change. Written instructions should remain the maintainable core.
Writing for Existing Experts
Skipping logins, links, clicks, context, or deliverables leaves newcomers unable to reproduce the process independently.
Turning the SOP Into a Live Checklist
Checking boxes inside the reference document makes it messy and confuses documentation with recurring task execution.
Is it for you?
Best for
It is best for recurring business processes that multiple people must execute consistently over time.
Not ideal for
It is not ideal for highly exploratory work where the desired process and output remain unknown.
From the transcript
“Our goal and standard for an SOP is if I dragged you in off the street, our SOPs are so good that you could just…”
“The goal for the SOPs Really is to be able to have things in written form, step by step.”
“And then the goal with this is to communicate the whole picture for how to do something step by step.”
From the episode
Why Systems Are the Secret to 8-Figure Growth