THURSDAY, AUGUST 13, 2026
VOL. III · NO. 524
Price: Free · Records open to the public
Public records, reported plainly — from every county in the Treasure State.
Established 2026
Late Edition: Records refreshed THURSDAY, AUGUST 13, 2026 · 56 Counties updated within the last hour.
/ Hill County / Daily Police Activity Report - Hill County Sheriff's Office
Daily Report sheriff pending

Daily Police Activity Report - Hill County Sheriff's Office

Hill County Sheriff's Office Β· 06/23/26

County

Hill County

Agency

Hill County Sheriff's Office

Incidents Indexed

25

Published Summary

The Hill County Sheriff's Office responded to 23 incidents. Below is a full log:

- 7:35 PM – Unknown at Cat.

- 7:35 PM – Unknown at Cat.

- 7:35 PM – Unknown at Cat.

- 7:35 PM – Unknown at Cat.

- 7:35 PM – Unknown at Cat.

- 7:36 PM – Unknown at Cat.

- 7:36 PM – Unknown at Cat.

- 7:36 PM – Unknown at Cat.

- 7:36 PM – Unknown at Cat.

- 7:37 PM – Unknown at Cat.

- 7:37 PM – Unknown at Cat.

- 7:37 PM – Unknown at Cat.

- 7:37 PM – Unknown at Cat.

- 7:37 PM – INFO - Processing text blotter from email body β€” Cat: other

- 7:37 PM – INFO - Text blotter: county=Hill, incidents=23 β€” Cat: other

- 7:37 PM – INFO - Created text blotter batch #660 β€” Cat: other

- 7:37 PM – INFO - βœ“ Text blotter #660 complete: 19 incidents indexed β€” Cat: other

- 7:38 PM – Unknown at Cat.

- 7:38 PM – INFO - Generated 1 posts for text blotter #660 β€” Cat: other

- 7:38 PM – Unknown at Cat.

- 7:38 PM – INFO - Audited post #603: PASS, 0 PII flags β€” Cat: other

- 7:38 PM – Unknown at Cat.

- 7:38 PM – INFO - dispatch_alerts: blotter_id=660 county=Hill sent=2 β€” Cat: other

Incident Log Behind This Report

25 source-linked records shown
19:38

19:38:47,340

Unknown

INFO - dispatch_alerts: blotter_id=660 county=Hill sent=2

View incident
19:38

19:38:44,961

Unknown

INFO - Facebook auto-queued 1 audited post(s) for text blotter #660

View incident
19:38

19:38:44,954

Unknown

INFO - Blotter auditor: 1 post(s) audited, 0 flagged for review

View incident
19:38

19:38:44,952

Unknown

INFO - Audited post #603: PASS, 0 PII flags

View incident
19:38

19:38:44,949

Unknown

INFO - Using free local audit path for post 603 (set MB_USE_PAID_LLM=1 to use Claude)

View incident
19:38

19:38:44,852

Unknown

INFO - Generated 1 posts for text blotter #660

View incident
19:38

19:38:44,851

Unknown

INFO - generate_posts(blotter_id=660): created 1 digest post

View incident
19:37

19:37:45,817

Unknown

INFO - βœ… Text blotter #660 complete: 19 incidents indexed

View incident
19:37

19:37:45,809

Unknown

INFO - Created text blotter batch #660

View incident
19:37

19:37:45,808

Unknown

INFO - Skipped 4 duplicate incident(s) before insert for text blotter

View incident
19:37

19:37:45,803

Unknown

INFO - Text blotter: county=Hill, incidents=23

View incident
19:37

19:37:45,789

Unknown

INFO - Processing text blotter from email body

View incident
19:37

19:37:31,135

Unknown

INFO - Havre roster ingested: filename=JAILROSTER.docx fetched=40 new=0 updated=40 missing=44

View incident
19:37

19:37:31,116

Unknown

INFO - Parsed 40 records from HCSO roster docx: /root/montanablotter/uploads/20260623_JAILROSTER.docx

View incident
19:37

19:37:31,080

Unknown

INFO - Havre roster DOCX saved: message_id= <CO6PR22MB2579C00C980E77F3A0A6723FAAEE2@CO6PR22MB2579.namprd22.prod.outlook.com> filename=20260623_JAILROSTER.docx path=/root/montanablotter/uploads/20260623_JAILROSTER.docx ro...

View incident
19:37

19:37:31,078

Unknown

INFO - Routing Havre PD roster email to jail_bookings pipeline: subject='JAILROSTER 6-23-26' sender='reichl <reichl@hillso.org>'

View incident
19:36

19:36:06,788

Unknown

INFO - Havre roster ingested: filename=JAILROSTER.docx fetched=44 new=0 updated=44 missing=38

View incident
19:36

19:36:06,768

Unknown

INFO - Parsed 44 records from HCSO roster docx: /root/montanablotter/uploads/20260622_JAILROSTER.docx

View incident
19:36

19:36:06,731

Unknown

