Notice or court paper
Upload the paper that shows the actual deadline, hearing, repossession risk, or collection event first.
Deadline help
When the intake is being driven by a real deadline.
This page is for files where the problem is already active: a garnishment, foreclosure step, repossession risk, court date, or another event that means timing matters as much as document gathering.
01
When To Treat It As Urgent
These are the kinds of facts that should move the file out of normal gathering mode.
- A wage garnishment is already in place or about to start.
- A foreclosure notice, sale date, or mortgage-default deadline is active.
- A vehicle is already at risk of repossession or has already been taken.
- A lawsuit, hearing, examination, or other court event is already scheduled.
- A creditor deadline is concrete enough that waiting on a perfect packet would be a mistake.
02
Upload First
Send the records that prove the timing problem before you finish every other category.
Basic intake identity
Add the filer name, contact details, and any existing Submission ID so the urgent file lands in one place immediately.
Income and bank proof
Even in urgent files, recent pay and account records help the office start understanding what kind of case posture is realistic.
Notes about what is missing
If the rest of the packet is incomplete, say exactly what is still being gathered and when you expect it.
03
Related Guides
Use the more specific page if the deadline is tied to one recurring pressure point.
Wage garnishment
Use this if wages are already being taken or a payroll order is in motion.
Foreclosure
Use this if the mortgage file is being driven by sale timing, default notices, or lender deadlines.
Repossession
Use this if vehicle timing is the main reason the file needs to move quickly.
Submission status
If the file already exists, check status before starting a second intake thread.
Need to move the urgent file forward now?
Call or email the office if the deadline is active, then use the portal to keep the record organized instead of scattering documents across separate channels.