How the Peoria County Daily Commitment Report Actually Works
The Peoria County Sheriff's Office maintains a daily commitment report that tracks who comes into the jail, who gets released, and who's currently housed there. It's not a single spreadsheet you can just download and import into Excel and be done with it. The system is managed through the Sheriff's administrative records, and the booking sheet is the operational backbone of that process. If you've ever tried to pull this data for research, legal work, or just general curiosity, you'll run into the same friction points I have. The most direct path is the Peoria County Sheriff's official website, under the Jail or Inmate Search section. They publish a daily roster that functions as the de facto commitment report. You'll find it updated once per day, usually within a few hours of the prior evening's shift change. The file is often in PDF format, sometimes as a CSV dump if the county has pushed toward open data. You do not need an account to access the basic roster. You do need one if you want historical data older than 30 days, or if you're trying to pull specific booking numbers rather than the full daily list. Here is the thing nobody tells you about the download process: the PDF version is almost always image-based or uses weird table formatting that makes copying and pasting a nightmare. I spent three weeks trying to parse the PDF directly before I realized the county also maintains a separate data feed behind the inmate search portal. If you can live with slightly less real-time data, the CSV export from the search interface is significantly more machine-readable. The tradeoff is that it only goes back about 90 days, whereas the daily PDFs are archived indefinitely on their server.
What the Booking Sheet Actually Contains
A standard daily commitment report from Peoria County includes the booking number, full name, date of birth, race, sex, booking date and time, the charging offense or bond amount, and whether the individual is currently incarcerated or has been released. It does not include arrest reports, case numbers tied to specific court filings, or detailed criminal history beyond the current charge. That requires a separate request through the county clerk's office or the Illinois Court Records system. The bond column is where things get murky. Sometimes the field is blank because the individual is being held without bond on a different charge from a prior booking. Sometimes it lists a dollar amount that was set at a bail hearing that hasn't happened yet, which means the number is a recommendation rather than a court order. I learned this the hard way when I was cross-referencing commitment report data with circuit court dockets and found five cases where the bond on the booking sheet did not match the bond set by the judge. The booking sheet reflects the initial magistrate's setting, not the judicial review outcome, and the two rarely happen on the same calendar day.
Practical Extraction Methods
If you need to work with this data in bulk, your best option is to write a small script that polls the sheriff's site daily and captures the CSV export. The URL structure tends to be stable, which means once you have the pattern mapped, it runs on autopilot. I built a Python script using requests and BeautifulSoup that handles the nightly grab, strips out the header rows that shift position depending on whether the county included overflow housing transfers, and outputs a clean consolidated file. The script runs in about 12 seconds per fetch. It is not elegant, but it works. For one-off requests, the manual approach is faster than you might expect. The daily PDF typically contains between 40 and 120 names depending on the day. A single person can transcribe that in roughly 20 minutes if they are just pulling the key fields. The bottleneck is not the transcription itself, it is verifying that a name on the roster actually matches the person you are looking for, especially when common names appear multiple times in a single shift. I stopped trying to match by name alone and started using the booking number and date of birth as the primary key. It eliminated about 80 percent of the false positives I was dealing with.
Get the Full Details
Where the Data Falls Short
The daily commitment report is not a comprehensive record of incarceration in Peoria County. It does not capture individuals who were transferred from other facilities and processed through Peoria as a receiving jail. It does not include people who were booked and released within the same shift if the county's reporting cutoff falls between their intake and their release. There is a roughly four-hour window every day where people can cycle through the system and never appear on the roster at all. I discovered this by tracking a specific case through court records and realizing the person's booking existed in the circuit court file but had zero presence on any daily commitment report for the dates in question. The workaround was to pull the arrest log from the Peoria County Sheriff's press release archive, which captures all bookings including same-day releases, and merge it with the commitment report manually. Another limitation is that the booking sheet does not distinguish between original bookings and re-bookings. If someone was released and then re-arrested the same week, they will appear as two separate entries with no linking mechanism. There is no flag that says this person was previously incarcerated in the same reporting period. For research purposes this means you will overcount unique individuals if you are not deduplicating by date of birth and name. For operational purposes it means the county knows who is who, but the public data does not carry that institutional knowledge.
Common Pitfalls to Avoid
The most frequent mistake I see people make is assuming the commitment report is chronological. It is not. The PDF is organized by shift, and within each shift it is roughly ordered by booking time, but the ordering is not guaranteed. If you are building a timeline of events, you must sort by the booking date and time field yourself. The visual layout of the document will mislead you into thinking the top entry happened first, which it usually does but not always. A second mistake is treating the release date as definitive. The commitment report marks a person as released based on the custodial status at the time the report was generated, not necessarily the actual release timestamp. Someone marked as released at 6 PM may have physically left the facility at 2 PM, or may have been transferred to another county rather than released into the community. If you need precise release timing, you have to pull the individual booking file from the records division, and that requires a formal public records request under the Illinois Freedom of Information Act. The response time is typically five to ten business days, and there is no fee for basic access, but the county can redact certain fields if they fall under arrestee privacy exemptions.
Legal and Ethical Boundaries
Using the daily commitment report for commercial purposes, such as building a people-search product or selling the data, is not explicitly prohibited by the county, but it is a gray area that the Sheriff's Office has pushed back on in the past. The data is public, but the county's terms of use for their online portal prohibit automated scraping at scale. I have seen at least one entity get their IP address blocked after pulling more than 200 requests in a single day. The fix is straightforward: space your requests out, use the CSV export endpoint instead of the PDF, and do not mirror the data on your own server without adding substantial transformation or analysis on top of it. When reporting on the data, it is worth noting that the commitment report is an administrative record, not a legal finding. A booking does not establish guilt. Charges can be dropped, reduced, or dismissed after the individual appears on the sheet. I have corrected my own published analyses multiple times when court outcomes diverged from the initial booking data. The commitment report is a snapshot of custody status, not a summary of case resolution.
Final Notes on Working With This Data
If you are building a database from Peoria County commitment reports, plan to spend about two hours on initial setup for data cleaning and validation, and then roughly 15 minutes per day for ongoing updates if you are tracking current population. The real work is in the deduplication logic and the reconciliation with court records, which is where most projects stall. The data itself is reliable within its own scope. The scope is narrower than most people assume, and that is the gap you need to account for before you start building anything on top of it.
