Best Practice: Capability and sustainment information is most available when the resource arrives — and most valuable when the incident becomes complex. This is a lot of information, but the easiest time to get it is at the beginning.

Best Practice: Radios from outside the local area may need to be reprogrammed for local frequencies. Radio ID numbers, personnel star/badge numbers, and the radios installed on Operations Assets need to be associated with one another so dispatchers can immediately identify whose emergency beacon is broadcasting.

Best Practice: Personnel base locations matter in the event that personnel and assets are forward deployed as part of the response — it is important so that personnel at one location are not assigned to assets at another. They may need to be updated as operational phases evolve — each change is recorded with a timestamp.

Best Practice: Operational decisions depend on capabilities, not inventory counts. Capture what this asset can do while the crew is available. Asset base locations may need to be updated as operational phases evolve — each change is recorded with a timestamp.

Best Practice: Radios from outside the local area may need to be reprogrammed for local frequencies. Radio ID numbers, personnel star/badge numbers, and the radios installed on Operations Assets need to be associated with one another so dispatchers can immediately identify whose emergency beacon is broadcasting.

Best Practice: Confirm each asset's fuel type at intake. When fuel infrastructure is disrupted in the affected area, resupply has to be planned by fuel type and base location together — nobody wants to be calling drivers mid-response to ask what their vehicle takes.

Best Practice: Personnel operating in uncontrolled environments should be positively accounted for at the conclusion of their assignment.

Best Practice: Every request should be documented when received, even when a solution is not immediately available. Each caller is a member of the community who should be counted.

Best Practice: Linking a Communication to one or more Purchases, Missions, Assignments, Requests, and/or Cache Issuances preserves the full operational narrative for after-action review — for example, a generator purchase, the mission that delivers it, and the announcement telling the requester it's on the way. Every field here supports linking more than one (Ctrl/Cmd-click to select several) — one announcement can cover two Missions distributing from the same inventory against a single Request and Purchase, or a single road-closure notice can cover two separate traffic-control assignments. Linkage is optional and works in either order — announce a distribution before it's actually issued, then come back and link the Cache Issuance once it's recorded; you are never blocked from logging a communication because a linked record doesn't yet exist.

Best Practice: Linking an issuance to the Mission, Assignment, or Request it supports preserves the full operational narrative — linkage is optional and never blocks logging the issuance.