ILLUSTRATIVE EXAMPLE — fictional shop, people and product data.
Prepared for the Orkas virtual assistant SOP guide. No two-account app
execution or customer result is claimed. No listings have been published.

SOP: Prepare 12 product-listing drafts
Version: 1.0 | Updated: 2026-11-04 | Maintained by: Maya, shop owner

RESULT AND PEOPLE
Deliver 12 records in listing-drafts-v1.json: source SKU, title (up to
70 characters), description (20–45 words), three factual bullets and issues.
Leo, the human remote assistant, prepares drafts. Maya reviews them.
Start when Maya assigns the batch. Example deadline: Nov 6, 2026,
16:00 Asia/Shanghai. Checkpoint: Maya reviews PCH-001 before the other 11.
This is a manual assignment; no recurring automation is included.

INPUTS AND ACCESS
products-source.json, version 1.0, contains 12 fictional product records.
Use the color, material, dimensions, closure, pack count and care as given.
Brand voice: plain English, no hype. Do not add sustainability claims,
certifications, delivery promises, discounts or invented product benefits.
No store login is needed for this draft-only task. Each person uses their
own AI account/model access if they choose to use AI.

WORK SEQUENCE
1. Confirm there are 12 unique SKUs; identify absent or conflicting facts.
2. Prepare PCH-001. Maya checks the structure and tone before the batch.
3. Prepare the other 11 with the same structure and original SKU.
4. Compare each title, description and bullet against its source record.
5. Check title and word limits, bullet count and completeness of the batch.
6. Deliver listing-drafts-v1.json and review-and-handoff.txt together.

DECISION AUTHORITY
Leo may draft and adjust wording. Maya decides on missing product facts
and all publishing, price changes, account access and spending.
PCH-012 has no care instructions. Draft from its other supplied facts,
omit care advice and label it needs_owner_input. Continue the other 11.
The full batch remains unapproved until Maya resolves the exception.

ACCEPTANCE CRITERIA
All 12 source SKUs appear exactly once; titles are at most 70 characters;
descriptions contain 20–45 whitespace-separated words; each has three
factual bullets. No invented attributes or care advice. Each issue names
the affected SKU and next decision. Maya can open the exact delivered
version and compare it with products-source.json.

HANDOFF AND UPDATES
Save the SOP, source, drafts and handoff to the agreed shared location.
In Orkas, add the files to the shared project's Library and ask the
recipient to Refresh and open them. A file in a private chat is not a handoff.
Maya reviews the version and exceptions before marking the to-do Completed.
Record agreed corrections in a new version rather than overwriting a
version Maya is already reviewing. Revise the SOP when the process changes.