← Deploy readiness

Role hub

Field Operator

Go-kit, activation checklists, tactical IDs, and spotter reporting for operators assigned to a site or roving position.

Start with go/no-go

Field doctrine

Before you key up on scene

Authorization: Confirm ARES or RACES activation — RACES checklist and county EC contact on ARES hub. Do not self-deploy.
Go/no-go: Weather, power, and safety first — go/no-go tool.
Tactical IDs: Use incident tactical callsigns on scene; legal ham callsign when not in tactical mode — tactical callsigns.
Listen first: Program receive-only and monitor the net before transmitting.

Deployment checklist

Field operator activation

Run go/no-go — weather, credentials, agency contact, safety gear.
Confirm activation on ARES checklist — do not self-deploy.
Pack go-kit checklist and verify battery dates in kit maintenance.
Program tactical freqs on scratch pad before leaving staging.
SKYWARN spotting? Keep spotter report ready on scene.

Go/No-Go ChecklistWorkflow step 1 ARES ActivationWorkflow step 1 RACES Served-Agency ChecklistWorkflow step 1 Go-Kit ChecklistWorkflow step 1 Frequency Scratch PadWorkflow step 2 Tactical Callsign GenWorkflow step 2 Field QSO LogWorkflow step 5 Call Sign CheckerWorkflow step 1 SKYWARN Spotter ReportWorkflow step 3

Pair with emcomm go-bag bundle and go-bag frequency sheet. Close out in incident workspace.

FAQ

Common questions

What does a field operator do in ARES?

Deploys to assigned sites with go-kit gear, checks in on directed nets, reports status, and logs activity for the incident.

When should I run go/no-go before deploying?

Before leaving home or staging — weather, power, credentials, agency contact, and safety items must pass.

Which tools belong in a field go-kit workflow?

Go/no-go, ARES activation, go-kit checklist, kit maintenance, scratch pad, and SKYWARN report if spotting.