Turn crew messages into draft job cards
Keep completed work, equipment issues and follow-up questions attached to the right job.
What you’ll produce
Draft job-card updates and an exception list, each linked to the crew message that supports it.
Inputs & connections
- A bounded set of field messages and the current job register
- Job identifiers, status definitions and equipment escalation contacts
Use exported or pasted crew messages for the pilot. Live message access and writes to the job tracker require separate permissions and setup.
Your starting prompt
Replace the bracketed fields. This is our suggested prompt, not a quote from the source.
Review [crew-message batch] against [job register] for [date]. Match each message to an existing job only when the identifier or location is unambiguous. Propose job-card updates for work stated as completed, materials used, next steps and equipment issues. Preserve message time and source reference. Keep reported completion separate from supervisor acceptance. Flag conflicting updates, unknown jobs and missing quantities for review. Put equipment faults in a separate queue for [responsible person]. Do not infer payment status from field chatter or assign a new job without approval. Return proposed changes before writing records or notifying anyone.
How to run it
- 01
Give each active job a consistent ID and define what each status means.
- 02
Import a single day of messages while retaining the originals.
- 03
Generate proposed job-card changes and inspect unmatched or contradictory messages.
- 04
Ask the supervisor to confirm completion and route equipment issues.
- 05
Apply approved updates, recording the source message and reviewer.
Review before you act
Confirm job identity, actual completion, quantities and whether an equipment issue affects safe operation.
Limitations & success checks
- Crew shorthand, reused addresses and delayed messages can attach work to the wrong job.
- A text mentioning an invoice is not evidence of the current accounts-receivable balance.
Measure: Correct job matches, supervisor corrections, unresolved messages and equipment issues reaching the assigned owner.
Sources & attribution
The sources below support the reported example or a tool capability. They do not validate our prompt or prove the outcome in your environment.
Source post and author checked through X public oEmbed on October 17, 2026. The source describes a ground-spraying business using Grok Bot with crew texts and daily reporting. The draft-only job-card process here narrows that reported workflow. The prompt, setup and checks are original editorial additions. The directory has not reproduced the reported deployment or results.
Creator / publisher: @TherealWitty22
Editorial review: 2026-10-17. How we label evidence.