Expert
AI for Operators
A shop someone else can run.
Anyone can use this page. Copy the prompt and try it today.
$7.99
Expert
A shop someone else can run.
Anyone can use this page. Copy the prompt and try it today.
$7.99
Everyday AI
The runbook, the handoff, the incident note.
You stay the editor. The model drafts. You decide.
$7.99 · 20 pages
Expert shelf · process notes · you stay accountable
CONTENTS
Read pages 3 through 6. Then copy one cream box.
THE IDEA
At 6:12 p.m., Lena finds three versions of the closing routine: a note by the till, a Tuesday message, and what Marco remembers.
A model can organize those scraps. It cannot know which version is real. It did not close the line, hear the compressor, or learn that Door 3 sticks when it rains.
Use it for shape: sequence, headings, questions, summaries, and a first draft.
Use the floor for truth: records, calculations, approved rules, and the people who did the work.
A useful request names a role, task, context, constraints, and format. Before anyone follows the result, ask whether a made-up line could change safety, staffing, cost, customer expectations, or timing.
The model drafts. You release.
WHAT THE LABS FOUND
Research does not prove that a chatbot will fix your floor. It does offer useful drafting guidance.
1 — Edit real material. Writing is about 40% of work-related ChatGPT messages. About two-thirds of those messages modify user text.
2 — Put long notes first. Anthropic advises clear roles and query-last placement, which improved quality by up to 30% in tests on complex long inputs.
3 — Name the job. Google lists objective, persona, constraints, context, and response format.
4 — Keep evidence in scope. A Stanford/MIT customer-support study found 14% higher issues resolved per hour on average and about 34% for novice and lower-skilled agents. It did not measure production, warehousing, incidents, or vendor performance.
Give the model source material and limits. Then check the draft against the work.
BEFORE YOU PASTE
Marta has eight receiving notes. One says “short again.” Another says “ask Lee.” She knows what they mean. A model does not.
Before pasting, ask: What happened first? What happened next? Which times, counts, names, and promises are recorded? What remains unknown? What must the next person do? What would be dangerous or expensive to guess?
Mark gaps: [time not recorded], [count needs checking], [cause unknown], [owner not assigned].
Separate fact, reported statement, and interpretation. A fluent draft may otherwise turn all three into facts.
Decide on one artifact before opening the chat. One SOP, recap, email, handoff, map, watch-list, brief, decision log, or capacity cut per thread.
HOW TO USE THIS
Choose the page matching the problem in front of you. Do not build all ten artifacts at once.
[unknown] when needed.Do not paste passwords, access codes, card data, medical information, full personnel files, private HR notes, or confidential customer records. Follow approved-tool and data rules.
Delete any line you cannot trace to a note, record, calculation, or responsible person. Watch for invented SLAs, causes, targets, overtime, vendors, and policies.
SOP
Priya is away Thursday. Dev covers the print shop and keeps calling because the rush-poster routine lives in Priya’s head.
Blind-paste risk: invented sequence.
COPY THIS
Role: Operations editor using verified floor notes.
Task: Draft a one-page SOP for [job].
Details: Shop: [ ]. User: [ ]. Actual ordered steps: [paste]. Known duration: [ ]. Uncertain points: [ ].
Format: Title; when to use; prerequisites; numbered steps; check after the risky step; exceptions; ticket record.
Hard nos: Do not invent equipment, safety instructions, vendors, prices, SLAs, duration, approval, or missing steps. Flag proposed reordering. Put unknowns in brackets.
Then do this: Have Dev walk the page without starting a live job. Correct every place where his next move differs from the draft.
OPS REVIEW
Tomas starts Monday with five texts, a late-truck note, and Friday’s unfinished action. His warehouse needs priorities, not a board deck.
Blind-paste risk: false priority.
COPY THIS
Role: Calm operations-review editor using only supplied evidence.
Task: Draft a one-page Monday ops review.
Details: Team: [ ]. Dated notes: [paste]. Confirmed wins: [ ]. Open commitments: [ ]. Real constraints: [ ]. Priority rule: [ ].
Format: Five facts; three priorities with source notes; supplied owners; one parking item; one floor question.
Hard nos: Do not invent KPIs, colors, owners, deadlines, costs, SLAs, causes, or unsupported priorities. Mark conflicts.
Then do this: Ask the floor, “What blocks today that this page missed?” Change the order when better evidence appears.
INCIDENT RECAP
Power drops at 4:18 p.m. on Elena’s catering line. By evening, people are compressing the story into blame.
Blind-paste risk: inferred cause.
COPY THIS
Role: Incident-record editor separating observations, actions, reports, and unknowns.
Task: Draft a short factual recap.
Details: Timeline: [ ]. Effects: [ ]. Actions: [ ]. People present: [roles or first names]. Unknowns: [ ]. Source for each fact: [ ].
Format: Timeline; immediate actions; effect; confirmed facts; open questions; records or people to check.
Hard nos: Do not invent cause, fault, cost, injury, temperature, SLA, breach, quotation, or corrective action. Do not turn “after” into “because.”
Then do this: Read the timeline to those present. Correct facts and label disputed details as disputed.
VENDOR EMAIL
Malik’s roasting bags have not arrived. He wants a firm answer without accidentally changing the deal.
Blind-paste risk: accidental concession or threat.
COPY THIS
Role: Editor helping an operator write a direct, courteous vendor email; not a lawyer.
Task: Draft an email requesting a confirmed delivery update.
Details: Sender: [ ]. Recipient: [ ]. Order: [ ]. Promised date: [ ]. Known status: [ ]. Ask: [ ]. My next action: [ ].
Format: Subject; under 120 words; facts first; one clear question.
Hard nos: Do not invent terms, penalties, fees, rights, volume, dates, leverage, legal claims, threats, or agreement to a change. Bracket missing facts.
Then do this: Compare every number and date with the purchase record. Malik removes any sentence that changes the deal and sends it himself.
SHIFT HANDOFF
June ends the hotel-laundry night shift with two slow machines and Room 412’s bags still drying. Pat starts at six.
Blind-paste risk: urgent work buried in a polished summary.
COPY THIS
Role: Shift-handoff editor making the next action visible.
Task: Draft tonight’s handoff from June to Pat.
Details: Raw notes: [ ]. Completed: [ ]. Must happen first: [ ]. Equipment concerns: [ ]. Work that can wait: [ ]. Approved escalation route: [or unknown].
Format: Three DO FIRST lines; waiting work; equipment; supplies; work that can wait; unknowns; acknowledgment line.
Hard nos: Do not invent counts, machine IDs, guest names, times, escalation rules, causes, priorities, or completion.
Then do this: June checks whether Pat could begin safely from the first three lines. Pat acknowledges and corrects ambiguity.
PROCESS MAP
The receiving sheet says full. The cart is short on milk. Two people have patched the mismatch in their heads.
Blind-paste risk: premature redesign.
COPY THIS
Role: Current-state process mapper describing work as performed.
Task: Map delivery-to-sheet receiving and show where records can diverge.
Details: Actual sequence: [ ]. Latest mismatch: [ ]. Roles: [ ]. Available records: [ ]. Unknowns: [ ].
Format: Steps; actor and record; handoffs; observed failure point; assumptions to verify; three questions; one reversible test using existing tools.
Hard nos: Do not invent software, scanners, staffing, policy, vendor duties, SLAs, motives, or best practices. Do not call suspicion a root cause.
Then do this: Walk the map with a receiver. Observe the next real delivery before approving a change.
WATCH-LIST
Claire has twelve dashboard tiles and ten minutes each morning. Only two mechanics are in before a holiday weekend.
Blind-paste risk: a plausible vanity metric.
COPY THIS
Role: Operations editor selecting from measures I already use.
Task: Choose what to review this week and what can wait.
Details: Existing list: [ ]. Current pressure: [ ]. Decisions Claire can make: [ ]. Review time: [ ].
Format: Three watch items; decision each informs; source; two deferred items; one floor question.
Hard nos: Do not invent KPIs, targets, percentages, thresholds, dashboards, trends, benchmarks, or sources. No status color without my rule.
Then do this: Finish: “If this changes, I will…” Drop any item that cannot inform a real decision this week.
CONTRACTOR BRIEF
Diego needs a contractor to recaulk a wash line during two nights. He knows the access plan, but not the rate.
Blind-paste risk: invented contract obligations.
COPY THIS
Role: Practical scope-brief editor; not legal counsel.
Task: Draft a one-page contractor brief for discussion.
Details: Site and job: [ ]. Approved windows: [ ]. Existing conditions: [ ]. Observable result: [ ]. Areas not to touch: [ ]. Access contact: [role only]. Open questions: [ ].
Format: “Draft scope brief—not an agreement”; summary; conditions; access process; windows; completion check; exclusions; open questions.
Hard nos: Do not invent rates, fees, insurance, warranties, materials, permits, legal clauses, SLAs, acceptance rights, safety rules, or access codes.
Then do this: Check it with facilities and the person authorized to approve terms. Send credentials separately through an approved channel.
DECISION LOG
Nora moved Friday’s packing cutoff from 2 p.m. to noon. In four weeks, someone will ask why.
Blind-paste risk: a better-sounding but false rationale.
COPY THIS
Role: Decision-log editor preserving the stated decision and reason.
Task: Draft one searchable log entry.
Details: Decision: [ ]. Date: [or unknown]. Reason in Nora’s words: [ ]. People present: [ ]. Trial period: [ ]. Review signs: [ ]. Supporting notes: [ ].
Format: Date; decision; reason; participants; what changes; what does not; review condition; evidence; open questions.
Hard nos: Do not invent feedback, metrics, savings, policy, consensus, dates, approval, or strategy. Do not imply agreement unless stated.
Then do this: Nora reads the reason aloud. If she would not have said it, restore her original words before saving.
CAPACITY
Samir has four people, their approved hours, and more jobs than the week can hold.
Blind-paste risk: hidden overtime or invented capacity.
COPY THIS
Role: Capacity arithmetic checker using only supplied hours and estimates.
Task: Separate work into fits, does not fit, and cannot calculate.
Details: People and approved hours: [ ]. Jobs and supplied estimates: [ ]. Promised work: [ ]. Reserved non-job time: [ ]. Confirmed skill or sequence limits: [ ].
Format: Total hours; reservations; fitted jobs with math; waiting jobs; missing estimates; unused or overbooked hours; assumptions.
Hard nos: Do not invent headcount, overtime, Saturday work, speed, efficiency, buffers, estimates, interchangeable skills, or split shifts.
Then do this: Recalculate with a calculator and confirm availability. Move every job without an estimate to “cannot calculate.”
WEEK PLAN
Pick the artifact that prevents the next interruption, misunderstanding, or false promise.
Cover keeps calling: draft and walk the SOP.
Stand-up is driven by scraps: build the ops review and let the floor challenge its order.
Stories are replacing facts: make the incident recap.
The next shift starts blind: put three actions at the top of a handoff.
Records and work disagree: map the current process before redesigning it.
A supplier answer blocks a decision: draft the email and verify every date.
Keep an artifact only if someone used it and found it accurate. A tidy document nobody trusts is another operational mess.
STUCK
A first draft may be polished, long, and slightly untrue. Use one direct correction.
Invented fact: “Use only traceable facts. Put missing facts in brackets.”
Inferred cause: “Separate sequence from cause. Keep the cause unknown.”
Hidden action: “Put the next three actions first.”
Invented commitment: “Remove promises, requirements, deadlines, and terms I did not provide.”
False capacity: “Use only named people, supplied hours, and supplied estimates. Show the math.”
Board-deck voice: “One page. Floor language. No framework or status colors.”
If source notes conflict, ask the people or check the record. Do not let the model choose. If old assumptions persist, start a new chat with one artifact and its source notes.
RELEASE CHECK
The draft is not finished because it reads smoothly.
Trace it: Find the source behind every important line.
Walk it: Follow SOPs, maps, and handoffs in the real workspace.
Count it: Recheck dates, order numbers, times, quantities, and arithmetic.
Name uncertainty: Keep unknown causes, disputes, and missing owners visible.
Confirm authority: A brief is not a contract. An email cannot change terms by itself. A log records a decision; it does not create one. A capacity cut does not approve overtime or headcount.
Ask the person closest to the work: “What would make this page wrong at 7 tomorrow morning?” Fix that before release.
SOURCES
Chatterji et al., “How People Use ChatGPT,” September 2025.
https://openai.com/index/how-people-are-using-chatgpt/
Anthropic, “Be Clear and Direct.”
https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/be-clear-and-direct
Google Cloud, “Prompt Design Strategies.”
https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/prompts/prompt-design-strategies
Brynjolfsson, Li, and Raymond, “Generative AI at Work,” NBER w31161; QJE 2025. This study concerned customer-support agents, not general operator work.
https://www.nber.org/papers/w31161
Research can guide how you draft. Your records, calculations, policies, and people decide what is true in your operation.