Installation
Get this open-source Field Day logging software running on your server in about 5 minutes. Works on any Linux machine with 2 GB of RAM, including a Raspberry Pi 4 running off a battery pack at your Field Day site.
Installing for the first time? Follow Install Field Day Commander for a guided walkthrough with hostname and connection checks. This reference covers supported systems, deployment flags, and advanced options.
System Requirements
Field Day Commander is designed to run on modest hardware, the kind of gear you'd actually bring to a field site. The deploy script installs everything it needs, so you're starting from a bare OS.
| Component | Minimum | Recommended |
|---|---|---|
| Operating System | Ubuntu 22.04 / Debian 12 (64-bit) | Ubuntu 24.04 LTS or Raspberry Pi OS (64-bit) |
| RAM | 2 GB | 4 GB+ |
| Storage | 16 GB | 32 GB+ |
| Network | LAN access | Gigabit Ethernet |
You do not need to install PHP, MariaDB, Node.js, or any other dependencies yourself. The deploy script handles all of it. It installs PHP 8.4, MariaDB, Redis, Node.js 22, Composer, and FrankenPHP automatically. It supports Ubuntu, Debian, and Raspberry Pi OS, plus RHEL, AlmaLinux, and Rocky Linux. The OS has to be 64-bit (x86_64 or ARM64), so on a Pi use the 64-bit Raspberry Pi OS image.
Install Steps
Clone the Repository
Pull down the source code from GitHub.
Run the Deploy Script
One command. The script installs PHP 8.4, MariaDB, Redis, Node.js, Composer, and FrankenPHP. It compiles front-end assets, runs database migrations, seeds reference data (bands, modes, ARRL sections, bonus types), and creates systemd services for the web server, queue worker, scheduler, and WebSocket server.
Open It in a Browser
Navigate to your server's address from any device on the network. The setup wizard has you set a password for the built-in SYSTEM admin account. Then create your event and start configuring.
1. Clone the Repository
2. Run the Deploy Script
Choose and Verify Your Server’s Hostname
Prefer a hostname your station devices can resolve. Run hostname on the server to check its device name. On a Raspberry Pi with mDNS working, a device named fd-commander can be reached as fd-commander.local. From a station laptop on the same network, run ping fd-commander.local, replacing the name with yours, and check that it resolves to the server’s LAN address. See Raspberry Pi’s hostname and address-discovery instructions.
Replace YOUR_SERVER_HOSTNAME below with the hostname you verified, including .local when using mDNS. For the example above, use --domain fd-commander.local and later open http://fd-commander.local. That name only applies if your device is actually named fd-commander and clients can resolve it. A name configured in your local DNS is another option.
The --domain flag configures the address Field Day Commander serves. It does not rename your computer, create a DNS record, or make an arbitrary .local name work. Choose an address your station devices can already use to reach the server:
- Your server’s actual hostname plus
.local, if mDNS works on the server and clients. A Pi you namedfd-commanderwould usefd-commander.localbecause of its device name, not because Field Day Commander is installed. Runhostnameon the server to check its name, then confirm the address resolves from a station device. - As a fallback if hostname resolution cannot be set up, the server’s actual LAN IP address. Find it with
hostname -Ion the server, and give it a DHCP reservation or fixed IP. Deploy with that IP and use the same IP in the browser. - A real domain like
fd.yourclub.orgif you're deploying with SSL for remote access
You can change this later by re-running the deploy script with a different --domain value.
The script runs through its phases in order: detecting your OS, installing system packages, copying and building the application, creating the database, installing Redis, configuring FrankenPHP, setting up SSL (if requested), creating systemd services, opening firewall ports, and caching the configuration. It logs everything to /var/log/fd-commander-deploy.log. The summary at the end suggests scheduling backups with backup.sh --install-schedule. See Backups.
3. Open It Up
Once the script finishes, open a browser on any device connected to your LAN and navigate to the domain or IP you specified. By default the server runs on port 80 (HTTP). The setup wizard appears on your first visit and has you set the password for the pre-created SYSTEM account, as described in First Event Setup.
Deploy Script Flags
The deploy script accepts several optional flags to customize the installation. Only --domain is required.
| Flag | Default | Description |
|---|---|---|
| --domain | (required) | Actual reachable hostname or LAN IP address; does not create or rename a hostname |
| --port | 80 (HTTP) / 443 (SSL) | Port for the web server |
| --ssl | off | Enable HTTPS. Uses Let's Encrypt by default |
| (none) | Email for Let's Encrypt certificate registration | |
| --ssl-cert | (none) | Path to a custom SSL certificate file |
| --ssl-key | (none) | Path to a custom SSL private key file |
| --db-name | fd_commander | MariaDB database name |
| --db-user | fd_commander | MariaDB username |
| --db-password | (generated) | MariaDB password. Auto-generated if omitted |
| --app-path | /var/www/fd-commander | Installation directory on the server |
| --reverb-port | 8080 | Local port for the WebSocket server (Laravel Reverb). It listens on 127.0.0.1 and browsers reach it through the web port, so you don't need to open it in the firewall |
| --branch | main | Git branch to deploy |
| --repo-url | (copy current directory) | Clone from this Git URL instead of copying the directory you ran the script from. The install will then be a Git checkout |
| --no-seeders | off | Skip database seeders (bands, modes, sections, etc.) |
| --dry-run | off | Print what would be done without making changes |
Example: Raspberry Pi on your LAN
This example assumes the Pi is named fd-commander and station devices can resolve fd-commander.local. Replace it with the hostname you verified above. This deploys on port 80 with HTTP; operators open http:// followed by the same hostname passed to --domain.
Example: HTTPS with Let's Encrypt
Caddy (the web server bundled with FrankenPHP) handles Let's Encrypt certificate provisioning and auto-renewal. This requires the server to be reachable from the internet on ports 80 and 443 during setup.
First Event Setup
The first time you open Field Day Commander, a setup wizard walks you through three steps. Step 1 sets the admin password for the pre-created SYSTEM account (callsign SYSTEM, email admin@localhost). Step 2 configures site branding: your site name (defaults to "Field Day Commander"), an optional tagline, and an optional logo upload. Step 3 sets your organization information and system preferences including timezone, date format, and time format. After the wizard completes, you're redirected to the login page.
Sign in with admin@localhost and the password you set. The app will display a prominent warning that the SYSTEM account is for initial configuration only. Your first action should be to create a personal account tied to your own callsign. Go to Administration > Users, click Add User, fill in your callsign, email, name, and password, and set the role to System Administrator. Then choose Sign Out from the account menu in the top-right corner and sign back in with your personal account. From that point on the SYSTEM account can be left alone. See the First Event Setup how-to for a detailed walkthrough.
Create an Event
Click Create Event on the dashboard. The form is split into cards. Under Event Information, give the event a name and pick the event type. For Field Day, the start and end times fill in from the ARRL schedule (fourth full weekend of June, 1800 UTC Saturday to 2059 UTC Sunday). For Winter Field Day, they come from the WFDA schedule (fourth full weekend of January, 1600 UTC Saturday to 2159 UTC Sunday). The form also shows when the setup window opens. For Winter Field Day that's 24 hours before the start, Friday at 1600 UTC. The Scoring Rules dropdown lets you pick which rule year to score by. It defaults to the event's year and locks once the event starts.
Under Event Location, the fields are technically optional, but latitude and longitude are required for the weather widget and NWS severe weather alerts to function. Fill them in if your site has internet access and you want weather data. City and state appear in auto-filled Section Manager messages, grid square is shown as a reference for operators, and talk-in frequency lets visitors know what frequency to tune to for directions to your site.
Under Station Configuration, fill in your station callsign, club name, section, operating class, and number of transmitters. Field Day uses classes A through F. Winter Field Day uses H (Home), I (Indoor), O (Outdoor), and M (Mobile), and a collapsible WFD rules: class, category and location panel explains how to pick one. Under Power Configuration, enter your maximum wattage and select your power sources (Commercial Power, Generator, Battery, or Alternate Power). On Field Day events the form shows the applicable power multiplier as you go. Winter Field Day doesn't use a power multiplier, so that part is hidden.
The GOTA Station (Get On The Air) card lets novice operators make contacts under supervision. It only appears for classes that allow a GOTA station, so you won't see it on a Winter Field Day event. Turn on Open to the public under Public Visitors if you want people to come see the operation. The directions, visiting times, contact details, website, and "What visitors will see" text you enter there show up in a Visit Us section on the public page. Last, Guestbook Settings turns on the visitor guestbook (see Visitor Guestbook).
Setup Checklist
The dashboard tracks five setup milestones:
Event configuration created
Your event exists with callsign, section, class, and power sources defined.
Equipment inventoried
At least one piece of equipment has been added to the system.
Stations set up
At least one station has been defined with band and mode assignments.
Shifts scheduled
Operator shifts have been created for your stations.
W1AW Bulletin schedule set up
The bulletin transmission schedule has been entered for the event. On Winter Field Day events this item reads WFD Bulletin schedule set up.
Invite Operators
The dashboard shows a registration link that you can share with your club. For a local install, this uses the server address configured during deployment (for example, http://fd-commander.local/register if that is your configured, reachable hostname), so operators need to be on the same LAN or Wi-Fi network as the server to reach it. If you've set up DNS and TLS, operators can register remotely using your public hostname. Operators visit the link, register with their callsign, and they're in the system. By default, new registrations get the Operator role. To change how registration works (open, approval required, email verification required, or disabled), set REGISTRATION_MODE in the server's .env file.
Dashboard
The dashboard is the first thing operators see after signing in. It's a grid of widgets showing the score, QSO rate, recent contacts, a countdown to the start or end of the event, and whatever else you put there. Each user has their own layouts, so the operator watching the rate chart and the event manager watching equipment status don't have to share one screen. If you have more than one dashboard, a Switch Dashboard dropdown lets you pick between them. Manage opens a dialog where you can create a new dashboard (blank or copied from an existing one), duplicate or delete one, and Set as Default.
Editing the Layout
Click Edit Layout to rearrange things. The toolbar has Add Widget, Undo, Save, and Cancel. Drag a widget to move it, with a mouse or a finger. The other widgets slide out of the way as you drag, so you can see where everything will land before you let go. To move one from the keyboard, focus the widget, press Enter or Space to pick it up, use the arrow keys to move it, and press Enter to drop it or Escape to cancel. Each widget also has buttons to resize, configure, and remove it.
Undo (or Ctrl+Z, Cmd+Z on a Mac) steps back through up to 30 changes made since you entered edit mode. Nothing is saved until you click Save, and the browser warns you if you try to leave with unsaved changes. Edit Layout and Manage are hidden on station-mode browsers (see Station Mode).
Widget Options
Click the configure button on a widget, or pick one from Add Widget, to set its options:
- Stat Card. A single number. Metric chooses which one it shows (Total Score, QSO Count, Sections Worked, Points Per Hour, Hours Remaining, Guestbook Entries, and more), with optional trend and comparison indicators.
- Chart. Chart Type (bar, line, pie, or doughnut), Data Source (QSOs per hour, band, or mode), and Time Range (last hour up to the entire event).
- Progress Bar. Progress Metric tracks the next 50-QSO milestone, a score goal, the operating class QSO target, or bonus point progress.
- List. List Type (Recent Contacts, Active Stations, or Equipment Status) and Number of Items.
- Info Card. Information Type can show event details, location and grid square, or operating class and power.
- Activity Feed. Show can filter the feed to all activity, contact milestones and new sections, QSO milestones only, or equipment events.
- Timer and Sections Worked. No options. The timer counts down to the start or end of the event.
User Roles
Field Day Commander ships with five built-in roles. Each role has a specific set of permissions that control what parts of the system a user can access. Roles are managed under System Settings > Role Management (a tab on the System Settings page).
| Role | What They Can Do |
|---|---|
| System Administrator | 26 permissions. Full access to everything: contact logging, all event management, all station and equipment functions, user administration, scheduling, content management, reporting, security logs, contact import, and weather management. Marked as Protected Role, so this role always exists and can't be deleted. |
| Event Manager | 23 permissions. Manages the full operational side of Field Day: logging and importing contacts, managing events, stations, equipment, schedules, bonuses, guestbook, photos, security logs, and weather. Cannot administer users, roles, or system settings. |
| Station Captain | 10 permissions. Logs and edits contacts, manages stations and equipment inventory, marks stations unavailable or ready, sets up station-mode browsers, handles equipment assignments, manages the W1AW bulletin schedule, views all equipment, and signs up for shifts. Runs an operating position and keeps operators on task. |
| Operator | 4 permissions. Logs contacts, views stations, manages personal equipment, and signs up for shifts. The default role for new registrations. Intentionally minimal so new hams can get on the air without seeing admin clutter. |
| Config Only | 8 permissions. A restricted bootstrap role: can manage users, roles, and settings, and has read-only access to events, stations, equipment, reports, and security logs. Cannot log contacts, manage events operationally, or participate in operations. Assigned exclusively to the built-in SYSTEM account. Marked as Protected Role. |
Permissions Reference
The permission system is organized into eight categories with 26 individual permissions. Each permission controls access to a specific area of Field Day Commander. The table below shows what each operational role gets out of the box. Config Only (the SYSTEM account role) is not shown here since it is not used for normal operations.
| Category | Permission | Description | Oper. | Stn. Capt. | Evt. Mgr. | Sys. Admin |
|---|---|---|---|---|---|---|
| Contact Logging | log-contacts |
Create new QSO entries | ✓ | ✓ | ✓ | ✓ |
edit-contacts |
Edit or delete existing QSOs | - | ✓ | ✓ | ✓ | |
import-contacts |
Import contacts from ADIF files | - | - | ✓ | ✓ | |
| Event Management | view-events |
View events list and details | - | - | ✓ | ✓ |
create-events |
Create new Field Day events | - | - | ✓ | ✓ | |
edit-events |
Edit existing Field Day events | - | - | ✓ | ✓ | |
delete-events |
Delete Field Day events | - | - | ✓ | ✓ | |
manage-bulletins |
Manage W1AW bulletin schedule | - | ✓ | ✓ | ✓ | |
verify-bonuses |
Approve or reject bonus point claims | - | - | ✓ | ✓ | |
| Station & Equipment | view-stations |
View stations list and details | ✓ | ✓ | ✓ | ✓ |
manage-stations |
Add and edit operating stations | - | ✓ | ✓ | ✓ | |
manage-equipment |
Manage shared equipment inventory | - | ✓ | ✓ | ✓ | |
manage-own-equipment |
Create, edit, and delete personal equipment in catalog | ✓ | ✓ | ✓ | ✓ | |
view-all-equipment |
View everyone's equipment catalog | - | ✓ | ✓ | ✓ | |
manage-event-equipment |
Manage equipment assignments for events | - | ✓ | ✓ | ✓ | |
edit-any-equipment |
Edit equipment details for any user | - | - | ✓ | ✓ | |
| User Administration | manage-users |
Create, edit, and delete user accounts | - | - | - | ✓ |
manage-roles |
Create roles and assign permissions | - | - | - | ✓ | |
manage-settings |
Configure system settings and preferences | - | - | - | ✓ | |
| Content Management | sign-up-shifts |
Sign up for and check in/out of volunteer shifts | ✓ | ✓ | ✓ | ✓ |
manage-guestbook |
Manage guestbook entries (verify, edit, delete, export) | - | - | ✓ | ✓ | |
manage-shifts |
Create, edit, and manage shift schedules and assignments | - | - | ✓ | ✓ | |
manage-images |
Upload and delete event photos | - | - | ✓ | ✓ | |
| Reporting | view-reports |
Access detailed score reports | - | - | ✓ | ✓ |
| Security | view-security-logs |
View security logs and activity records | - | - | ✓ | ✓ |
| Weather | manage-weather |
Manually enter weather data and trigger storm alerts | - | - | ✓ | ✓ |
Creating Custom Roles
The five default roles cover most clubs, but you can create your own. Go to System Settings > Role Management and click Create Role. Give the role a name, then check the permissions you want it to have. Permissions are grouped by category with a Select All toggle at the top of each group, so you can quickly grant an entire category at once or pick individual permissions one by one. Click Save Permissions when you're done.
A few ideas for custom roles: a Logger role with log-contacts and edit-contacts for experienced operators who need to fix mistakes, a Public Info role with just manage-guestbook and view-reports for the person running the public information table, or a Tech Lead with manage-stations and manage-equipment but no event management access.
Assigning Roles to Users
Go to Administration > Users to see everyone registered in the system. The table shows each user's callsign, name, email, current role (shown as a colored badge), license class, and account status. Open the actions menu on any user row and choose Edit to open their profile, where you can change their role from the Role dropdown. You can also update their callsign, email, name, and license class from this same form.
New registrations default to the Operator role.
User Management Actions
The Users page also gives administrators a few account management tools. From the actions menu on any user row, you can Lock Account to temporarily disable a user's access (and Unlock Account to restore it), Force Password Change to require them to change their password on next login, Reset Password to generate a new one, or Delete to remove the account entirely. These actions are only available to users with the manage-users permission.
Callsign-Only Accounts
A callsign-only account is a callsign with no login. Field Day Commander creates one when it sees a new callsign at a station-mode browser, from an external logger, or in an ADIF import. The account lets contacts be credited to that callsign. It has no personal sign-in; the operator can still use their callsign at a station-mode browser.
Callsign-only accounts show a No Sign-In badge on the Users page. To list them, set the Status filter to No Sign-In (callsign only).
To give a callsign-only account a personal sign-in, choose Activate Account from its actions menu. Enter an email, confirm the name, and copy the Temporary Password to give the operator. Click Activate Account. The account gets the Operator role if it has none, and they'll have to change the password the first time they sign in.
Stations
Stations represent individual operating positions. Each one is a radio, an antenna, and someone in a chair. Go to Event Management > Stations to see your station list for the current event. The page shows a summary bar with total stations, how many are active right now, and total equipment items assigned. Idle and Unavailable counts appear there too when any station is in those states. A station is idle when it has an open session but no contact in the last 30 minutes.
Creating a Station
Click Add Station to open the station form. It has three tabs: Configuration, Equipment, and Activity. The Configuration tab has four sections:
Basic Information: Give the station a name (must be unique within the event), an optional hostname, and confirm which event it belongs to. The hostname lets Field Day Commander match contacts from external software to this station. N1MM Logger+ matches on the computer (NetBIOS) name of the PC running it, while WSJT-X, JTDX, and other ADIF senders match on the station callsign.
Station Type: Check any special designations that apply. GOTA (Get On The Air) marks it as the special station for new operators; only one GOTA station is allowed per event. VHF/UHF Only marks it as a station that operates only on VHF/UHF bands. Satellite marks it for satellite communications.
Primary Radio: Select the main transceiver. The dropdown pulls from all user equipment catalogs, showing the radio name, wattage, and owner. Once selected, Field Day Commander displays the radio's power capability so you can verify it fits your power class.
Power Configuration: Set the max power output in watts. Field Day Commander validates this against the event's power limit and shows a confirmation when it's within range. Pick a Power Source (Generator, Commercial Mains, Battery, Solar, or Other) and add optional Power Source Notes. Both the power and the power source feed the power multiplier: the highest station power sets it for the whole entry, and a station on generator or commercial power rules out the 5x QRP multiplier.
Assigning Equipment
Switch to the Equipment tab to assign additional gear beyond the primary radio. The left panel shows what's already assigned to the station. The right panel lists available equipment, filterable by type, owner, and whether it's committed to this event or from the general catalog. Use the search and filters to find equipment, then drag items from right to left to assign them.
Station Activity
The Activity tab on a station's edit page shows what the station has done so far: Total QSOs, Total Sessions, and an Operating Sessions table listing each operator's band, mode, start and end times, duration, and QSO count.
Marking a Station Unavailable
To keep operators off a station that's broken or being worked on, mark it unavailable. Station captains, event managers, and admins (anyone with manage-stations) see a Mark Unavailable button on each station card. Pick a Reason (Equipment Failure, Antenna Problem, Maintenance / Setup, or Other) and add an optional Note. Any session running on the station is ended.
The card then shows the reason, note, and who marked it down and when. On the Log Contact station list, the station shows "Down" with the reason, and nobody can start a session on it or take it over. When it's fixed, click Mark Ready to put it back in service.
Cloning from a Previous Event
If you're running the same station setup as last time, click Clone from Event on the main Stations page. This copies all station definitions (names, types, power configurations) from a previous event into the current one, so you don't have to rebuild everything from scratch.
Station Mode
Station mode is for a computer that stays at a station while operators take turns on it, whether it's club equipment or a member's laptop. Once a laptop is bound to its station, anyone can sit down, type their callsign, and log on that station without a password, including the GOTA station, visitors who want to make a contact, and members who never got around to registering. In exchange for skipping the password, the session is locked down to logging and read-only pages.
Setting Up a Browser
Station captains, event managers, and admins can enroll a browser. On the laptop that will stay at the station, sign in and go to Event Management > Stations. Each station card has a Station-Mode Browsers block. Click Use This Browser for Station Mode and confirm. You're signed out right away, and the browser now shows the station-mode screen for that station. The enrollment lasts a year, and a station can have more than one enrolled browser.
What Operators See
The station-mode screen shows the station name, a Your callsign field, and a Start Logging button. If Field Day Commander doesn't know the callsign yet, it asks for a first and last name and creates a callsign-only account for it. An existing member's callsign works too, without their password, but they only get station-mode powers. On a GOTA station the field is labeled Control operator callsign. The GOTA coach signs in and stays put, and each GOTA operator is entered on the logging screen as usual.
After signing in, the operator goes straight to Log Contact with the station already chosen. They pick band, mode, and power and start logging. The session can only log for that station. Admin pages, Transcribe Paper Log, Message Traffic, the bulletin page, photo uploads, and dashboard editing are all off limits, and the safety checklist is read-only. An admin who types their own callsign at the terminal still gets only logging powers. Operators can view the dashboard, the log, the section map, scoring, the shift schedule, and similar read-only pages.
Ending a Session
The header has a red Sign Out button in place of the user menu. Clicking it (or End Session on the logging screen) ends the operating session, signs the operator out, and returns the browser to the callsign screen for the next person. If nobody touches the keyboard, mouse, or screen for 15 minutes, an Are you still operating? dialog counts down 60 seconds. Click Keep Session Open to keep going. Otherwise the session ends on its own, so a forgotten session doesn't stay open for the next person who walks up.
Revoking and Exiting
To take a browser out of station mode from anywhere, click Remove Browser next to it on the Stations page. Any operator session on it ends at the next click, and the browser can't start new sessions. At the laptop itself, click Station captain: exit station mode at the bottom of the callsign screen and enter the email and password of someone with Manage Stations permission. This exits station mode without signing that person in. A captain who signs in normally on an enrolled browser also gets a Station Mode Browser link in the user menu, with Sign Out and Exit Station Mode buttons.
If a station is marked unavailable, the station-mode screen shows a warning. Operators can still sign in to view the log, but they can't start a session until the station is marked ready.
Volunteer Scheduling
The scheduling system lets you define shift blocks and roles, then lets volunteers self-sign-up for open slots. Event Management > Shift Schedule is the operator-facing board where people browse and claim shifts. Its Dashboard button opens the Shift Dashboard, which shows coverage at a glance. Administration > Manage Schedule is where the event manager builds the schedule.
Setting Up Roles
Before creating shifts, define the roles you need. Go to Administration > Manage Schedule and click the Roles tab. Field Day Commander ships with sample roles that cover common Field Day positions: Safety Officer, Site Responsibilities, Public Information Table, Public Greeter, GOTA Coach, Message Handler, Event Manager, Station Captain, and Operator. Each role has a description, an optional bonus point value, and two key settings:
Requires Confirmation means a manager must confirm a volunteer's check-in before it counts. Giving a role bonus points turns this on automatically. The bonus points on a role are a reminder of what it's worth. Only the Public Information Table role awards its bonus when a check-in is confirmed, and it carries an Auto-awarded on confirmation badge. The other bonus roles need more than a person on the schedule, so their bonuses come from the safety checklist, supervised GOTA sessions, message traffic, or a manual claim. See Plan Your Bonuses and Objectives.
Click Add Custom Role to create roles specific to your club, like "Antenna Setup Crew" or "Food Coordinator." You can delete or edit the sample roles if they don't fit.
Creating Shifts
Switch to the Shifts tab and click Add Shift. Each shift needs a role (from the dropdown), a start time and end time (entered in your local timezone and shown to each volunteer in theirs), a capacity (how many people can fill the slot), and optionally notes. The Open for Sign-ups toggle controls whether operators can self-assign or whether the manager must assign them manually.
For events with lots of shifts, use the Create Multiple Shifts button to generate multiple shift blocks at once instead of creating them one at a time.
Managing Shifts
Each shift card on the admin Shifts tab has buttons to edit or delete the shift. Unfilled slots have an Assign button so the event manager can manually place someone without waiting for self-sign-up. For each person already assigned to a shift, the manager can Check In, Check Out, Mark No-Show, or Remove Assignment directly from the card. A no-show frees the slot, so you can assign someone else to it.
To credit volunteers who forgot to check out at the end of a shift, mark them worked. Once a shift has ended, each assignment gets a Mark Worked button that credits the person for the full shift, and a shift with several loose ends gets a Mark N worked button for all of them. If any ended shifts still have unresolved assignments, a banner at the top of the Shifts tab says how many, with Show past shifts to review them and Mark all worked to clear them in one go. No-shows and existing check-outs aren't changed. Undo Mark Worked reverses a single one.
Confirmations
The Confirmations tab on Manage Schedule lists check-ins to roles that require confirmation, with Confirm and Reject buttons on each entry. Everyone who can manage shifts gets an in-app notification when one comes in. If you'd rather not, turn off Shift Confirmations under In-App Notification Categories on your profile.
Shift Dashboard
To see who's covering the overnight hours, open Event Management > Shift Schedule and click Dashboard. Any signed-in user can view it, and it refreshes itself every minute. The Timeline card draws each role's shifts across the event, shaded full, partial, or empty, with a marker for the current time. The Coverage card gives an overall percentage plus filled slots, open slots, fully staffed shifts, and who's on duty now. Coverage Gaps lists upcoming shifts that are unstaffed or under half staffed. Managers can click an open shift on the timeline, or a gap in the list, to assign someone on the spot.
The Operator View
Operators go to Event Management > Shift Schedule to see available shifts filtered by role. Check-in opens 15 minutes before a shift starts and closes when it ends. They can sign up for open slots and click My Shifts to see only their own assignments. My Shifts is also in the user menu in the top-right corner.
Equipment Tracking
Field Day Commander gives every operator a personal equipment catalog and ties it into the event workflow so you always know what gear is where. There are four equipment pages depending on your role and what you're looking at.
My Equipment
Go to Equipment > My Equipment and click Add Equipment. The form captures everything you'd want to know about a piece of gear:
Equipment Details: Make and model (required), type (Radio, Antenna, Amplifier, Computer, Power Supply, Accessory, Tool, Furniture, or Other), serial number, and a free-text description. Admins also see an Owner dropdown to assign equipment to any registered user. Operators creating their own gear won't see this field. Their equipment is assigned to them automatically.
Technical Specifications: Power output in watts (used when the radio is selected as a station's primary transceiver) and estimated value in USD.
Operational Information: Emergency contact phone, comma-separated tags (e.g., "HF, Portable, Contest"), and notes.
Supported Bands: Check every band the equipment can operate on, from 2200m through 1mm, plus Satellite. This is used when assigning radios to stations.
Equipment Photo: Upload a PNG or JPEG (up to 5 MB) so people can visually identify the gear on-site.
Club Equipment
Admins and event managers can click Add Club Equipment (visible on both the My Equipment page and under Equipment > Club Equipment) for gear that belongs to the club rather than any individual member. Operators won't see this button. The form is the same as personal equipment except there's no owner field. Instead there's an optional Managed By field to assign a specific person to be responsible for it. Club equipment has its own dedicated listing page where you can filter by type and status.
Equipment Catalog
Station captains, event managers, and admins can go to Equipment > Equipment Catalog to see every piece of equipment in the system across all members, filterable by owner, type, and status. Event managers and admins (anyone with edit-any-equipment) also get an Add Equipment for Owner button, so they can add gear directly to a member's catalog without logging in as that user, and a menu on each item to Edit it, Commit to Event, update a commitment's status or notes, or Delete it.
Committing to an Event
Committing equipment pledges it for an event. Gear you assign from the general catalog on a station's Equipment tab is committed for you. There are two commitment paths:
Operators commit their own gear directly from Equipment > My Equipment. Click the actions menu on any item and choose Commit to Event. A dialog asks which event to commit to, an expected delivery date, and optional delivery notes.
Admins commit club equipment from the Equipment Dashboard at Administration > Event Equipment. Click Commit Club Equipment to assign club gear to the event. Committed gear can then be assigned to specific stations on the station's Equipment tab.
Equipment Dashboard
The Equipment Dashboard (Administration > Event Equipment) tracks each item through its lifecycle: Committed (pledged for the event), Delivered (physically on-site), Returned (back with the owner after the event), or flagged with issues (Lost, Damaged, or Cancelled). Status cards at the top give a quick count across all items. You can view equipment in four groupings: Overview (all equipment in one table), By Owner, By Type, and By Station.
The Export button offers reports grouped by phase. Pre-event: Commitment Summary (CSV) and Delivery Checklist (PDF), Station Inventory (PDF and CSV). Post-event: Return Checklist (PDF) and Historical Record (CSV). Reference and incidents: Owner Contacts (PDF and CSV) and Incident Report (PDF and CSV).
Safety Checklists
Field Day awards a bonus for documenting site safety, and which one depends on your class. Class A gets the Safety Officer checklist and its 100-point bonus. Classes B through F get the Site Responsibilities checklist and its 50-point bonus. Winter Field Day doesn't have a safety bonus, so its classes don't get a checklist. Go to Event Management > Site Safety to work through it. The page shows a progress counter and lists every item with a checkbox. Work Through the Safety Checklist walks through it step by step.
The Default Checklists
The Safety Officer checklist has the 15 items from the ARRL rules, all required. Items cover the essentials you'd expect at a field site: safety officer on-site for the duration, fuel properly stored, fire extinguisher located, first aid kit on hand, CPR/AED-trained person present, NWS weather monitoring, tent stakes marked, antenna structures secured, tripping hazards cleared, site arranged to reduce hazards, stations and equipment grounded, access to police/fire/rescue, designated safety point of contact, minimizing risk to the public, and keeping everyone hydrated. The Site Responsibilities checklist has 13 similar items, 8 of them required, written for smaller setups where some items (a generator, a tent) may not apply.
Working Through the Checklist
To check off items, you must be assigned to a Safety Officer or Site Responsibilities shift for the event (scheduled, checked in, or checked out, but not marked as a no-show). The shift doesn't have to be running right now, so the safety officer can walk the site during setup. Field Day Commander records who completed each item and when, and the progress counter updates in real time. The bonus is awarded automatically: Safety Officer when every item is checked, Site Responsibilities when every required item is checked and more than half the list is done. Unchecking an item takes the bonus back. On a station-mode browser the checklist is read-only.
Customizing the Checklist
Go to Administration > Manage Safety Checklist to add, edit, or remove items. Click Add Item to create new entries. Each item has a Checklist Type (Safety Officer or Site Responsibilities) that sets which checklist it belongs to. If your club has additional safety requirements beyond the ARRL defaults (like generator exhaust ventilation or lightning grounding), add them here.
Contact Logging
Operators log contacts under Logging > Log Contact. The station selection screen shows every station with its current status, the current operator's callsign, active band and mode, and running QSO count. An available station has a Select Station button. A station with an open session but no recent contacts shows as idle with a Take Over button, and a busy one shows In Use. A station that's been marked unavailable shows "Down" with the reason, and its button is disabled. To set up several stations logging into the shared log over your LAN, see the Multi-Station Logging how-to.
Starting a Session
After selecting a station, you choose the band, mode, and power in watts before the logging interface opens. The session bar has band and mode pickers for switching without leaving the logging screen. A switch ends the current session and starts a new one on the same station with the same power. Switching is refused while offline, if the station is unavailable, or if another non-GOTA station already uses that band and mode. GOTA stations are exempt from the conflict check. The rules allow only one transmitter per band and mode at a time, so if another station already has an active session on the same band and mode, Start Session won't start a new one and names the station that's using it. GOTA stations are the exception. Once a session is running, the logging header rechecks every 30 seconds and shows a warning if another station has since landed on the same band and mode. For GOTA stations, there's an additional option to mark the session as supervised (GOTA Coach present), which enables the 100-point coach bonus if 10 or more contacts are supervised. On a station-mode browser, the list is skipped and setup opens for that browser's station.
Making Contacts
The logging interface shows a sticky bar at the top with the station name, band, mode, power, and a live QSO counter. Next to the mode is an optional Sub-mode field for the specific flavor you're running (USB, FT8, RTTY, SSTV, and so on). It stays set between contacts. The entry field accepts the full exchange in one shot (callsign, class, section) with autocomplete suggestions as you type. Hit Enter to log. Below 1280px wide, the session bar uses two rows, with station, power, QSOs, and End Session above the band, mode, and sub-mode controls. End Session opens an in-app confirmation dialog. Open Advanced fields below the exchange box for Freq (MHz), RST sent, RST rcvd, Grid, Name, and Notes. Alt+A toggles the panel, and this device remembers the choice. With it open, Tab from the exchange box moves through the fields in that order. Shift+Tab from Freq (MHz) returns to the exchange box. Enter logs or saves a recalled edit, and Esc returns to the exchange box. Frequency stays filled between contacts and across a switch if it fits the new band. The other fields clear after each contact. Frequency, reports, grid, and name appear in Details, or on the contact card line on phones. Up-arrow recall loads the advanced fields for editing too. A frequency on another band blocks logging and offers a button such as Switch to 40m. Enter switches and logs the entry, including its advanced fields. If validation fails on the new band, the entry stays with an error. Esc returns without switching.
Dupe checks run in real time against every contact logged by every station, so you'll see an immediate warning if the callsign has already been worked on the same band and mode. You'll also get a warning if the callsign belongs to one of your own participants (the event callsign, the GOTA callsign, or anyone operating or signed up for a shift), since contacts with your own people don't count. Neither warning blocks the contact. A class from the wrong rulebook does: Field Day events accept classes A through F and Winter Field Day events accept H, I, O, and M, and anything else is rejected with "Class X is not valid for this event." If a contact fails to sync, it appears in a failed contacts dropdown in the header with a retry button.
On a desktop screen, a Recent QSOs list appears above the entry field. It shows this session's contacts, oldest at the top, numbered from 1, and scrolls to the newest as you log. Click a row (or arrow to it) to pull that contact back up for editing.
Use Alt+B or Alt+M to focus the band or mode picker, arrow keys to choose, Enter to switch, and Esc to cancel. Mouse or touch selections switch immediately. Typing a band or mode alone in the exchange box and pressing Enter also switches: "40M" or "40", "CW", "PH" or "SSB", "DIG", or a pair such as "20M PH". After a switch, up to 20 recent contacts from the chain of earlier sessions appear greyed out and read-only, under dividers such as "40m Phone · 21:52". The current session divider is highlighted. Earlier contacts cannot be recalled, edited, or deleted here. Use Logging > View Log to edit or delete them. Starting fresh after End Session or from Station Select shows an empty log. Contacts waiting to sync keep their original session when you switch. All contacts go into a shared database, and Laravel Reverb pushes each new one over WebSocket to every connected browser. The scoring page, section map, and dashboard widgets all reflect new contacts instantly.
GOTA Operator Tracking
On a GOTA station, the logging interface shows additional fields to identify the operator making the contact: search for a registered user by name or callsign, or manually enter a first name, last name, and callsign for unregistered visitors. This attaches the GOTA operator to each contact for reporting purposes. GOTA Operator and the session's Supervised Session (GOTA Coach present) setting carry over through a band or mode switch. The operator does not carry over into a fresh session. A GOTA contact can't be logged until a GOTA operator is entered, either a linked user or a first and last name. The same rule applies to paper log transcription for the GOTA station. Contacts that reach the GOTA station from an external logger or an ADIF import count as GOTA contacts, but they aren't tied to a GOTA operator. For setting up and scoring the GOTA station, see the GOTA Station how-to.
Browsing the Logbook
Go to Logging > View Log to open the Logbook Browser. Stats at the top show running totals: total QSOs, total points, unique sections worked, QSOs by mode, and QSOs by band. Below that, a full set of filters lets you slice the log by band, mode, station, logger, ARRL section, callsign, time range, duplicate status (all, exclude dupes, dupes only), and whether the contact was transcribed from paper. The contact table shows QSO time (UTC), callsign, band, mode (with the sub-mode, like "Digital · FT8"), class, section, points, station, and the logger who entered it. On Winter Field Day 2027 events, contacts that earn nothing get a red no credit badge, and hovering it says why (see Winter Field Day). Users who can edit contacts can select rows and use Change Logger or Delete on all of them at once. Use the Export CSV button to download the filtered log.
Post-Event Editing
After the event, operators with the right permissions can edit contacts to fix exchange errors or delete accidental entries. There's a configurable grace period (default: 30 days) during which late contacts can still be added. This is useful for transcribing paper logs (see Paper Log Transcription).
External Logger Integration
Field Day Commander can share the event log with N3FJP contest logs over TCP, receive contacts from external software over UDP, and import ADIF files after the fact. Operators running N3FJP, N1MM Logger+, digital-mode programs like WSJT-X and fldigi, or any other program that outputs ADIF don't need to double-log their contacts. That software handles the radio side and Field Day Commander handles scoring, deduplication, and Cabrillo export. All of this is optional: stations without external software log directly in Field Day Commander.
Contacts from external loggers keep frequency, sent and received reports, grid, name, and comment when supplied. Frequency, reports, grid, and name appear in Details, or on the card line on phones. These fields are exported like browser-logged fields. ADIF-based loggers also preserve other record fields for ADIF export. All listener settings are found under Logging > External Loggers. Each listener can be enabled or disabled independently, and its port is configurable.
N1MM Logger+
N1MM Logger+ can broadcast contact data over UDP. Field Day Commander listens for these broadcasts and creates contacts automatically. To set it up:
- In N1MM+, go to Config > Configure Ports > Broadcast Data.
- Check the Contacts and Radio checkboxes.
- Ensure the server's firewall allows inbound UDP on the configured port (default: 12060). For example:
sudo ufw allow 12060/udp - Set the destination IP to the Field Day Commander server's address with the configured port.
- Optionally, enter each logging PC's computer name in its station's Hostname (NetBIOS Name) field on the Stations page for automatic station matching.
The listener shows live stats: packets received, errors, and uptime. You can expand "Last Contact Received" to see the most recent contact data. When an operator edits or deletes a contact in N1MM+, the change carries over to Field Day Commander. Edits and deletes from N1MM and N3FJP are recorded in the audit log with the sending PC and its IP address.
N3FJP
Field Day Commander can act as the network server for N3FJP's ARRL Field Day Contest Log and Winter Field Day Contest Log. Each N3FJP PC connects as a client instead of connecting to another PC running as the N3FJP server. To set it up:
- Under Logging > External Loggers, turn on the N3FJP card. The TCP Port defaults to 1000.
- In N3FJP, open Settings > Network (or the top-level Network menu), choose TCP networking as a client, and check Enable Status / Chat Functions.
- Set Server Name or IP to the Field Day Commander server's IP and use the same TCP port.
- Allow inbound TCP on that port through the server's firewall. For the default port:
sudo ufw allow 1000/tcp.
The card shows the port the server is listening on and how many PCs are connected. Each PC downloads the whole event log when it connects. Contacts logged in either program reach every connected N3FJP log within about a second, so dupe checks include contacts from the other stations. Edits and deletes go both ways. N3FJP chat works between the PCs, and Field Day Commander's operating stations appear in N3FJP's band status grid. Clock sync requests are ignored.
For the full setup, see Connect N3FJP Contest Logs.
WSJT-X / JTDX
WSJT-X and JTDX can send logged QSOs as ADIF records over UDP. This is ideal for FT8, FT4, JT65, and other digital modes where WSJT-X handles the decoding and the operator logs contacts from within WSJT-X. To set it up:
- In WSJT-X, go to File > Settings > Reporting > UDP Server.
- Set the UDP server address to the Field Day Commander server's IP and port (default: 2237).
- Use the server's regular IP address, not a multicast address.
- Set Settings > Reporting > Op Call to the operator's callsign so contacts are credited to them.
- For Field Day events, turn on Settings > Advanced > Special operating activity > ARRL Field Day so the class and section are logged.
- Contacts are matched to a station by the station callsign (My Call), so give the receiving station's name or hostname that callsign on the Stations page.
- Ensure the server's firewall allows inbound UDP on the configured port. For example:
sudo ufw allow 2237/udp
Generic UDP ADIF (fldigi, etc.)
For any application that can send plain ADIF text over UDP, Field Day Commander provides a generic ADIF listener (default port: 2238). This works with fldigi and any other program that supports ADIF UDP output. To set it up:
- Configure the application to send ADIF records via UDP.
- Set the destination to the Field Day Commander server's IP and the configured port.
- In fldigi specifically: Configure > Config Dialog > Logging/Cloud-UDP, then set the address and port in the Broadcast UDP ADIF record group and check Enable.
- Contacts are matched to a station by the station callsign (fldigi's Station Callsign), so give the receiving station's name or hostname that callsign on the Stations page.
- Ensure the server's firewall allows inbound UDP on the configured port. For example:
sudo ufw allow 2238/udp
For a step-by-step walkthrough, including firewall setup, operator credit, and testing, see Connect External Loggers.
ADIF File Import
If you have contacts in an ADIF file (from a previous logging session, a backup, or another program), you can import them through a three-step wizard. Click Import ADIF at the top of the Logging > External Loggers page.
- Step 1: Upload. Select your .adi or .adif file and click Parse & Continue. Field Day Commander reads the file and shows a summary: record count, date range, bands, and modes.
- Step 2: Map Fields. If the ADIF file contains station identifiers that don't match your configured stations, you'll see them listed under "Unmapped Stations" with a dropdown to assign each one to an event station.
- Step 3: Review & Import. Every record is shown in a table with its status: New, Merge Candidate, Skipped, or Invalid. Records outside the event time window are flagged as invalid with an explanation. You can skip individual records before importing. A summary at the top shows counts for each category.
ADIF import keeps frequency, reports, grid, name, and comment, plus other record fields for ADIF export, including MY_GRIDSQUARE, TX_PWR, QSO_DATE_OFF, TIME_OFF, and APP_ fields. Merging into an existing contact fills only empty fields. The import is non-destructive. You review everything before any contacts are written to the database, and invalid records must be resolved (skipped or fixed) before the import can proceed.
Every listener and the import record the ADIF sub-mode (FT8, USB, and so on) along with the mode, and they apply the event's rulebook the same way live logging does. On a Winter Field Day 2027 event that means WSJT-mode and satellite contacts come in with no credit.
Scoring
The scoring page (Event Management > Scoring) shows your live score using the formula for your event's rulebook. Field Day events use the ARRL Field Day formula below. Winter Field Day scores differently, with objectives instead of bonus points (see Winter Field Day).
QSO points are weighted by mode: CW and digital contacts are worth 2 points each, phone contacts are worth 1. Power multiplier is determined automatically from your configured power sources (5x for ≤5W natural power, 2x for ≤5W or 6-100W with commercial/generator, 1x for over 100W). Bonus points come from the 18 bonus categories in the ARRL rules (7.3.1 through 7.3.18). The GOTA bonus is one of them, but it's added after the power multiplier: 5 points per GOTA contact, plus a 100-point coach bonus if 10 or more contacts are supervised.
Bonus Categories
The scoring page lists all 18 categories with their status: verified, claimed, or unclaimed. Some bonuses are tracked automatically (like the safety checklist or the visitor guestbook). Others are claimed manually by the event manager (like media publicity or the educational activity). Availability depends on your entry class.
| Bonus | Points | Tracking |
|---|---|---|
| Emergency Power | 100/transmitter (max 2,000) | Based on configured power sources |
| Media Publicity | 100 | Manual claim |
| Public Location | 100 | Manual claim |
| Information Booth | 100 | Manual claim |
| Section Manager Message | 100 | Automatic (NTS message tracking) |
| NTS Messages Handled | 10 each (max 100) | Automatic (per radiogram logged) |
| Satellite QSO | 100 | Automatic from a logged satellite contact (Classes A, B, F) |
| Natural Power QSOs | 100 | Manual claim |
| W1AW Field Day Bulletin | 100 | Automatic (W1AW Bulletin page) |
| Educational Activity | 100 | Manual claim |
| Elected Official Visit | 100 | Automatic (guestbook visitor category) |
| Served Agency Visit | 100 | Automatic (guestbook visitor category) |
| GOTA Bonus | 5 per GOTA QSO, plus 100 for a coach | Automatic (GOTA contacts and supervised sessions) |
| Web Submission | 50 | Manual claim |
| Youth Participation | 20 each (max 100) | Automatic (youth accounts) + manual entry |
| Social Media | 100 | Manual claim |
| Safety Officer | 100 | Automatic from the Safety Officer checklist (Classes A, F) |
| Site Responsibilities | 50 | Automatic from the Site Responsibilities checklist (Classes B, C, D, E, F) |
Manual Claims
Bonuses that Field Day Commander can't track automatically are claimed on the event's detail page (Administration > Events, then View Details from the event's Actions menu) in the Manual Bonus Claims card. Event managers and admins (anyone with verify-bonuses) can use it. Checking a box claims and verifies the bonus in one step, and bonuses that can be earned more than once have a Count field. For planning tips and what proof each bonus needs, see Plan Your Bonuses and Objectives.
Rules Versions
Each event is scored by a specific rule year, set with Scoring Rules on the event form. Field Day Commander ships ARRL Field Day 2025 and 2026 (identical rules) and Winter Field Day 2026 and 2027. The footer of the scoring page says which version the event is using. A Corrections & Notices box at the bottom flags things worth a look before you submit, like a high dupe rate or claims that haven't been verified.
Winter Field Day
Winter Field Day events get their own rulebook, picked automatically from the event type. The WFD 2026 rules follow the WFDA's 2026 SOP, and WFD 2027 follows the 2027 rules (Version 3). Most of the app works the same as for Field Day. The differences are in the exchange, the scoring, and what you submit.
QSO points are the same as Field Day: 1 for phone, 2 for CW and digital. OM is the objective multiplier, the sum of the multipliers for every objective you've earned. The +1 means a station that earns no objectives still scores its QSO points. There's no power multiplier, no GOTA station, and no bonus points, and every station is capped at 100 W PEP. The scoring page shows two columns instead of three and an Objectives Completed progress bar, since the WFDA tracks completion from year to year.
Classes and Exchange
The class is the number of transmitters you can run at once (and have operators for) plus a category letter: H (Home), I (Indoor), O (Outdoor), or M (Mobile). The exchange looks like "2O EPA". US and Canadian stations send their ARRL/RAC section, stations in Mexico send MX, and everyone else sends DX. On WFD events, MX and YT (Yukon) count as sections of their own. The event form's WFD rules: class, category and location panel covers the rest: class, category, and location stay fixed for the whole event, everything has to fit in a 300 m circle, and remote operation isn't allowed. Setup opens 24 hours before the start.
Objectives
WFD 2027 has 13 objectives worth up to 34 in total. Field Day Commander earns five of them for you from the log and the bulletin page. The rest you claim on the event's detail page, in the Manual Objective Claims card (see Manual Claims for how to get there).
| Objective | OM | Tracking |
|---|---|---|
| Station Equipment on Alternative Power | x1 | Manual claim (earned too when you claim 100% alternative power) |
| Operate 100% on Alternative Power | x2 | Manual claim |
| Operate Away From Home | x3 | Manual claim |
| Deploy Multiple Antennas | x1 | Manual claim |
| Send and Receive the WFD SSTV Image | x2 | Manual claim |
| Cross-Band Repeater Contacts | x3 | Manual claim |
| Send and Receive a Winlink Email | x1 | Manual claim |
| Copy the WFD Bulletin | x1 | Automatic (saved on the WFD Bulletin page) |
| Three Contacts on Six Bands | x6 | Automatic (satellite doesn't count) |
| Three Contacts on Twelve Bands | x6 | Automatic |
| Use Multiple Modes | x2 | Automatic (two of CW, Phone, Digital) |
| Operate the Event QRP | x4 | Automatic (every contact at 10 W or less on phone, 5 W or less on CW and digital) |
| Operate Six Continuous Hours | x2 | Manual claim |
WFD 2026 events use the 2026 list instead: 12 objectives worth up to 32, including the two satellite objectives that were dropped for 2027. Each objective has a ? icon on the scoring page that expands the WFDA rule text.
No-Credit Contacts
WFD 2027 doesn't allow WSJT modes (FT8, FT4, JT65, Q65, and the rest of the family), and satellite contacts earn nothing. Field Day Commander decides this from the contact's sub-mode, so log the sub-mode when you can. JTTY is allowed and counts as digital. These contacts are still accepted from every source and kept in the log, but they score 0 points, count toward no objective, and are left out of the Cabrillo and ADIF exports. The logbook marks them with a no credit badge, and the scoring page shows a No Credit count.
What Else Changes
The bulletin page becomes the WFD Bulletin (WFD Special Bulletin for 2026), and saving a copy earns its objective. Message traffic isn't scored, so the message page tracks radiograms for your records only. At the end, the Reports page gives you a WFDA-format Cabrillo log and a Winter Field Day Summary (PDF) in place of the ARRL submission sheet (see Reports).
Section Map
The Section Map is an interactive visualization of the ARRL and RAC sections across the United States and Canada: 71 US sections including territories, plus the Canadian RAC sections. On Field Day events that's 85 sections, with Yukon counted as part of TER. Winter Field Day treats YT as its own section, so the map draws Yukon separately and shows 86. DX contacts (and MX, which counts as DX for Field Day and as its own section for Winter Field Day) are scored normally but do not appear on the map. As contacts are logged, sections light up on the map in real time. It's accessible from the main sidebar under Section Map.
Region Filters
Across the top of the map, a row of filter buttons lets you focus on a specific region: All, US, Canada, or individual call areas (W1 through W0). Selecting a call area zooms the view and dims sections outside that area so you can quickly see which sections within a region you've worked and which you still need.
Color Modes
Three color modes control how sections are shaded:
- Band. Each section is colored by the band on which it was most recently worked (20m, 40m, 80m, etc.), using the band color from the legend. Color intensity indicates depth: pastel means 1 band, vivid means 2 bands, and deep means 3 or more bands have been worked in that section.
- QSO Count. A green heat map where darker sections have more contacts. Useful for spotting which areas are producing the most activity.
- Recency. A red-yellow-green scale based on how recently each section was last worked. Green means the contact is fresh, yellow means it's aging, and red means it's been a while. This helps operators see where activity is happening right now versus earlier in the event.
Section Details
Hover over any worked section to see a tooltip with the section name and abbreviation, total QSO count, bands and modes worked, and how long ago the last contact was made.
Using It During the Event
The Section Map works well on a big screen at the Field Day site. It gives the whole club a visual sense of progress without needing to read a log table. Operators can glance at the map to see which call areas have gaps, and station captains can use it to guide band and direction strategy.
Visitor Guestbook
Field Day is a public event, and the ARRL awards bonus points for public outreach. The guestbook (Guestbook in the sidebar) makes it easy to track who stopped by. It can check a visitor's location to mark them as in-person, and it categorizes guests for cleaner reporting after the event.
How It Works
The guestbook page is designed to be handed to a visitor on a tablet. It shows a friendly welcome message and a simple form. No account, no password, no friction. During an active event, visitors fill it out and tap submit. When the event isn't running, the page shows a "No Active Event" notice so nobody signs a stale book.
The form collects the following information:
- Name (required). The only mandatory field.
- Callsign (optional).
- Email (optional). Useful for follow-up or club outreach after the event.
- I am visiting as. A dropdown with eight options: General Public, Ham Club Member, Youth, ARES/RACES, Media, Agency (FEMA, etc.), ARRL Official, and Elected Official. This helps with reporting, and Elected Official and Agency visits count toward their bonuses automatically once you verify them.
- Comments (optional). A free-text area for anything the visitor wants to say.
The form also asks How are you visiting?, where the visitor chooses In Person or Online. The system pre-selects this based on the location check (see below), but the visitor can change it. This distinction shows up in the guestbook management table so you can see at a glance who was physically present.
Setting Up the Guestbook
Guestbook settings live inside the event configuration. Go to Event Management > Edit Event. The coordinates used for proximity detection are set in the Event Location section (latitude and longitude are required for this feature to work). Scroll further down to the Guestbook Settings section, which has three settings:
1. Enable the guestbook. Toggle the "Enable Guestbook" switch to on. The description reads "Allow visitors to sign in when physically at your event location." When this is off, the guestbook page shows a "No Active Event" notice.
2. Set the detection radius. A slider lets you choose how far from your coordinates a visitor can be and still count as "in-person." The range is 100 to 2,000 meters. The current value displays in both metric and imperial (for example, "500m (1,640 feet)"). If your Field Day site covers a large park or fairground, increase the radius. For a smaller backyard setup, bring it down.
3. Add local subnets (optional). If you have a known network at your site, you can enter one or more subnets in CIDR notation, one per line. For example, 192.168.1.0/24 or 10.0.0.0/8. The location check doesn't currently use them, so they won't mark anyone as in-person.
Location-Based Check-In
When a visitor opens the guestbook page, the system tries to determine whether they are physically at your event site. It does this with browser geolocation.
The page asks the visitor's browser for their GPS coordinates using the standard Geolocation API. If the visitor allows the location prompt and their device has GPS (most phones do), the system compares the visitor's coordinates against the event coordinates you configured. It calculates the distance using the Haversine formula (great-circle distance on the Earth's surface). If the visitor is within the detection radius, they pass the check and are marked "in-person."
If the check fails or the location isn't available, the visitor can still sign the guestbook. They're recorded as "online" rather than "in-person."
HTTPS and the Location Feature
There is an important caveat with browser geolocation: modern browsers require HTTPS to use the Geolocation API. On a plain HTTP connection, the browser will silently block the location request without even showing a permission prompt. The visitor's form will still work, but the GPS check will never fire, and everyone will be marked "online."
This matters because Field Day Commander is a LAN-hosted application and many Field Day setups run it over plain HTTP on a local IP address (like http://192.168.1.50). In that scenario, the GPS-based location check will not function at all. Visitors signing the guestbook on their own phones will never get a location prompt, and the system will mark them as "online."
If you want GPS-based location detection to work, serve Field Day Commander over HTTPS with a certificate the browser trusts. Over plain HTTP, visitors at your site can switch How are you visiting? to In Person themselves.
Managing Entries
Event managers and admins can view and manage all entries under Administration > Manage Guestbook. Cards at the top count total, verified, in-person, online, and bonus-eligible visitors. Each entry shows the visitor's name, callsign (if provided), category, presence type, and timestamp, and you can filter by presence, category, and verification status. Select rows to Verify, Unverify, or Delete them in bulk, or edit an entry to fix its category and Mark as Verified. Only Elected Official and Agency visits are bonus eligible. A media visit doesn't earn the Media Publicity bonus on its own, so claim that one by hand.
Export CSV downloads the entries that match your current filters, with name, callsign, email, category, presence, verification, and sign-in time. Handy for the club's follow-up emails after the event.
Weather
The weather page (Weather in the sidebar) shows live conditions and forecasts for your Field Day site. It requires latitude and longitude to be set in your event configuration. Data comes from two sources: Open-Meteo for forecasts and current conditions, and NWS (National Weather Service) for official weather alerts. Both are fetched automatically with no API key required.
Weather Dashboard
The page shows current conditions (temperature, wind speed and direction, gusts), an hourly table for the next 12 hours, and a multi-day daily forecast. Active alerts, both NWS and any local alert an admin has posted, appear in a banner that stays pinned below the header on every page. If an admin has entered a manual override, a notice indicates who entered it and when. The data source and last-updated time are shown at the bottom.
Managing Weather
Users with the manage-weather permission can access Administration > Manage Weather, which has four sections:
Unit System. Switch between metric and imperial. This affects all temperature and wind displays site-wide.
Weather Sources. Shows the connection status for Open-Meteo and NWS. Both sources require the server to have internet access. Open-Meteo forecast polling and NWS alert polling each have their own on/off toggle. When enabled, you can filter which NWS event types are shown (e.g. hide watch-level alerts and only show warnings). Disabling NWS clears stored NWS alerts but preserves any manual alerts you've entered.
Manual Forecast Override. If your site has no internet access, you can enter conditions manually: temperature, wind speed, wind direction, rain chance, and optional notes. The dashboard shows the override data with a notice that it was manually entered. Clear the override at any time to return to live data.
Local Alerts. Local alerts work without internet access. Post a local alert that broadcasts immediately to all connected users as a prominent banner. The NWS won't tell you how far away the lightning is, so this is how the safety officer calls everyone in. Two quick buttons, Lightning < 15 mi and Lightning < 10 mi, send ready-made warnings. Pressing one replaces the current local alert, so you can escalate or step down. For anything else, type a Custom Alert Message and click Post Local Alert. Local alerts and NWS alerts show side by side, and neither replaces the other. Clear Local Alert lifts yours and leaves any NWS alerts in place. The panel also has a How to monitor for lightning guide with apps, detectors, and the flash-to-bang count.
NTS Messages / Message Traffic
The National Traffic System (NTS) bonus awards 10 points for every radiogram your station handles during the event, up to a maximum of 100 points. Field Day Commander tracks three types: originated, relayed, and received & delivered. Originated and relayed messages count once you mark them sent, and received messages count as soon as you log them. Find this page under Message Traffic in the Event Management section of the sidebar.
Winter Field Day awards nothing for message traffic. On WFD events the page says so, the point tallies are gone, and messages are tracked for your records only.
Logging Messages
Click Log Message to record each radiogram with its type and details. On Field Day events, the running count and point total show at the top of the page alongside the SM/SEC and W1AW tallies.
Section Manager Message
On Field Day events, the Section Manager/SEC message bonus (100 points) has its own button on the page: SM/SEC Message. Send a formal message to your ARRL Section Manager or Section Emergency Coordinator from the event site via amateur radio RF during Field Day to claim it. This is tracked separately from the per-radiogram bonus.
ICS-213 Support
If your group practices ARES/RACES emergency communications, Field Day Commander also supports the ICS-213 General Message format. Enable it under System Settings > System Preferences > Enable ICS-213 Message Format to get the standardized form alongside the traditional radiogram format.
W1AW and WFD Bulletins
Both Field Day and Winter Field Day reward copying a special bulletin off the air, and each has its own page in the sidebar while an event is active. The menu item is named for your event's rulebook: W1AW Bulletin for Field Day, WFD Bulletin for Winter Field Day 2027, and WFD Special Bulletin for 2026. For Field Day, W1AW (and K6KPH on the West Coast) transmit the bulletin on the regular W1AW frequencies, and copying it earns 100 bonus points. For Winter Field Day, copying the bulletin earns its objective (OM x1). Either way, the credit comes automatically when you save the copy.
Transmission Schedule
The top of the page shows a transmission schedule so your team knows exactly when to listen, with a countdown to the next one. Each entry lists the Time (UTC), Mode, Frequencies (MHz), and Source. Station captains, event managers, and admins use the Add Transmission form to build out the schedule from the published times. For Field Day the source is W1AW or K6KPH. For Winter Field Day you type in the sending callsign. Everyone gets a reminder 15 minutes before each transmission, and each user can change the timing (up to five reminders) under Bulletin transmission reminders on their profile.
Bulletin Details
When someone copies the bulletin, fill in the Frequency (MHz) you received it on, the Mode, and the Received At (UTC) timestamp. Paste the full text of the bulletin into the Bulletin Text field and click Save Bulletin. Any operator who can log contacts can save it. The bulletin must be copied over the air. It won't appear on Internet bulletins or BBS sites. An accurate copy is required as proof, so Field Day Commander prints it on its own page in the ARRL Submission Sheet or the Winter Field Day Summary.
Photos
The photo gallery (Event Management > Gallery) gives your group a shared place to collect pictures during the event. Photos are organized into event albums automatically. Each event gets its own album with a cover thumbnail, date, and photo count.
Uploading
Any logged-in user can click Upload Photo from the gallery page or snap a picture directly from a phone browser (except on a station-mode browser). Everything is stored on the local server with no cloud dependency, so uploads work even at sites with no internet. Upload JPEG, PNG, GIF, or WebP images up to 25 MB each. Each photo is tagged with who uploaded it and when. Uploaders can delete their own photos, and event managers and admins can delete any.
After the Event
The gallery persists after the event ends, so you can browse photos later and grab a whole album as a download (Download on the album card, or Download Album inside it) for your club newsletter, social media, or the ARRL Field Day submission page. Album downloads are prepared as ZIP files, and download links expire after 24 hours. Photos from previous events stay in their own albums and don't clutter the current one.
Reports
When the event wraps up, go to Reports in the Administration section of the sidebar. Event managers and admins (anyone with view-reports) can open it. The Export & Download cards depend on the event type: every event gets Cabrillo Log, ADIF Log, and Logbook CSV, plus Submission Sheet for Field Day or Winter Field Day Summary (PDF) for Winter Field Day. Duplicates and no-credit contacts are left out of the Cabrillo and ADIF files, and contacts you transcribed from paper are included. For a step-by-step walkthrough, see Submit Your Field Day Entry.
Cabrillo Log
Field Day Commander pulls together every QSO across all stations and writes a Cabrillo file in the format your event needs. For Field Day, that's the ARRL format with your callsign, class, section, category lines, claimed score, and every contact, saved as CALLSIGN-YEAR-field-day.log and ready to upload to the ARRL Field Day submission page. For Winter Field Day, it's the WFDA format (contest WFD, your location, power category, operators, and exchange), saved as CALLSIGN.log as the WFDA asks, for upload at winterfieldday.org. Below 1 GHz, QSO lines use the logged frequency in kHz when available, otherwise the band frequency. Bands above 1.2 GHz use the Cabrillo GHz designators (2.3G, 10G, and so on).
ADIF Log
Downloads an ADIF 3.1.4 file (CALLSIGN.adi) of every credited, non-duplicate contact, with band, mode, sub-mode, class, section, station callsign, and operator. When logged, frequency, reports, grid, name, and notes are included as FREQ, RST_SENT, RST_RCVD, GRIDSQUARE, NAME, and COMMENT. Other preserved ADIF fields are included too. Values held in Field Day Commander take precedence over the original record. Reports such as "5NN" that do not fit the app's fields are preserved for export. Use it to import the log into other logging software.
ARRL Submission Sheet
Field Day events only. Downloads a PDF formatted to the official ARRL Field Day submission sheet. It has your entry information, power sources, bonus claims, claimed score, and a band and mode breakdown, plus a GOTA page if you ran a GOTA station. If you saved a W1AW bulletin copy, it gets its own page. Useful as a backup record even if you submit electronically.
Winter Field Day Summary
Winter Field Day events only. Downloads a PDF that mirrors the WFDA summary form: your station details, the objectives checklist with each OM, your QSO point totals, and the final score worked out as QSO points x (OM + 1). A second page has the bulletin copy if you saved one.
Logbook CSV
Downloads a spreadsheet of all contacts in the logbook, with time, callsign, band, mode, section, class, points, dupe status, logger, and station. Useful for post-event analysis or sharing with club members.
On-Page Reports
Below the downloads, the page shows QSO Rate by Hour broken out by mode, Contacts by Logger with each logger's non-dupe QSOs, total logged contacts, and dupes, the Sections Worked grid, and Volunteer Hours. Volunteer Hours opens with totals for hours worked, hours scheduled, and number of volunteers. A setting under System Settings > System Preferences decides whether overlapping shifts count once (wall-clock hours) or once per shift, including overlapping time.
Audit Logs
The Audit Logs page (Administration > Audit Logs) is a record of every significant action taken in the system. Anyone with the view-security-logs permission can open it, which by default means event managers and admins.
Each log entry shows the timestamp, the user who performed the action, the action type, and the IP address. Clicking an entry opens a detail modal with the full context, including any changes made. Critical security events are flagged with a warning indicator.
You can filter the log by user, action type, date range, or IP address. Quick-filter buttons let you jump to the last 24 hours, last 7 days, or last 30 days. Results are paginated with 25, 50, 100, or 250 entries per page. The full filtered set can be downloaded as a CSV via the Export CSV button.
Offline Resilience
Field Day Commander has two layers of resilience. First, the entire platform runs on your LAN and doesn't need the internet. Weather is the only feature that uses it, and only if you turn it on. Second, if a browser temporarily loses its connection to the server (someone trips over the ethernet cable, Wi-Fi drops out), contacts will queue locally on the device. When the connection comes back, they'll sync automatically. A status indicator shows how many contacts are queued and when they've been synced.
Paper Log Transcription
If the server goes down and you fall back to paper for a while, Field Day Commander has a transcription feature that lets you enter those contacts after the fact with the correct timestamps. This way nothing is lost and your Cabrillo export stays complete. There is a configurable post-event grace period (default: 30 days) during which operators can still enter late contacts.
Go to Logging > Transcribe Paper Log, pick the station, and set the date (in UTC or local time). Then type each line the way it's written on the sheet, time first: "1423 W1AW 3A CT". There's an optional Sub-mode field, and the same dupe, own-participant, and class checks as live logging apply. A Recently Transcribed list shows what you've entered for that station so you can spot a skipped line.
Network Setup
Field Day Commander runs on your local network. Operators connect by opening the server's address in any web browser. A typical field setup looks like this:
Server
A Raspberry Pi, laptop, or any Linux box connected to your field network via ethernet. Runs FrankenPHP on port 80 (or 443 with SSL). Laravel Reverb (WebSocket) runs on the same box and is reached through the web port, so browsers only ever talk to port 80 or 443.
Network
A router or access point providing your field LAN. Can be Wi-Fi, ethernet, or both. No internet connection needed.
Client Devices
Any device with a web browser: laptops, tablets, phones. Windows, Mac, Linux, Android, iOS. Connect to the field network and open the server's address.
sudo ufw allow 1000/tcp.
Email is entirely optional. By default, Field Day Commander detects that no mail transport is configured and hides every email-related feature from the UI. Admins set passwords manually, and operators manage their shifts through the web interface. Nobody sees broken links or grayed-out options.
When email is configured, five features appear automatically: the "Forgot password?" link on the login page, a "Send password reset email" option in the admin panel, a "Send invitation email" checkbox when creating users, an "Email Notifications" section on user profiles (security alerts, event notifications, system announcements), and an "Email shift reminders" toggle on user profiles.
Enabling Email
Set MAIL_MAILER to a real transport (like smtp) in your .env file and provide SMTP credentials:
Then clear the config cache:
The email features will appear on the next page load. To disable them again, set MAIL_MAILER=log and re-run the cache command.
MAIL_MAILER value. If it's log or array (the defaults), all email features are disabled and hidden. Any real transport enables them. A backend guard in ReminderService also prevents email sends even if a preference is set in the database while email is unconfigured.
For a detailed walkthrough with provider-specific settings (Gmail, SES, Mailgun), see the Email Setup how-to guide.
Docker
Field Day Commander includes a Docker Compose setup for containerized deployment. The stack runs three services: an application container (web server, WebSockets, queue worker, scheduler), a MySQL 8.4 database container, and a Redis container for cache, sessions, and the job queue.
Quick Start
The setup script creates .env from .env.example and generates all secrets, including APP_KEY, DB_PASSWORD, and REVERB_APP_KEY. Run it again on an existing .env to fill in any missing secrets without overwriting existing values. The app will be available at http://localhost (or whichever port you set with APP_PORT). Log in as described in First Event Setup.
Configuration
These environment variables in .env are used by docker-compose.yml:
| Variable | Default | Description |
|---|---|---|
| APP_KEY | (required) | Encryption key, generated by setup.sh. Two-factor secrets are encrypted with it, so keep a copy with your backups |
| APP_PORT | 80 | Host port mapped to the container's port 8000 |
| DB_DATABASE | fd_commander | MySQL database name |
| DB_USERNAME | fd_commander | MySQL user |
| DB_PASSWORD | (required) | MySQL password (auto-generated by setup.sh) |
| DB_ROOT_PASSWORD | rootsecret | MySQL root password |
| N1MM_PORT, WSJTX_PORT, UDP_ADIF_PORT, N3FJP_PORT | 12060, 2237, 2238 (UDP), 1000 (TCP) | Published Docker ports for the external loggers. N3FJP_PORT publishes the N3FJP TCP server port |
| REDIS_MAXMEMORY | 256mb | Memory cap for Redis (setup.sh sizes it for your machine) |
To run on a custom port:
Architecture
The app container runs as the unprivileged www-data user (uid 33), not root. It runs four processes via supervisord:
| Process | Purpose |
|---|---|
| Octane (FrankenPHP) | HTTP server on port 8000 inside the container |
| Reverb | WebSocket server (port 8080, internal) |
| Queue Worker | Background job processing |
| Scheduler | Scheduled tasks (runs every 60s) |
WebSocket connections reach Reverb through Caddy's reverse proxy at the /app path, so the only TCP port exposed to the network is APP_PORT. The external logger UDP ports are published too.
First Run
On startup, the entrypoint checks that DB_PASSWORD and APP_KEY are set and refuses to start without them. If you see "ERROR: APP_KEY is not set.", run bash docker/setup.sh and then docker compose up -d again. It then waits for the database, runs all migrations, runs production seeders (event types, bands, modes, sections, roles, permissions, etc.), generates Reverb WebSocket credentials if not set, and caches configuration, routes, views, and events. Seeders only run once. A marker file in the persistent storage volume prevents re-seeding on subsequent starts.
Data Persistence
Three named volumes store persistent data:
| Volume | Contents |
|---|---|
| app-storage | Uploaded files, logs, framework cache |
| mysql-data | Database files |
| redis-data | Redis data |
These survive docker compose down. Use docker compose down -v to remove them (this destroys all data). To back them up, see Backups.
HTTPS with a Reverse Proxy
The container serves plain HTTP (port 8000 inside, APP_PORT on the host). For HTTPS, place a reverse proxy (like Nginx) in front of it. The app includes trustProxies(at: '*') so X-Forwarded-Proto and X-Forwarded-For headers are respected automatically. When behind a TLS proxy, update your .env:
Managing Services
Rebuilding After Updates
The entrypoint runs php artisan migrate --force on every start, so new migrations are applied automatically.
"<host>:80", change it to "<host>:8000". If the app stops with "is not writable by www-data (uid 33)", fix the storage volume's ownership with docker compose run --rm --no-deps -u root --entrypoint chown app -R www-data:www-data /app/storage, then docker compose up -d.
Backups
To protect your log, photos, and settings, run the backup script. Field Day Commander ships backup.sh and restore.sh in the install directory. Each backup writes three files with the same timestamp: the database, your uploaded files (photos, logo, equipment pictures), and a copy of .env. Keep the .env copy with the rest. It holds the APP_KEY that two-factor secrets are encrypted with, and without it anyone using 2FA is locked out after a restore.
Backups on the same SD card won't survive the card dying, so copy them somewhere else. restore.sh will take a fresh backup of the current data before it replaces anything, and with --new-server it can carry your APP_KEY over to a different machine. See Back Up and Restore for scheduling, copying backups off the server, and restoring onto the same server or a new one.
Updating
Field Day Commander includes an update.sh script that will pull the latest code, update dependencies, run new database migrations, and restart services. Run it as root from the directory you cloned and deployed from. It doesn't take a backup, so run backup.sh first.
If you're already current, it says so and stops. It also takes care of one-time housekeeping from older installs, like upgrading Node.js and FrankenPHP to the pinned versions. If Redis isn't installed yet, it offers to install it and switch the cache, sessions, and queue over (everyone has to sign in again once afterward).
| Flag | Default | Description |
|---|---|---|
| --tag | (none) | Deploy a specific release, like v26.10.6, instead of the latest code on the branch |
| --branch | main | Git branch to update from |
| --app-path | /var/www/fd-commander | Installation directory |
| --force | off | Run the full update even if nothing has changed |
| --with-redis | off | Install Redis and switch drivers without asking |
| --no-redis | off | Skip the Redis step and keep your current drivers |
Release Versions
Releases are numbered by year and month, YY.MM.N, where N counts releases within the month. For example, 26.10.6 is an October 2026 release, tagged v26.10.6. The running version is shown in the app's footer and at the end of every update. To see the available tags, run git tag --list 'v*' in your clone.
Run updates at home when preparing for the next event, not during the event itself.