logo
← Back to News
Title IVJuly 15, 2026· 6 min read

Satisfactory Academic Progress for Clock-Hour Title IV Programs: What the Rules Actually Require

SAP is one of the most misread areas of Title IV compliance at clock-hour schools. Here's what 34 CFR 668.34 actually requires — including the clock-hour treatment many schools get wrong — and the one real change on the horizon.

Avatar for Edudigital Editorial TeamEdudigital Editorial Team

Satisfactory Academic Progress (SAP) is one of the most misread areas of Title IV compliance at clock-hour schools — and much of the confusion comes from applying credit-hour and term-based assumptions to programs the regulation treats differently. Here’s what the SAP regulation at 34 CFR 668.34 actually requires, and what it doesn’t.

The two parts of a SAP policy

At its core, a school’s SAP policy has to measure progress two ways:

  • A qualitative measure — a minimum grade or its clock-hour equivalent.
  • A quantitative component and a maximum timeframe — the outer limit on how long a student can take to finish and still receive Title IV aid.

For an undergraduate program, the maximum timeframe is generally 150% of the published length of the program. For clock-hour programs, that length is expressed in calendar time (34 CFR 668.34).

The clock-hour nuance schools miss

The most common mistake is assuming clock-hour programs must apply the same term-based pace calculation as credit-hour programs. Per FSA’s own SAP guidance, the pace component is handled differently for clock-hour programs than for standard-term programs — so a policy copied from a credit-hour institution can impose a calculation the rules don’t require, or apply it incorrectly.

Rather than restate a specific formula here, confirm your policy directly against 34 CFR 668.34 and the current FSA Handbook (Volume 1). If your SAP policy was inherited from a credit-hour template, have your financial aid team check the pace and maximum-timeframe language against the clock-hour provisions specifically.

SAP does not govern leave of absence

Another frequent conflation: the SAP regulation does not address leave of absence (LOA). LOA is an enrollment-status and Return of Title IV (R2T4) concept, governed by 34 CFR 668.22, not the SAP rule. If your SAP procedures try to define LOA re-entry or pace treatment during a leave, you’re mixing two different regulatory frameworks. Keep LOA in your withdrawal and R2T4 procedures.

The one real change on the horizon

There is a genuine, dated Title IV change coming — but it’s R2T4, not SAP. The Return of Title IV Funds final rule takes effect July 1, 2026, and it changes how clock-hour programs calculate the percentage of a period completed (moving to a single scheduled-hours method, among other updates). If you operate clock-hour programs, that’s the deadline to plan around — and it’s separate from your SAP policy.

What to do now

  • Review your SAP policy against 34 CFR 668.34 and the current FSA Handbook — not a credit-hour template.
  • Confirm your maximum timeframe is expressed correctly for clock-hour programs (150% of published length, in calendar time).
  • Make sure LOA is handled in your withdrawal/R2T4 procedures, not folded into SAP.
  • Put the July 1, 2026 R2T4 rule on your compliance calendar and confirm your SIS will support the new clock-hour method.

Sources: 34 CFR 668.34; FSA Satisfactory Academic Progress guidance; 2025–26 FSA Handbook, Volume 1; U.S. Department of Education R2T4 regulations effective July 1, 2026. This article is general information, not compliance advice — verify against current federal guidance for your programs.

Built for compliance

Edudigital supports SAP, R2T4, and attendance workflows — with staff review checkpoints at every compliance-sensitive step.

Campus Operations, Unified

Get practical insights on compliance, enrollment, and student success for career-focused institutions.