Fireguy|Repeater Planner is a terrain-aware radio planning workspace for wildland incidents. The map is the reason the site exists: you place repeater sites, run coverage and links over real terrain, and keep those results with the fire. Kits, batteries, roster, and radio log are there when the assignment needs them — they are not required to plan a talk path.
Create an account with your name, email, and a password (at least eight characters, including a letter and a number). Confirm the email within a couple of days; login has a resend if the first message wandered off. You can also ask for a six-digit sign-in code instead of a password, which is handy when government mail filters eat links. Optional Google or Apple sign-in appears when the site offers it. Sessions stay open long enough for a multi-day radio watch; logout asks you to confirm before it drops you.
After you sign in you land on the Dashboard. That is the only place that creates incidents, and it is how you switch among the ones you can reach. Summary tiles roll up kits, battery alerts, and similar counts across those incidents; they stay quiet until you have an incident open and those modules turned on. My Incidents is every fire you already have access to — open a row to make it active. Open Incidents sits beside it on a wide screen (under it on a phone) and lists other Live fires you are not on yet; Join sends a request to the owner (and anyone who can accept join requests). “Pick up where you left off” jumps back into Mapping or the last ops pages you used. Create can import a WFIGS fire up front so the name, Incident ID, and map perimeter already have something to hang on.
New incidents start in mapping-only mode. You pick Test (default) or Live on create — Live stores as Open so others can ask to join from the Dashboard. You get Overview and the full map; Inventory, Batteries, People, and the rest stay out of the way until someone with access turns them on under Admin → Modules. That keeps a coverage assignment from feeling like a warehouse app.
Once an incident is active, the top nav grows. Mapping is the workspace — sites, coverage, and a drive to a pad. Incident opens Overview (or a module panel if field ops are enabled). Field Recorder appears when you can log reception tests. Admin holds Modules, Access (people and permissions), Integrations, and Presets for people who have those rights. Help is this guide — search the box above, or skim the Glossary when you just want a word defined.
Next: Map workspace and sites. If you already know the map and need a word, start at the Glossary.