Workflow · Offline

Emcomm Deployment Workflow

Ordered steps for activation through documentation. Each link opens an offline tool — work top to bottom or jump to your role. These workflows apply in any U.S. county; East Tennessee nets and repeaters on this site are a worked example, not a geographic limit.

Open incident workspace

Jump by role: Field op COML / planner Net control COMT / tech HF traffic General class Amateur Extra Close-out

1 — Deploy readiness

Before you leave for an assignment or net activation.

Go / No-GoWeather, power, safety, agency contact ARES activationMembership, go-kit, credentials RACES authorizationAgency activation & §97.407 Go-kit checklistRadios, power, medical, maps Kit maintenance calendarBatteries, SWR, CHIRP backup schedule Field power hubSize battery and solar

2 — Plan communications

PACE layers and frequency assignments per ICS/NIMS practice. Include digital mesh and DMR as contingency paths.

PACE plannerPrimary, alternate, contingency, emergency ICS-201 briefingSituation, objectives, organization ICS-202 objectivesCommand emphasis and safety message ICS-205Radio frequency assignment plan ICS-210 comm unit planCOML assignments, PACE summary, ref 205 ICS-203 org chartCommand and general staff layout ICS-215 ops worksheetOperational period assignments Frequency scratch padTactical freqs on scene Tactical callsignsIncident identifiers Meshtastic field workflowLoRa mesh contingency steps Meshtastic presetsModem settings reference ICS-208 safety planSafety message & hazards COML tool hubPlanner role tool chain DMR & digitalTalkgroups and East TN digital ICS-206 medical planField medical support planning

3 — Operate the net

Net control, logging, and time references.

SKYWARN District 7 (WX4TN) Counties: Carter, Hawkins, Johnson, Sullivan, Unicoi, Washington. GMRS Tuesday 7 PM on NETNRC linked GMRS. 2m Tuesday 8 PM on 146.805 PL 203.5. Hub · skywarn7.org

WR4CC 146.700 — Holston Mtn SKYWARN Historical Tri-Cities SKYWARN repeater (Carter Co / CCARA). Friday 8 PM ET Skywarn net; Monday 8 PM ET club net. PL 77.0. RepeaterBook lists UTC — times are Eastern local. RepeaterBook

MTEARS statewide Monday 8 PM CT (9 PM ET) on linked UHF — East TN node 443.825 PL 100.0. Weather and emergency activation. mtears.org

NCS tool hubNet control tool chain Net control referenceCheck-ins, traffic, prowords Net script generatorOpening and closing scripts SKYWARN spotter reportStructured severe weather observation ICS-211 rosterCheck-in log with CSV export World clocksUTC, US zones, global nets Phonetic & Q-signalsClear voice traffic

4 — HF & message traffic

When VHF/UHF and internet paths are unavailable.

HF nets & SWL guideTN Phone Net, emergency HF, broadcast highlights HF emcomm bundlePropagation, NVIS, Winlink Winlink session workflowNBEMS session steps end-to-end Digital emcomm hubFT8, VARA, NBEMS, Winlink, APRS Digital modes bundleDMR, Meshtastic, tool cards Winlink templatesFormatted message traffic ICS-213 messageGeneral message form Radiogram worksheetARRL-style formal traffic HF propagationSFI/K band advisor with offline cache 60m channel referenceUSB liaison when repeaters fail — Extra/General

Tennessee Phone Net Weekday morning 6:45 AM CT on 3.980 MHz LSB — evening Mon–Sat 6:30 PM CT. Full schedule on HF nets guide.

5 — Document & close

ICS-214 activity logTimestamped unit log ICS-217 resource statusComms radios & gateways demob ICS-221 demob checkoutPersonnel & equipment release ICS-209 status summaryCommand status briefing Field QSO logContacts with CSV export Resource requestICS-style resource form Demob close-out workflow214 → 217 → 221 → export Incident workspaceExport one close-out packet

How to use this workflow

This workflow mirrors how ARES, RACES, and served-agency emcomm teams actually operate: confirm you are safe and authorized to deploy, plan layered communications before you leave, run the net with consistent scripts and UTC time, shift to HF or message traffic when local repeaters fail, then document everything for debrief.

Every step links to an offline tool on KI4TQN. Install the site as a PWA on your phone, open the tools once while online, and they remain cached for field use. Start at the East TN emcomm hub for SKYWARN D7, MTEARS, and canonical links to the go-bag sheet or full frequency guide.

Not sure where to start? Open the incident workspace, name your event, and fill forms as you go — it tracks which tools have saved data and exports a single text packet when you are done.

Planning comms for a ranch, estate, or multi-building property — not just a volunteer deployment? Start with the free assessment checklist and PACE worksheet, then see emergency communications consulting for assessment, integrated design, and optional on-site validation.

FAQ

Workflow questions

Does this workflow only apply in East Tennessee?

No. The five steps mirror ARES/RACES practice nationwide. East Tennessee nets and repeaters on this site are a worked example — substitute your county's frequencies and net schedules.

Where do I start if I am brand new to emcomm?

Open the go/no-go checklist and ARES activation tools in step 1, then build a PACE plan in step 2. Filter tools.php?persona=deploy for deploy-focused utilities.

When do I jump to step 4 (HF and message traffic)?

When VHF/UHF repeaters, LTE, and internet paths are unavailable or insufficient — check propagation and NVIS before picking band, then Winlink or radiogram as your net directs.

What is the incident workspace for?

A single offline hub that tracks which ICS tools have saved data for your event and exports one close-out text packet — useful across all five workflow steps.

How do digital modes fit this workflow?

Meshtastic and DMR appear in step 2 as contingency paths. FT8, VARA, NBEMS, and Winlink are step 4 when HF data or formal message traffic is required — see digital-emcomm.php for mode placement in PACE.

Net schedules change — confirm on-air or with the club. Wrong listing? Submit a local update. East TN operators: East TN tools bundle. Property owners: consulting.