The Workforce Pell completion metric is unforgiving in one specific way: it is a deadline test. At least 70 percent of program participants must complete within 150 percent of the normal time to completion. A student who finishes in week 19 of a 12-week program is, for this metric, indistinguishable from a student who never finished at all. That makes completion tracking a scheduling problem, not just a records problem — and scheduling problems are solvable with monitoring.

Computing each student's deadline

The formula is simple: deadline = start date + (1.5 × normal completion weeks).

(Workforce Pell programs run at least 8 but fewer than 15 weeks, so every deadline lands between 12 and 21 weeks after start.)

Three practical rules:

1. "Normal time" is the published length you certified for the program — the same figure in your program approval documents and your cohort file's normal_completion_weeks field. Don't let marketing materials, catalogs, and certification documents disagree on program length; any mismatch surfaces in an audit or review.
2. Compute the deadline at enrollment and store it (deadline_150) rather than recalculating ad hoc. A stored deadline can be monitored; a formula in someone's head cannot.
3. Half-weeks: pick a convention and document it. For odd-week programs (1.5 × 9 = 13.5 weeks), decide whether you round to the scheduled class day and write the convention into your methodology notes. Confirm whether your state's methodology prescribes a convention before you rely on yours.

If your school runs clock-hour Title IV programs, you already track a 150 percent maximum timeframe for SAP. The parallel is useful — the muscle memory transfers — but do not assume the two calculations are interchangeable. SAP is governed by the FSA Handbook; the 70/70 completion window is governed by the final rule (FR 2026-10013) and, in the transitional years, your state's methodology.

Edge cases: leaves, re-entries, transfers

This is where completion tracking gets litigated. After award year 2028–29, the completion calculation runs under the clock-hour completion methodology of 34 CFR 668.8(f); how the tricky cases count during the transitional years is largely in your state's hands.

• Leaves of absence. For Title IV purposes, an approved LOA has strict conditions, and an LOA that fails them becomes a withdrawal (with R2T4 consequences). Whether an approved LOA pauses the 150 percent clock for the 70/70 completion metric is not something to assume — confirm against the final rule and your state's methodology. Until confirmed, plan conservatively: treat the calendar deadline as fixed and the LOA as consuming it.
• Re-entries. A student who withdraws and later re-enrolls raises two questions: is that one enrollment or two, and which start date governs the deadline? Document your treatment, apply it uniformly, and get your state's written concurrence.
• Transfers between programs. A student who moves from one of your programs to another is a withdrawal from the first program's cohort unless your state's methodology says otherwise. Eligibility and rates attach per program — the receiving program's cohort file gets a new row with a new start date.
• Still-enrolled at measurement time. A student whose deadline has not yet passed when you cut a report is neither a completer nor a failure; your methodology notes should state how in-window students are handled in any interim rate you publish. The report preparation guide covers cohort-period framing.

For award years 2026–27 through 2028–29, completion and placement rates are determined and verified under your state's methodology — confirm specifics with your governor's office or state workforce board before relying on any calculation.

The four exclusions that shrink your denominator

One set of adjustments is not in your state's hands — it is written into 34 CFR part 690, subpart H. Exactly four circumstances allow a student to be excluded from the completion math: the student died, suffered a totally disabling condition, was called to military service for more than 30 days, or was incarcerated. Nothing else qualifies — not a family emergency, not a job offer, not a move out of state. An excluded student comes out of both the numerator and the denominator (of the placement rate too), and each exclusion must be documented with evidence; an undocumented exclusion is an audit finding.

Worked example of what the exclusions and the 70 percent line mean in practice: a cohort of 40 enrolled students with 2 documented exclusions has a denominator of 38. If 29 complete within 150 percent of normal time, the rate is 29/38 = 76.3 percent. The 70 percent line sits at 26.6 students — so this cohort clears it with roughly two additional non-completions of slack. That is the margin a typical small cohort actually operates with, which is why the monthly monitoring below is not optional. Record exclusions in the exclusion column of your cohort file, one evidence file per excluded student.

The monthly monitoring cadence

A deadline-based metric rewards early detection. The rhythm that works:

Monthly (registrar + program director, 30 minutes per program):

• Sort the cohort file by deadline_150. For every active student, compute weeks remaining and percent of program completed (hours earned ÷ hours scheduled to date).
• Flag every student who is behind pace — attendance shortfalls in a clock-hour program translate directly into blown deadlines.
• Reconcile withdrawals: every R2T4 determination this month must appear as a withdrawal_date in the cohort file.
• Recompute the program's projected completion rate under two scenarios: (a) all active students finish by deadline, (b) currently-behind students do not. If scenario (b) drops you below 70 percent, you are in intervention territory now, not at year-end. Run both scenarios in the 70/70 Report Generator from your current roster.

Weekly (instructor level): attendance exceptions only — any student missing enough scheduled hours that their pace slips, reported to the program director the same week.

Early-intervention triggers

Write these into procedure so intervention is automatic, not discretionary:

• Pace trigger: student's completed hours fall below a set fraction of scheduled hours (you choose the threshold; make it early enough that make-up hours are feasible).
• Absence trigger: any absence streak long enough to threaten LOA/withdrawal territory — intervene before the paperwork question arises.
• Deadline trigger: fewer than N weeks to deadline_150 with more than the normally scheduled remaining hours outstanding — meaning the student now needs above-normal pace to finish. Offer make-up sessions immediately.
• Cohort trigger: projected completion rate under the conservative scenario falls below 75 percent — a self-imposed buffer above the 70 percent floor that gives you one cohort's warning before a real failure. A failed program loses Workforce Pell eligibility and cannot return (nor can a substantially similar program) for two years, so the buffer is cheap insurance.

What to do now

1. Store deadline_150 for every enrolled student in your cohort file this week; verify normal_completion_weeks matches your certified program length.
2. Stand up the monthly monitoring meeting with the two-scenario projection as a standing agenda item.
3. Write your LOA / re-entry / transfer treatment into a one-page methodology memo and send it to your state workforce board for confirmation.
4. Define your early-intervention triggers numerically and assign who acts on each within what timeframe.
5. Set a make-up hours pathway (open lab, extra range time, weekend sessions) so a flagged student always has a concrete route back to pace.