Standard Operating Procedures · JSON Structure

Standard Operating Procedures Sop Structure

Structural documentation for a Standard Operating Procedure (SOP) document

Type: Properties: 16

ComplianceDocumentationProcess ManagementQuality AssuranceRegulated IndustriesWorkflows

Standard Operating Procedure Structure is a JSON Structure definition published by Standard Operating Procedures, describing 16 properties.

Properties

id title version status effective_date review_date department category purpose scope responsibilities steps author approver revision_history regulatory_references

Meta-schema:

JSON Structure

{
  "name": "Standard Operating Procedure Structure",
  "description": "Structural documentation for a Standard Operating Procedure (SOP) document",
  "properties": {
    "id": { "type": "string", "description": "Unique document ID (e.g., SOP-QA-001)" },
    "title": { "type": "string", "description": "Name of the procedure" },
    "version": { "type": "string", "description": "Document version (e.g., 1.0, 2.3)" },
    "status": { "type": "string", "description": "Lifecycle status: draft, review, approved, effective, retired, superseded" },
    "effective_date": { "type": "string", "description": "ISO 8601 date the SOP becomes effective" },
    "review_date": { "type": "string", "description": "ISO 8601 scheduled review date" },
    "department": { "type": "string", "description": "Owning department or function" },
    "category": { "type": "string", "description": "Process category (e.g., Quality Assurance, Safety)" },
    "purpose": { "type": "string", "description": "Why this SOP exists" },
    "scope": { "type": "string", "description": "Who and what is covered" },
    "responsibilities": {
      "type": "array",
      "description": "Role/responsibility pairs",
      "items": {
        "role": { "type": "string" },
        "responsibility": { "type": "string" }
      }
    },
    "steps": {
      "type": "array",
      "description": "Ordered procedural steps",
      "items": {
        "step_number": { "type": "integer" },
        "title": { "type": "string" },
        "instruction": { "type": "string" },
        "responsible_role": { "type": "string" },
        "expected_output": { "type": "string" },
        "decision_point": { "type": "boolean" },
        "cautions": { "type": "array", "items": { "type": "string" } }
      }
    },
    "author": {
      "type": "object",
      "properties": {
        "name": { "type": "string" },
        "role": { "type": "string" }
      }
    },
    "approver": {
      "type": "object",
      "properties": {
        "name": { "type": "string" },
        "role": { "type": "string" },
        "approval_date": { "type": "string" }
      }
    },
    "revision_history": {
      "type": "array",
      "items": {
        "version": { "type": "string" },
        "date": { "type": "string" },
        "author": { "type": "string" },
        "changes": { "type": "string" }
      }
    },
    "regulatory_references": {
      "type": "array",
      "description": "Applicable regulations this SOP satisfies",
      "items": { "type": "string" }
    }
  }
}

Work with this as data

Every JSON Structure here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for json structure

4 MCP tools reach this

find_json_structuresBrowse and filter every JSON Structure in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This JSON Structure

curl "https://apis.io/api/v1/json-structures/standard-operating-procedures-sop-structure"

All json structure

curl "https://apis.io/api/v1/json-structures?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.