Every institution that participates in Title IV must report its students' enrollment to the National Student Loan Data System (NSLDS). The obligation is easy to describe and easy to fail: NSLDS enrollment reporting is one of the most frequently cited findings in program reviews and compliance audits, and at small clock-hour schools it is often nobody's clearly assigned job. This article covers what must be reported, on what clock, and what happens when it goes wrong.

What you report

Enrollment reporting operates at two levels, and both are mandatory:

• Campus-level enrollment status — whether each Title IV student is enrolled full-time, three-quarter-time, half-time, less-than-half-time, withdrawn, graduated, on an approved leave of absence, or never attended, with an effective date for each status.
• Program-level enrollment — for each program the student is enrolled in: the program identifiers (CIP code, credential level, program length), the student's status in that program, and program-specific dates.

Program-level reporting is where clock-hour schools most often fall down. If your school offers a 600-hour program and a 1,500-hour program, NSLDS must know which one each student is in — the data feeds downstream processes, including loan servicing, aggregate eligibility checks, and, increasingly, the metrics plumbing that supports program-level accountability reporting.

Most schools report through the NSLDS enrollment reporting roster process — either directly on the NSLDS Professional Access site, via batch files, or through a servicer such as the National Student Clearinghouse. Using a servicer does not transfer the compliance obligation: the institution remains responsible for the accuracy and timeliness of what NSLDS receives.

When you report

Two clocks run simultaneously:

Institutions set a reporting schedule in NSLDS; the schedule must produce reporting at least every two months. Confirm the exact certification and status-change deadlines against the current NSLDS Enrollment Reporting Guide on the FSA Knowledge Center — the operative numbers live there, and ED has tightened them over the years.

For clock-hour schools the statuses that matter most are W (withdrawn) and G (graduated), each with an accurate effective date. The withdrawal effective date should align with the last date of attendance you determined for the R2T4 calculation — a mismatch between the R2T4 file and NSLDS is a finding auditors check for specifically.

Why accuracy matters downstream

NSLDS enrollment data is not a bureaucratic side channel. It drives real consequences:

• Loan servicing. A late-reported withdrawal delays a borrower's grace period start, causing interest and repayment-timing errors that trace back to your school.
• Eligibility at the next school. Transfer monitoring and aggregate checks rely on your data being right.
• Your own metrics. Program-level enrollment data increasingly feeds accountability reporting. Schools building Workforce Pell cohort data will find that clean NSLDS program-level reporting and clean cohort tracking are the same discipline — sloppy enrollment records poison both.

Workforce Pell raises the stakes on that last point considerably. Under the Workforce Pell final rule (91 FR 29254), ED compiles program completer lists from NSLDS data, and institutions get a 60-day window to correct the compiled lists. That changes the character of the obligation: NSLDS is no longer just a reporting channel whose errors surface in audits — it is the source of record for who counts as a completer in your 70/70 completion data. A graduation reported late, with the wrong effective date, or against the wrong program record shows up as a distorted completer list, and you have 60 days from compilation to catch and correct it. The correction window is a safety net, not a workflow: if your ordinary reporting is stale, you are reconstructing a term's worth of registrar history against a deadline, for a list that feeds a rate with program-eligibility consequences. Schools running Workforce Pell programs should treat every completion and withdrawal as an NSLDS event in the same week it happens — and should reconcile their own cohort file against each ED-compiled completer list the day it arrives, so the 60-day clock is spent fixing discrepancies rather than discovering them.

Common findings

Program reviews and annual compliance audits repeatedly surface the same enrollment reporting failures:

• Late or missed roster responses — the roster arrives, nobody owns it, it goes stale.
• Withdrawals reported late or not at all — especially unofficial withdrawals identified after the fact, where the school completes the R2T4 but never updates NSLDS.
• Wrong effective dates — status changes reported with the processing date instead of the actual date of the change.
• Missing or incorrect program-level data — wrong CIP code, wrong program length, students reported at campus level only.
• Servicer set-and-forget — the school contracts with a servicer, then never reconciles what the servicer actually transmitted against its own records.

Consequences scale with severity. Enrollment reporting failures produce audit findings and program review findings; systematic failures can lead to fines and, in extreme cases, jeopardize Title IV participation. More prosaically, every finding costs staff time, auditor time, and credibility in your next review.

Enrollment reporting errors also compound other problems: if the withdrawal date in NSLDS disagrees with the date used in your R2T4 file, one of the two is wrong, and the reviewer will pull the thread. Keep the enrollment reporting workflow attached to the same event stream that drives your withdrawal processing and disbursement gating.

What to do now

1. Assign a named owner for NSLDS enrollment reporting, with a named backup, and put roster deadlines on a shared compliance calendar.
2. Pull your current NSLDS reporting schedule and confirm rosters are being certified on time — then spot-check the last two roster submissions against your SIS for accuracy.
3. Reconcile program-level data for every active student: CIP code, credential level, program length. Fix mismatches now, before an auditor samples them.
4. Wire status changes to events, not memory — every withdrawal, graduation, and LOA should trigger an NSLDS update as part of the same checklist that triggers R2T4 review.
5. Download the current NSLDS Enrollment Reporting Guide from the FSA Knowledge Center and verify your timelines against it — do not rely on what the deadlines were when your procedures were last written.