Shared dispatch, separate records: planning a multi-agency CAD

Separate coordination from record access

A county dispatch center may coordinate police, fire and EMS at the same incident. That does not mean every responder needs every agency's reports. Start your design with two questions: who needs the operational call, and who needs the records created by each agency afterward? Treating those as separate decisions makes the workspace easier to administer and test.

In Quick CAD, one CAD workspace can serve multiple response agencies. Dispatch can share a selected call with participating agencies, while their reports remain private to the agency that owns them. A shared incident is therefore a coordination point, not a blanket grant to all the reporting behind it.

Create agencies around responsibility, not just labels

In Agency settings, the response-agency configuration includes Dispatch for multiple agencies. Enable it when more than one bounded agency needs to operate within the workspace. Add each agency with a meaningful name, short name and service type. Make the default agency an intentional choice rather than leaving staff to guess which organization it represents.

An agency boundary is more than a department name shown on a screen. Users, units and private records belong to an agency. Before adding accounts, write down which organization owns each unit and which people administer that organization's work. If one person performs several functions, review their actual access rather than treating their job title as permission.

Test user roles and unit ownership together

Create agency users with the appropriate role and module permissions, then assign units to the correct agency. Dispatcher, management, field-user and administrator responsibilities are different. Center-wide coordination and private report access should be assessed separately; do not assume that seeing an operational call also authorizes access to its related reports.

Use a fictional test call to inspect the experience from each account. A responder should have enough information to do the assigned work, while unrelated agencies should not gain access just because they use the same CAD provider. Test searches and the incident log as well as the main operational screen.

• Check a dispatcher account that coordinates the response.
• Check a field-user account in an agency participating in the call.
• Check an account in an agency that is not participating.
• Check report access separately from call visibility.

Share a call deliberately when the response expands

Consider a fictional collision that starts as a law-enforcement response and later needs fire assistance. The dispatcher can coordinate selected call sharing for the additional agency. Review the participating agencies and unit assignments as part of that handoff. Avoid creating inconsistent copies of the same operational story simply to give another team visibility.

When each agency documents its work, choose the correct reporting agency. Quick CAD's report views identify agency scope, including for shared incidents. The law-enforcement report should remain within its reporting boundary; sharing the call does not convert it into a joint report. Keep your agency's own rules for disclosures and external information requests separate from routine dispatch access.

Enable only the reporting that each agency uses

Every response agency has an incident log. Additional reporting is configured for that agency and is also subject to user permissions. Law-enforcement agencies can enable NIBRS and RIPA reporting. Traffic-collision reporting can be enabled for other agency types when appropriate. A security organization does not need to adopt a law-enforcement reporting workflow simply because it shares the dispatch workspace.

For fire agencies, the current NERIS option is preparation: reference configuration and incident-data preparation. It is not a claim of complete NERIS validation or submission. Check the enabled program, available validation coverage and your receiving authority's requirements before deciding a report is ready to send outside your organization.

Plan agency changes without opening old records

A simpler operation may later return to single-agency mode. Quick CAD requires other agencies to be inactive and their active work to be resolved before that change. Historical agency boundaries remain in place. Deactivation also prevents that agency's users from signing in, so include staff access and unfinished work in the change plan.

Use the same access checklist after adding an agency, changing a role or enabling a reporting module. Confirm both the work that should succeed and the access that should be unavailable. This gives administrators a repeatable way to review a shared dispatch arrangement as staffing and service responsibilities evolve.