The questions people ask government are public before the documents are.
Every day, thousands of people file records requests with city and state governments. Read one at a time, they are errands. Read at scale, every day, they are an early-warning feed of who is about to sue whom, whose loss is being worked, and what deal is being diligenced. PreDocket reads them and delivers the ones on your watchlist first.
Pre-launch. Access is granted by request. Sample data shown throughout.
A signal forms weeks before it reaches a docket.
By the time a case is filed or a claim is litigated, the work started long ago. The investigator, the carrier, the opposing firm, the diligence team have all been pulling records for weeks. Those pulls are public the moment they land, and nobody reads them together.
A request names the parties, the loss date, and the theory in plain language before a single document is produced. PreDocket reads that record at scale so you see the matter form while it is still early.
When a warehouse in Los Angeles burned, the same building drew six separate records requests in two weeks. One of them pulled the same building's 2024 prior fire.
That pull is prior-notice evidence, filed in the open, weeks before anyone brought a claim.
We watch, daily
We monitor hundreds of public-records portals every day, across cities and states, so no window closes before we see it.
We classify and cluster
We type each request into the signals that mean money in motion, then cluster the ones that point at the same event, party, or property.
We deliver, first
You get the signals on your watchlist before anyone else is reading them, with the request text and why it matters attached.
An insurer or its investigator pulls a loss report. The insured, carrier, and loss date, named before any suit.
A firm pulls a property's dispatch or incident history. A premises or liability theory being built.
Repeated requests around one operator or site signal an enforcement or compliance action forming.
Requests for permits, liens, or code history that read like a company or asset under strain.
A records pull on a company or building that looks like a deal being diligenced ahead of a transaction.
Finder and recovery activity around estates, property, and funds that are owed and unclaimed.
Subrogation teams
See a recoverable loss the day the investigator starts pulling records, not the day the file lands on your desk. Get to the subrogation lead before the trail cools.
See the subrogation sample →Litigation funders
Read the pre-litigation window at scale. See which matters are being worked, by whom, and against whom, weeks before a complaint is on file.
See the funder sample →Insurers
Watch for the loss reports, incident pulls, and regulatory activity that touch your book, and price or reserve against them earlier.
See the full feed →Diligence shops
Catch the records pulls that read like a deal in motion or a company under strain, and know who else is already looking.
See the full feed →Reading one portal is easy. Watching all of them is an operation.
Any analyst can read one city's request log for one matter. Watching hundreds of portals every day, and resolving the noise into named, clustered events, is a machine and a staff you would have to build and run. The most sophisticated requesters already do a version of this by hand, one portal at a time.
PreDocket does it across every portal at once, refreshed daily, typed and clustered, with your watchlist applied.
Request access
PreDocket is pre-launch and access is granted by request. Sourcing and method are shared on a call or under NDA.