By Rovaryn Digital · June 27, 2026 · 6 min read
The Audit Request That Starts with an SSA Letter
The letter usually arrives without warning: a request from the Social Security Administration, or from the program manager acting on SSA's behalf, asking an Employment Network to produce the file supporting a specific milestone or outcome payment already received. Somewhere in that file needs to be proof the Ticket was actually assigned, proof the individualized work plan existed and was followed, and proof the services claimed were actually delivered in the months the EN is billing for. If that proof lives in three inboxes, a shared drive nobody has reorganized since 2022, and one counselor's memory, the response takes days instead of minutes — and a payment already booked can come back into question.
This is not a hypothetical. It's the ordinary operating reality of running an EN inside a program built on documented services, not just delivered ones. The record set below is what most ENs need to have on hand before that letter shows up, organized the way an auditor — or a new staff member covering a caseload — would actually need to find it.
By the end of this, you'll know exactly what belongs in an EN's documentation file, in what order it accumulates, and where the gaps usually open up.
What SSA Actually Requires an EN to Keep on File
Employment network documentation under Ticket to Work isn't one form — it's a layered record that builds as the case moves from assignment through payment. At a minimum, a defensible EN file typically contains: proof of Ticket assignment to the EN, the individual work plan (IWP) itself, contemporaneous notes or logs showing the services in the IWP were actually delivered, and the certification and payment-request paperwork tied to each milestone or outcome claim. Missing any one of these doesn't just create an audit headache — it can be the difference between a payment that holds and one that gets clawed back.
Because Ticket to Work operates under SSA's national program rules rather than state-by-state variation, the documentation expectations are more uniform than, say, workers' compensation reporting deadlines across different states. That uniformity is a relief, but it doesn't remove the obligation to check the current version of those rules directly with SSA's Ticket to Work program before treating any checklist — including this one — as final. Program specifications and payment-agreement terms are revised, and an EN's own payment agreement may carry additional documentation terms beyond the baseline.
The Individual Work Plan: The Record That Anchors Everything Else
The IWP is the document every later claim gets measured against. It's the beneficiary-specific plan the EN and the beneficiary agree to, describing the services and supports the EN will provide and the beneficiary's employment goal. Every later certification, every service log, every payment request should trace back to something the IWP actually promised — an auditor reading the file should be able to follow that thread without asking for clarification.
In practice, IWPs are where documentation habits either take hold or fall apart. A plan drafted once at intake and never revisited doesn't reflect a beneficiary whose goals shift, whose services change, or whose case gets reassigned to a different counselor. Keeping the individual work plan current — and keeping a dated record of any revision — is part of what makes the rest of the file defensible. A deeper walkthrough of what belongs in the IWP itself, and how to structure it so it holds up on review, is covered separately in the individual work plan breakdown.
Certifications of Services: Proving the Ticket Was Actually Assigned and Worked
Between the IWP and a payment request sits the certification layer: the documentation confirming that a Ticket was validly assigned to the EN, and that the services described in the IWP were delivered as claimed. This is frequently where files thin out. Counselors deliver the service — a job placement call, a resume review, a coaching session — but the contemporaneous record of that service, dated and tied to the specific beneficiary and IWP item, doesn't get written down until weeks later, if at all.
The fix isn't heroic effort at audit time; it's a habit of logging services at or near the point of delivery, in a format that maps directly to what the IWP promised and what the eventual certification will need to state. A closer look at what a certification of services actually needs to contain — and the common gaps that trip up otherwise solid files — is covered in the certification of services breakdown, and the broader reporting obligations an EN carries across the life of a case are laid out in the SSA Ticket to Work reporting requirements overview.
Payment Documentation: Milestone and Outcome Support
Every milestone or outcome payment an EN requests needs its own supporting packet: the payment request itself, the certification tying it back to services actually rendered, and — critically — a record of what's already been paid and what remains available under that beneficiary's Ticket. Overlapping or duplicate claims are one of the more avoidable ways an EN file draws scrutiny, and they're avoidable almost entirely with a running payment tracker per beneficiary rather than a memory of "I think we already billed for that milestone."
This is also where documentation and cash flow meet operationally. An EN juggling more than a handful of active Tickets across different milestone stages, without a single place tracking what's been requested, what's been paid, and what's outstanding, is exposed to both billing errors and slower cash collection. The mechanics of tracking EN payments against milestone and outcome stages are covered in the employment network payment tracker guide, and the payment-cycle structure itself — how milestone and outcome payments are earned and requested in the first place — is covered in the Ticket to Work employment network payments overview.
Building an Audit-Ready Habit, Not a Scramble
The EN files that hold up under review aren't the ones assembled carefully after the audit letter arrives — they're the ones where IWP, service logs, certifications, and payment records accumulate in the same structure, case after case, as a matter of routine. That structure matters more than any single document. An IWP without a matching service log is incomplete. A certification without a traceable IWP behind it is unsupported. A payment request without a certification is, functionally, a claim with nothing behind it.
For a solo CRC or a small EN team running this on spreadsheets and a shared folder, that structure is maintainable for a while — until caseloads grow, staff turn over, or SSA sends the letter for a case the original counselor no longer remembers in detail. At that point, the gap between "we probably have that" and "here it is, dated and tied to the milestone" becomes the entire difference in how the response goes.
Where This Fits Into a Practice's Workflow
Rehabilitation Management Suite organizes exactly this record set — IWP, service documentation, certifications, and payment history — around each beneficiary case, so the file an auditor asks for is the file that already exists, rather than one assembled under deadline pressure. It doesn't replace the professional judgment behind an IWP or a certification; it keeps the paper trail behind that judgment complete and easy to produce.
If a practice is still managing this across separate documents and a payment spreadsheet, the SSA Ticket-to-Work Case Documentation & Milestone Template Pack is a lighter starting point — a structured set of templates for the IWP, certifications, and milestone tracking that can be adopted without a system change. For practices ready to see how that documentation lives inside a full caseload and billing workflow, a walkthrough is available through a demo of Rehabilitation Management Suite.