OctiAI

Categories

SOP Builder: Convert Fragmented Notes & Screenshots into a Production SOP

A ChatGPT prompt pack that turns messy process fragments into an auditable, operator-ready Markdown SOP with checks, KPIs, rollback, and versioning.

What You'll Get

How to Use

Provide owners, environment, and SLAs up front

Include the stakeholder list (owners and reviewers), the target environment (production or staging), and any SLA/KPI definitions in your initial input. This minimizes clarifying questions and ensures the SOP contains accurate verification and escalation details.

Works Best With

Use this SOP prompt pack when you have fragmented process notes, screenshots, and at least a named owner and environment.

Prompt Template


## Goal
- Convert a fragmented process description and supporting screenshots into a complete, production-ready Standard Operating Procedure (SOP) that a frontline operator can follow without additional clarification.

## Inputs
- Provide the fragmented process description (paste raw text), screenshots (or a description of each screenshot), stakeholder list (owners and reviewers), environment (production/staging), any existing SLAs or KPIs, desired tone (concise/verbose/technical), and required output format (Markdown/PDF).
- If any of the above items are missing, the prompt below will ask focused clarifying questions before producing the SOP.

## Prompt
You are an expert technical writer and process engineer. Convert the provided fragmented process description and screenshots into a fully executable SOP. Follow these rules precisely and ask clarifying questions if any required detail is missing.

Instructions to follow when composing the SOP:
1. Output must be in Markdown and immediately usable.
2. Required top-level sections (in this exact order): Purpose, Scope, Prerequisites, Inputs, Outputs, Roles and Responsibilities, Procedure, KPIs and Success Criteria, Failure Modes and Rollback Steps, QA Checks, Escalation Matrix, Single-line Summary, Version History.
3. Under Procedure present a numbered step-by-step sequence. Each step must include:
   - Expected outcome
   - Exact commands, UI paths, clicks, API endpoints, or sample payloads where applicable
   - Expected runtime or SLA for the step (e.g., 2-5 minutes)
   - Verification check(s) the operator must perform and the exact log or UI element to confirm success
   - Recovery action for that specific step if it fails
4. Include a short actionable checklist at the end of Procedure (checkbox-style bullets) that an operator can use during execution.
5. KPIs: list measurable metrics, thresholds, measurement frequency, and where to get the data.
6. Failure Modes and Rollback: enumerate likely failure scenarios, root-cause indicators, rollback commands or steps, and validation after rollback.
7. QA Checks: include pre-run, in-run, and post-run tests with pass/fail criteria.
8. Escalation Matrix: list role, contact method, SLA for response, and exact wording for escalation messages (copy-paste ready).
9. Single-line Summary: one sentence describing the purpose and outcome of the SOP.
10. Version History: include a single-line entry for the change you just authored (date YYYY-MM-DD, author placeholder, one-line summary of change).
11. At top of the document, clearly label facts (directly from the provided source material) and assumptions you made. For each assumption, state why it was necessary and how to validate it.
12. Do NOT invent missing operational values (times, addresses, credentials). If a required value is missing, list it as a Clarifying Question and do not proceed until answered.
13. Provide a short “how to test in staging” plan with the minimal safe test data and verification steps.
14. Keep language operational and imperative (e.g., “Run command X”, “Verify Y equals Z”).
15. Produce an executive checklist summary (3-5 bullets) that managers can scan quickly.
16. At the end, output a JSON metadata block (single-line) with keys: title, last_update, author, environment, complexity_estimate (low/medium/high), and required_reviewers (comma-separated). The JSON must be valid and on a single Markdown code line.

If any required input is missing from the content you were given, ask only the specific missing question(s) needed to proceed. Once all missing inputs are provided, produce the complete SOP according to the rules above.

## Output Format
SOP: Purpose → Scope → Procedure → QA checks → Escalation
- The final SOP must contain all sections listed in the Prompt and must follow this main order exactly. Additional sections (Prerequisites, Inputs, Outputs, Roles, KPIs, Failure Modes, Single-line Summary, Version History, facts vs assumptions, checklist, staging test plan, JSON metadata) must appear where specified in the Prompt.

Required document formatting:
- Use Markdown headings for each section (H2 or H3).
- Use numbered lists for Procedure steps and nested sub-steps for commands or verifications.
- Use bold for commands, filenames, UI labels, and thresholds.
- Use checkboxes for the operator checklist.
- The JSON metadata must be valid and on a single line.

