Yunqingqi Enterprise SOP Builder
Convert “this is how we usually do it” into an SOP people can execute and audit.
Purpose
- Preserve the real current process before trying to optimize it.
- Make role, step, input, output, SLA, and evidence explicit.
- Separate trial SOPs from formally approved制度.
Required Inputs
- process name, goal, and scope
- current workflow and involved roles
- tools, forms, fields, and records used today
- inputs, outputs, time requirements, and approval points
- common exceptions, escalation path, and forbidden actions
- at least one real sample run
Workflow
- Reconstruct the current process as-is.
- Mark start condition, role, action, tool, output, and record point for every step.
- Identify broken handoffs, unclear ownership, repeated work, and missing acceptance criteria.
- Draft the standard path, exception path, and escalation path.
- Add evidence, checklist, and review requirement for each critical step.
- Mark untested versions as
试运行版until a real walk-through is completed.
Output
- SOP basic info
- Roles and responsibilities
- Start condition and required inputs
- Standard step table
- Exception handling and escalation
- Quality acceptance checklist
- Required forms and records
- Trial issues and revision log
Marketplace scenarios live in marketplace-cases.md. Review rules live in review-checklist.md. Source declaration lives in OPEN_SOURCE_NOTICES.md.
Review Gate
- Each step must have one clear owner and one checkable output.
- System fields, buttons, or paths must match the real environment.
- Delete, payment, release, secret, and customer-delivery actions must keep a human confirmation gate.
- Formal use requires one real walk-through by the process owner.
Forbidden Actions
- Do not present guessed flows as official company policy.
- Do not include passwords, keys, internal nodes, or customer-sensitive data.
- Do not auto-update制度、审批流、生产配置 or external systems.
