Short answer: An SSA hearing runs on two dates. The notice must reach the claimant and representative at least 75 days before the hearing (20 CFR 404.938(a)). Written evidence must reach the judge no later than five business days before the hearing (20 CFR 404.935(a)). Between those two dates sits a countdown that most offices run on a paper calendar. AI workflow automation can keep that countdown from being the thing that gets missed, as long as the attorney or representative owns every deadline and every decision.
Most missed evidence deadlines are not caused by carelessness. They are caused by a notice that sat in a stack, a records request that was never followed up, or a date counted from the wrong day. The rules are short. The work of keeping them in view across a caseload is not.
What the rules actually set
Three provisions carry most of the countdown:
- The notice window. SSA must mail or serve notice of the hearing at least 75 days before it (20 CFR 404.938(a)). That notice states the issues, how to request a change of time or place, and the evidence deadline (404.938(b)(6)).
- The evidence cutoff. Each party must make every effort to get written evidence to the judge no later than five business days before the scheduled hearing (20 CFR 404.935(a)).
- The late-evidence exceptions. Under 404.935(b), late evidence can still be accepted in limited circumstances. One of them, in 404.935(b)(3)(iv), applies when the party actively and diligently sought the evidence, and it was not received or was received less than five business days before the hearing.
That last exception is the one that rewards good file management. “I asked for it” only helps if there is a dated record that you did.
Build the countdown from the notice, not from memory
Start each case with the notice itself. Confirm the hearing date, the time, the place or video link, and the stated evidence deadline. Then build four milestones on the same calendar:
- Notice received. Record the date the notice arrived, because it shows how much runway the case had.
- Records requests out. Every treating-source and agency request gets a sent date and a follow-up date.
- Internal review target. Set a date by which the representative has read the whole file, with enough time to send a second request.
- Evidence cutoff. Count back five business days from the hearing date. Confirm with the hearing office how it counts business days rather than guessing.
Counting by hand is where errors start. A hearing on a Monday does not make the cutoff the previous Monday. A holiday in the window moves the count. Let the calendar do the arithmetic, then check the result against the notice.
Where AI workflow automation earns its place
AI automation is useful for the parts of the countdown that repeat on every case:
- Pulling the hearing date, deadline and notice requirements from the notice into one case summary.
- Listing every open records request, with its sent date, last follow-up and the next follow-up due.
- Flagging a request that has gone quiet for longer than the firm’s own cadence allows.
- Drafting the follow-up letter or fax cover for an attorney to review and approve before it goes out.
- Keeping a log of every contact, so the diligence record exists when it is needed under 404.935(b).
Each of those tasks is repetitive and easy to forget on a busy week. None of them requires the software to decide what the case needs. Those decisions stay with the representative.
Keep the decision with a person. Automation can flag a deadline. Only the representative can decide whether a late record is worth a request to the judge, and whether the circumstances fit the exceptions in 404.935(b).
Where the case file comes in
A countdown is only as good as the list of evidence it is tracking. The earlier the file shows what is missing, the earlier the requests go out. Precision Case Lens is SSA disability case development software built by a Social Security Vocational Expert. It reads the whole record and shows what the record supports, what is inconsistent and what is missing, with every finding cited to exhibit and page. Hearing Prep Blueprints then arrive with the hearing strategy drafted for the representative to review, refine and finalize.
Five ways the countdown breaks
- Counting from the wrong date. Using the date the notice was signed instead of the hearing date.
- Requests without follow-up. A treating source is asked once, in the first month, and never again.
- No log. The evidence arrives late, but there is no dated record that it was sought, so the exception cannot be argued.
- Holiday and business-day errors. The cutoff lands a day earlier than the calendar showed.
- Last-week evidence. Records arrive the Friday before the hearing, with no time left to review them against the Blueprint.
Why the Friday before the hearing is the wrong time to find out
A records request that comes back four business days before the hearing leaves almost no room to read the new material against the Blueprint, to draft a request for a short continuance if one is needed, or to decide whether the exception in 404.935(b) applies. The same record that arrives three weeks out is a routine update. The countdown exists to move the second case toward the first.
What I would do this week
Pull every hearing set in the next 90 days, check each one against its notice, and write the five-business-day cutoff on the front of the file. Then list the open records requests and set a follow-up date for each. If the firm is not yet using any AI automation, start there: deadline reminders and a request log. They take an afternoon to set up and they protect the one exception a late record depends on.
Frequently Asked Questions
How much notice must SSA give before a hearing?
Under 20 CFR 404.938(a), SSA must mail or serve notice of the hearing at least 75 days before the hearing date. The notice also tells the claimant and representative that evidence should be submitted no later than five business days before the hearing, unless the conditions in 404.935(b) apply.
What is the evidence deadline at an SSA hearing?
Under 20 CFR 404.935(a), each party must make every effort to ensure the administrative law judge receives the evidence, and must inform SSA about or submit written evidence no later than five business days before the scheduled hearing. Evidence received later may be declined unless an exception applies.
What if a records request comes back late?
Under 20 CFR 404.935(b)(3)(iv), the judge may still accept late evidence if the party actively and diligently sought it and it was not received, or was received less than five business days before the hearing. That exception depends on a record of the requests actually made, so the requests must be logged when they are sent.
Can AI automation calculate my deadlines for me?
A workflow tool can read the hearing date, count the dates, and set reminders. The representative still confirms the hearing date against the notice, confirms how the hearing office counts business days, and owns every filing decision.
From the same founder: Precision AI Group — AI intake and follow-up for law firms, built around your firm’s rules. For SSA disability case development, see Precision Case Lens.
Find the missing evidence before the cutoff
Open a fully developed synthetic SSA case on the free Precision Case Lens demo to see how a record gap list is laid out, or talk to Allan about your own file.
Take the PCL Challenge Free TrialSee a Developed Case — Free DemoEach trial run returns a Premium Hearing Prep Blueprint. No login required to view the demo. Nothing to buy. Learn more at precisioncaselens.com or talk to Allan.
This article is general information for disability representatives, not legal advice. Precision Case Lens works for the representative; it does not represent claimants and does not guarantee outcomes.

