DATA METHODOLOGY
Data Methodology
JailScope turns public county custody information into a consistent directory while keeping the source, timing, and limits of each record visible.
Our publishing standard
A county page is published when its public source can be identified and the type of information it provides can be described accurately. We use official county, sheriff, detention, corrections, or other government sources as the basis for a page. JailScope does not create a record when a source does not publish it.
The directory is built for discovery and source context. It helps a visitor find a county jail roster, inmate search, booking record, or local facility detail, then understand what the displayed result represents before relying on it.
What a published record represents
County systems do not all publish the same kind of information. A page may contain a roster snapshot, recent booking activity, selected custody records, or a link to an official search experience. These categories are kept distinct in the page language and field labels.
“Current” describes the source’s own published view at the time it was successfully captured. It does not promise a live connection to a jail, a complete population, or an immediate reflection of a change made by the responsible agency. If a source is delayed, unavailable, or limited, that context is shown with the page.
How fields are handled
- Names, booking identifiers, dates, charges, bond details, and custody labels are shown only when the source provides them.
- Similar source fields are presented with consistent labels so visitors can compare pages more easily.
- Blank or unavailable fields remain blank; they are never filled with an assumption.
- Contact, address, visitation, bond, and funds information is included only when it has a documented official basis.
- Source wording is kept separate from JailScope’s explanatory labels so a summary is not mistaken for an agency statement.
Quality and freshness checks
Before a county page is published, its source context and record shape are reviewed against representative examples. Updates are checked for expected fields, readable dates, usable identifiers, and changes that could make a result incomplete. A successful update records when the snapshot was captured and when it was published.
If an update fails or a source changes unexpectedly, the last successful snapshot can remain available while the page communicates that the information may be delayed. This protects visitors from a blank page being mistaken for an empty roster and keeps the timing distinction visible.
What the status and timestamp mean
The timestamp on a county page refers to the latest successful published snapshot, not a live probe of the jail system. A source health message describes the update state known to JailScope. It does not certify that an agency’s underlying database is complete or currently reachable from every location.
A record count is the number of records included in that snapshot. It is not a population estimate, a case count, or a statement about how many people are currently held by a county.
Privacy, identity, and responsible use
JailScope publishes public-source context for lookup purposes. A name match is not identity verification, and a booking, charge, or custody entry is not proof of guilt. A missing or unavailable record does not prove release, transfer, or absence from custody.
Do not use a directory snapshot as the sole basis for a legal, employment, housing, immigration, safety, medical, or other high-impact decision. For a time-sensitive question, contact the responsible agency or court through its official channel.
Corrections and source changes
If a page contains an incorrect field, source description, contact detail, or update note, send the exact page URL and a direct official reference through the Contact page. We review requests for provenance and update the directory when the evidence supports a change.
For the broader purpose and boundaries of the directory, read About JailScope. Privacy and browser technology choices are covered in the Privacy Policy and Cookie Policy.