Records Request SLA

Measure a records-request response against a caller-supplied SLA.

Description

A records-request SLA measures elapsed time between supplied timestamps.

A records-request SLA measures elapsed time between supplied timestamps. Its limit is expressed in continuous hours.^[1]

Measure a records-request response against a caller-supplied SLA.

When to use Records Request SLA

Use this tool to measure a records-request response against a caller-supplied SLA.

Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.

How to use Records Request SLA and understand its results

Prepare the text, recorded observations, aligned figures or editorial criteria requested. Confirm what each label, count, timestamp or supplied flag represents before interpreting the result.
Enter receivedAt, respondedAt, slaHours using the field table and calculation rules, then run the tool.
Read elapsedHours, slaMarginHours, metSla. The explanation below defines the units, signs, ordering and any flags or placeholder values.
If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.

Input field	Meaning	Value type; see rules below	Requirement
receivedAt	Request received timestamp	string	Required
respondedAt	Response timestamp	string	Required
slaHours	Response SLA (h)	number; minimum: 0	Required

Enter parseable request/response timestamps and nonnegative maximum hours. Reject invalid dates and a response before the request. Return elapsed hours, maximum-minus-elapsed SLA margin and inclusive gate. ISO timestamps with explicit offsets provide an unambiguous basis.

elapsedHours=(response−request)/3,600,000; within=elapsed≤maximum

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
elapsedHours	Elapsed response time (h)	number; minimum: 0
slaMarginHours	SLA time remaining (h)	number
metSla	Met supplied SLA	boolean

json

{
  "input": {
    "receivedAt": "2025-01-01T00:00:00Z",
    "respondedAt": "2025-01-02T12:00:00Z",
    "slaHours": 48
  },
  "output": {
    "elapsedHours": 36,
    "slaMarginHours": 12,
    "metSla": true
  }
}

Limitations and assumptions

No business-hour calendar, holidays, statutory deadline or request status is modeled. Native date parsing determines accepted formats.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors. A successfully returned false flag is an evaluated outcome; its meaning is explained above.

Alternative or Complementary methods

Use Records Request Deadline Sorter: Parse and sort agency request deadlines, identify overdue agencies, and find the next due date. For a complementary task, use Live-Blog Staleness: Measure live-blog update age against a supplied staleness threshold.

References

Records Request SLA — tool.io

Similar or alternative tools

Records Request Deadline Sorter
Parse and sort agency request deadlines, identify overdue agencies, and find the next due date.
Live-Blog Staleness
Measure live-blog update age against a supplied staleness threshold.