Field comms SOPs

The field does not need an essay. It needs the next sentence, the hold point, and who is allowed to talk. Grok is a clerk for that document. It is not the PIC.

Why this matters

People ask Grok to “write a drone SOP” or “write a field safety plan” and get a generic Part 107 pamphlet: check weather, maintain VLOS, don’t fly over people. None of it names this gate, this frequency, this livestock, this county road, or who calls abort. Crews do not execute pamphlets. They execute the next line.

This track is Russell Tech field standard: geospatial, drone, ag, utilities, land. The same discipline applies to a rover crew that never leaves the ground. If you do not fly, write for the job you do — GPS, scouting, construction layout, spray records, a walk of a corridor. Do not copy a school packet. Do not invent a job you will never stand on.

Grok will cheerfully clear you to launch. That sentence is never allowed to survive.

Teach

An SOP here is an operating document, not a policy binder. Six parts, in this order:

1. Trigger. When this document is in force. “Mapping flight, rural development site, two-person crew, Class G, daylight.” Not “all aviation activities.”
2. Roles. Names of functions: PIC, visual observer, rover, driver, mixer. Who may speak on the radio. Who may say abort. One person, one function, even if one human wears two hats — write the hats.
3. Steps. Numbered. One action per line. Times if they exist. “Arrive 45 minutes before launch slot. Walk the takeoff pad. Confirm the card.”
4. Hold points. Work stops until a human says go. Examples: airspace / LAANC or equivalent is current; landowner or superintendent said today; weather abort line you named; livestock or road traffic; battery / control link; the map or data dictionary is the one for this site. Hold points are not decorations. They are the reason the SOP exists.
5. Comms. What is said on the radio vs what is written on the tailboard vs what waits for the office. Short calls. No jokes on the air. Who you call if the plan breaks (dispatch, PIC, the superintendent — not “someone”).
6. Abort and sign. What conditions kill the job. Who signs that you flew or collected what you said you did. Empty signature lines stay empty.

Tailboard, radio, after-action. Three products, three lengths.

• Tailboard: one page, read aloud in two minutes, hazards + holds + comms.
• Radio: the calls you will actually make. “On station.” “Hold, vehicle on the county road.” “Land, abort, cattle on the pad.”
• After-action: what broke, what data is missing, what the office must not assume.

Grok can draft all three from one brief. You fill the site facts. If a fact is missing, the line is NEED — not a plausible frequency.

What Grok must never invent

• Frequencies, gate codes, passcodes, phone numbers.
• “You are clear to launch,” “LAANC approved,” “airspace is Class G so you’re fine,” “the spray buffer is 50 feet,” “the rover is on NAD83 (2011) / this zone.”
• Wind numbers, ceiling, NOTAMs, livestock counts, landowner mood.
• A second crew member you do not have.

Grok may list questions a PIC should answer from official sources and from the walk. It may not answer them from a training prior.

Part 107, labels, and ag rules. If you fly under FAA Part 107, Grok can help you remember to check the current chart, the current LAANC or authorization path, the current weather source, and your own ops manual. It cannot be that check. The same for pesticide labels, worker-protection, and county road permits. Search is allowed later in this track for finding the page. The page, plus you, is the authority.

Language. Numbered. Short. Verbs first. No “ensure situational awareness.” Replace with “VO watches the county road and calls HOLD if a vehicle enters the approach.” If a line cannot be read on a tailgate in the wind, cut it.

Ground crews. A rover SOP is the same shape. Trigger: collect the west fence line, data dictionary v3. Hold: correct CRS and feature class on the data collector; control check against the known point; storm. Comms: who you call if the collector dies. Abort: you do not “just use the phone GPS and fix it later” unless that is a written, signed product with a different accuracy claim.

Worked example

A two-person mapping flight. Rural South Dakota development, prairie to the west, a slough on the south line, one county road, cattle in the adjacent pasture. Aircraft under 55 lb, daylight, visual observer required by the company’s own rule even when the regulation would allow a solo. Product: orthomosaic for the superintendent, not a marketing still set.

Bad brief: “Write a professional drone safety SOP.”

Useful brief:

Intent: A one-page tailboard plus a 10-line radio card the VO can hold. Context: Two people. PIC flies. VO is also the driver. County road on the east. Cattle through one wire to the south. Takeoff pad is the gravel spur, not the lot. Launch window 10:00–11:30 if wind at the pad is under our company abort (PIC measures; do not invent a number). No published frequency — we use phones. Superintendent is on site. We do not have a second aircraft. Constraints: Numbered lines. Hold points must include road, cattle, airspace check, and landowner/superintendent same-day yes. Do not clear the flight. Do not invent a frequency, a wind number, a class of airspace, or a LAANC status. Write NEED where I left a hole. No pep talk.