## Guardrails
- Clearly separate facts (sourced from provided text/screenshots) from assumptions. Mark them explicitly.
- Do not fabricate credentials, URLs, or SLA numbers. If not provided, list them as Clarifying Questions.
- Cite the screenshot number or text snippet for any fact claimed from inputs.
- For any regulatory or policy statements, do not assert compliance unless a named source is provided; instead, flag as “Requires compliance verification.”
- Ensure steps include safe fallbacks and a tested rollback path before destructive operations.
- Use precise language: when giving commands include exact flags/options; when citing UI flows include menu names and button labels.
- Timezones must be explicit (e.g., UTC or local) wherever time or SLA is referenced.
- Keep the SOP platform-agnostic unless UI elements or commands were provided; if platform-specific, state environment (production/staging).

## Examples
Mini decisions/actions excerpt:
- Decisions:
  - Use nightly batch job for data sync (from screenshot 2).
- Actions:
  - Owner: Alice — implement cron schedule and test in staging by 2026-02-10.
  - Owner: Bob — create monitoring dashboard and alert thresholds by 2026-02-12.

Use the Prompt above by pasting it and then supplying the fragmented process text and screenshots (or screenshot descriptions). The prompt will ask any clarifying questions needed and then produce the full SOP in the required format.

Variables

Usage Notes

Not for

Do not include

SOP Builder: Convert Fragmented Notes & Screenshots into a Production SOP

Convert fragmented process descriptions and screenshots into a complete, production-ready Markdown SOP that includes purpose, scope, prerequisites, inputs/outputs, exact stepwise procedure, KPIs, rollback steps, QA checks, a single-line summary, and version history.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

What you'll get

Output format

Markdown

Best used when

Avoid when

Sign in to save, like, or rate this prompt.

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

No placeholders required for this prompt.

Rules

Canonical Examples

Input: Fragments: notes from a sprint doc explaining deploy steps for 'payments-consumer' microservice, two screenshots: (1) CI pipeline showing a 'deploy-production' job; (2) Kubernetes Deployment YAML snippet with image: registry/<repo>/payments-consumer:VERSION. Stakeholders: Alice (owner), SRE team (reviewers). Environment: production. Desired tone: concise. Output format: Markdown.

Loading result...

Failed to load output.


## Purpose
Ensure safe production deployment of payments-consumer using CI job 'deploy-production'.

## Procedure
1. Trigger CI job 'deploy-production' -> Expected outcome: new image rolled out to production (2-5 mins) -> Command: curl -X POST <CI_TRIGGER_URL> -d '{version:...}' -> Verify: kubectl get pods -l app=payments-consumer

(See full SOP below.)

Why it works: This example supplies all required inputs (fragmented text, screenshot descriptions, owners, environment, tone). The resulting SOP follows the prompt's strict structure and includes precise commands with placeholders, verification checks, rollback paths, a staging test plan, and a single-line JSON metadata block. It demonstrates converting messy CI/UI screenshots into an operator-ready SOP.

Input: Fragments: meeting notes and screenshots describing a nightly ETL data sync from source warehouse to reporting DB. Screenshot 1: cron job schedule '0 02 * * *' in airflow UI. Screenshot 2: sample SQL showing COPY FROM s3://bucket/path. Stakeholders: Data Team (owner: Bob), Analytics (reviewers). Environment: production reporting DB. Tone: technical, verbose. Output format: Markdown.

Loading result...

Failed to load output.


## Purpose
Run and validate the nightly ETL data sync from warehouse to reporting DB triggered by Airflow. Procedure includes triggering DAG, monitoring tasks, verifying row counts, and restoring from backup if needed.

Procedure: 1) Validate source data, 2) Trigger DAG (airflow dags trigger etl_nightly), 3) Monitor tasks, 4) Verify row counts, 5) Rollback using latest backup if validation fails.

Why it works: This example uses the provided fragmented notes and two screenshot descriptions to produce a complete SOP for running and validating the nightly ETL job. It demonstrates inclusion of exact commands (Airflow CLI trigger, SQL sample with placeholders), verification checks, rollback (restore) steps, QA tests, staging test plan, and the required JSON metadata on one line.

Works Best With

Use this SOP prompt pack when you have fragmented process notes, screenshots, and at least a named owner and environment.