TIME & CREDITS — FIXING THE SCORE

Challenging a PATTERN Score: The Step-by-Step Playbook

When the risk score is built on wrong inputs — a misread criminal history, a missing program completion, an infraction that should not count — the error taxes every month that follows at five days per thirty, and can block credit application entirely. Scores built on bad data are challengeable, and the challenge is free. Here is how it is done.

LAST REVIEWED: July 5, 2026 · FEDERAL SYSTEM ONLY · EDUCATIONAL — NOT LEGAL ADVICE

TIME LEDGER — CASE FILE SUMMARY AUDIT THE INPUTS

What is challengeable	The inputs and the arithmetic: criminal-history data, program and education entries, infraction records, assessment scheduling
What is not (inside BOP)	The tool’s design — cut points, factor weights, the instrument itself as published
First forum	The program review with the unit team, with documents attached
Escalation	BP-8 → BP-9 → BP-10 → BP-11; computation consequences can support a §2241
Evidence that wins	Presentence report, judgment, program certificates, expungement or appeal orders, prior assessments
Cost	$0

Why input errors are common — and costly

PATTERN scores are only as good as the records keyed into them, and those records travel a long road: court documents to the presentence report, the presentence report to BOP intake systems, institution to institution with every transfer. Data degrades in transit. A criminal-history point that should not exist, a completed drug-education course that never posted, a disciplinary finding later overturned but never removed — each is a few score points, and a few points near a cut line is the difference between low and medium.

The cost compounds. Medium instead of low means earning at 10 days per 30 instead of qualifying toward 15, and it can block applying credits at all. Over a two-year stretch, a single wrong input can quietly consume months of liberty. That asymmetry — small clerical cause, large liberty effect — is why score auditing belongs on every family’s checklist.

Step one: get the score and its ingredients

The person inside requests, at any program review or by written request to the case manager: the current PATTERN risk levels (general and violent), the assessment date, and the underlying scoring inputs. The FSA Time Credit Assessment shows the risk-level history; the fuller picture lives in the intake and review records the team scores from. Politely insisting on seeing what was scored is not confrontational — it is the review working as intended.

The family gathers the comparison set from outside: the presentence report if the person has their copy or counsel can supply it, the judgment from PACER, program completion certificates mailed home over the years, and any court orders expunging or reversing prior matters. You are assembling two columns — what the BOP scored versus what the documents say — and the challenge will live in the gaps.

Step two: audit the dynamic factors first

Dynamic factors are the easiest wins because the proof is recent and often in your own file cabinet. Check that every completed EBRR program and productive activity appears — our program guide lists the categories. Check education entries, work assignments, and drug-treatment participation. Check infraction recency: PATTERN weighs how recent misconduct is, so an old incident scored as recent is a pure clerical error.

Also audit the calendar itself: assessments are supposed to recur on the review cycle, and a stale score is its own challengeable failure — nobody can reach two consecutive minimum/low assessments if reassessment never happens. The written ask is simple: please conduct the overdue reassessment reflecting the completions listed and attached.

Step three: audit the static factors carefully

Static factors — age at assessment, criminal history, offense characteristics — are scored from the presentence report and central records, and errors here usually mean a transcription problem or a document conflict. Compare the criminal history the tool assumes against the presentence report line by line. If the presentence report itself is wrong, understand the hard truth: the time to litigate PSR accuracy was at sentencing, and the BOP will generally follow the report as written — though a court order correcting the record changes everything and should be pressed hard.

Where a prior conviction was later vacated, expunged, or reduced, obtain the certified order; that document outranks the stale entry. Where the tool double-counts or miscategorizes the instant offense, cite the judgment. Static-factor challenges rise or fall on paper hierarchy: court order beats BOP record beats memory.

Step four: raise it at the review, in writing

The program review is the first forum, and preparation beats improvisation. The person inside brings a one-page written summary: the current score, the specific input believed wrong, the document proving it, and the requested fix — rescore with corrected data, enter the missing completions, conduct the overdue assessment. Hand the page over; ask that it and the attachments go in the file; request the corrected score in writing when done.

Tone matters strategically. Unit teams fix documented clerical errors all the time when the ask is specific and the paper is attached; they dig in when the ask is a generalized accusation. The framing that works is collaborative and precise: the record appears to contain an error, here is the document, here is the correction requested.

Step five: escalate through the remedy program

If the review does not fix it, the Administrative Remedy Program does what it always does: forces a written answer from someone with authority. The BP-9 to the warden states the input error, attaches the proof, and requests rescoring; the BP-10 and BP-11 appeals carry it to the region and central office. Keep each filing to the documentary point — score inputs, not score philosophy — and calendar every deadline.

Frame the harm in credit terms, because that is the score’s legal significance: the erroneous medium classification is denying the enhanced earning rate and blocking application of earned credits under 18 U.S.C. §3624(g). A remedy file built that way does double duty — it either wins administratively or becomes the exhaustion record for court.

Step six: court, in the right posture

There is no direct judicial appeal of a PATTERN number, and courts give the BOP wide room on how it assesses risk. What courts do hear, via §2241, are the concrete sentence-execution consequences: credits earned at the wrong rate, credits not applied when statutory conditions are met, computations that ignore the corrected record. If the score error has matured into a credit error, the petition targets the credits and tells the score story as the cause.

This posture is why the earlier steps matter so much: the review requests, the BP file, and the document set are the difference between a petition that says the score feels unfair and one that says the record proves the inputs were false and the credits are being miscalculated as a result. The first gets dismissed. The second gets read. Our pro se guide covers the craft that carries it the rest of the way.

Frequently asked questions

Can you appeal a PATTERN score directly?

Not to a court, no — there is no direct judicial review of the number itself. The effective path is correcting the inputs through program reviews and the administrative remedy program, and taking any resulting credit miscalculation to court under §2241 once remedies are exhausted.

What documents prove a PATTERN input error?

The presentence report and judgment for criminal-history and offense factors; program and education certificates for dynamic factors; certified court orders for vacated or expunged priors; and prior FSA assessments showing the scoring history. Court paper outranks BOP records; BOP records outrank recollection.

The presentence report itself is wrong. Can the BOP fix that?

Generally no — the BOP follows the PSR as written. Corrections to the report itself run through the sentencing court, which is difficult after sentencing and typically a question for counsel. What the BOP can and must fix is scoring that misreads an accurate PSR.

How long does a score challenge take?

Documented clerical fixes at a program review can happen in days. The BP ladder adds weeks to a few months per level when escalation is needed. Reassessment timing matters too — pair every challenge with a request that the corrected data be rescored promptly rather than at the next annual cycle.

Is challenging the score worth it at medium risk with years remaining?

Usually more than anyone realizes. Reaching low starts the two-consecutive-assessment clock toward the 15-day rate and opens credit application — and every month at the wrong level is five days of earning lost. Long runways make score correction more valuable, not less.