Skip to content
OpenMeshTak
Search
Install
Run an event
Participants
Help
For developers
API basics
API examples
SDK
API reference
Menu
Return to top
On this page
Event day checklist
Tick these off around an event. Each line links to where it is explained.
A few days before
The event is
active
and the latest configuration is published; see
Set up an event
.
Members' profiles show no callsign or name conflicts.
The
TAK group mode
fits the event; for many participants, groups save bandwidth.
The server is big enough and its upload fast enough; see
Server size and bandwidth
.
System status
shows only green checks, and the TAK server certificate is valid well past the event; see
System status and logs
.
One test phone enrolls, receives the Data Packages and shows other positions.
If you want a replay later,
recording
is switched on with a suitable retention; see
Live view and history
.
A recent backup exists; see
Backup and upgrade
.
For an HQ without internet, the
Offline HQ
is prepared and tested without network.
On the day
Keep
Live TAK
and
System status
open in the operations room.
Participants who cannot get in: send a new access or setup link, or set up their device for them; see
Participant setup
.
Revoke the app of a lost phone right away; see
Users and permissions
.
Many "TAK client too slow" warnings at once mean the upload is too small; see
Warnings
.
Afterwards
Export the tracks you want to keep from
History
before the retention period ends.
Keep the event accounts of people who stay, then
archive
the event; other event accounts are removed.
Remove offline data from the HQ computer.
Switch off recording if the event continues without it.