Skip to content

Main content

Court Docket Case Reference

Format caller-supplied court, year and case-sequence fields without resolving a court registry or selecting an official jurisdictional format.

Loading tool…

Description

Format a supplied court, year and docket-sequence reference.

Justice records distinguish timestamps, civil dates, case references, hearing slots and document offsets. A calendar-day count depends on its endpoint policy, while a signed clock gap can be negative. Formatting a docket reference or comparing pseudonyms does not authenticate a case, identify a person or establish lawful disclosure.

Format a supplied court, year and docket-sequence reference.

When to use this tool

Use Court Docket Case Reference when you already have courtCode, year, sequence and need to format a supplied court, year and docket-sequence reference.

How to use the tool and how it works

  1. Enter courtCode, year, sequence. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read reference. Use the output convention below.

Require courtCode/sequence nonempty and year a whole number 1..9999; join court/year/sequence.1

Input fieldMeaning and unitsAccepted input
courtCodeCourt CodeRequired. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
yearWhole calendar-year label 1..9999; formatted without zero padding.Required. Safe integer; minimum 1; maximum 9999.
sequenceNonempty literal docket sequence, not parsed as an integer.Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192.
Output fieldInterpretationReturned shape
referenceReferenceRequired. Text; maximum UTF-16 length 8192.
json
{
  "input": {
    "courtCode": "COURT-A",
    "year": 2026,
    "sequence": "0017"
  },
  "output": {
    "reference": "COURT-A/2026/0017"
  }
}

Limitations and assumptions

  • Sequence is unparsed text and the year is not padded. No docket, court identity, unique case or legal record is retrieved or verified.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Check the original custody, court, service and document records alongside the applicable rules. Verify clock alignment, calendar conventions and permissions before using local counts or labels in a real proceeding.

References

  1. Calculation and input contract: criminal-justice/court-docket-case-reference — tool.io

Similar or alternative tools