Document a real recurring workflow with roles, controls, exceptions, evidence, and handoff criteria. 제공할 내용: Current process evidence, Rules and controls, SOP use constraints. 예상 결과: A runnable SOP with scope, prerequisites, steps, decision branches, records, checks, escalation, and revision log.
1
맥락 추가
텍스트는 이 브라우저에 유지됩니다. AILesson Prompts는 이를 모델이나 서버로 보내지 않습니다.
2
프롬프트
채워지지 않은 필드는 플레이스홀더로 표시되므로 프롬프트를 복사하고 편집할 수 있습니다
Draft an executable SOP from the supplied observed process and approved controls.
Trigger, purpose, frequency, roles, steps, tools, inputs, outputs, time, and variation:
[process]
Quality, approvals, access, safety, privacy, finance, exceptions, records, retention, and escalation:
[controls]
Users, skill, format, owner, effective date, review cycle, training, systems, and unverified items:
[use]
Separate observed current practice, approved rule, proposed improvement, and unresolved decision. Define purpose, scope and exclusions, trigger, owner and backup, prerequisites, inputs, system permissions, numbered actions, expected result and evidence at each control point, decision branches, handoffs with acceptance criteria, exception paths, stop conditions, escalation, records and retention, completion definition, and process measures. Use one actor and one action per step. Never invent a policy, role, approval, legal or safety requirement, system behavior, access right, duration, retention period, or exception. Put warnings before risky work and avoid exposing secrets or customer data. Add a quick checklist without replacing the detailed procedure, a test scenario for normal and exception paths, training notes, version owner, and change log. Flag any step that cannot yet be run safely.
기본적으로 비공개프롬프트 구성은 브라우저에서 로컬로 이루어집니다. 조직에서 허용하지 않는 한 기밀 정보를 AI 서비스에 입력하지 마세요.
입력에서 결과까지
적용 예시
구체적인 맥락이 이 레시피를 바로 사용할 수 있는 결과로 바꾸는 방법을 확인하세요
실제 입력
Current process evidence
Small online shop packs paid orders each weekday at 15:00. Operations Assistant exports paid, unfulfilled orders from ShopDesk; verifies SKU and quantity; picker retrieves items; assistant scans SKU, packs, weighs parcel, buys carrier label, photographs sealed parcel, marks fulfilled, and places it in pickup cage. Typical 20 orders, 90 minutes. Owner covers absence. Inputs: order export, inventory, packaging. Outputs: labeled parcel and fulfillment record. Variations: missing stock, damaged item, address rejected, order change request.
Rules and controls
Only paid orders may ship. A second person checks orders over CNY 1,000. Customer address must not be copied outside ShopDesk/carrier portal. Missing or damaged stock stops packing and goes to Owner; no substitution without written customer approval. Address rejection goes to Customer Support. Order changes received before label purchase may be reviewed by Support; after label purchase require Owner decision. Keep parcel photo and carrier tracking in ShopDesk; retention period not yet decided. Daily parcel count must equal carrier manifest before cage handoff.
SOP use constraints
For Operations Assistant and trained owner backup. ShopDesk and carrier portal. Plain numbered SOP plus checklist. Owner is document owner. Effective date and quarterly review date not yet approved. New assistant shadows one complete run. System permissions are assigned outside the SOP. Do not invent menu paths.
예시 출력
SOP: weekday paid-order packing
Owner: Shop Owner. Status: draft; effective and quarterly review dates require approval. Scope: paid, unfulfilled physical orders processed at 15:00. Excludes unpaid orders, substitutions without written approval, and system-access provisioning.
Prerequisites: Operations Assistant or trained Owner backup; access already provisioned to ShopDesk and carrier portal; packaging available; pickup cage ready. Never copy customer addresses outside the two approved systems.
Operations Assistant exports the paid, unfulfilled order list at 15:00. Evidence: export timestamp and order count. Stop if payment status is unclear.
Assistant verifies SKU and quantity against each order. For value above CNY 1,000, a second person records completion of the required check; the eligible checker is not specified and must be approved before use.
Picker retrieves the listed units. Missing or damaged stock stops that order; record the exception and route it to Owner. Do not substitute unless Customer Support records written customer approval.
Assistant scans each SKU. Expected evidence: scanned SKU and quantity match the order. A mismatch returns to step 2.
Assistant packs and weighs the parcel, then buys the carrier label in the approved portal. An address rejection goes to Customer Support. A change received before label purchase may be reviewed by Support; after purchase, stop and request Owner decision.
Assistant seals and photographs the parcel without exposing unnecessary customer data, records photo and tracking in ShopDesk, then marks fulfilled. Retention remains unresolved; do not delete records or invent a period.
Assistant places the parcel in the pickup cage. Before handoff, compare physical parcel count with carrier manifest. Any difference stops handoff until reconciled.
Completion: counts match, all parcels have labels, tracking and photos are recorded, and exceptions remain outside the cage. Daily measures: orders received, packed, exception count by type, elapsed time, count mismatch. Quick checklist: paid; SKU/quantity; high-value check; scan match; safe address handling; label; photo/tracking; manifest count. Test one normal order plus missing-stock and post-label-change scenarios before approval.
효과가 있는 이유
1
Control-point evidence makes the SOP auditable instead of a narrative description.
2
Exception and stop paths keep standardization from forcing unsafe improvisation.
결과 확인
Can a trained backup execute every normal step from the supplied information?
Do control points have observable evidence and named authority?
Are exceptions, stop conditions, escalation, records, and unresolved decisions visible?
안심하고 사용하세요
자주 묻는 질문
이 레시피를 언제 사용해야 하는지, 무엇을 제공해야 하는지, 그리고 어떤 부분에서 사람의 검토가 여전히 중요한지에 대한 실용적인 답변
What should I prepare before using “Draft an SOP for a recurring small-business process”?
For “Draft an SOP for a recurring small-business process,” prepare Current process evidence, Rules and controls, and SOP use constraints. Replace placeholders only with information you can verify. If a detail is unknown, preserve that uncertainty explicitly instead of asking the model to infer it.
When is the “Draft an SOP for a recurring small-business process” result not ready to use?
The result is not ready if it does not yet deliver the stated outcome—A runnable SOP with scope, prerequisites, steps, decision branches, records, checks, escalation, and revision log—from the supplied evidence, or if it relies on unresolved assumptions, missing approvals, or invented details. Use the checks as release gates: revise the source inputs or assign a named, authorized reviewer instead of polishing an unsupported output.
Which AI tools have recorded tests for “Draft an SOP for a recurring small-business process”?
The published test record for “Draft an SOP for a recurring small-business process” lists ChatGPT as of 2026-08-28. This confirms recorded runs, not guaranteed compatibility or identical results in later product versions. For another tool or version, keep every constraint visible and repeat the result checks before use.
ChatGPT
