Job SOP

The crew needs the next step, the hold, and who texts the customer. Grok is a clerk for that page. It is not the lead.

Why this matters

People ask Grok to “write a job SOP” or “write a kitchen safety plan” and get wallpaper: wear PPE, follow all applicable laws, maintain a clean workspace. None of it names this crawlspace, this allergen card, this loading dock, or who calls the customer when the part is not on the truck. Crews do not execute pamphlets.

This track is for contractors, mechanics, kitchens, retail, janitorial, and event crews. It is not geospatial, drone, or ag. If you need CRS, LAANC, spray maps, or a flight comms card, that is the Geospatial track. Do not copy one. Do not invent a job you will never stand on.

Grok will cheerfully add a second tech and a two-hour standard. Those sentences do not survive.

Teach

An SOP here is a tailboard, not a binder. Six parts, in this order:

1. Trigger. When this document is in force. “Residential water-heater swap, occupied house, two-person crew, weekday.” “Saturday catering for a count the client emailed.” Not “all plumbing activities.”
2. Roles. Functions: lead, helper, driver, line cook, closer, load-in. Who may text the customer. Who may say abort. One person, one function, even if one human wears two hats — write the hats. Do not add a person you do not have.
3. Steps. Numbered. One action each. “Verify the data plate. Photograph the T&P. Shut the breaker. Confirm the replacement on the truck.”
4. Hold points. Work stops until a human says go. Examples: customer not home; lockout missing; wet floor / ice; allergen list not in the bag; cash drawer short; lift gate down; you do not have the part you thought you had.
5. Comms. What is a text, what is a call, what waits for the shop. Short phrases. Who you call if the plan breaks (lead, shop, the customer — not “someone”). No invented radio frequency.
6. Abort and sign. What kills the job. Who signs that you did what you said. Empty signature lines stay empty.

What Grok must never invent

• A second person, a permit status, a “typical 90 minutes,” a price, a part number.
• “You are clear to start,” “the hall is nut-free,” “the breaker is already locked out.”
• Gate codes, alarm codes, locker codes, the customer’s garage PIN.
• CRS, airspace, LAANC, spray buffers, flight windows. Wrong track.

Grok may list questions the lead should answer from the walk, the plate, or the client email. It may not answer them from a training prior.

Language. Verbs first. No “ensure situational awareness.” Replace with “Helper watches the stairs and calls HOLD if a kid enters the work area.” If a line cannot be read in a van or on a pass window, cut it.

Same shape, different floors. A retail open, a nightly clean, a wedding load-in, a bay oil change — same six parts. The holds change. The pamphlet does not.

Tools. grok.com. Phone is for a photo of the plate, the ticket, or the whiteboard — not for writing policy in the parking lot while the customer waits.

Worked example

Saturday catering, 80 guests, two cooks, one van. Client emailed an allergen list (tree nuts). Load-out 3:00. Hall kitchen is unknown; they will plate on site.

Bad brief: “Write a professional catering SOP.”

Useful brief: two people, allergen card in the bag, no third cook, do not invent the hall’s rules, do not invent a 45-minute load, holds for missing card and for a protein they did not order.

Grok adds a prep cook, “the venue is nut-free,” and a 45-minute standard. The lead deletes all three. The hall’s allergen status is a check, not a memory. The load time is theirs to measure. What Grok got right was the comms card: text the client if a protein is short; call the lead if the van will miss 3:00; do not text a price.

The lead added one hold the model missed: confirm the count on the ticket matches the email — last week’s 60-person run is still on the clipboard.

Your turn

Open grok.com. New thread named job sop — [job]. Use a job you run or will run in the next 30 days: a changeout, a rush, an open, a clean, a load-in. Not a mapping flight.

Exercise d-trades-l01-e1

Copy-ready prompt

I am in Grok Mastery (Russell Tech), Pathway D, Trades & local work, lesson 1 — job SOP.

Interview me with exactly seven short questions, one at a time:
1) What the job is (changeout, kitchen, retail open, clean, event load-in, bay) and the product
2) Where, in plain language
3) How many people, and their functions
4) The real holds I already know (missing part, access, allergen, wet floor, cash, customer not home)
5) How we actually talk (text, call, ticket). Do not invent a radio frequency
6) Who can abort
7) What I will never let an assistant "clear"

Then write a Job SOP:
- Trigger
- Roles
- Steps (numbered, one action each, no more than 16)
- Hold points (each one a human go/no-go)
- Comms (exact short phrases)
- Abort / sign
- NEED list
- Session stamp: today's date and "Job SOP written by Grok in this thread."

Rules:
- Do not say we are clear to start, serve, enter, or bill.
- Do not invent a person, a permit, hours, a price, a part number, a code, CRS, LAANC, or a spray buffer.
- If a hold depends on a check I have not done, write "Lead checks [thing] — status not in this SOP."

Artifact to paste

1. The Job SOP (all parts, including NEED and stamp).
2. Your seven answers.
3. One line from you: a person, hour, or hold Grok invented or skipped, and what you did.

Rubric

• Pass: SOP is Grok-authored and stamped. No clearance sentence. No invented person, hour, or permit. Holds include one site-specific item you named. Headcount matches what you gave. Job is real and is not a drone/GIS job.
• Fail: OSHA wallpaper. You wrote it offline. “Ensure safety” as a step. A solo crew that magically has a helper. LAANC, CRS, or a spray map. No stamp.

Common failure

The common failure is regulatory wallpaper. Two pages of “comply with all applicable laws” and no line about the allergen card or the locked basement. The crew already knew they had to follow the law. They needed the hold.

The other failure is Grok as dispatcher. You ask it in the driveway whether you can start. Put the phone down. Walk the job. Check the thing you already named. The SOP is for humans on the floor.

What’s next

You can write a job SOP that does not staff itself. Next: an estimate or parts list that leaves prices and SKUs blank unless you typed them.

I am in Grok Mastery (Russell Tech), Pathway D, Trades & local work, lesson 1 — job SOP.

Interview me with exactly seven short questions, one at a time:
1) What the job is (changeout, kitchen, retail open, clean, event load-in, bay) and the product
2) Where, in plain language
3) How many people, and their functions
4) The real holds I already know (missing part, access, allergen, wet floor, cash, customer not home)
5) How we actually talk (text, call, ticket). Do not invent a radio frequency
6) Who can abort
7) What I will never let an assistant "clear"

Then write a Job SOP:
- Trigger
- Roles
- Steps (numbered, one action each, no more than 16)
- Hold points (each one a human go/no-go)
- Comms (exact short phrases)
- Abort / sign
- NEED list
- Session stamp: today's date and "Job SOP written by Grok in this thread."

Rules:
- Do not say we are clear to start, serve, enter, or bill.
- Do not invent a person, a permit, hours, a price, a part number, a code, CRS, LAANC, or a spray buffer.
- If a hold depends on a check I have not done, write "Lead checks [thing] — status not in this SOP."