Response Time Priority One Target Minutes Lookup
Exact independently verified priority-one response targets registry lookup in explicit agency, incident classification, clock definition and policy edition context, retaining source and as-of date. Caller supplies actual applicable records, qualifications and uncertainty; illustrative examples are not authoritative data. No complete/current catalog, eligibility, authenticity, clinical, legal, safety or compliance determination.
Description
Priority-one response targets depend on agency policy, incident classification and clock definitions.
Priority-one response targets depend on agency policy, incident classification and clock definitions.1
A recorded target needs its policy edition and measurement scope. Use this tool to retrieve a caller-supplied reference with its source context.
When to use Response Time Priority One Target Minutes Lookup
Use this tool to retrieve a caller-supplied reference with its source context. Establish the jurisdiction or research scope, observation and event definitions, reference date, matched period and denominator basis.
How to use Response Time Priority One Target Minutes Lookup and understand its results
- Establish the jurisdiction or research scope, observation and event definitions, reference date, matched period and denominator basis.
- Enter callerVerifiedSource, callerVerifiedContext, callerVerifiedAsOfDate, callerReferenceKeys, callerReferenceTexts, queryReferenceKey, using the field meanings and rules below, then run the tool.
- Read result.matchedCallerReference, result.source, result.context, result.asOfDate. Interpret each field using the units, signs and evidence rules below.
- If input validation fails, correct the reported field and run again. Before applying a successful result, check the stated reference scope, units, assumptions and any retained unknown evidence.
| Input field | Meaning | Value type | Requirement |
|---|---|---|---|
| callerVerifiedSource | Caller verified source; caller assertion whose applicability must be independently established | string | Required |
| callerVerifiedContext | Caller verified context; caller assertion whose applicability must be independently established | string | Required |
| callerVerifiedAsOfDate | Caller verified as of date; real Gregorian YYYY-MM-DD date for the supplied record | string | Required |
| callerReferenceKeys | Caller reference keys | list of string | Required |
| callerReferenceTexts | Caller reference texts | list of string | Required |
| queryReferenceKey | Query reference key; exact key or bounded coordinate, according to the rules below | string | Required |
Supply nonblank source and context strings, each at most 256 UTF-16 units, and a real Gregorian YYYY-MM-DD as-of date in years 0001–9999. Enter nonempty aligned reference keys and texts; keys must be unique and nonblank, and texts nonblank. Select an exactly matching key, with case-sensitive matching and no trimming or normalization. The implementation returns its matched text and copies the supplied source, context and date unchanged. These verification labels are caller assertions: the tool does not fetch, verify or update a reference.
matchedText=texts[indexOfExact(queryKey,keys)]; provenance=copied caller assertions Apply the field units and exact ordering, boundary and evidence rules above.
| Output field | Meaning | Value type |
|---|---|---|
| result | Structured result containing the calculation or selected reference fields below | object |
| result.matchedCallerReference | Caller text at the exact matched reference key, returned unchanged | string |
| result.source | Caller source assertion copied unchanged | string |
| result.context | Caller applicability context copied unchanged | string |
| result.asOfDate | Caller date copied unchanged after Gregorian validation | string |
{
"input": {
"callerVerifiedSource": "independently-reviewed-source/edition",
"callerVerifiedContext": "agency, incident classification, clock definition and policy edition",
"callerVerifiedAsOfDate": "2026-01-01",
"callerReferenceKeys": [
"record-a",
"record-b"
],
"callerReferenceTexts": [
"Caller independently verified priority-one response targets record a",
"Caller independently verified priority-one response targets record b"
],
"queryReferenceKey": "record-a"
},
"output": {
"result": {
"matchedCallerReference": "Caller independently verified priority-one response targets record a",
"source": "independently-reviewed-source/edition",
"context": "agency, incident classification, clock definition and policy edition",
"asOfDate": "2026-01-01"
}
}
}Limitations and assumptions
A successful lookup establishes an exact key match to supplied text. The tool does not obtain or authenticate the reference, confirm its applicability, or update its date.
Every listed input requires an explicit value. Unexpected fields, incorrect value types, nonfinite numbers and sparse numeric arrays fail validation; tool-specific bounds and alignment rules apply as described above. Extremely large inputs or outputs can also be rejected. An input error is distinct from a successful calculation that reports a false comparison or retains unknown evidence.
Alternative or Complementary methods
Use Patrol Beat Workload Hour Balance Calculator to examine a related aspect: Patrol workload balance compares recorded service hours with independently available staffing hours.
Use Officer Per 1000 Population Staffing Benchmark Lookup where its separate inputs and scope apply: Officer staffing benchmarks depend on duties, population basis and agency context.
References
Similar or alternative tools
- Patrol Beat Workload Hour Balance Calculator
Patrol workload balance compares recorded service hours with independently available staffing hours.
- Officer Per 1000 Population Staffing Benchmark Lookup
Officer staffing benchmarks depend on duties, population basis and agency context.