INFO - Havre roster DOCX saved: message_id= <CO6PR22MB257947C81F03AD0F47B22217AAEF2@CO6PR22MB2579.namprd22.prod.outlook.com> filename=20260622_JAILROSTER.docx path=/root/montanablotter/uploads/20260622_JAILROSTER.docx ro...

View incident
19:36

19:36:06,729

Unknown

INFO - Routing Havre PD roster email to jail_bookings pipeline: subject='JAILROSTER - 6/22/26' sender='reichl <reichl@hillso.org>'

View incident
19:35

19:35:18,977

Unknown

INFO - Havre roster ingested: filename=JAILROSTER.docx fetched=44 new=0 updated=44 missing=40

View incident
19:35

19:35:18,960

Unknown

INFO - Parsed 44 records from HCSO roster docx: /root/montanablotter/uploads/20260621_JAILROSTER.docx

View incident
19:35

19:35:18,921

Unknown

INFO - Havre roster DOCX saved: message_id= <DS0PR22MB597192150633A07E9EE5DAE6A8E02@DS0PR22MB5971.namprd22.prod.outlook.com> filename=20260621_JAILROSTER.docx path=/root/montanablotter/uploads/20260621_JAILROSTER.docx ro...

View incident
19:35

19:35:18,919

Unknown

INFO - Routing Havre PD roster email to jail_bookings pipeline: subject='Hill County roster' sender='Kelly Bracha <bracha@hillso.org>'

View incident
19:35

19:35:07,065

Unknown

INFO - Havre roster published to jail_bookings: message_id= <CO6PR22MB25796461FE93272C7123EB79AAE12@CO6PR22MB2579.namprd22.prod.outlook.com> filename=JAILROSTER.docx county=Hill

View incident

County Alert

Get notified when new activity is posted for Hill County

THURSDAY, AUGUST 13, 2026
— A-1 —
© 2026 Montana Blotter · Free Public Records
Editorial Standards

Montana Blotter is designed to make public records and public meeting information easier to access. It is not a government office, and it does not replace official notice, clerk records, court files, or agency databases.

1. Primary Source Rule
We prefer direct links to official county, city, court, sheriff, police, and state judiciary pages. Where possible, each page should point readers back to the original public record, agenda, minutes page, or official document listing.

2. What We Standardize
Date and time formatting — location and body-name labeling — document labels such as agenda, packet, or minutes — searchable statewide filters and metadata.

3. What We Do Not Claim
We do not claim to be the official keeper of public records. We do not guarantee that a third-party government site is complete, current, or correctly maintained. We do not treat summaries or extracted text as a substitute for the official source file.

4. Update Cadence
Automated sources are checked on a recurring basis. If a source is stale, broken, or moved, the originating public body remains the authoritative reference until the source is repaired.

5. Provenance and Visibility
We aim to show where information came from, when it was last refreshed, and how users can verify it.

6. Redactions and Sensitive Material
We may review records for obvious sensitivity, legal restrictions, or redaction issues. The existence of a public record does not automatically mean every field or derivative presentation should be amplified without review.

7. Corrections
If a source link breaks, a meeting is mislabeled, a record is duplicated, or a page needs clarification, see the Corrections Policy for the reporting workflow.

8. Government and Clerk Communications
If you work for a Montana public body and need a source updated, corrected, or removed, contact us directly. We prefer exact URLs, dates, and a brief explanation of the change.

9. Contact
Montana Blotter — records@montanablotter.com

Read full standards →

Corrections Policy

We want corrections requests to be specific, easy to verify, and fast to act on. The more concrete the report, the faster it can be reviewed.

1. What To Report
Broken official source links — moved agenda or minutes pages — incorrect meeting date, body name, or location label — duplicate records or meetings — stale source pages — material factual errors in a summary or description.

2. What To Include
The exact Montana Blotter URL — the exact official source URL that should be used — a short description of what is wrong — if timing matters, the date and time the official source changed.

3. Where To Send It
Email records@montanablotter.com with subject line Correction Request or Source Update. If you represent a government office, say so in the message.

4. Review Standard
We review corrections against the official source when available. If a report cannot be verified, we may ask for a clarifying URL, screenshot, or exact document reference before changing the page.

5. Response Goal
Our goal is to review straightforward source and labeling issues within two business days. Complex disputes, legal issues, and record-sensitivity questions may take longer.

6. How Fixes Are Handled
Broken or moved source URLs are updated at the source-config level when possible. Mislabeled dates, titles, or locations are corrected in the public presentation. If a government source removes or replaces a document, the official source controls.

7. Limits
A correction request does not automatically guarantee removal. Montana Blotter may preserve accurate public-record references while updating labels, links, timestamps, or explanatory text.

Read full corrections policy →

Montana Laws Reference
Browse Montana Blotter
Sign In Join

Look up records

Public Meetings Jail Rosters New Bookings Bail Bonds Case Tracking

Maps & trends

Crime Map Crime Data Leaderboard

Safety alerts

Code Violations License Sanctions Offender Alerts Active Warrants

News & help

Blog Know Your Rights Help & Support

Stay updated

Subscribe