Getting To Grips With King County I-MATS
I-MATS is King County's alerting and notification platform. It connects emergency operations centers, fire departments, law enforcement agencies, and public health officials across the county so they can share information during incidents. The system pulls from NIMS-compliant messaging templates and routes alerts through multiple channels depending on what the sending agency configures. If you work in public safety communications in the Puget Sound area, you will eventually deal with it. That phrase shows up in a lot of marketing materials and conference brochures, but the reality is more mundane. I-MATS has been around since the mid-2000s and has gone through several iterations. The current version is built on an alerting infrastructure that supports both mass notification and inter-agency messaging. The "future" angle mostly comes down to integrations with 911 dispatch systems, GIS mapping layers, and automated weather feeds. None of that is magic. It is just the system doing what it was always designed to do, only less manually. I have used it for years across a few different agencies. The workflow is straightforward once you know where the buttons are. Here is how it actually works in practice.
You start by logging into the I-MATS portal. Your agency needs an account set up by the King County Emergency Management division before you get access. Once you are in, you select the type of message you are sending. There are predefined templates for everything from evacuation orders and shelter announcements to inter-agency tactical updates. The templates follow standard ICS formats, which helps when multiple agencies are reading the same alert. You fill in the fields, choose which recipients get it, and pick the delivery methods. Messages can go out via email, SMS, voice call, or through connected radio systems depending on your agency's integration level. The recipient list is where people usually run into problems. I-MATS uses an organizational tree structure. Your account is scoped to your agency, and you can only send messages to entities within that tree unless someone with higher-level permissions adds cross-agency distribution lists. I spent about three weeks trying to figure out why my shelter notification wasn't reaching a neighboring city's emergency management office. The issue was not technical. It was organizational. That city was in a different I-MATS jurisdiction node, and nobody had set up a contact relationship between us. The workaround was getting our county EM director to formally request an inter-jurisdictional agreement through the King County ESD 112 administrative panel. That process took about ten business days. After that, I could select those agencies from the recipient dropdown. Another thing nobody tells you about I-MATS is how aggressively it validates message content. The system checks for completeness on every required field, and if you leave something out, it will not let you send. This sounds like a good thing until you need to send an urgent initial notification at 2 AM and you are missing one optional field that you do not actually need. The workaround I use is keeping a draft template saved for each incident type. I fill it in completely during business hours when someone is available to verify everything. Then at 2 AM I just open the draft, swap out the date and location fields, and hit send. Cuts the time down from maybe twenty minutes of fumbling to about two.
The system also has a message tracking feature that logs delivery status for each recipient. This is useful for after-action reporting but the interface is not great for real-time monitoring. The tracking page loads slowly when you have more than a couple hundred recipients, and the status categories are limited to delivered, failed, and pending. There is no granular breakdown if a message fails, so you end up calling your IT support to figure out whether an email bounced or an SMS gateway rejected it. I keep a spreadsheet alongside I-MATS tracking for high-volume activations. It is redundant but it saves time when you need to explain to your director why half the recipients never got the alert. One counter-intuitive thing about I-MATS is that more integration is not always better. When your agency is plugged into automated data feeds, the system will sometimes generate and send messages without direct human input. This sounds efficient but it introduces error propagation. I saw a situation where an automated weather alert triggered a cascading notification to five agencies because a threshold was misconfigured. No human had reviewed the trigger conditions. The fix was to disable the automated routing and route everything through manual approval until the configuration was audited. Your mileage will vary depending on how your county has set up the automation rules. There are legitimate limitations to the platform. The mobile app exists but it is essentially a read-only interface with basic messaging capability. If you are in the field and need to compose a detailed message with attachments, you are better off using the web portal on a laptop. The attachment size limit is 10 MB per file, which is fine for a PDF map but not for a large image file from a drone feed. People work around this by uploading to a shared drive and including a link in the message body instead, but the link is not always accessible from every recipient's device depending on their network permissions.
Get the Full Details
Training is another bottleneck. New users typically get maybe four hours of formal training, which covers the basics but not the edge cases. The user manual is thorough but formatted like a government document, which makes it hard to quickly find answers when you are in the middle of an active incident. I keep a one-page quick reference card taped to my monitor with the common workflows: how to edit a draft, how to add a cross-jurisdictional recipient, how to export the message log, and the support phone number. That card has saved me more times than I can count. If your agency is small and does not have a dedicated emergency management staff, I-MATS can feel like overkill. The setup overhead, the account management, the compliance requirements, they add up. In those cases, some departments pair it with a simpler mass notification tool for day-to-day communications and only bring in I-MATS for multi-agency incidents. That hybrid approach is perfectly valid and I have seen it work well. The trade-off is that you need clear procedures for when to switch between the two systems, otherwise you end up with fragmented communication during an actual event. For downloading or requesting access, you go through the King County Emergency Services District 112 website. They have a request form for new agency onboarding and the contact page lists the system administrators. There is no self-service download for the platform itself since it is a cloud-based service tied to specific agency accounts. Some training materials and template libraries are available publicly on the county website, which is useful for preparing before you even get your login credentials.
The platform works. It is not elegant and it has friction points that frustrate people daily, but it gets the job done when you need to coordinate a response across thirty different jurisdictions in a county of four million people. The people who get the most out of it are the ones who invest time in understanding the organizational structure, pre-build their templates, and keep a manual backup for when the system slows down or misbehaves. That last part is not theoretical. I have been in activations where the portal became so slow that sending a text message took eight minutes, and the voice call backup went out first because it routed through a different pipeline. Knowing that ahead of time changes how you prepare.
