A program review is the Department of Education's direct examination of how your institution administers Title IV funds. Unlike the annual compliance audit, which is performed by an auditor you hire, a program review is conducted by Federal Student Aid's own staff — and it can end with a demand that you repay federal funds. The FSA Handbook and fsapartners.ed.gov describe the framework; this article walks through what actually happens and how to come out intact.

What triggers a review

ED selects institutions using a risk-based model plus statutory priorities. Common triggers include:

• Audit findings — especially repeat findings or a late/missing annual audit.
• Data anomalies — unusual patterns in disbursement, withdrawal, or enrollment reporting data ED already holds (NSLDS, COD, G5).
• Student complaints and referrals from accreditors, state agencies, or other federal agencies.
• Financial responsibility concerns — composite score problems, late refunds, letter-of-credit events.
• High-risk indicators in cohort default rates or program performance data.
• News coverage or whistleblower reports.

Some reviews are simply cyclical or randomly selected. You can't fully control selection — you can control what the reviewers find.

For schools entering Workforce Pell, assume scrutiny rises. A new program type, new reporting streams, and per-program eligibility decisions all create fresh data for ED's risk model. Clean FVT/GE and enrollment reporting is one of the cheapest ways to stay out of the selection pool.

The process, start to finish

1. Announcement and document request. Most reviews are announced in advance by letter, with a data/document request and a review period (typically the current and prior award years, though reviewers can expand scope). Expect to produce: policies and procedures, catalogs, organizational charts, third-party servicer contracts, fiscal records, and a complete student universe from which the review team selects its sample. Some reviews are unannounced — your front desk should know that federal reviewers may arrive with credentials and must be routed to a designated administrator immediately.

2. Entrance conference. The review team explains scope and logistics. Designate one point of contact through whom all documents and questions flow. Answer what is asked, accurately; do not volunteer speculation.

3. Fieldwork. Reviewers test sampled student files the same way an auditor would — eligibility, verification, disbursement timing, R2T4, SAP, attendance, enrollment reporting — but with more latitude to follow threads. At clock-hour schools, expect deep attention to attendance records, scheduled-hours R2T4 math, and payment-period progression. If a sampled file is missing, that is a finding; see records retention for why "we purged it" is not a defense inside the retention window.

4. Exit conference. Before leaving, the team previews likely findings. This is your best early-warning system. Take detailed notes, ask clarifying questions, and start assembling responsive documentation immediately — but don't argue the merits on the spot.

5. Program Review Report (PRR). The written report lists findings and required actions. You get a response window (the report will state the deadline). Your response is the main event: for each finding, either provide documentation showing compliance, or acknowledge the issue and show a full file review and corrective action. Findings often require you to review the entire population affected — not just the sampled files — and to quantify the dollar impact.

6. Final Program Review Determination (FPRD). After considering your response, ED issues the FPRD, which closes findings, assesses liabilities (funds to repay, with instructions), and may impose ongoing requirements. Appeal rights for disputed liabilities are described in the FPRD itself.

Findings and liabilities

Liabilities arise when funds were disbursed improperly — to ineligible students, in wrong amounts, without required documentation, or not returned under R2T4. When a sampled error rate is high, ED can require a full-file review or project the error across the population, which is how a handful of bad files becomes a six-figure demand. Serious findings can also cascade: referral to the Administrative Actions and Appeals Service Group, provisional certification, letter-of-credit requirements, or — in extreme cases — fine, limitation, suspension, or termination proceedings.

The most reliable mitigations are boring: complete files, contemporaneous attendance records, timely R2T4, and a documented corrective-action history that shows problems get fixed once and stay fixed.

Corrective action that actually closes findings

A corrective action plan that says "staff have been retrained" closes nothing. What closes findings:

• Root cause identified (a process gap, not a person).
• Full-population review where required, with a spreadsheet of every affected student and dollar amount.
• Repayment calculated and remitted per the FPRD instructions.
• Process change in writing — updated procedure, new checklist, system edit — with an owner and a date.
• Monitoring — evidence a quarter later that the new process is being followed.

Treat every program review finding as a template: whatever ED found, your next annual audit will test again.

What to do now

1. Designate and document your program review point of contact and an unannounced-visit protocol for front-line staff.
2. Keep a standing "review-ready" package: current policies, ECAR/PPA, catalogs, servicer contracts, and a reconciled student universe you could produce within days.
3. Self-test five files per quarter against the same elements reviewers sample — eligibility, disbursement timing, R2T4, attendance.
4. Close every audit finding with evidence, since audit findings are a leading trigger for review selection.
5. If you run short-term programs, get your Workforce Pell data house in order — start with building your cohort file so program-level questions have program-level answers.