Debt Collection and the Automatic Stay
When a debtor files for bankruptcy, the automatic stay under 11 U.S.C. § 362 takes effect at the moment of filing — not when you learn about it, not when it appears in a credit report, not when a letter arrives. If your outreach cycle runs while a stay is in effect, that contact is a potential sanctions event. The exposure window is the gap between Day 0 and the day your operations team finds out.
The Automatic Stay and Your Exposure
Credit bureaus typically reflect a bankruptcy filing 7 to 30 days after the petition is filed. Manual PACER checks happen on whatever cadence your team runs them. Neither closes the gap reliably. A single collection call into that window — one automated outreach, one letter generated before the next review cycle — is enough to constitute a stay violation.
The practical problem is not that collectors are unaware of bankruptcy law. It is that awareness and operational awareness are different things. Knowing that the stay exists does not help if your first notice of the filing arrives three weeks after the fact.
What the Docket Tells You
The bankruptcy docket is the authoritative record for everything that matters to a collections operation. It reflects the case from the moment of filing. Key events that appear on the docket include:
- The petition itself — chapter filed, filing date, assigned district
- Orders granting, modifying, or lifting the automatic stay
- The bar date for proofs of claim
- Plan confirmation or dismissal
- The discharge order
Each of these events carries operational consequence: the petition triggers an outreach halt; a stay modification may reopen collection on certain assets; the discharge signals final file closure. The docket tells you which event has occurred and when.
How DocketLayer Fits In
DocketLayer monitors a known case — identified by a court code and a case number — and returns what has changed since the last time you checked. We do not search by debtor name. The workflow assumes you have already identified that a case exists: through a PACER alert service, a credit bureau notification, a client disclosure, or any other source.
Once you have a case number, the monitoring becomes continuous and structured. An agent checks each case in your active portfolio on whatever cadence you set, receives a structured response, and takes action — pausing outreach, flagging a file, scheduling a proof-of-claim review — without requiring a human to run a manual check. Each query costs $0.99. A case with no new activity since the last check returns quickly and costs the same as one with significant docket movement.
What You Need to Query
Every DocketLayer query requires two things: a court code and a case number. The court code identifies the bankruptcy district — deb for the District of Delaware, nyeb for the Eastern District of New York, cacb for the Central District of California. The full list is at docketlayer.ai/coverage or returned by GET /v2/status.
The case number is the identifier assigned by the court at filing. For bankruptcy cases this typically follows a district-specific format — the court registry entry for each bankruptcy court includes the expected pattern and an example.
What to Monitor Once You Have a Case
The most common monitoring pattern for collections is polling at a daily cadence using the last_checked parameter. Pass the timestamp of your last query; DocketLayer returns only activity since that time. This keeps responses tight and processing efficient across a large portfolio.
Specific events worth flagging in your workflow:
- Any new filing within 24 hours of the petition — indicates active counsel engagement
- A stay modification or relief order — may restore collection rights on specific assets
- A dismissal without discharge — case ends; collection rights generally restored
- A discharge order — permanent injunction on collecting discharged debts; close the file
The /v2/monitor endpoint is designed for this use case: it returns a lightweight delta — count of new entries and most recent activity timestamp — without the full case payload. Use it for high-frequency polling across a large portfolio, and call /v2/case with context=full only when activity is detected.