Grok invented “Class G, 400 feet, LAANC not required” and a 15-mph abort. The PIC deleted all three. Airspace is a check, not a memory. The abort is in the company manual, not in the model. What Grok got right was the radio card: HOLD for the road, HOLD for cattle on the pad, LAND if the VO loses the aircraft behind the barn. Those lines are useful because the site had a barn and a road.

The PIC added one hold the model missed: confirm the correct mission file — last week’s adjacent section is still on the tablet.

Your turn

Open grok.com. New thread named field comms — [site or job]. Use a job you fly, walk, collect, or will collect in the next 30 days. If your work is classroom-only, use a field day you actually run with students — still no invented airspace.

Exercise d-geo-l01-e1

Copy-ready prompt

I am in Grok Mastery (Russell Tech), Pathway D, Geospatial, lesson 1 — field comms SOPs.

Interview me with exactly seven short questions, one at a time:
1) What the job is (flight, rover, scout, spray support, corridor walk) and the product
2) Where, in plain language (no need for a legal description)
3) How many people, and their functions
4) The real hazards I already know (road, livestock, power, public, weather)
5) How we actually talk (radio frequency I will type, phones, or both). If I do not give a frequency, write NEED later — do not invent one
6) Who can call abort
7) What I will never let an assistant “clear”

Then write a Field Comms SOP:
- Trigger
- Roles
- Steps (numbered, one action each, no more than 16)
- Hold points (each one a human go/no-go)
- Radio or phone calls (exact short phrases)
- Abort
- Sign / after-action (what the office must not assume)
- NEED list
- Session stamp: today's date and "Field comms SOP written by Grok in this thread."

Rules:
- Do not say we are clear to launch, spray, enter, or collect.
- Do not invent frequencies, codes, CRS, wind numbers, airspace class, buffers, or a person I do not have.
- If a hold depends on an official source, write "PIC/lead checks [source] — status not in this SOP."

Artifact to paste

1. The Field Comms SOP (all parts, including NEED and stamp).
2. Your answers to the seven questions.
3. One line from you: a hold point Grok invented or skipped, and what you did about it.

Rubric

• Pass: SOP is Grok-authored and stamped. No clearance sentence. No invented frequency/CRS/wind. Hold points include at least one site-specific hazard you named. Roles match the headcount you gave. Job is real.
• Fail: A generic Part 107 essay. You wrote the SOP without Grok. “Ensure safety” as a step. A solo crew that magically has a VO and a driver. Airspace declared from memory.

Common failure

The common failure is regulatory wallpaper. Two pages of “comply with all applicable laws” and no line about the county road. The crew already knew they had to follow the law. They needed the road call.

The other failure is Grok as dispatch. You ask it on the tailgate, in the wind, whether you can launch. Put the phone away. Walk the pad. Check the source you already named. The SOP is for humans on the ground.

What’s next

You can write a comms SOP that does not clear itself. Next: imagery and GIS analysis prompts — how to brief Grok on a map without letting it invent acres, coordinates, or a clearance.

I am in Grok Mastery (Russell Tech), Pathway D, Geospatial, lesson 1 — field comms SOPs.

Interview me with exactly seven short questions, one at a time:
1) What the job is (flight, rover, scout, spray support, corridor walk) and the product
2) Where, in plain language (no need for a legal description)
3) How many people, and their functions
4) The real hazards I already know (road, livestock, power, public, weather)
5) How we actually talk (radio frequency I will type, phones, or both). If I do not give a frequency, write NEED later — do not invent one
6) Who can call abort
7) What I will never let an assistant “clear”

Then write a Field Comms SOP:
- Trigger
- Roles
- Steps (numbered, one action each, no more than 16)
- Hold points (each one a human go/no-go)
- Radio or phone calls (exact short phrases)
- Abort
- Sign / after-action (what the office must not assume)
- NEED list
- Session stamp: today's date and "Field comms SOP written by Grok in this thread."

Rules:
- Do not say we are clear to launch, spray, enter, or collect.
- Do not invent frequencies, codes, CRS, wind numbers, airspace class, buffers, or a person I do not have.
- If a hold depends on an official source, write "PIC/lead checks [source] — status not in this SOP."