# Prompt Pack: Cannabis Ops Manager

Twelve prompts for the work that eats an ops manager's week. Free to copy, edit, share. From Distru's No Bullshit AI Course (learnai.distru.com).

Every prompt uses the same five-part shape: **who you are → what you want → rules → output shape → example or source.** Paste your own material where you see `[brackets]`. Never paste customer PII, employee IDs, passwords, or API keys.

Rule that applies to all twelve: add the line **"Use only the information I gave you. If something is missing, say MISSING instead of guessing."** It is already in each prompt. Keep it.

---

## 1. Monday restock email to a supplier

```
You write short, direct purchasing emails for a licensed cannabis distributor.
Write an email to [supplier name] requesting a restock.
Items and quantities: [paste list]
Needed by: [date]
Rules: under 100 words, no pleasantries beyond one line, include our license number [XXX] and delivery address [address], ask them to confirm availability and a delivery window.
Output: the email only, subject line first.
Use only the information I gave you. If something is missing, say MISSING instead of guessing.
```

## 2. Collections follow-up for an overdue invoice

```
You write firm, friendly collections emails for a wholesale cannabis business.
Customer: [name]. Invoice: [number]. Amount: [$]. Days overdue: [n]. Prior contact: [none / one email on date].
Rules: under 120 words, no threats, no legal language, one specific ask (pay by [date] or call to arrange terms), keep the relationship.
Match this tone: [paste one email you wrote that you liked]
Output: the email only.
Use only the information I gave you. If something is missing, say MISSING instead of guessing.
```

## 3. Explain a Metrc error to a new hire

```
You explain Metrc (the state cannabis tracking system) to new dispensary and distribution staff in plain language.
Error text: [paste exactly]
What we were trying to do: [one sentence]
Rules: explain what the error means in two sentences, then list the 2-3 most common causes, then the first thing to check. No jargon without a one-line definition. Do not invent Metrc rules; if you are not sure, say so and tell me to check the state's Metrc bulletin.
Output: three short sections with headers.
Use only the information I gave you. If something is missing, say MISSING instead of guessing.
```

## 4. Turn a buyer's messy order into line items

```
You normalize wholesale cannabis orders against a product catalog.
Our catalog (name | SKU | unit): [paste catalog rows]
Buyer's order, exactly as sent: [paste text / spreadsheet rows]
Rules: match each line to one SKU. Output quantity and unit. If a line could match more than one SKU or none, write UNKNOWN and copy the buyer's original text. Do not guess. Do not invent SKUs.
Output: a table with columns buyer_text | SKU | product_name | qty | unit | confidence (high/medium/UNKNOWN).
Use only the information I gave you. If something is missing, say MISSING instead of guessing.
```

## 5. Compliant menu description (40 words)

```
You write menu copy for a licensed cannabis retailer in [state].
Product: [name]. Type: [flower/vape/edible/etc]. Strain: [name]. Weight: [x]. THC: [x%]. CBD: [x%]. Top terpenes: [list]. Grower/brand: [name].
Rules: exactly 35-45 words. No medical or health claims (no "treats", "cures", "helps with anxiety"). Describe aroma, flavor, and reported effects in neutral language ("customers describe"). No emojis. Match this voice: [paste one description you like].
Output: the description only.
Use only the information I gave you. If something is missing, say MISSING instead of guessing.
```

## 6. SOP from a voice memo

```
You turn spoken process descriptions into written SOPs for a cannabis operation.
Transcript: [paste]
Rules: numbered steps, one action per step, each step under 20 words. After each step add an indented line "Watch for:" with the most likely mistake. End with a "Before you finish" checklist of 3-5 items. Do not add steps I did not describe; if a step seems missing, add a line "GAP: [what seems missing]" so I can fill it.
Output: markdown.
Use only the information I gave you. If something is missing, say MISSING instead of guessing.
```

## 7. Budtender one-pager for a new product line

```
You write training one-pagers for budtenders.
Product line: [name]. Products and specs: [paste spec sheet]. Lab results summary: [paste]. Price points: [paste].
Rules: three sections. "Say this" (3 bullets a budtender can say to a customer, no medical claims). "Never say this" (2 bullets, compliance risks specific to this product). "If they ask" (3 likely customer questions with one-line answers). Under 250 words total.
Output: markdown.
Use only the information I gave you. If something is missing, say MISSING instead of guessing.
```

## 8. Summarize a state bulletin for our operation

```
You read cannabis regulatory bulletins and tell an operator what changed for them.
Bulletin text: [paste full text]
Our license type: [distributor / retailer / cultivator / manufacturer]. State: [state].
Rules: first, one sentence: does this affect our license type, yes/no/unclear. Then list each change that affects us, with the exact sentence from the bulletin quoted under it. Then list deadlines with dates. Do not paraphrase rules without the quote next to it.
Output: markdown with headers "Affects us?", "Changes", "Deadlines".
Use only the information I gave you. If something is missing, say MISSING instead of guessing.
```

## 9. First-pass expense sort (COGS vs. not) for the accountant

```
You do a first-pass classification of expenses for a cannabis business. A licensed accountant will review every row; you are speeding them up, not replacing them.
Transactions (date | vendor | description | amount): [paste rows]
Rules: for each row output category (inventory purchase, packaging, lab testing, cultivation supplies, rent, payroll, marketing, software, other), cogs_candidate (yes/no/unsure), and a one-clause reason. Mark anything ambiguous "unsure". Do not give tax advice or cite 280E rulings.
Output: a table with the original columns plus category | cogs_candidate | reason.
Use only the information I gave you. If something is missing, say MISSING instead of guessing.
```

## 10. Explain a Metrc vs. inventory mismatch

```
You help cannabis operators understand why Metrc and their inventory system disagree.
Mismatches (tag | metrc_qty | our_qty | unit | product | last_activity): [paste rows]
Rules: for each row, give the single most likely cause from this list: unaccepted transfer, unrecorded lab sample, unrecorded waste, split not synced, package finished on one side only, manual edit, unit mismatch, unknown. Add confidence (high/medium/low) and one thing to check first. Do not suggest changing any quantity; I will decide.
Output: table.
Use only the information I gave you. If something is missing, say MISSING instead of guessing.
```

## 11. Weekly ops summary for the owner

```
You write a weekly operations summary for the owner of a cannabis business who has five minutes.
Data: [paste: orders shipped, on-time %, returns, inventory value, top 5 products, top 3 issues from the week]
Rules: under 150 words. Lead with the one number that changed most vs last week [paste last week's numbers]. Three bullets max under "Good", three under "Watch". One line "Decision needed" or "No decision needed this week". No adjectives like "great" or "concerning"; let the numbers speak.
Output: plain text.
Use only the information I gave you. If something is missing, say MISSING instead of guessing.
```

## 12. Write the script instead of the answer

Use this when the data is too big to trust the AI's counting.

```
You write small scripts for a cannabis ops manager who is not a programmer.
I have a CSV with these columns: [paste header row]. First three rows: [paste].
I want to know: [question, e.g., total quantity per product where status is Active].
Rules: write a spreadsheet formula I can paste, OR a short script in [Python/JavaScript] that reads the file and prints the answer. Explain in two sentences how to run it. Do not compute the answer yourself from the sample rows.
Output: the formula or script in a code block, then the two-sentence explanation.
Use only the information I gave you. If something is missing, say MISSING instead of guessing.
```

---

### Make these yours

Save the ones you use as a project instruction, custom GPT, or a `SKILL.md` (course module 06). Replace the bracketed example with one real, good example from your own files. That single change improves results more than any other edit.

License: CC0. Do whatever you want with this.