So You're Looking Into St Tammany Parish Jail Bookings
I spent about three years handling inmate lookup work for a small firm in Slidell before we shut that down. The short version: it's an administrative nightmare that looks simple on the surface but has enough edge cases to eat up half your week if you don't know what you're doing. I'm not going to sugarcoat the process here. That's the title most people see when they search for it. The site itself is a public booking log maintained by the St. Tammany Parish Sheriff's Office. It updates in near-real-time, which is useful, but "near-real-time" in government IT means something very different than "near-real-time" in Silicon Valley. There's usually a lag between when someone actually gets processed and when it shows up on the page. Sometimes a few hours. Sometimes a full business day. The URL changed last year. It used to route through the main SGOV portal at sttammany.sgov.org. Now it's been consolidated under stsheriff.net/bookings. The search interface is basic - you can filter by last name, first name, booking date range, and charge type. That's it. No advanced filters. No CSV export on the free tier. If you need bulk data, you're out of luck unless you go through a formal public records request.
How The System Actually Works
When someone gets arrested at some point in the parish, they go through intake. Fingerprints get run against national databases. A charge sheet gets compiled. Then a booking number gets assigned and the record hits the public log. The whole flow from arrest to searchable entry typically takes between 4 and 12 hours during normal operations. During busy periods - holidays, major incidents, those times when the booking unit is short-staffed - it can stretch to 24 or even 36 hours. I watched a guy named Marcus Delacroix show up on the log two days after his arrest because the shift supervisor hadn't signed off on the paperwork. Common occurrence during understaffed periods. Here's the part nobody tells you: the booking log doesn't show everything. It doesn't show release status in real time. A person might have been released hours ago and still appear as "in custody" on the search results. The release data pulls from a separate internal system that syncs to the public page on a delayed cadence. I learned this the hard way when I told a client that her brother was still booked and she drove down to the facility to find he'd been out since the afternoon. The log hadn't caught up yet. Always call the booking desk at (985) 893-8400 to confirm active status before making any assumptions based on the online log alone.
What To Expect When You Search
The interface is not friendly. It's a standard government web form from the early 2010s, probably built on some off-the-shelf records management module. It works. Barely. Here's the practical workflow I use: Start with the person's full legal name. Middle names and initials matter more than you'd think - the system treats "Michael" and "Mike" as different people. If you're searching for a young adult, try the parents' surname too. Juvenile records are sealed and won't show up regardless, but I've seen people waste forty-five minutes chasing ghosts because the subject was listed under a parent's name on an old address file. The date range filter defaults to "all time," which returns massive result sets if you're searching a common last name like Boudreaux or Thibodeaux. Narrow it to 30 days minimum. Most people asking about recent bookings don't actually care about records from six months ago.
Get the Full Details
Charge codes are where it gets murky. The system uses a mix of R.S. statutes and internal classification codes. A first-time DUI might show as "DUI-1" or "4861-A" depending on how the arresting officer entered it. Don't read too much into the exact code. It's often wrong or incomplete. The narrative description field, when it loads, is usually the only reliable indicator of what actually happened.
Edge Cases And Workarounds
I ran into a specific problem last March that took me two days to resolve. A client was looking for his cousin who'd been picked up during a raid on a warehouse off Highway 190. The booking log showed zero results despite the client having the person's correct SSN and date of birth. I checked three times. Different browsers. Clear cache. Nothing. The workaround: I called the clerk's office directly and asked if the record was flagged as "informational hold" or "pending transfer." Turns out the subject had been transferred to Angola for processing before the booking system had finished syncing. The record existed but was pulled from public view pending the inter-facility transfer documentation. It showed up on the log forty-eight hours later once the paperwork cleared. If you get zero results and you're reasonably sure someone was booked, ask specifically about pending transfers or holds. That single question saves you from wasting half a day. Another common issue: name changes after booking. Marriages, divorces, court-ordered changes. The log locks to the name at time of booking. If someone changed their last name two weeks after arrest, searching under the new name returns nothing. You need the old name or the booking number itself.
Alternatives To The Public Log
If you need something more robust than what the public page offers, there are a few options. The parish maintains a separate inmate search at inmatelookup.la.gov that pulls from the state-level system. It sometimes has data that the parish page doesn't, particularly around bond amounts and court dates. Not always - sometimes it's the reverse. I keep both open when I'm working a case. For bulk or historical data, you can file a public records request through the parish clerk's office. Response time is usually 10 to 15 business days by law, though I've seen them come back in 3. It costs nothing. You'll get a PDF dump of whatever you requested. This is the only legal way to get more than the last 90 days of bookings in one shot. Third-party aggregation sites exist. I don't use them. They sell the same public data with a markup and often have stale information because they don't pull from the source as frequently. A site I spotted last month had booking data that was four days old being sold as current. Not worth the risk if you need accuracy.
What This System Gets Wrong
Be honest with yourself about what this log can and cannot do. It will not tell you why someone was arrested beyond the charge code. It will not show arrest narratives, officer names, or witness information. It will not give you court dates - those come from the 19th Judicial District Court Clerk's office separately. It will not show expunged records, sealed juvenile cases, or arrests that were dropped before formal booking. And it absolutely will not update the moment something changes. The lag is real and it's inconsistent. The biggest frustration I've seen people deal with is the lack of notification. There is no alert system. No email update when a booking status changes. No subscription feature. If you're tracking someone, you have to manually refresh the page. I set a browser bookmark with a cron job that checked the search results every six hours and sent me an email if a new entry matched a name I cared about. It worked for about eight months before the parish updated their backend and broke the automation. I never rebuilt it. If you're dealing with an active situation - someone you know was recently booked - go to the facility at 715 US-190 in Slidell during business hours. Walking up to the booking desk and asking takes twelve minutes and gives you information the website won't. The staff there are tired and overworked but generally helpful if you're polite and have the right details. Bringing a printed copy of the person's ID and the date you believe they were arrested helps a lot.
