Section 1
Quick start and essential concepts
Prepare for the first practice incident
- 1.Create your account and confirm your email when prompted. Sign in using the email address associated with your department invitation.
- 2.Create the department if you are its first owner, or join the existing department through an invitation. Confirm the active department before entering any data.
- 3.Configure organization lists, incident types, assignments, and defaults. Add at least one active roster member so an Incident Commander can be selected.
- 4.Choose a department plan, invite the app users who need access, and have them sign in on their devices. Selecting a plan starts the 14-day free trial and enables incident creation. Before selecting a plan, you can configure the department and load its roster. Complete this preparation first to make full use of the trial.
- 5.On an iPad, open Manage Incidents and select Start New. Use a clearly identified practice incident, choose the Incident Commander, and review its structure settings. The creating device becomes the primary board.
- 6.On the primary board, add personnel, form a group, update an assignment and location, and complete a practice PAR.
- 7.Open the same incident on a second device. Check live status, connected users, and a coordinated handoff. Finish by closing the practice incident and reviewing its report.
Know which record you are changing
- App user
- A person with an FGM login and a role in a department. App users consume the access capacity of a department plan.
- Roster member
- A saved firefighter/personnel profile that can be added to incidents. Creating one does not create a login or send an invitation.
- Incident member
- A person attached to one incident, with that incident's assignment, location, PAR status and history.
- Primary board
- The device authorized to make the main incident-board changes. Other connected boards receive synchronized information.
- Incident Commander
- The person designated to command the incident. This designation is separate from the device holding primary control.
Section 2
Accounts and the home screen
Create an account and sign in
- 1.Open Fireground Manager and choose the account creation option on the sign-in screen.
- 2.Enter your first name, last name, email address and password. For an invitation, use the exact invited email address.
- 3.Submit the form. If email confirmation is required, open the confirmation message and follow its instructions. Check junk mail if it does not arrive; use the resend confirmation option when available.
- 4.Return to FGM and sign in with your email and password. Review and accept the user agreements when presented before continuing. If department access is missing, choose Check for Department Access before creating a new department.
Use the home screen
| Department and account | Confirm the selected department, signed-in email and your department role. |
| Manage Incidents | Start a new incident, open an active incident, review history, find archived incidents, and access Reports when permitted. |
| Roster | Maintain the department's saved personnel records. Use filters to find home-department or mutual-aid members. |
| Settings | Open Department Setup, Incident Types and Defaults, Users & Access, department switching, and Sign Out. |
| Department Plan | Owners and administrators can review the department's plan, app-user capacity and available plan actions. |
Switch departments
- 1.On iPad, open Settings; on iPhone, open Account & Departments. Select the department-switching option in the Active Department area.
- 2.Select a department to which your account has access. If you belong to only one department, a switch option may not appear.
- 3.Confirm the department name and role after switching. Your role can differ between departments; roster, incidents, settings and plan information follow the active department.
Edit your profile or delete your account
On iPad, open Settings > Edit my Profile. On iPhone, open Account & Departments > Edit my Profile. Use the profile controls to review or update your account information.
To request account deletion, select Delete my Account and follow the confirmation prompts. Deleting your account removes your ability to sign in with it. Coordinate any outstanding department responsibilities before proceeding.
Section 3
Create and configure a department
Create a department
- 1.If you have no department access, choose Set Up a New Department. From an existing department, use Settings > Create New Department when you need a genuinely separate organization.
- 2.Enter the Department Name, Abbreviation and State. Use a consistent abbreviation that operators will recognize.
- 3.Select Create. The account creating the department becomes its owner.
- 4.Open Settings > Department Setup and confirm the details before building the organization and roster.
Configure the organization
Department owners and administrators maintain these settings. Configure lists before importing the roster so imported values can match the department's spelling and hierarchy.
| Department details | Maintain the department name, abbreviation and state. |
| Use Divisions | Enable when your organization uses divisions; configure those divisions before assigning dependent units. |
| Use Battalions | Enable when your organization uses battalions; configure their relationships as offered on screen. |
| Companies | Create the companies or units used in personnel records. If divisions and battalions are both disabled, companies report directly to the department. |
| Ranks and Order | Add ranks and arrange their order. Rank order helps place personnel in command selection lists and select a group supervisor. |
| Mutual Aid Departments | Add responding organizations with consistent names and abbreviations so personnel can be identified and filtered correctly. |
Configure incident types, assignments, and defaults
- 1.Open Settings > Incident Types and Defaults.
- 2.Open Incident Types and maintain the choices your department needs, such as structure fire, vehicle incident or investigation.
- 3.Open Assignments and maintain the operational tasks operators will select for members and groups.
- 4.Select the Default Incident Type and save. Review the actual settings whenever starting an incident rather than assuming the default is appropriate.
Section 4
Build and maintain the roster
Add a member manually
- 1.Open Roster and select Roster Actions > Add Roster Member.
- 2.Enter the member's name and available identifying information, including badge number. Set department, company, division, battalion and rank as applicable.
- 3.Use the correct mutual-aid department when the member belongs to another organization. Set the record's active status appropriately.
- 4.Save, then search for the person and review the result. Check for an existing record before adding another person with the same name.
Import a roster CSV
- 1.Prepare a CSV file with the required headers First Name and Last Name.
- 2.Add optional columns as needed: Badge Number, Department, Division, Battalion, Company, Rank, Notes and Active. Match configured organization and rank values.
- 3.In Roster, choose Roster Actions > Import CSV, then Choose CSV File.
- 4.Review the preview and summary. Records identified as duplicates are marked to be skipped. Resolve unexpected matches or missing information before importing.
- 5.Select Import for the displayed number of members. Review the imported and skipped counts, then spot-check names, badge numbers, departments and ranks.
Scan a tag into the roster
Roster Actions also offers Scan Accountability Tag. Review the recognized information before saving a permanent record. A tag scan assists data entry; it should not be accepted without checking the person and organization.
Use a practice department when importing sample personnel. Review the CSV headers and import preview before saving. For scanning practice, use the sample tag for Jane Doe, badge 151, DMFD (Demo Fire Department). Print the tag or display it on another screen; scan it using a physical device with camera permission. Verify the name, badge and department before accepting a roster match.
Maintain records without confusing incident history
Use department and company filters to narrow a long roster. Search for the existing record before adding a replacement. Review a member's details when their company, rank, or badge information changes.
Permanent roster information and the copy used in an incident are separate. An incident-only edit does not automatically update the permanent roster. Within an incident, Refresh from Permanent Roster replaces roster-owned information while preserving operational status, assignment, location, PAR, group membership and incident notes.
Section 5
Invite users and manage access
Invite an app user
- 1.As an Owner or Administrator, open Settings > Users & Access.
- 2.Review the department subscription and remaining app-user capacity. Pending invitations may reserve seats.
- 3.Choose Invite User. Enter the person's email address and select the appropriate Access Role.
- 4.Select Invite. Ask the recipient to create an FGM account or sign in using that same email address.
- 5.Confirm that the recipient appears with the intended access. Department access is claimed when the person signs in using the invited address.
| Owner | The department's owning account, with department administration responsibilities. |
| Administrator | Manages department configuration and app-user access; can manage board transfers. |
| Command | Command-level application access. Available actions also depend on incident state and board control. |
| Accountability / Safety | Operational board access and incident-only personnel entry without changing the permanent roster; can manage board transfers. |
| Member | Standard application access. Use the actions available for the incident and device; do not assume administrator permissions. |
| Read Only | Viewing access intended for users who do not make operational changes. |
Change access or resolve an invitation
- 1.In Users & Access, select the user and open the access editor.
- 2.Change Role or Status as needed and save. Inactive users remain associated with the department but cannot access its FGM data until reactivated.
- 3.Review Pending Invitations. Revoke an invitation that is no longer needed or was sent to the wrong address, then issue a corrected invitation if appropriate.
Section 6
Department plans and subscriptions
Choose a plan before creating incidents
A department needs an eligible plan to create incidents. Purchasing an Apple subscription plan activates a 14-day trial, or contact Fireground Manager for a custom department plan. Custom department plans are intended for larger departments with a need for a large number of users. Plan prices are not listed in this guide; review the current terms shown before confirming a purchase.
- 1.Sign in as an Owner or Administrator and confirm the active department.
- 2.Open Department Plan on the home screen, or the subscription area in Users & Access.
- 3.Review the available plan and application-user capacity. Standard capacity options are 5, 10 or 20 users, with custom arrangements available.
- 4.Complete the available subscription flow and review any trial or renewal terms shown by Apple. For custom requirements, contact Fireground Manager through its website.
- 5.Return to FGM and confirm that the correct department shows the expected plan and access capacity before creating an incident or sending additional invitations.
Restore an existing Apple purchase
Confirm the intended department and use the Apple account that made the purchase. Go to Users and Access, Subscription Plans → Restore purchases (at the bottom), follow any Apple prompts, and then confirm the department's plan and user capacity. If access is still missing, contact support before making another purchase. Restoring an Apple purchase does not replace a separately managed custom department plan.
If plan access is unavailable, check the active department and signed-in account first. Reopen the plan information and retry loading it if it could not be retrieved. If the plan or seat count still appears wrong, contact the department owner or support with the department name and the displayed message. Avoid making a second purchase solely because the screen has not refreshed.
Section 7
Start an incident
Open the new incident form
- 1.Open Manage Incidents and select Start New.
- 2.Confirm the active department and complete the Incident information.
- 3.Select an Incident Commander from the active roster. Chiefs are listed first, followed by captains, other officers and remaining members. Use the Home Department or Mutual Aid choices as appropriate.
- 4.Review the Structure settings and Floor List Preview, then select Start Incident.
- 5.Confirm the incident name, selected commander, elapsed timer and primary-board status. The device that creates the incident becomes its primary board. Ownership is device-specific and login-specific: signing in with the same account on another device does not automatically transfer control.
| Incident Name | A clear, recognizable name that other operators can use to select the correct incident. |
| Address / Location | The operational address or location description. |
| Incident Type | Choose from the department's configured incident types. |
| Incident Commander | Select an active roster member. Add an active roster record first if the list is empty. |
| Building Shape | Choose the footprint that best represents the incident. Incident Config also offers No Building for incidents where a footprint is not useful. |
| Highest Floor | Set the highest above-grade floor. The form supports floors 1 through 50. |
| Basement | Indicate whether a basement should be included. |
| Below-Grade Levels | Set any below-grade levels offered by the form, from 0 through 5. Check the resulting floor list to avoid misunderstanding basement labels. |
| Roof Operations Possible | Enable when a roof location is relevant to this incident. |
| Floor List Preview | Verify all generated locations and their short labels before starting. |
Section 8
Understand and configure the board
Read the incident screen
| Top status area | Incident identity, connection state, personnel and group counts, PAR information, task counts, significant events and elapsed incident time. |
| Incident Personnel panel | People currently assigned to the incident. Select a member to review details; use Add Member to Incident to add personnel. |
| Board canvas | The tactical grid, optional building outline, side labels, member and group icons, command post and free-form drawing. |
| Board panel | Incident Config, alarm escalation, Significant Events, Move/Draw/Erase, group creation, command-post visibility, PAR, notes, timeline, Leave Incident and Close Incident. |
| Primary board status | Open Board synchronization to inspect synchronization state, connected users and primary-control options. |
| Canvas controls | Use available centering, find and view controls to locate personnel and bring the structure back into view. |
Change the building and side labels
- 1.Select Incident Config and choose Building Shape. Select No Building for an incident where the outline would distract from the tactical grid.
- 2.Use Rotate Building 90° Clockwise as needed. This rotates the footprint only; it does not change Side A or the A/B/C/D designations.
- 3.Turn Show A/B/C/D Side Designations on or off. Set Side A Location to Top, Right, Bottom or Left to match the agreed incident orientation.
- 4.Review the board with the other operators, then select Done. Side labels can remain visible even when No Building is selected.
Set time checks and the command post
In Incident Config, choose Time Check: Never, 5, 10, 15, 20, 30 or 60 minutes. At the selected interval, FGM displays a reminder; it also suggests a PAR if none has been completed since the previous time check. Reminders should not be interpreted as a completed accountability check. If you return after several missed intervals, reminders are consolidated rather than stacked.
Use Show Cmd Post or Hide Cmd Post in the Board panel to control the command-post marker. Hiding the marker does not remove the Incident Commander designation. The Incident Time display is elapsed incident time; it is not a countdown to the next PAR.
Section 9
Add and update incident personnel
Add personnel from the roster
- 1.On the primary board, select Add Member to Incident.
- 2.Use Roster, search, department filters or company filters to find the person. Hide Members Already Added can reduce the list.
- 3.Select the correct member and confirm Add Member to Incident. Check the incident personnel list before repeating the action.
- 4.Open the added member and review status, assignment, operational location and floor as appropriate.
Add a temporary member
- 1.In Add Personnel, choose Manual Quick Add.
- 2.Enter the name and badge number if known. Indicate Mutual Aid Member when appropriate and fill in department, company, division, battalion and rank as available.
- 3.Select Add, then verify the person on the incident board. Temporary members belong to this incident and are not automatically saved to the permanent roster.
Scan an accountability tag
- 1.In Add Personnel, choose Scan Tag and allow camera access when requested.
- 2.Hold the tag clearly in view and review the recognized text and Suggested Matches.
- 3.Confirm the correct member before adding them. If there is no confident match, select the correct roster member, rescan, or return to Manual Quick Add.
- 4.Check the incident list for the new member. A similar name, an unclear tag, or an already-added record requires review rather than repeated scanning.
Edit member details and operational state
Select a member from the personnel list or board. Update the accountability status, assignment, operational location and PAR status using the available controls. Floor and operational location are distinct: a member can be Interior on a particular floor. Use Legends to understand the displayed colors and symbols rather than relying on color alone.
Use an incident-only edit for information that applies to this response. Use Refresh from Permanent Roster when you intentionally want current saved identity and organization details. For a lasting correction, use the permanent-roster update action when offered and review its confirmation. Otherwise, have an authorized roster administrator make the correction after the incident.
Change the Incident Commander
In Member Detail, use the Incident Command control to designate another active member. Confirm the transfer. This changes the command designation without changing the member's assignment, location, group or PAR result. Transfer command before releasing the current Incident Commander. This action does not transfer primary-board control.
Section 10
Create and manage groups
Create a group
- 1.Add the personnel to the incident first, then select Create Group.
- 2.Enter a recognizable Group Name, such as a company identifier or assigned team name.
- 3.Set the group Status, Assignment and Floor / Location as appropriate.
- 4.Select the personnel who belong together. The available list excludes members already assigned to a group.
- 5.Review the selected count and supervisor, then select Create. The highest-ranking selected member is assigned as supervisor; ties are resolved by selection order.
Move members and groups
- 1.Choose Move in Board Mode so a drag moves an icon rather than drawing a line.
- 2.Drag the member or group to its intended board position. Review its details afterward when the move should also change operational location or floor.
- 3.To add a member to a group using drag and drop, drop the member onto the intended group and read the confirmation before accepting.
- 4.If the member already belongs to another group, confirm the intended membership change and inspect both groups afterward.
Change a group and its members
Select the group icon to open its details. Review its name, status, assignment, members, operational location and floor. Where Apply location changes to group members is offered, turn it on when the change should apply to the whole group. Review the individual members after the change, particularly when a member is detached for another task.
Dissolve or release a group
Use Dissolve Group when its members should remain active on the incident as individual personnel. Use Release Group when the group and its assigned members are leaving the incident. Read the confirmation carefully: these actions have different results.
Section 11
Run and review a PAR
Start and work through a PAR
- 1.On the primary board, select PAR Check or Start PAR Check when offered by a time-check reminder.
- 2.Review the active round and the personnel included. Follow the department's normal radio/accountability procedure to obtain actual responses.
- 3.Update each member's PAR result as responses are confirmed. Tap the PAR status button once to mark PAR OK. Press and hold it, or tap its down arrow, to select another PAR result.
- 4.Setting a group's PAR status applies the same result to every member of that group. Confirm the result for the entire group before applying it.
- 5.Inspect unresolved and exception results. Confirm that the recorded result describes what is known, especially for No Response, Missing or Unknown.
- 6.Complete the round using its completion control when the record is ready. Review the summary and any remaining exceptions.
| Pending | A result has not yet been recorded for the current round. |
| PAR OK | A satisfactory response has been recorded by the operator. |
| No Response | The member has not responded as expected. |
| Missing | The member is recorded as missing. |
| Unknown | The member's accountability result is not established. |
| Rehab | The round records the member in rehab. |
| Released | The member is recorded as released from the incident. |
Review current status and PAR history
The top PAR chip summarizes the incident's current or latest PAR information. Use PAR History to open completed rounds, review responses, and compare times and exceptions. An active round can be viewed from another synchronized board or the iPhone Command Board, subject to device and access controls.
If you select a PAR action twice or receive a message that the round changed, return to the current PAR state before trying again. Another action or a recent synchronization may already have completed or updated the round.
Section 12
Record events, notes, and drawings
Increase the alarm level
- 1.Check the current alarm level shown on the board.
- 2.Select the displayed Transmit Next Alarm action, such as Transmit 2nd Alarm, and confirm when prompted.
- 3.Check the new alarm level and the timeline entry. Coordinate the actual alarm request through your department's dispatch and communications procedure.
Record significant events and a Mayday
Use the Mayday action to record a Mayday. If the caller is not yet known, record the event without guessing a name. When the member is identified, update the Mayday record. Active Maydays are emphasized on the incident display. End the Mayday in the app when the responsible operator has confirmed that it should be ended, and review the resulting timeline entry.
Recording or ending a Mayday in FGM does not replace radio traffic or the department's Mayday procedure. Make sure the board record follows the actual incident information.
- 1.Select Significant Events and choose the appropriate milestone, such as Water Supply Established, Water on the Fire, Overhaul Starting or Searches Complete.
- 2.Complete any information requested and confirm the event.
- 3.Check the status chip and incident timeline. On the iPhone Command Board, recorded significant events also show their timestamps.
Add a note and review the timeline
- 1.Select Add Incident Note and enter a clear factual note.
- 2.Save the note and open Timeline to confirm the entry.
- 3.Review the sequence of actions and recorded events. Use the available timeline export/share action when a copy is needed, or include the timeline in the incident report.
Draw on the board
- 1.Choose Draw in Board Mode and select a color. Draw the needed markings on the tactical grid.
- 2.Use Erase to remove a mark, or Undo and Redo to correct a recent drawing action.
- 3.Use Clear Board only when the displayed confirmation describes the drawing you intend to remove. It clears free-form drawing, not the incident itself.
- 4.Return to Move before dragging personnel or groups. Check synchronization before leaving or handing off the primary board.
Section 13
Work with multiple devices
Open the same incident on another device
- 1.Sign in on the second device with an account authorized for the same department.
- 2.Select the same department and open the existing incident from Manage Incidents. Do not create another incident with the same name.
- 3.Check the incident identity, live connection status and primary-board status. The secondary board receives synchronized updates. Signing in with the same account does not transfer control; editing the main board remains controlled by the primary device. Use a coordinated handoff when another device should take control.
- 4.Keep the incident open while observing. Confirm the other operator's device and user before arranging any transfer.
See who is connected
- 1.Tap the primary-board/synchronization status to open Board synchronization.
- 2.Review Connected users above Manage primary board. Each card identifies the user, device, mode, role and recent contact information.
- 3.Use the PRIMARY label to identify the current controlling board. An eligible receiving board offers Transfer to this board.
- 4.If a device is missing, confirm that it is online, on the same incident, running a compatible app version and keeping the incident open in the foreground.
Understand connection loss
A brief disconnection does not automatically move primary control to another board. Secondary screens may show their last synchronized information while disconnected. Check the synchronization details instead of assuming all visible changes reached the server.
The primary board can retain supported work locally during a connection interruption. When connectivity returns, review synchronization and any queued or retained work. Connected boards will receive updates from the primary board automatically after it reconnects.
- 1.If communication is interrupted, coordinate verbally with the primary operator and check the displayed status.
- 2.When the connection returns, reopen synchronization details and use Retry synchronization if offered.
- 3.If primary control changed during the interruption, follow Load current incident and retained-work instructions before continuing. Do not attempt to force old queued changes onto the current incident.
Section 14
Transfer primary board control
Coordinated handoff overview
A coordinated handoff is the normal way to move primary control. Owners, Administrators and Accountability / Safety users can manage transfers. Both devices should be online with the same incident open. Phones cannot receive primary control in any mode; use an eligible full-board device.
Transfer using Connected users
- 1.On the current primary, open Board synchronization and find the intended receiving user and device.
- 2.Select Transfer to this board on that specific eligible device card. Primary, phone and other ineligible entries do not offer a transfer action.
- 3.Review the receiving board and enter the reason requested. Select Save and request handoff. The sending board saves pending work and pauses editing.
- 4.On the receiving board, review the highlighted handoff notification. Confirm the requesting person, device and reason.
- 5.Select Accept primary control. The receiving device loads the current incident and becomes primary. It can also select Decline handoff.
- 6.Confirm the primary indicator on both devices before resuming board work.
Transfer using the four-digit code
- 1.On the current primary iPad, tap Primary board to open Board synchronization, then select Manage Primary Board.
- 2.Under Coordinated handoff, select Save and prepare for handoff. Give the displayed four-digit code to the authorized receiving operator.
- 3.On the receiving full-board device, open the same incident and select Manage Primary Board from the board synchronization screen. Keep Emergency takeover off.
- 4.Enter the four-digit code and a reason for transfer. For a practice handoff, use Testing. Check the confirmation that you coordinated with the primary operator, then select Make This Device Primary.
- 5.Confirm that the receiving board has loaded the current incident and is shown as primary.
Section 15
Recover control after a device failure
Use emergency takeover only when normal handoff is unavailable
Emergency takeover is for an unrecoverable primary device, not an ordinary short loss of connectivity. Unsynchronized work on the old primary may be missing from the server and will not be included in the replacement board's state.
- 1.Coordinate with the incident operators and confirm the primary device cannot be recovered for a normal handoff.
- 2.On an eligible full-board device, sign in as an Owner, Administrator or Accountability / Safety user and open the incident.
- 3.Open Board synchronization > Manage primary board, then select Emergency takeover.
- 4.Read and acknowledge the warning that unsynchronized work may be missing. Enter a reason and confirm coordination or that the old device cannot be recovered.
- 5.Use Refresh board information to check eligibility. Emergency takeover requires at least two minutes without primary contact; the server determines when takeover is allowed. Follow any additional restriction displayed on screen.
- 6.When enabled, select Make This Device Primary. Load the current incident if prompted and confirm the primary indicator.
- 7.Reconcile personnel, assignments, locations, current PAR and recent events with the operators before relying on the restored view.
When the former primary returns
The old device must recognize that control changed. Its earlier pending operations and drawings are retained for review rather than automatically merged into the current incident. Use Load current incident when offered to obtain the current shared state.
Compare retained work with the new primary's incident record. Communicate any missing operational information and enter only the corrections that are still valid through the current primary. Do not assume all retained changes should be replayed; some may have been superseded.
If transfer cannot proceed
- 1.Check that the receiving device is a full board rather than an iPhone, Command Board mode or scan mode.
- 2.Check the receiving user's role and active department membership.
- 3.Keep the incident open and online on the receiving device so its presence is current.
- 4.For a normal handoff, check that the code or request has not expired.
- 5.For emergency takeover, refresh eligibility and follow the displayed reason for any remaining restriction.
Section 16
Use Fireground Manager on an iPhone
Choose the right phone mode
The iPhone offers Command Board for incident monitoring and Scan to an Incident for personnel intake. Account & Departments provides account settings and department switching. Owners and Administrators also see Roster and Setup. The full incident-management workflow is operated on iPad; iPhones cannot receive primary-board control.
Use Roster to maintain saved department personnel and Setup to configure department settings when your role permits. Use Account & Departments to switch departments or open Edit my Profile. These administrative options are separate from the read-only Command Board.
Use Command Board
- 1.Open Command Board mode and choose the incident in the active department.
- 2.Confirm its name, alarm information, elapsed time and connection state.
- 3.Review personnel, completed PAR and team/group counts, then scroll through the operational snapshot and any exceptions.
- 4.Expand PAR Status to see the active round or most recent completed information. Collapse it when you need more space.
- 5.Review significant events and their timestamps beside the status icon. Active Mayday information is emphasized.
- 6.Expand the timeline to review entries; its collapsed view retains the latest event. Scroll within the displayed timeline as needed.
Use Scan to an Incident
- 1.Select Scan to an Incident and choose the correct active incident before scanning.
- 2.Confirm the incident name shown under Scanning into. Allow camera access when requested.
- 3.Scan the accountability tag, review recognized text and suggested roster matches, and confirm the correct person.
- 4.Check the result and continue with the next member. Coordinate with the primary-board operator to verify additions are visible there.
- 5.Use Incidents to return to incident selection before scanning into a different incident.
Section 17
Leave, close, reopen, and archive incidents
Leave without closing
Select Leave Incident when you want to exit that screen while the incident continues. Leaving does not close the incident for other users. If you are operating the primary board and another operator will continue, arrange and confirm a handoff before leaving.
Release members before concluding the record
Open Member Detail, select Release Member and confirm. The member is marked released, including their PAR release status. Their participation remains part of the incident history. Transfer the Incident Commander designation before releasing the current commander. Use Release Group only when all assigned group members are being released.
Close and reopen
- 1.Review personnel, any active PAR, notes and significant events. Resolve outstanding recording tasks before closing.
- 2.On the authorized primary board, select Close Incident and read the confirmation.
- 3.Confirm closure. The incident becomes historical and read-only, and its elapsed duration is preserved.
- 4.Open the incident from History to review its board, timeline, PAR history or report.
- 5.If a correction requires reopening, have an Owner or Administrator use Reopen Incident and confirm the action. Recheck board control before making changes, then close the incident again when finished.
Find incidents in Manage Incidents
Use the Active, History and Archived chips to narrow the list. All includes nonarchived active and historical incidents. Apply the available search, status and date filters when looking for a specific record. Open the existing incident rather than starting a duplicate.
Archive and unarchive
- 1.Find the closed incident you want to remove from the normal list.
- 2.Select Archive. Check that the incident is marked archived and no longer appears in All or the normal History list.
- 3.Select Archived to find it again. Other search/date filters can still narrow the results.
- 4.Select unArchive to return it to the normal historical list. The incident remains closed unless separately reopened.
Section 18
Reports and incident exports
Review an incident report
- 1.Open the completed incident through Manage Incidents > History, or Archived if it is archived.
- 2.Open its report and verify the incident identity and time range.
- 3.Review the recorded board, personnel, groups, PAR rounds, alarm changes and timeline. Final recorded positions are shown; released personnel and groups remain listed even when absent from the final board picture.
- 4.Select Share PDF to create a shareable report. Choose the intended destination in the device's share sheet and inspect the resulting document.
Review organization reports
- 1.From Manage Incidents, open Reports when your role provides access.
- 2.Confirm the active department and select the date range. Use the custom range controls when a specific start and end date is needed.
- 3.Filter by incident Status, Incident Type or Incident Commander as needed.
- 4.Select Refresh to reload the report. Review the summary and incident list, and open individual incidents for supporting detail.
- 5.Use Clear Filters to remove secondary filters when results appear incomplete, and separately verify the selected date range.
Review temporary members and roster corrections
After the incident, review temporary personnel and identity corrections. Match each person to the existing permanent roster before creating another record. Keep incident-only observations with the incident; update the permanent roster only for lasting, verified identity or organization information.
When a roster review or permanent-roster update action is available, inspect the proposed change before confirming it. If no such action is available to your role, give the correction to the department's roster administrator. Recheck the resulting record to prevent duplicate people or an incorrect mutual-aid affiliation.
Section 19
Troubleshooting and tester checks
What you see / What to check
| Department is missing | Verify the signed-in email, invitation and active membership. Use Check for Department Access before creating a new department. |
| Cannot create an incident | Check the plan, connection, department role and active roster. Confirm whether the incident already exists before retrying. |
| A board is read-only | Check whether the incident is closed, your user role is limited, the device is secondary, or a handoff has paused editing. |
| A device is absent from Connected users | Use the same incident and department, update the app, reconnect, and keep that incident in the foreground. |
| Cannot transfer to a phone | Phones are intentionally ineligible. Use an authorized operator on an eligible full-board device. |
| Recent changes are missing | Review synchronization state on both devices. Confirm primary control and check for retained work after a transfer. |
| An incident seems to have disappeared | Check department, Archived, date range and search filters. All excludes archived incidents. |
| A tag matches the wrong person | Rescan or select the correct roster record. Review badge number and department; do not accept the suggestion blindly. |
| A drag draws a line | Change Board Mode from Draw to Move. |
| Roster information differs in an incident | Decide whether the incident-only difference is intentional before using Refresh from Permanent Roster. |
Before a tester session
- 1.Record the app version/build and use clearly named practice incidents. On iPhone, the version and build appear at the bottom of the mode-selection screen.
- 2.Use two devices and appropriate test accounts when checking live refresh, presence and handoff.
- 3.Check setup, roster import, member intake, group changes, PAR, events, drawing and report export.
- 4.Exercise leave versus close, archive versus unarchive, and reopening with an authorized account.
- 5.Test interrupted connections and transfer recovery in a controlled practice session; inspect queued or retained work afterward.
Report a problem clearly
Provide the app version/build, device model, department and test incident, your role, whether the device was primary, and the connection state. List the steps, expected result and actual result. Include the time and a screenshot when helpful. For a synchronization problem, identify what each device displayed. Do not include passwords or access codes in a shared bug report.