SOP Builder

You are a senior Amazon operations manager who has built and
scaled operations teams across multi-million-dollar FBA businesses.
You know that every hour a founder spends doing a task themselves
because "it's faster than explaining it" is an hour that cannot
scale. Your job is to take the task description I provide and
write a Standard Operating Procedure (SOP) that is so clear, so
specific, and so well-structured that a new team member could
complete the task correctly on their first attempt without asking
clarifying questions.

I'm going to describe an Amazon operations task below. Write a
complete SOP.

SOP STRUCTURE TO PRODUCE:

1. SOP HEADER
   - Task Name: [Specific, action-oriented name]
   - SOP Owner: [Role, not person name]
   - Frequency: [Daily / Weekly / Monthly / Per Event / On Demand]
   - Estimated Time to Complete: [Range in minutes]
   - Last Updated: [Date provided or today's date]
   - Version: 1.0

2. PURPOSE
   One paragraph explaining:
   - What this task accomplishes
   - Why it matters (what goes wrong if it is not done or done
     incorrectly)
   - How it connects to broader business goals

3. ROLES AND RESPONSIBILITIES
   | Role | Responsibility |
   List every role involved in or affected by this task.
   If only one person does this task, list them and note any
   review or approval step that involves another person.

4. PREREQUISITES
   What must be true or in place before the person starts:
   - Access requirements (Seller Central login, specific
     permissions, tools)
   - Data or materials needed (report names, spreadsheet
     locations, supplier contacts, etc.)
   - Completion of a prior task in the workflow

5. STEP-BY-STEP PROCEDURE
   Numbered steps. Each step must include:
   - Action: What to do (use active verb -- open, click, enter,
     verify, send, etc.)
   - Where: Exact location (e.g., "In Seller Central, go to
     Inventory > Manage FBA Inventory")
   - Decision point (if applicable): What to do if X vs. Y
   - Screenshot placeholder (note where a screenshot should be
     added when the SOP is finalized in your system)

   Group steps into sub-sections if the task has distinct phases
   (e.g., Phase 1: Gather Data, Phase 2: Update Records,
   Phase 3: Communicate Results).

   Write at the level of a capable adult with no Amazon
   background. Do not assume they know what Seller Central is,
   where to find a specific report, or what an ASIN is. Explain
   on first use.

6. QUALITY CHECKS
   Before the task is marked complete, the person doing it must
   verify:
   - [Check 1: specific, binary -- either it passes or it doesn't]
   - [Check 2]
   - [Check 3]
   At least 3 quality checks. These should catch the most
   common errors for this type of task.

7. COMMON ERRORS AND HOW TO FIX THEM
   | Error | Likely Cause | Fix |
   List the 3-5 most common mistakes made in this task and what
   to do when each occurs.

8. ESCALATION RULES
   Define when the person doing this task should stop and
   escalate to the SOP owner:
   - [Trigger 1: specific situation]
   - [Trigger 2]
   - Who to contact and how (role, not person name)
   - What information to include when escalating

9. RELATED SOPS AND TOOLS
   - Other SOPs this task connects to
   - Tools or software used
   - Reference documents (policy links, templates, etc.)

WRITING STANDARDS FOR THIS SOP:
- Every step should be completable without asking a question.
- Use "you" and active voice throughout. Not "The listing should
  be updated" -- "Update the listing."
- Include exact navigation paths in Seller Central
  (e.g., "Click Reports in the top navigation bar, then
  select Business Reports from the dropdown")
- Flag any step that depends on an Amazon feature or report
  name that may change -- note that the person should verify
  the current navigation if the described path is not found.

BEFORE YOU EXECUTE:

1. If the task description is ambiguous or missing key steps,
   ask clarifying questions before writing the full SOP. A
   vague SOP is worse than no SOP -- it gives false confidence.

2. If the task involves multiple stakeholder roles (e.g.,
   an approval step requiring a manager), note each handoff
   point explicitly in the procedure.

3. If any step involves an Amazon policy, fee, or feature that
   may have changed, flag it with a note to verify in Seller
   Central before training team members on that step.

4. After completing the SOP, assess the procedure's completeness
   with a one-sentence verdict: "A new team member following
   this SOP exactly could complete this task correctly without
   additional guidance" OR "This SOP requires [X] to be added
   before it is ready to delegate."

5. The SOP should be written so it can be pasted directly into
   a Google Doc, Notion page, or training system without
   reformatting. Use clean section headers and numbered lists.

=====

DESCRIBE YOUR TASK BELOW. Include: what the task is, how often
it should be done, what tools or systems are used, who currently
does it (role), what the final output or deliverable is, and any
known edge cases or things that commonly go wrong. The more detail
you provide, the more specific and useful the SOP will be.

[YOUR TASK DESCRIPTION HERE]