Supplies on a loop, not a scramble
Lesson 3 of 6 · Front Office & Events
1 · Learn the move · Recipe pattern
Running out of anything is a system failure that everyone in the building experiences as your failure. The recipe pattern converts reordering into a loop with days attached: what gets counted, when, the reorder point for each item, who approves above a dollar line, and where the order goes. The counts and the thresholds are yours, always, because the AI has no idea how fast this office goes through toner and shouldn't pretend it does. Once the loop exists it runs off a recurring Outlook reminder instead of off somebody noticing the last box.
Build my supply reorder loop from my item list and usage notes: a count day, a reorder point per item, an approval step over [$ threshold], and the order path. Output a one-page checklist plus the recurring Outlook reminders that drive it. Never invent a usage rate or a reorder point I didn't give you, write [NEEDS: your count] instead. [item list + usage notes]
2 · Your turn. You write the prompt
You ran out of toner the morning of a board meeting and paid rush shipping to fix it. There are three supply closets, no counts anywhere, and ordering happens when somebody shouts down the hall. Write a prompt that turns that into a loop that runs off a calendar instead of off a shout.
Remember: the AI sees only your prompt, not this page. If the situation isn't in your prompt, it doesn't exist.
Optional. These shape the output when you run your prompt below, not your score.