AI for Operators

Dear reader,

You may have a job that lives mostly in your head.

You know which key sticks. You know what must be checked twice. You know which screen comes next. You may explain the same steps every time someone covers for you.

This book helps you put one real job on paper.

You do not need to be good with computers. You can use a phone or iPad. You can go slowly.

You will gather your own notes. An AI tool can help arrange them into a first draft. Then you will walk through the draft in the real place.

The tool does not know your shop. It cannot see a loose cord, a blocked door, or a machine that sounds wrong. It may fill a gap with a sentence that sounds sure. That sentence can still be wrong.

So you stay in charge.

Your goal is simple: make one set of steps that another person can follow without calling you every few minutes.

Start small. Pick one job. Make it true before you make it pretty.

You are turning real work notes into one clear set of steps.

Lena runs a small print shop. Marco covers when she is away. The closing routine is spread across a note by the till, an old message, and Lena’s memory.

She will make one closing SOP. An SOP is a written set of steps for doing a job the same safe way each time.

1. Pick one job.
2. Gather the notes.
3. Copy a short line from this book.
4. Paste it into ChatGPT, Claude, or Gemini.
5. Read the draft.
6. Walk through it in the real shop.
7. Fix it before anyone uses it.

Use only an official app or website approved by your workplace. Do not paste passwords, door codes, card numbers, private staff notes, medical details, or secret customer records.

The tool makes a draft. It does not approve a rule, promise a delivery, set a price, or decide what is safe.

Stop here. Choose the one job you want another person to run.

Prompt
A short request you type into an AI tool. It tells the tool what help you want.

Copy box
The cream-colored box in this book. Replace words inside square brackets with your own words.

Paste
Place copied words into the message area of the AI app. On a phone, press and hold in the message area. Tap Paste.

Check
Compare the answer with your notes, records, and real workplace. Smooth writing is not proof that a detail is true.

Official app
The real app or website from the company that provides the tool. Check the publisher’s name before you sign in. Follow your workplace rules.

A word in square brackets is a space for you to fill. If you do not know the answer, write [unknown].

Do not guess just to fill a blank.

Stop here. Open the approved app, but do not send any shop notes yet.

You are collecting what truly happens before asking for a draft.

Lena finds a closing list, a message from Marco, and two steps she remembers only when she reaches the door.

1. Put all notes in one place.
2. Ask what happens first.
3. Keep going one step at a time.
4. Add known times, counts, tools, and checks.
5. Mark every gap as [unknown].
6. Mark disagreements as [notes do not match].

Do not: Paste passwords, codes, full customer records, or private staff files.

Next: Compare the list with your original notes. Circle anything the tool added or changed.

Watch out for tidy filler. The tool may add a normal-sounding step that your shop does not use.

Stop here. Do not ask for polished wording until the rough list is true.

You are turning the checked list into a short first draft.

Lena wants Marco to close the shop without calling her. She chooses only the closing job. She does not mix in opening, ordering, or machine repair.

1. Start a new chat.
2. Paste the checked steps.
3. Say who will use the page.
4. Ask for short numbered steps.
5. Keep unknown points visible.
6. Ask for a final check at the end.

Do not: Trust the order just because it looks neat.

Next: Read each line beside your original notes. Put back useful detail that was shortened too far.

The main danger is a changed order. A real step in the wrong place can cause missed work, waste, or harm.

Stop here. Save the page with the word DRAFT at the top.

You are testing the page in the place where the work happens.

Marco holds the draft while Lena watches. He reaches for the front-door key before the last customer pickup has been checked. The wording was clear. The order was wrong.

1. Use a quiet time. Do not test on a live risky job.
2. Let the cover person hold the page.
3. Ask that person to point to each tool or screen.
4. Note every pause and question.
5. Mark missing checks.
6. Correct the page from what you saw.

Do not: Let the tool decide whether a safety step is correct. Use the official manual, posted rule, or responsible person.

Next: Walk the changed lines again.

Watch out for “check as usual.” A new person may not know what “usual” means.

