Records Request Deadline Sorter

Parse and sort agency request deadlines, identify overdue agencies, and find the next due date.

Description

Sorting request deadlines helps identify overdue records requests and the next upcoming due date.

Sorting request deadlines helps identify overdue records requests and the next upcoming due date. Each supplied record carries an agency and date.1

Parse and sort agency request deadlines, identify overdue agencies, and find the next due date.

When to use Records Request Deadline Sorter

Use this tool to parse and sort agency request deadlines, identify overdue agencies, and find the next due date.

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 Deadline Sorter and understand its results

  1. 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.
  2. Enter requests, asOfDate using the field table and calculation rules, then run the tool.
  3. Read sortedRequests, overdueAgencies, daysUntilNextDeadline. The explanation below defines the units, signs, ordering and any flags or placeholder values.
  4. 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 fieldMeaningValue type; see rules belowRequirement
requestsAgency deadline recordslist of stringRequired
asOfDateAs-of datestringRequired

Enter agency|date records and an as-of date. Trim and require agencies, parse date strings at UTC midnight, and sort records stably by due timestamp. Extra pipe-separated fields are ignored. Return original sorted records, overdue agency labels in sorted order and next-due days; −1 means none. A due date equal to as-of is upcoming.

overdue=count(due<asOf); daysToNext=ceil((nextDue−asOf)/day)

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

Output fieldMeaningValue type
sortedRequestsRequests sorted by deadlinelist of string
overdueAgenciesOverdue agencieslist of string
daysUntilNextDeadlineDays until next deadlineinteger
json
{
  "input": {
    "requests": [
      "Transit|2025-03-15",
      "Police|2025-02-20",
      "Parks|2025-04-01"
    ],
    "asOfDate": "2025-03-01"
  },
  "output": {
    "sortedRequests": [
      "Police|2025-02-20",
      "Transit|2025-03-15",
      "Parks|2025-04-01"
    ],
    "overdueAgencies": [
      "Police"
    ],
    "daysUntilNextDeadline": 14
  }
}

Limitations and assumptions

No legal deadline is derived. Empty requests are allowed; native parsing may normalize calendar dates or accept formats beyond YYYY-MM-DD.

Numeric inputs must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.

Alternative or Complementary methods

Use Records Request SLA: Measure a records-request response against a caller-supplied SLA. For a complementary task, use Document Entity Date Sorter: Parse compact document records, sort them by dateline, and collect unique named entities.

References

  1. Records Request Deadline Sorter — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies