Operations & SOPs prompts

Create a Standard Operating Procedure (SOP) for [PROCESS_NAME] at a [BUSINESS_TYPE]. Process details: - What it covers: [PROCESS_DESCRIPTION] - Who performs this task: [ROLE_RESPONSIBLE] - How often: [FREQUENCY] - Tools/software used: [TOOLS_USED] - Most common mistakes to avoid: [COMMON_MISTAKES] Format the SOP with: 1. SOP Title and Version number (v1.0) 2. Purpose (1 sentence on why this matters) 3. Scope (who this applies to) 4. Prerequisites (what they need before starting) 5. Step-by-step instructions (numbered, with sub-steps) 6. Quality checkpoints (what "done correctly" looks like) 7. Common mistakes and how to avoid them 8. What to do when something goes wrong 9. Related SOPs (list 2-3 related processes) 10. Last updated date placeholder Write at a 6th-grade reading level. Use action verbs. Be specific.

Write a project status update email from [AGENCY/COMPANY] to [CLIENT_NAME] about [PROJECT_NAME]. Project details: - Sender company: [AGENCY/COMPANY] - Client name: [CLIENT_NAME] - Project: [PROJECT_NAME] - Update period: [PERIOD] (e.g., Week of March 18) - What was completed this period: [COMPLETED] - What's in progress right now: [IN_PROGRESS] - What's coming next: [UPCOMING] - Any blockers or items needed from client: [BLOCKERS] - Overall status: [STATUS] (On Track / At Risk / Behind) - Next touchpoint: [NEXT_MEETING] Write the email in two formats: 1. Full update (for monthly/milestone updates): structured with headers, 300-400 words 2. Quick pulse (for weekly updates): bullet points, under 150 words For both: - Lead with the overall status (don't bury the lede) - Be specific about what was done (not vague "worked on project") - If behind, state it clearly with recovery plan — surprises are worse than bad news - Keep ask-of-client items prominent and specific - End with next meeting or checkpoint confirmation

Write a negotiation email from [BUSINESS_NAME] to [VENDOR_NAME] about [NEGOTIATION_GOAL]. Context: - Your business: [BUSINESS_NAME] - Vendor/supplier: [VENDOR_NAME] - What you're negotiating: [NEGOTIATION_GOAL] (e.g., price reduction, extended payment terms, service upgrade, contract renewal terms) - Your relationship history: [RELATIONSHIP] (e.g., 2-year customer, new vendor) - Current deal: [CURRENT_DEAL] - What you want: [DESIRED_OUTCOME] - Your leverage: [LEVERAGE] (e.g., payment volume, long-term contract commitment, referrals) - Your walkaway point (internal only): [WALKAWAY] Write 2 versions: 1. Renewal negotiation: You're up for renewal and want better terms 2. Mid-contract ask: Requesting a pricing review outside of a renewal cycle For each: - Open by acknowledging the relationship positively - State the ask clearly and early (don't dance around it) - Provide justification (your volume, loyalty, or market alternatives) - Be specific about what you want - Give them a path to say yes (make it easy) - Tone: confident, not apologetic; professional, not aggressive

Write a 3-email onboarding sequence the owner of [BUSINESS_NAME], a [BUSINESS_TYPE], can paste into Gmail or Mailchimp and send to [CLIENT_NAME] after [SERVICE_OR_PROJECT] is booked. Context: - Business name: [BUSINESS_NAME] - Business type: [BUSINESS_TYPE] - Client first name: [CLIENT_NAME] - What they booked: [SERVICE_OR_PROJECT] - Kickoff or start date: [KICKOFF_DATE] - The one next step you want from them now: [NEXT_STEP] - Link for that next step, or "reply to this email": [NEXT_STEP_LINK] - What they should send or prepare: [PREP_TO_SEND] - How they should reach you: [HOW_TO_REACH_US] - Timeline in plain language: [TIMELINE] - The one thing you need at the first check-in: [CHECK_IN_ASK] - Sender first name: [SENDER_NAME] Write all 3 emails now. Label when each one sends. Do not write a fourth email. 1. Day 0 — welcome, sent the day the job is booked. Two subject-line options, then the body. Under 150 words. 2. Day 2–3 — logistics and prep. Two subject-line options, then the body. Under 140 words. 3. Day 7–10 — short check-in. Two subject-line options, then the body. Under 90 words. Email 1 (day 0) must: - Open by naming [SERVICE_OR_PROJECT] and that it is booked. Welcome them in one plain sentence. No "we are thrilled to welcome you to the family" and no "your journey starts here." - Say what happens next in two or three short sentences, using [KICKOFF_DATE] and [TIMELINE]. If [KICKOFF_DATE] is blank, say you will confirm the start date when they reply. Do not invent a date. - Give exactly one next step: [NEXT_STEP]. If [NEXT_STEP_LINK] is a real URL, that URL is the step. If [NEXT_STEP_LINK] is blank or "reply to this email", tell them to reply to this email. Do not invent a client portal, intake form, calendar link, app login, or a second CTA. - Sound like [SENDER_NAME], the owner who just booked the work. Not a SaaS onboarding drip and not a welcome series from a marketing platform. Email 2 (day 2–3) must: - Say what to send or prepare, using [PREP_TO_SEND]. If [PREP_TO_SEND] is blank, ask them to reply with anything they already have that will help the job start. Do not invent a document checklist. - Say how to reach you, using only [HOW_TO_REACH_US]. If that is blank, tell them to reply to this email. Do not invent a phone number, Slack channel, text line, or portal. - Restate the timeline in one or two sentences using [TIMELINE] and [KICKOFF_DATE]. Do not add phases, milestones, or deadlines they did not give you. - One ask. Do not also ask them to book a call, leave a review, or refer a friend. Email 3 (day 7–10) must: - Be a short operations check-in: how the start is going, then one ask — [CHECK_IN_ASK]. - If [CHECK_IN_ASK] is blank, ask whether anything is stuck on their side that would hold the timeline. Do not invent a problem. - Do not ask for a review, testimonial, Google rating, or referral unless [CHECK_IN_ASK] is explicitly that ask. Prefer the operations ask. If they did ask for a review or referral, put it in one sentence after the operations point, and make it easy to skip. - No second CTA. No "while I have you." Rules for every email: - Use [CLIENT_NAME]. Sign off with [SENDER_NAME] and [BUSINESS_NAME]. - No corporate fluff: "excited to partner", "circle back", "leverage", "synergy", "onboarding journey", "valued client", "touch base", "I hope this email finds you well", "just circling back." - No fake urgency: "act now", "limited time", "don't miss this", "last chance to send your files", "spots are filling up." - Do not invent portals, logins, apps, intake forms, booking links, phone numbers, or attachments the owner did not put in the variables. - Short sentences. Contractions are fine. Write like the person who will also show up to do the work. - No emoji. No newsletter footer. No unsubscribe line. No upsell. Output in this order: EMAIL 1 — Day 0 (welcome): SUBJECT A / SUBJECT B, then the body. EMAIL 2 — Day 2–3 (prep): SUBJECT A / SUBJECT B, then the body. EMAIL 3 — Day 7–10 (check-in): SUBJECT A / SUBJECT B, then the body. A one-line send guide: day 0 the day the job is booked, day 2 or 3 for prep, day 7 to 10 for the check-in. A one-line note on whether a link was used, based on [NEXT_STEP_LINK].

Write a one-page opening SOP for [BUSINESS_NAME], a [BUSINESS_TYPE] that opens at [OPEN_TIME]. Facts, and only these facts: - Who opens: [OPENER_ROLE] - Tools they touch: [TOOLS] - Checks that must pass before the first customer: [MUST_PASS] - Cash, card, or drawer step, or "none": [DRAWER] - Safety or compliance check, or "none": [SAFETY] - What "open" means: [OPEN_MEANS] - Who they text if a check fails: [BACKUP] Format: 1. Title, version v1.0, and a blank "last tested" date. 2. Purpose in one sentence. 3. Who does this, and who covers if they are out. 4. Numbered steps in the order they happen. Start each step with a verb. Name the tool or the physical thing. 5. A "do not open" line: the checks that stop the doors. 6. What to do when a check fails. Name [BACKUP]. Do not invent a vendor, a phone number, or a fine. 7. A done line the opener can initial. Rules: - One page. If a step is not in the facts, do not add it. - If a field is blank or "none", leave that step out. Do not write "N/A" filler. - No corporate language. No "leverage", "ensure compliance", or "circle back". - Do not invent temperatures, alarm codes, prices, or legal requirements.

Write an invoice mailing SOP for [BUSINESS_NAME], a [BUSINESS_TYPE]. Facts: - Accounting tool, or "none": [ACCOUNTING_TOOL] - Who is allowed to send an invoice: [SENDER_ROLE] - What has to be true before an invoice goes out: [READY_WHEN] - How it is delivered: [DELIVERY] (email, mail, or both) - Where the customer pays: [PAY_PATH] - Reminder days, using only the numbers given: [REMINDER_DAYS] - Who gets told if it is still unpaid after the last reminder: [ESCALATE_TO] - What the tool already does by itself, or "nothing": [TOOL_DOES] - What a person still does by hand: [PERSON_DOES] Format: 1. Title, version v1.0, blank last-updated date. 2. Purpose: get a correct invoice to the customer and know the date it went. 3. Trigger: the moment [READY_WHEN] is true. 4. Steps in order. Mark each step "Person" or "Tool". 5. A "sent" definition. Sent means the customer has the invoice, not that someone meant to send it. 6. The reminder schedule from [REMINDER_DAYS] only. Do not add extra reminders. 7. The failure case: bounced email, wrong amount, or no pay path. Name [ESCALATE_TO]. 8. A one-line note titled "Automate after this is true" that lists only the [TOOL_DOES] steps. If [TOOL_DOES] is "nothing", say the SOP stays manual until the tool can send and log the invoice. Rules: - Do not invent prices, late fees, interest, or legal threats. - Do not invent a software feature. If [TOOL_DOES] does not name it, a person does it. - If [ACCOUNTING_TOOL] is "none", say "the invoice tool" and do not pick QuickBooks, Xero, or any other product. - No "just circling back". The reminder wording can be firm and plain.

Write a weekly SOP review for [BUSINESS_NAME]. It should take about 30 minutes and update exactly one SOP. Facts: - Who runs the review: [REVIEWER] - Day and time: [WHEN] - Where the SOPs live: [LIBRARY] - The SOP that broke this week: [BROKEN_SOP] - What happened: [WHAT_BROKE] - The step that was missing or wrong: [MISSING_STEP] - Who has to follow the new step: [ROLE] Output: 1. A 30-minute agenda with times. Five blocks at most. 2. The questions the reviewer asks the person who did the job. No more than four questions. 3. The replacement step, written as a verb, using only [MISSING_STEP]. Do not add steps they did not ask for. 4. A change log line: date, SOP name, what changed, who approved. 5. A "do not do this" line: do not rewrite the whole manual in this meeting. Rules: - One SOP. If they list two, tell them to pick the one that cost time this week and review the other next week. - Do not invent a tool, a fine, or a new policy. - Plain language. The change log should be something they can paste into the top of the SOP.

Write an employee offboarding checklist SOP for [BUSINESS_NAME], a [BUSINESS_TYPE]. The owner fills in the facts. You turn them into a dated checklist one person can finish on the last day. This is the close-out list, not a policy manual and not a script for a temporary day off. Facts, and only these facts: - Person leaving, first name: [EMPLOYEE_NAME] - Role: [ROLE] - Last day: [LAST_DAY] - Who runs this checklist: [OWNER] - Systems and tools they can still sign in to: [ACCESS] - Shared logins they know (a password other people still use), or "none": [SHARED_LOGINS] - Equipment they hold, or "none": [EQUIPMENT] - Open work and clients, each with the person who owns it now: [HANDOFF] - Payroll provider: [PAYROLL] - Who needs an internal note, or "none": [TEAM] - Clients who need a note, or "none": [CLIENTS] Format: 1. Title, version v1.0, the date set to [LAST_DAY], and a blank "completed" line with [OWNER]'s name. 2. Purpose in one sentence: on [LAST_DAY], [EMPLOYEE_NAME] is done, and nothing they can still open, hold, or owe a client stays with them. 3. A checklist. Every line has a name on it. The default name is [OWNER] unless [HANDOFF] names someone else. Every access, equipment, and handoff line says done on [LAST_DAY]. Do not write "later", "when you get to it", "next week", or "as time allows". 4. Access removal. Walk [ACCESS] and [SHARED_LOGINS]. Include a line only when the facts name that thing. When a fact matches, use these words: shared login, email, POS, CRM, banking or card, Google or Microsoft account, door code or key. For a shared login, the step is change the password on [LAST_DAY] and tell the people who still need it. For a personal login, the step is turn it off on [LAST_DAY]. If they did not list a system, leave it out. Do not add Slack, BambooHR, Rippling, or any other product they did not name. 5. Open work and client handoff. One line per item in [HANDOFF], with the named owner. If an item has no named owner, do not invent a person. Write "needs a name before [LAST_DAY]" and put [OWNER] on that line. 6. Equipment return. One line per item in [EQUIPMENT]: what it is, who collects it, and "back on [LAST_DAY]". If [EQUIPMENT] is blank or "none", write one line that there is nothing to collect. 7. Final paycheck and benefits. Three steps, owned by [OWNER]: tell [PAYROLL] the last day, ask [PAYROLL] what they need from you to run the final pay, and ask what benefit changes they will handle. Then this note, in these words: confirm your state's final paycheck rule and any benefits obligations with [PAYROLL] or an employment attorney before you promise a date or a form. Do not state a deadline, a number of days, a state rule, or a benefits timeline as a fact. 8. A short exit conversation [OWNER] can say out loud. Six to ten lines. Respectful, specific to [ROLE], about the work and the handoff. No speech about culture, loyalty, or "the family". Then three blank lines labeled "notes" for what was actually said. 9. An internal announcement [OWNER] can paste to [TEAM]. Under 80 words. Last day, who owns the open work, nothing else. No reason for the departure unless the facts include one. No gossip. If [TEAM] is blank or "none", say no internal note. 10. A client-facing note, only if [CLIENTS] is not blank and not "none". Under 80 words. Who they talk to now, taken only from [HANDOFF]. If [CLIENTS] is blank or "none", say no client note. Rules: - Short lines. Start each checklist step with a verb. - If a field is blank or "none", leave that block out or say there is nothing to do. Do not write filler. - Do not invent passwords, account names, dollar amounts, PTO balances, severance, or a last check amount. - Do not name a benefits law or a state deadline unless the owner typed it. You still tell them to confirm the final paycheck rule and benefits obligations with their payroll provider or an employment attorney. - No corporate language. No "stakeholders", "leverage", "circle back", "ensure compliance", "offboarding journey", or "human capital". - Plain and practical. This is a shop owner closing out a person. Related, for the owner, not inside the checklist they hand someone: New Employee Welcome Email (/prompts/hr-hiring/new-hire-welcome-email-template) is the other end, when someone starts. Weekly SOP Review (/prompts/operations/weekly-sop-review) is how you fix this page after the first time you run it. The SOP hub is /sop.

Write a weekly stock count and purchase order check for [BUSINESS_NAME]. One person finishes it in about 30 minutes. This is the weekly look at the shelf and the open purchase orders. It is not a full inventory valuation, not a tax count, and not an automatic reorder. The owner fills in the facts. You turn them into a one-page sheet they can finish this week, plus a blank copy of the same sheet for next week. Do not draft a supplier email. Asking a supplier to change a price or terms is a different page. Facts, and only these facts: - Who runs it: [REVIEWER] - Day and time: [WHEN] - Where the count is written: [COUNT_SHEET] - Who is allowed to place the order: [ORDERER] - Items counted this week. Each one needs the item and the on-hand quantity they just counted, with the unit. Or "none": [COUNTED] - Reorder numbers they already use. Each one needs the item and the number. Or "none": [REORDER_AT] - Stock already on a purchase order that has not arrived. Each one needs the item, the quantity, the supplier, and the purchase order. Or "none": [ALREADY_ORDERED] - What they already decided to order this week. Each one needs the item, the quantity, and the supplier. Or "none": [WILL_ORDER] - Open purchase orders to check. Each one needs the purchase order, the supplier, what was ordered, whether it has arrived, and any date they already wrote. Or "none": [OPEN_POS] - Items they will not order this week, and the reason they already wrote. Or "none": [HOLD] - Who answers bookkeeping questions: [BOOKKEEPER] - One decision they already need to make this week, or "none": [DECISION] Format: 1. Title, [BUSINESS_NAME], version v1.0, the day taken from [WHEN], and a blank "done" line with [REVIEWER]'s name. 2. Purpose in one sentence: once a week, [REVIEWER] writes what is on the shelf, the reorder number [BUSINESS_NAME] already uses, which purchase orders are still open, and what [ORDERER] will order. 3. A timed agenda. Five blocks. About 30 minutes. The blocks are: count the shelf, write the reorder numbers you already use, check open purchase orders, write what you will order, mark what you are holding. Do not add a sixth block for prices, tax, or a full valuation. 4. A filled sheet for this week, using only the facts: - Each item in [COUNTED], with the on-hand quantity and unit they wrote. If [COUNTED] is blank or "none", write "Nothing counted yet. Leave the lines blank and count the shelf before you order." - The reorder number from [REORDER_AT] on the matching item. If an item has no reorder number in the facts, write "no reorder number in the facts" and do not invent one. - You may write "below the reorder number you wrote" or "at or above the reorder number you wrote" only when both numbers are in the facts for that same item. Do not write a third number. Do not subtract. - Already on order, from [ALREADY_ORDERED] only. If [ALREADY_ORDERED] is blank or "none", write "Nothing already on order." - This week's order, from [WILL_ORDER] only. Copy the quantity and the supplier they named. [ORDERER] places it. If [WILL_ORDER] is blank or "none", write "Nothing to order this week." - If an item is in [WILL_ORDER] without a quantity, write "needs a quantity before you order" and do not choose one. - If an item is below the reorder number and is not in [WILL_ORDER], write "not on this week's order." Do not add it to the order. - Open purchase orders, from [OPEN_POS] only. Keep the received or still-out status they wrote. If a purchase order has no status, write "needs received or still out" and do not choose. If [OPEN_POS] is blank or "none", write "No open purchase orders." - If the same purchase order is in [ALREADY_ORDERED] and [OPEN_POS], write it once under open purchase orders and name it on the item line. Do not turn it into two orders. - Holding, from [HOLD] only. Do not order those items from this sheet. If [HOLD] is blank or "none", write "Nothing on hold." 5. A blank sheet with the same headings and empty lines, so they can print next week's check without running this prompt again. 6. The decision, from [DECISION] only. If [DECISION] is blank or "none", write "No extra decision this week." 7. A stop line, in these words: This is not a full inventory valuation, not a tax count, and not an automatic reorder. Confirm cost, sales tax, and what you owe a supplier with [BOOKKEEPER] or an accountant before you record a dollar amount you did not look up. Rules: - If a field is blank or "none", say there is nothing in that block. Do not invent an item, a quantity, a supplier, a price, a date, or a purchase order number. - Do not subtract on-hand from the reorder number. Do not compute a suggested order quantity. The only order quantity is the one in [WILL_ORDER]. - Do not add a price, a unit cost, a shipping charge, or an order total. If they did not type a dollar amount, the sheet has no dollar amount. - Do not mark a purchase order received unless the facts say it arrived. - Do not turn a weekday or other words they typed into a calendar date they did not write. - Do not name Shopify, Square, Toast, WooCommerce, QuickBooks, Xero, or any other product unless that name is written in [COUNT_SHEET]. Name [COUNT_SHEET] as the place they look. - Do not write the supplier email. [ORDERER] places the order from this sheet. The negotiation email is a separate prompt. - Short lines. Start each agenda step with a verb. - No corporate language. No "optimize", "leverage", "stakeholders", "circle back", "SKU rationalization", or "ensure compliance". Related, for the owner, not on the sheet: Vendor Negotiation Email (/prompts/operations/vendor-negotiation-email) is for asking a supplier to change terms. Weekly Cash and Bills Check (/prompts/finance/weekly-cash-and-bills-check) is the bank and the bills. A purchase order is not a bill until you owe it. Receiving and Delivery Check-In SOP (/prompts/operations/receiving-and-delivery-check-in-sop) is the sheet when a delivery arrives. An open purchase order on this weekly check is not that arrival. Weekly SOP Review (/prompts/operations/weekly-sop-review) is how you fix this page after the first week you run it. Tool-specific stock alerts are a different page: /automate/category/inventory-management. The SOP hub is /sop.

Write a receiving and delivery check-in for [BUSINESS_NAME]. One person finishes it before the driver leaves. This is the sheet for the physical arrival. It is not the weekly stock count, not an inventory valuation, and not a dispute letter. The owner fills in the facts. You turn them into a one-page sheet for this delivery, plus a blank copy of the same sheet for the next delivery. Do not draft a supplier email. Asking a supplier to change a price or terms is a different page. Counting the shelf once a week is a different page. Facts, and only these facts: - Who checks the delivery: [RECEIVER] - When it arrived, as they wrote it, or "blank": [WHEN] - Where the check is written: [CHECK_SHEET] - Supplier, or "blank": [SUPPLIER] - Purchase order or order reference they already have, or "none": [PO] - What was ordered. Each line needs the item, the quantity, and the unit. Or "none": [ORDERED] - What showed up. Each line needs the item, the quantity, and the unit. Or "none": [RECEIVED] - Damage they already saw. Each line needs the item, what is wrong, and the quantity. Or "none": [DAMAGE] - Partials they already marked. Each line needs the item and the quantity still out, in their words. Or "none": [PARTIALS] - Who may sign the vendor paperwork, or "none": [SIGNER] - Where accepted goods go, or "blank": [PUT_AWAY] - Who they tell if something is short, damaged, or not on the order: [BACKUP] - Who answers bookkeeping questions: [BOOKKEEPER] - One decision they already need to make about this delivery, or "none": [DECISION] Format: 1. Title, [BUSINESS_NAME], version v1.0, the time taken from [WHEN], and a blank "done" line with [RECEIVER]'s name. 2. Purpose in one sentence: when a delivery arrives, [RECEIVER] writes what was ordered, what showed up, any damage already seen, any partial already marked, who signs, and where the accepted goods go. 3. A short agenda. Five blocks. Finish before the driver leaves. The blocks are: write the supplier and the purchase order, write what was ordered, count what showed up, write damage and partials, write who signs and where it goes. Do not add a sixth block for prices, a credit, or the weekly shelf count. 4. A filled sheet for this delivery, using only the facts: - If [WHEN] is blank or "blank", write "Arrived: ________" and do not invent a time or a date. - Supplier, from [SUPPLIER] only. If [SUPPLIER] is blank or "blank", write "Supplier: ________" and do not invent one. - Purchase order, from [PO] only. If [PO] is blank or "none", write "No purchase order in the facts. This sheet is still the arrival. It is not the weekly stock count." - Ordered, from [ORDERED] only. Each line is the item, the quantity, and the unit they wrote. If [ORDERED] is blank or "none", write "Nothing ordered in the facts." - Received, from [RECEIVED] only. Each line is the item, the quantity, and the unit they counted. If [RECEIVED] is blank or "none", write "Nothing counted yet. Leave the lines blank and count the delivery before anyone signs." - If the same item is in [ORDERED] and [RECEIVED], keep both lines. Do not subtract. Do not write a difference, a shortage, or an overage. - If an item is in [ORDERED] and not in [RECEIVED], write "not on the received lines." Do not call it short unless [PARTIALS] already says so. - If an item is in [RECEIVED] and not in [ORDERED], write "not on the order." Then write "needs a keep or send-back" and do not choose. - Damage, from [DAMAGE] only. Each line names the item, what is wrong, and the quantity they wrote, and says tell [BACKUP]. If [DAMAGE] is blank or "none", write "No damage written." - Do not write a claim, a credit, a refund, or a dollar amount for damage. If they did not type a dollar amount, the sheet has no dollar amount. - If a damaged item has no place in the facts, write "needs a place for the damaged item" and do not choose one. Do not send it to the put-away place. - Partials, from [PARTIALS] only. Copy the quantity still out in their words. Do not calculate it from ordered minus received. If [PARTIALS] is blank or "none", write "No partials written." - If a partial line and an order line name the same item with different quantities, keep both and write "the order line and the partial line do not use the same words. Fix them before you sign." Do not pick a winner. - Signer, from [SIGNER] only. The signature line stays blank. Do not write a signature, initials, or "signed". If [SIGNER] is blank or "none", write "needs a name before anyone signs." - Put away, from [PUT_AWAY] only, and only for goods that are not on the damage line. If [PUT_AWAY] is blank or "blank", write "needs a place before it leaves the dock." 5. A blank sheet with the same headings and empty lines, so they can print the next delivery without running this prompt again. 6. The decision, from [DECISION] only. If [DECISION] is blank or "none", write "No extra decision this delivery." 7. A stop line, in these words: This is not an inventory valuation, not a dispute letter, and not legal advice. Confirm cost, a credit, and what you owe a supplier with [BOOKKEEPER] or an accountant before you record a dollar amount you did not look up. Rules: - If a field is blank, or the words "none" or "blank", use the empty-line wording in the format. Do not invent an item, a quantity, a SKU, a supplier, a price, a date, a damage claim, or a signature. - Do not subtract ordered from received. Do not compute a shortage, an overage, or a good quantity after damage. - Do not add a price, a unit cost, a shipping charge, or a delivery total. - Do not mark a weekly stock count received from this sheet. This sheet is only what is in front of them. - Do not add a SKU, a lot number, or an expiration date unless they already typed it. - Do not name Toast, Square, MarketMan, Shopify, or any other product unless that name is written in [CHECK_SHEET]. Name [CHECK_SHEET] as the place they look. - Do not write the supplier email, a dispute letter, or a customer apology. [RECEIVER] finishes this sheet. The negotiation email is a separate prompt. - Short lines. Start each agenda step with a verb. - No corporate language. No "optimize", "leverage", "stakeholders", "circle back", "SKU rationalization", or "ensure compliance". Related, for the owner, not on the sheet: Weekly Stock Count and Purchase Order Check (/prompts/operations/weekly-stock-count-and-purchase-order-check) is the weekly shelf and the open purchase orders. A purchase order that was expected is not this sheet until the goods are at the door. Opening Shift Checklist (/prompts/operations/opening-shift-checklist-sop) is the morning open, not the delivery. Vendor Negotiation Email (/prompts/operations/vendor-negotiation-email) is for asking a supplier to change terms, not for a shortage on this delivery. The SOP hub is /sop.