A list is a set of lines you can buy or bill. Empty is better than a made-up SKU. Grok can name the kinds of lines. It cannot price your book.
Why this matters
You describe a water heater, a ticket, or a Saturday headcount. Grok fills a brand, a part number, $1,149 installed, and 2.5 hours because that is what a training prior looks like. You order the wrong element. You text a number you cannot stand on. The customer hears a bid. You meant a sketch.
This lesson is the list: parts, trays, SKUs, labor lines. The dollars stay NEED until you type them from your book, your vendor, or the shelf in front of you. It is not a legal bid unless you say it is and you fill the dollars.
Not a spray map. Not a materials takeoff from an orthomosaic. If that is the job, stop and go to Geospatial.
Teach
Pick one product for the thread:
- Parts / shopping list — what you must have on the truck, in the van, or on the line.
- Estimate — those lines plus labor and tax as blanks or as numbers you typed.
Same rails. Name the thread list — [job].
What you paste
Job (one sentence):
What I saw / what the ticket says:
Brand, model, or plate text I can actually read (or UNKNOWN):
Count I own (guests, units, rooms) — only if I typed it:
My book or vendor I will price from (name, not the numbers unless I paste them):
"Or equivalent" is allowed: yes/no (I decide)
This is: shopping list / estimate / not a bid
If you have a photo of a data plate, a ticket, or a shelf, attach a crop. Transcribe first. Grok misreads stamps and small type. Your transcription is the source. The photo is a check.
What Grok may write
A table:
| Line | Kind | Qty | SKU / spec | Price | Hours | Status |
|---|
| … | part / labor / tax / fee / question | NEED or your number | NEED or your text | NEED or your number | NEED or your number | NEED / OURS |
A questions list: expansion tank? drip pan? vegetarian count? extra tablecloths? Those are holds, not guesses.
What Grok must not invent
- A SKU, UPC, or model you did not type.
- A price, a tax rate, a trip fee, a “usual 2.5 hours.”
- “Or equivalent” as a gift. That is a policy you type.
- A second laborer to make the hours look cheap.
- A permit cost. Write NEED and who pulls it.
Estimate language. If you did not type “this is a bid,” the header says NOT A BID — list for the lead. If you are bidding, you still fill every dollar. Grok does not.
Kitchen, retail, events. Same table. 80 guests is not 12 half-pans unless you typed the pan math. A retail restock is not last week’s vendor quote unless you pasted it. Event rental counts stay NEED until the client’s email is in the thread.
Tools. grok.com. Think if the plate is messy. Fast is fine once the transcription exists. Do not let Search invent a current Home Depot price as yours. If you Search a spec sheet, you open it; the price is still yours to type.
Worked example
Residential 40-gallon electric water heater. Photo of the data plate. Owner transcribes brand, model, wattage. They will not paste the rate card. They want a shopping list plus labor lines, not dollars.
Grok’s first table invents a replacement SKU, $1,149 installed, 2.5 hours, and a permit already pulled. The owner sends the table back: “Every price, SKU I did not read, and hour is NEED. Permit is NEED — I pull it. Do not write installed total.”
Reprint: tank (match plate), expansion tank (question), T&P, drip pan, supply lines — qty NEED where they did not count, SKU NEED, price NEED, labor line present with hours NEED. Header: NOT A BID. That list can go to the counter. The first table would have gone to the customer as a number the shop did not set.
Your turn
Open grok.com. New thread. Use a real job from this week: a changeout, a ticket, a headcount, a restock, a load-in. Attach a plate or ticket crop if you have one, after you transcribe.
Exercise d-trades-l02-e1
| Field | Value |
|---|
| whereToDo | grok.com |
| time | 22 min |
Copy-ready prompts
Message 1:
I am in Grok Mastery (Russell Tech), Pathway D, Trades & local work, lesson 2 — estimate or parts list.
Job: [one sentence]
What I saw / ticket:
Plate or spec I can read: [or UNKNOWN]
Count I own: [or none]
This is: shopping list / estimate / not a bid
"Or equivalent": yes/no
I will price from: [book or vendor name]. Do not invent those numbers.
If I attach a photo: transcribe only what is readable. Do not guess a model.
Write a List table:
Line, kind, qty, SKU/spec, price, hours, status (NEED or OURS).
Every price, SKU, and hour I did not type is NEED.
Add a questions list. No second person I did not give. No permit marked done.
Header: NOT A BID unless I said this is a bid and I typed the dollars.
Stop before pricing.
Message 2:
I fill only these cells (all others stay NEED):
[paste any qty / SKU / price / hours you actually own]
Reprint the table. Then a 5-line "what I still have to look up."
Session stamp: today's date and "List written by Grok in this thread."
Artifact to paste
- The reprinted table, questions, and look-up list.
- Your transcription (if a photo).
- The session stamp.
- One line from you: the price, SKU, or hour you refused.
Rubric
- Pass: Table is Grok-authored and stamped. NEED on every price/SKU/hour you did not type. Job is real. Not a bid unless you filled dollars. No CRS or spray takeoff.
- Fail: A priced quote Grok invented. “Typical 2.5 hours.” You typed it offline. A GIS materials estimate. No stamp.
Common failure
The common failure is helpful pricing. You did not give a number. Grok did. You forwarded it because it looked like a shop. You now have a bid.
The other failure is trusting the plate read. The model invents a digit. You order that SKU. Transcribe first. If you cannot read it, write UNKNOWN and go look.
What’s next
You have a list that does not spend money by autocomplete. Next: the customer text from the truck — short, true, no invented ETA.