Stop here. Keep the page marked DRAFT.

You are putting the next person’s first actions at the top.

A handoff is a short note from one shift or person to the next. Marco should not search through a long paragraph to learn what needs attention first.

1. List what is finished.
2. List what must happen first.
3. List equipment or stock to watch.
4. Keep unknowns visible.
5. Name an owner only if one was assigned.
6. Put work that can wait at the bottom.

Do not: Let urgent work disappear inside a smooth summary.

Next: Ask the person taking over to say the first three actions back.

A handoff can fail by sounding complete when it is not.

Stop here. Fix any line that led to a different meaning.

You are recording what happened without guessing why.

One afternoon, the print shop loses power for twelve minutes. The cutter stops. The lights return after the building contact checks the panel. That order does not prove what caused the outage.

1. Write the times you know.
2. List what people saw or heard.
3. List actions people took.
4. Name the source of each key fact.
5. Keep the cause unknown unless confirmed.
6. Save opinions for the later review.

Do not: Change “this happened after that” into “this happened because of that.”

Next: Read the timeline to the people who were there. Keep disputed points marked.

Watch out for blame hidden in verbs.

Stop here. Use your normal incident process.

You are writing a clear question without changing the deal.

Lena is waiting for paper that was due Tuesday. She has the order number and date in her record. She wants a confirmed update, not an angry letter.

1. Open the order record.
2. Copy the correct order number.
3. Check the promised date.
4. State what is known today.
5. Ask one clear question.
6. Read the final message before sending it.

Do not: Accept a changed date, price, or term unless you mean to and have permission.

Next: Compare every number and date with the order. Remove any promise you did not choose.

Watch out for strong legal-sounding lines.

Stop here. You, not the tool, send the final email.

You are showing the current path before trying to improve it.

The stock sheet says a delivery was complete. The shelf is short. Lena first needs to learn where the written count and the real count split apart.

1. Start where the item arrives.
2. Follow each handoff.
3. Name the person or job at each step.
4. Name the note, form, or screen used.
5. Mark where a count can change.
6. Observe one real delivery before making a change.

Do not: Treat a likely weak point as a proven cause.

Next: Walk the map with one person who does the job.

The danger is redesigning too early. Another shop’s common practice may not fit yours.

Stop here. Observe first. Improve later.

You are turning scraps into a short weekly review.

Lena has late-order notes, a supply question, and one unfinished promise from Friday. A long report will not help the Monday talk.

1. Date each note.
2. Separate finished work from open work.
3. Write down the shop’s real priority rule.
4. Use that rule to order the work.
5. Add an owner only when one was named.
6. Ask the people doing the work what is missing.

Do not: Accept the ranking because it sounds sensible.

Next: Read the priorities aloud. Ask what is blocking the team that the page missed.

Watch out for made-up color ratings. A color means little without a real rule.

Stop here. Change the order when the floor has better facts.

You are checking what fits with visible arithmetic.

Capacity means the people and hours truly available for work. It is not the hours you wish you had.

1. List each available person.
2. Confirm approved hours.
3. Subtract meetings, leave, and other work.
4. Add only supplied job estimates.
5. Separate jobs without estimates.
6. Check every total with a calculator.

Do not: Assume every hour can be used perfectly or that two people have the same skills.

Next: Check availability with the named people. Recalculate outside the chat.

The danger is false room in the week.

Stop here. If a number is missing, leave the job uncounted.

You are describing a job for discussion without pretending you have an agreement.

A contractor brief explains the place, the work, and the open questions. It does not set legal terms by itself.

1. Write “Draft brief—not an agreement” at the top.
2. Describe the area and present condition.
3. Give only approved work windows.
4. Describe the result you can see and check.
5. List areas that must not be touched.
6. Leave prices and legal terms open.
7. Keep entry codes out of the document.

Check these two things:

• Does the brief state a fact you did not confirm?
• Does any sentence sound like a promise or legal term?

Do not: Invent rates, fees, materials, warranties, safety rules, permits, or approval rights.

