Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Records Management topic
No spam. Unsubscribe anytime.
Lake County E‑911 Authority considers changing incident‑number generation to reduce duplicate cases
Summary
Authority members discussed whether status changes (for example, follow‑up calls or routine business checks) should create new incident numbers in records management, and asked staff to adjust practices to reduce unnecessary case creation.
At its Jan. 3 meeting, the Lake County E‑911 Authority discussed whether the county’s records/dispatch system should generate new incident numbers automatically for routine status changes, such as foot patrols or business checks.
An authority member described a case where follow‑up work at a school repeatedly generated new incident numbers, complicating follow‑up documentation. “If we know it, we can reopen,” a staff member said, arguing that known cases should be reopened instead of creating new IDs. Members said some calls that should be tracked as inactive were becoming active incident charges for agencies, which could affect interagency billing tied to incident counts.
Staff proposed two practical fixes: (1) allow the system to create an incident as inactive by default where appropriate, and (2) train officers to reference the original case or provide a date and brief descriptor (for example, “follow‑up on school threat, 12/01”) when they radio in so dispatchers can attach the activity to an existing record rather than generating a new one.
Members also discussed operational triggers for incident generation — interactions that convert a status into an incident (for example, two people arguing, activation of body cameras, or other contact). The authority emphasized that officers should document the reason for reopening a case so dispatchers can find the original report; staff said they would ask CallWorks/Flex support whether dispatchers can search by case number.
No formal policy or vote was taken; the board directed staff to pursue configuration changes and training so that routine status changes do not create unnecessary charges or duplicate incident records.
