Entry Standard

• Log time, network, station or node, and current status. Every entry.
• Use # mentions to tie entries to MC / MT contacts by name.
• State confidence. Choose one: confirmed / likely / possible / unconfirmed / stale / inferred.
• Attach +GPS when position matters. Do not estimate coordinates.
• Close every ALERT and ACTION. An unresolved entry is an open task.
• Chat is for conversation. Log is for record. Keep them separate.

Quick Launch

Op Phase

Category Reference

Mobile Operations

1. Log PLAN before departure: objective, route, radio state, GPS state, risks, and first checkpoint.
2. Confirm MC / MT connectivity before moving. Log COMMS if no acknowledgement from target station.
3. Log POSITION at departure, each turn or stop, and arrival. Attach GPS when available.
4. Log COMMS after any terrain, antenna, channel, or radio change. Record result and retry plan if failed.
5. Log CONTACT for new MC / MT stations: first heard, path, signal, distance if known.
6. Log INTEL for signal patterns, RC captures, movement observations, or infrastructure notes. Tag accordingly.
7. Log ALERT only for actionable risk. Reserve it for things that need a response, not every problem.
8. Close the route with SITREP: current status, contacts added, unresolved actions, and next planned activation.

Static Station

1. Open with SITREP: location, power, GPS state, MC radios, MT nodes, antenna setup, monitoring channels.
2. Log SITREP every 30–60 minutes, or immediately after any meaningful change.
3. Log COMMS for net checks, MC pings, MT channel checks, messages, relay behavior, and failed paths.
4. Log CONTACT for new arrivals, renamed nodes, unexpected stations, or stations to be added to contacts.
5. Log ACTION for assigned tasks: add contact, move antenna, retry route, restart radio, verify position.
6. Log ALERT for power loss, weather, safety risk, device failure, or loss of expected comms path.
7. At shutdown or handover: export log, add final SITREP with open items and next activation plan.

Remote Assets

• Treat each RC / RPTR unit as a remote station with a callsign (e.g. Argus). Log by callsign.
• Before deploying, log POSITION: placement, antenna orientation, power state, and confidence level.
• Log COMMS for each session: login, OMCOLLECT command, relay import result, or failed attempt.
• After collection, log INTEL: new stations found, strong signals, unusual paths, stale data, and assessment.
• Log ACTION for follow-up: redeploy, reset, firmware check, route verify, or next scheduled collection.

Degraded Comms

• On first sign of degradation: log ALERT with affected network, scope, and immediate mitigation step.
• Log COMMS for each test attempt. Record what changed between attempts, not the discussion around it.
• Log ACTION for each named step: move, retry, swap radio, check power, restart service, verify route.
• When stable: log SITREP. State what is restored, what remains degraded, and the next check time.

Cadence