SOP Studio in practice.
These example facts are fictional inputs, not SOP Studio policies or customer results.
The sample package
SOP STUDIO — COMPLETE FICTIONAL SAMPLE Cedar Desk Creative | Demo version 1.0 Demonstration only. Both procedures document fictional approved facts from facts.txt; they are not certified or recommended workplace policies. SOP 1 — PROJECT SETUP AND KICKOFF HANDOFF Purpose: Prepare an accurate project record for the design lead. Start: Account lead confirms approved brief and initial invoice paid. Finish: Design lead accepts the handoff; tracker shows Ready for kickoff. Preparer: Project coordinator. Scope/date decision owner: Account lead. Receiving owner: Design lead. Required inputs: Project code, signed scope, approved deliverable list, approved customer contact channel, agreed dates, approved source assets and invoice-paid confirmation. Procedure 1. Confirm approved brief and invoice-paid confirmation in the tracker. If either is missing, stop and ask the account lead to resolve it. 2. Check all required inputs. List missing items, set Awaiting information and send the list to the account lead. Do not substitute guessed scope, assets or dates. 3. Compare scope and dates across the tracker and signed brief. Pause kickoff until the account lead records resolution of any conflict. 4. Create project-code_client-short-name with 01-Brief, 02-Source, 03-Working, 04-Review and 05-Final subfolders. 5. Link signed scope in 01-Brief and approved assets in 02-Source. Copy agreed dates accurately to the tracker. Never include passwords or access credentials. 6. Give the design lead the tracker/folder links, deliverable list, dates and resolved exceptions. 7. Ask the design lead to confirm that inputs are complete and the next action is understood. Return unresolved items to the account lead. 8. Record design-lead acceptance and set Ready for kickoff. Checklist [ ] Approved brief and invoice-paid confirmation verified. [ ] All required inputs supplied. [ ] Scope/date conflicts resolved by account lead and recorded. [ ] Correct folder name and five subfolders created. [ ] Signed scope and approved assets linked; dates accurate. [ ] No credentials included. [ ] Complete handoff received and accepted by design lead. [ ] Acceptance recorded and Ready for kickoff set. Owner handoff Project code: __________ Tracker / folder links: __________ Deliverables / agreed dates: __________ Resolved exceptions: __________ Prepared by / date: __________ Receiving owner: Design lead Next action: Confirm inputs and accept kickoff readiness. Accepted by / date: __________ Outstanding items and decision owner: __________ Exceptions: Missing input -> account lead supplies; conflicting scope/date -> account lead resolves; absent acceptance -> coordinator does not mark ready. Completion evidence: Acceptance record and Ready for kickoff status. Source gaps: No response deadline or retention rule supplied; neither added. SOP 2 — APPROVED FINAL DESIGN DELIVERY Purpose: Deliver the exact approved set through the approved channel. Start: Design lead records final approval. Finish: Delivery evidence recorded, status Delivered, design lead notified. Roles: Designer prepares; design lead verifies; account lead sends; coordinator records completion. Inputs: Project code, final approval record, signed deliverable list, approved final files/formats and approved customer destination. Procedure 1. Designer verifies that approval covers the version being prepared. If unclear, ask design lead before proceeding. 2. Compare files with signed deliverable list and approved formats. Identify omissions before packaging. 3. Name files project-code_deliverable-name_final.extension and place in 05-Final. 4. Design lead opens every file, checks readability, counts files against scope, checks formats and matches versions with approval. 5. Return missing, unreadable or unapproved files to designer with specific issues. Repeat verification after correction. Do not send a partial set. 6. Account lead compares destination with approved customer destination. Resolve a mismatch before sending. 7. Account lead sends approved folder link through approved contact channel and records sent time. 8. Coordinator records link/time, sets Delivered and notifies design lead. Checklist [ ] Approval applies to prepared version. [ ] Complete file set and formats match signed scope. [ ] Naming convention used; files in 05-Final. [ ] Design lead opened and checked every file. [ ] Corrections verified; complete set approved. [ ] Account lead verified destination and channel. [ ] Folder link sent; sent time recorded. [ ] Delivery evidence saved; Delivered set; design lead notified. Owner handoff Project code / approval record: __________ Deliverable count / formats: __________ Verified folder link: __________ Verified by / date: __________ Receiving owner: Account lead, then coordinator Approved destination / channel: __________ Sent by / time: __________ Completion recorded by / time: __________ Exceptions resolved: __________ Exceptions: Missing/unreadable file -> designer corrects and design lead rechecks; unapproved version -> design lead resolves; destination mismatch -> account lead verifies. Completion evidence: Sent time, link, Delivered status and notification. Source gaps: No deletion, retention or legal-signoff rules supplied; none added.
Read the fictional source facts
SOP STUDIO — FICTIONAL APPROVED SOURCE FACTS All names and procedures below are invented solely for demonstration, not instructions for a real workplace. Approval here refers only to the fictional process owner in this example. Company: Cedar Desk Creative, a fictional design agency. Process 1: Project setup. Account lead confirms approved brief and initial invoice paid. Coordinator checks project code, signed scope, approved deliverables, customer contact channel, agreed dates and source assets. Folder naming: project-code_client-short-name; subfolders: 01-Brief, 02-Source, 03-Working, 04-Review, 05-Final. Coordinator links scope/assets, records agreed dates and requests design-lead acceptance. Missing input: Awaiting information; account lead resolves. Conflicting scope/dates: account lead resolves and records before kickoff. Design lead confirms inputs and next action; coordinator records acceptance and sets Ready for kickoff. Process 2: Final delivery. Design lead records approval. Designer compares files with signed deliverable list and approved formats, names files project-code_deliverable-name_final.extension and places in 05-Final. Design lead opens every file and checks count, format and approved version. Missing/unreadable/unapproved files return to designer; no partial delivery. Account lead verifies approved customer destination, sends folder link through approved contact channel and records sent time. Coordinator records link/time, marks Delivered and notifies design lead. No credentials belong in these documents. No retention schedule, legal requirement, safety procedure or response deadline is provided; none may be invented.