Next: Have the facilities lead and the person allowed to approve terms review it.

A polished brief can look like a contract. That is the danger here.

Stop here. Do not send it as an agreement.

You are choosing one useful document instead of making a pile.

Lena starts with closing because it causes the most calls when she is away. She does not try to document the whole shop in one weekend.

1. If cover keeps calling, make the SOP.
2. If the next shift starts blind, make the handoff.
3. If stories are replacing facts, make the incident note.
4. If a supplier answer blocks work, draft the vendor email.
5. If the record and shelf disagree, map the process.
6. If the week is overfull, count capacity.

Choose the job that causes the next likely interruption, error, or false promise.

Do not choose the biggest job just because it sounds important. Choose a small job that happens often and can be watched from start to finish.

At the end of the week, ask:

• Did someone use the page?
• Did the page match the real work?

If either answer is no, fix the page or stop using it.

Stop here. Write the name of your one job at the top of a blank note.

You are giving one short correction instead of arguing with the tool.

A first draft may sound sure, hide the next action, or add a fact. Do not keep a false line because the rest looks good.

1. Find the first wrong line.
2. Compare it with your source.
3. Delete invented words yourself.
4. Ask for one clear repair.
5. Start a new chat if old guesses keep returning.

Do not: Ask the tool to choose between notes that conflict. Check the record or ask the people involved.

Next: Read the repaired part beside the source. If it is still wrong, write the line yourself.

An SOP may change order. A recap may guess a cause. A handoff may bury urgent work. A capacity list may add hours.

Stop here. You are allowed to stop using the draft.

You are making sure another person can rely on the page.

The document is not ready just because it reads well.

1. Trace each key line to a note, record, count, or person.
2. Walk steps in the real space.
3. Recheck dates, times, order numbers, and totals.
4. Keep unknown facts visible.
5. Confirm who can approve the page.
6. Add a date and owner for future updates.
7. Ask the person closest to the work to read it.

Check these two things:

• Could a made-up line change safety, staffing, cost, customer expectations, or timing?
• Could a new person tell what to do first without calling you?

If the first answer is yes, verify or remove the line. If the second answer is no, make the first action clearer.

Do not: Let a brief become a contract, a message change terms, or a capacity list approve overtime.

Next: Write the final date only after the checks are complete.

Stop here. Release only the checked version.

You are keeping the page close to the work after its first use.

A good SOP can become wrong when a screen, tool, supplier, layout, or rule changes.

1. Put the page where the user needs it.
2. Add the owner’s name or job.
3. Add the date it was last checked.
4. Give workers a simple way to report a wrong step.
5. Review it after a change or near miss.
6. Remove old copies.
7. Keep a short note about what changed.

Lena places the closing page near the final counter check. Marco marks one unclear line after his first solo close. Lena watches the step, fixes the wording, and replaces the old copy.

Do not: Update a safety or legal instruction from memory. Check the current official rule or manual.

Next: Ask the next person who uses the page where they paused.

The goal is not a perfect library. The goal is a shop another person can run with fewer surprises.

A useful page is short enough to use, true enough to trust, and easy to correct.

Stop here. Set the next review only when your shop can truly do it.

These sources support a simple idea: start with real material, give clear instructions, and edit the result.

OpenAI. “How People Are Using ChatGPT.” September 2025.
The report says writing is a large part of work use. Much of that use involves changing text supplied by the user. This supports starting with real notes rather than asking for a shop process from nothing.

https://openai.com/index/how-people-are-using-chatgpt/

Anthropic. “Be Clear and Direct.”
This guide recommends clear requests and useful background. It also advises placing long source material before the final question.

https://docs.anthropic.com/en/docs/build-with-claude/prompt-engineering/be-clear-and-direct

Google Cloud. “Prompt Design Strategies.”
This guide explains that a useful request should state the goal, needed background, limits, and desired kind of answer.

https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/prompts/prompt-design-strategies

These guides can help you get a clearer draft. They do not prove that the draft is true for your shop.

Your records, official rules, calculations, and people decide what is true.