Clock-Hour vs Credit-Hour: Why Your SIS Choice Is Different

A credit-hour program measures learning in credits tied to seat time and outside work. A clock-hour program measures it in actual hours the student is present and instructed. That sounds like a unit conversion. It is not. The clock-hour world ties federal aid directly to attendance, and that one fact ripples through attendance tracking, Satisfactory Academic Progress, Return of Title IV Funds, and the disbursement schedule. A platform designed around credit hours can look like it supports clock hours while quietly mishandling every one of those.

If you run a clock-hour program, the question is not whether a system can store an hours number. It is whether attendance is the spine the whole compliance model hangs from. In credit-hour systems it rarely is.

Where the two models actually diverge

Attendance: in a clock-hour program, hours present are the official academic record, not a courtesy log, and a missed hour is a compliance event. Disbursements: clock-hour aid is typically released after a student completes both the scheduled hours and the weeks of instructional time in a payment period, so you cannot disburse on a calendar date alone, you disburse on hours earned. SAP: pace is measured in hours completed against hours scheduled, and an attendance floor often sits inside the standard. R2T4: the percentage of the period completed is scheduled hours through the last date of attendance, so the withdrawal calculation is an attendance calculation. Across all four, the common thread is the same: the clock-hour model fuses attendance to money.

How a credit-hour SIS quietly breaks

The failure is rarely a hard error. It is a system that lets you disburse on a date instead of on completed hours, that computes pace in credits and bolts on an hours field nobody reconciles, that asks you to enter a last date of attendance by hand for R2T4 because attendance lives somewhere else, that cannot express an attendance-based SAP floor. Each gap is survivable alone. Together they mean your compliance posture depends on staff remembering to do by hand what the system should enforce, which is exactly what a program review finds.

How ApolloSRM handles clock-hour programs

ApolloSRM treats attendance as a first-class part of the student record, captured against the student and shared by every surface that needs it. That one decision is what makes the rest correct: pace and SAP can be measured in scheduled versus completed hours with an attendance floor folded into the standard, the last date of attendance flows straight into the R2T4 worksheet instead of being retyped, and the same attendance figure feeds the registrar, the aid office, the student view, and your reporting. One attendance model, many readers, instead of an hours field stranded next to a credit-hour engine.

Frequently asked questions

What is the difference between a clock hour and a credit hour?

A clock hour is a unit of actual attendance, typically about 50 to 60 minutes of instruction. A credit hour is an academic unit that represents class time plus expected outside work over a term. Clock-hour programs measure progress and aid eligibility by hours physically attended; credit-hour programs measure them by credits earned over calendar time.

Why does clock-hour vs credit-hour matter for financial aid?

In clock-hour programs, Title IV disbursements are tied to completing both scheduled hours and weeks of instructional time, SAP pace is measured in hours, and R2T4 uses scheduled hours through the last date of attendance. Attendance is directly linked to aid, so the calculations differ from a credit-hour program at every step.

Can a credit-hour SIS handle a clock-hour program?

Many can store an hours value, but storing a number is not the same as enforcing the clock-hour model. The risk is disbursing on a date instead of completed hours, computing SAP in credits, and re-keying the last date of attendance for R2T4. A clock-hour program needs attendance to be the spine of the record, not an add-on field.