SAPD Non-Dispositioned Calls And JPAK Workflow Optimization For 2026
The San Antonio Police Department (SAPD) utilizes specialized data management systems to handle high volumes of incoming calls for service. For dispatchers and administrative units, the term "non-dispositioned" refers to calls that have reached a terminal state in the Computer-Aided Dispatch (CAD) system but lack the necessary administrative closure codes—or dispositions—required for final reporting. When these calls are flagged within the JPAK (Joint Police and Administrative Knowledge) framework, they create a backlog that impedes operational transparency and statistical accuracy. This guide details the 2026 technical requirements for clearing these records and maintaining departmental compliance.
Understanding the Lifecycle of a Non-Dispositioned Call
In the context of SAPD operations, a call reaches a non-dispositioned status when a unit completes the field response but fails to append the final disposition code before the CAD log is locked for the shift. This creates a data gap in the JPAK system, which acts as the primary interface for syncing real-time patrol data with the municipal records management databases.
Non-dispositioned calls are more than mere clerical errors; they represent significant regulatory challenges. Under 2026 performance auditing standards, accurate call disposition is mandatory to ensure that the Uniform Crime Reporting (UCR) and National Incident-Based Reporting System (NIBRS) data remain compliant with state and federal oversight requirements.
Operational Impact of Missing Dispositions
Resource Allocation Analytics When calls remain non-dispositioned, the JPAK system cannot accurately calculate the average response time or the frequency of specific crime types in defined districts. This leads to inefficient patrol distribution for the current fiscal year.
Liability and Audit Risks Departmental liability increases when incident reports are not properly closed. Discrepancies between dispatch logs and secondary incident reports create gaps that are frequently exploited during legal discovery or administrative internal affairs reviews.
Technical Requirements for JPAK Record Reconciliation
To rectify non-dispositioned calls within the 2026 administrative framework, supervisors must utilize the JPAK reconciliation module. This interface allows for the retrospective entry of codes that were missed during the initial patrol transition. The following table outlines the status codes required for successful system synchronization.
| Status Code | Description | Technical Requirement |
|---|---|---|
| DISP-01 | Resolved on Scene | Requires specific incident narrative ID. |
| DISP-02 | Referred to Specialist | Requires secondary agency case number. |
| DISP-03 | Administrative Closure | Requires supervisor override and timestamp. |
| DISP-99 | System Error / Dupe | Requires audit trail documentation. |
When attempting to clear these records, users must ensure that the JPAK server is synchronized with the primary CAD database. Attempting to force a disposition on a call that is currently marked as "Active" or "En-Route" in the CAD system will result in a hard lock, requiring manual intervention from the technical support desk.
Civil rights attorney representing George Floyd's family calls out SAPD ...
Step-by-Step Workflow for Clearing Backlogged Records
Effectively managing non-dispositioned calls requires a methodical approach to data verification. Follow this 2026-standardized protocol to minimize system latency and ensure record integrity.
- Access the JPAK Dashboard: Navigate to the administrative portal using your secure departmental credentials. Use the "Pending Reconciliation" filter to isolate calls from the previous 72-hour window.
- Cross-Reference with CAD Logs: Compare the timestamps of the non-dispositioned entry with the corresponding unit’s radio transmission logs. Verification of the actual event outcome is mandatory before entering a disposition code.
- Verify Jurisdiction and Unit ID: Ensure that the unit assigned to the call matches the authorization levels within the JPAK system. If a multi-agency response occurred, ensure the primary responding unit is the one authorized to append the final code.
- Finalize and Validate: Once the code is entered, the system will prompt for a secondary validation signature. Input your unique badge number and the active 2026 supervisor authorization key to commit the record to the permanent database.
Common Obstacles in 2026 Data Management
Despite system updates, technical friction remains a hurdle. Many non-dispositioned calls are the result of "dropped signals" in areas of the city with legacy network infrastructure. When a unit moves out of range before clearing a call, the CAD record may time out.
The primary remedy is the use of the mobile-integrated JPAK interface, which allows for offline caching. Officers are encouraged to sync their devices upon returning to high-connectivity zones, as this automatically clears most cached dispositions and prevents the "non-dispositioned" flag from ever being generated.
Frequently Asked Questions regarding JPAK Dispositions
What defines a non-dispositioned call? A non-dispositioned call is a recorded service request that has finished its operational lifecycle but lacks a formal final disposition code in the JPAK system. This usually occurs when the CAD entry fails to capture the final status update from the responding officer.
Why is it important to clear these calls immediately? Clearing these calls is essential for accurate NIBRS reporting and for ensuring that the city's 2026 crime statistics remain transparent and compliant with state standards. Unresolved calls artificially inflate response time metrics and obscure actual patrol workload data.
What should I do if a call refuses to accept a disposition code? If the JPAK system returns a "System Error" or "Authorization Denied" message, stop manual attempts immediately to prevent a permanent lockout. Document the call ID and report the issue to the departmental CAD administrator for manual database override.
How do I handle multi-unit responses? Only the primary responding unit or the assigned supervisor should enter the disposition for a multi-unit call. Standard procedure dictates that the primary unit’s disposition applies to the total incident record, while secondary units must be marked as "Assisting" without creating conflicting dispositions.
Is there a deadline for fixing non-dispositioned records? Per 2026 internal administrative policies, all non-dispositioned records must be reconciled within 48 hours of the initial incident. Records remaining in a non-dispositioned state beyond this window are flagged for supervisor review and potential internal audit.
Strategic Recommendations for Administrative Staff
To maintain maximum efficiency, supervisors should run a JPAK "Non-Dispositioned Exception Report" every morning at 06:00. By identifying calls that slipped through the process during the previous shifts, administrators can resolve issues before they become permanent statistical discrepancies. Furthermore, continuous training on the 2026 JPAK mobile interface for all incoming patrol cohorts will significantly decrease the occurrence of these errors, ensuring that the San Antonio Police Department maintains its high standards of data-driven operational excellence.
For further technical support regarding specific CAD-JPAK integration errors, personnel should submit a ticket through the standard departmental IT portal, ensuring all relevant incident IDs and timestamp fragments are included for rapid resolution.
