Sentence Monitoring Computation Sheet

By Elizabeth Franklin-Best, Esq., and Christopher Zoukis, JD, MBA

Document name	Sentence Monitoring Computation Data — the Bureau’s own name for it in policy
Form number	None. It is not a BP-numbered form. It is a printout generated by the Bureau’s Sentence Monitoring application
Published by BOP?	No. BOP publishes no blank or specimen version of this document. Probed under bop.gov/policy/forms/ on 2026-09-07; no matching file exists
Governing Program Statement	5880.28, Sentence Computation Manual (CCCA of 1984), base text February 21, 1992, cover date “CN-06, 7/19/99,” with Change Notices through CN-07
Companion Program Statements	5800.15, Correctional Systems Manual (January 1, 2009) §§ 402, 502, 903; 5880.30 (Old Law); 5880.33 (D.C. Code)
Governing regulation	None prescribes the printout. The credits it reports are governed by 28 C.F.R. § 523.20 (good conduct time) and 28 C.F.R. part 571, subpart D (release)
Governing statutes	18 U.S.C. § 3585 (commencement and prior custody credit); 18 U.S.C. § 3624(a)–(b) (release date and good conduct time)
Who prepares it	The Designation and Sentence Computation Center (DSCC), Grand Prairie, Texas
Who audits it	A second DSCC staff member — “The final auditor will certify the computation”
Does the inmate get a copy?	Yes — BOP policy directs that “a copy will be sent to the inmate”
Privacy Act notice / false-statement warning / signature line	Cannot be stated. The document is unpublished; we will not describe features we have not seen

Checked against the BOP policy set · 2026-09-07 · How we verify

If you are holding a printout headed something like “Sentence Monitoring Computation Data,” you are holding the Bureau of Prisons’ arithmetic — the document that turns a judgment into a projected release date. BOP does not publish this document. There is no blank version, no specimen, and no form number for it, so what follows explains it from the Program Statements that govern how it is made, and says plainly where those Program Statements stop.

The policy behind the numbers is on the Sentence Computation Manual page, and the credit that usually drives the projected date is on good conduct time. If you already believe the arithmetic is wrong, go to challenging a BOP sentence computation.

What this document is — and why there is no blank copy of it

The Bureau’s sentencing arithmetic is not done on a paper form. It is done in the Bureau’s Sentence Monitoring application, and what a person receives is a printout of the resulting record. BOP’s own policy calls it exactly that: “The original paper copy, a SENTRY printout, shall be placed in the inmate’s file, and copies shall be sent to the contractor, inmate, and U.S. Parole Commission, if applicable. The official computation in the file must be signed and dated by the individual completing it and the staff member performing the audit.” Reproduced from Program Statement 7300.09 at p. 257 — the community-corrections manual, quoted here because it is the clearest published description of what the document physically is.

Because the document is generated rather than printed as a stock form, there is nothing on bop.gov to link. That absence is worth saying out loud: it is why so much of what circulates about “how to read your computation sheet” is guesswork. We will not reconstruct a document we could not obtain. What the rest of this page does instead is set out what the governing Program Statements say each named quantity means — and mark where they say nothing.

Two related documents are published, and neither is this one:

• BP-A0333, Work Sheet Sentence Computation Record (PDF) — a worksheet whose fields are old-law concepts: Mandatory Release Expires With Good Time, Parole Eligibility Date, 2/3 Date, Special Parole Term. Pre-November 1987 offenses only; see sentence computation (old law).
• BP-A0559, Sentence Computation Checklist (PDF) — the staff quality-control list, ending in two signature blocks: “Sentence Computed by” and “Sentence Audited by.”

The rule the Bureau works to

What governs here is not the printout; it is the Program Statement text that says when the computation must be done, who audits it, and who gets a copy. This is the Bureau’s instruction to its own staff — it is policy, not law, and it is quoted verbatim.

502. SENTENCE COMPUTATIONS AND AUDITS

The DSCC is to ensure that a SENTRY Monitoring Update Judgment/Warrant transaction is performed on all designated inmates within 48 hours of receipt of the complete packet (excluding weekends and holidays).

An inmate’s sentence must be computed and audited immediately if the inmate is within 30 days of the statutory release date and within five working days if the inmate is within six months or less of the statutory release date. For terms in excess of six months from the statutory release date, the sentence must be computed and audited within 30 calendar days.

The Chief, DSCC, will determine the assignment of auditing sentence computations by relying on staff experience and training.

SENTRY will automatically capture the electronic ID of staff computing sentences at initial computation or subsequent updates. The final auditor will certify the computation in SENTRY.

Reproduced verbatim from Program Statement 5800.15 at p. 32.

And the sentence that answers “how do I get my sentence computation,” from the Records Office chapter of the same manual:

All sentence computation functions will be performed by the DSCC, except for the following:

• The SCSS will generate a daily roster of computation changes and will notify the unit team.
• A copy of the audited sentence computation will be sent to unit staff for inclusion in the inmate central file and a copy will be sent to the inmate.

Reproduced verbatim from PS 5800.15 at p. 28 (emphasis added).

Three things follow. The computation is made centrally, not at the institution. It is audited by a second person before it is certified. And a copy is supposed to reach the person whose sentence it is — which makes a written request to the Records Office the first step when one has not arrived. A second copy is filed in the inmate central file.

Reading the named quantities — where policy defines them

Below are the terms the Sentence Computation Manual defines. These are definitions of concepts, not descriptions of boxes on a page, because the page itself is unpublished. Nothing here tells you what any number on your printout should be.

The date the sentence began

The Manual quotes the statute and then states the outer limit in its own words. 18 U.S.C. § 3585(a) provides that “A sentence to a term of imprisonment commences on the date the defendant is received in custody awaiting transportation to, or arrives voluntarily to commence service of sentence at, the official detention facility at which the sentence is to be served.”

The Bureau’s flat rule follows: “In no case can a federal sentence of imprisonment commence earlier than the date on which it is imposed.” PS 5880.28 at p. 33. Where a court authorizes voluntary surrender, the Manual directs that “the sentence does not commence until the prisoner arrives at the designated facility,” and that any federal custody after sentencing but before departure “shall be treated as presentence time credit.” Same page.

Prior custody credit — jail credit

Governed by 18 U.S.C. § 3585(b): a defendant “shall be given credit toward the service of a term of imprisonment for any time he has spent in official detention prior to the date the sentence commences” as a result of the offense of conviction, or of any other charge arising after that offense — “that has not been credited against another sentence.” That last clause is where most disputes live, and it is a statutory limit, not an agency preference. See prior custody credit.

The Manual also defines the raw starting figure: “Raw EFT: The Raw EFT for both a federal and non-federal sentence is determined by adding the total length of the sentence to be served to the beginning date of the sentence resulting in a full term date of sentence (Raw EFT) that does not include any time credit, e.g., presentence or prior custody time or good time.” PS 5880.28 at p. 34. “EFT” is Expiration Full Term.

Inoperative time

A term of art most readers will never have seen. The Manual: “Once a sentence has begun to run, it may become ‘inoperative’ (stop running) for a number of reasons, such as, escape, civil contempt, and release pending appeal.” PS 5880.28 at p. 68. It states three application rules: inoperative time is applied “before jail time is deducted”; it “is added to the full term date of the sentence that is running at the time the inoperative time occurs”; and “The Anniversary Date, and thus the Vested Date, must always be adjusted as the result of inoperative time.” PS 5880.28 at p. 70.

Good conduct time

This is the credit that moves the projected date most, and the one place where the Program Statement is behind the law. PS 5880.28 at p. 88 quotes a version of 18 U.S.C. § 3624(b) that has since been amended, so read the current regulation instead. 28 C.F.R. § 523.20(b), effective March 14, 2022, provides that for offenses on or after November 1, 1987, “The Bureau will award inmates up to 54 days of GCT credit for each year of the sentence imposed by the court,” that it “will award prorated credit for any partial final year of the sentence imposed,” and — the sentence that explains why a projected date exists at all — “Consistent with this methodology, the Bureau will initially determine a projected release date by calculating the maximum GCT credit possible based on the length of an inmate’s imposed sentence.” For offenses on or after April 26, 1996, the same regulation sets the annual award at “up to 54 days” where the person has earned or is making satisfactory progress toward a high school diploma or equivalent, and “up to 42 days” where they have not. Full treatment on good conduct time.

A projected date is a projection. It assumes credit not yet earned, and disciplinary action can reduce it — see how to file a BP-9. It is also separate from First Step Act time credits, which are earned and applied differently.

What we cannot tell you

The printout is unpublished, so this page cannot tell you: the exact printed label of any field; the order the fields appear in; whether there is a signature line, a Privacy Act notice or a false-statement warning anywhere on it; what the header or footer says; or how many pages it runs. Anything online that describes those things is either working from a document BOP does not publish or inventing it. If your printout carries a term this page does not define, ask the Records Office in writing what it means.

What to do if you think the computation is wrong

Nobody can tell you from a web page whether your computation is right or wrong, and this page does not try. What it can do is name the route.

1. Get the document itself. Policy directs that a copy of the audited computation go to the person whose sentence it is. If none arrived, an Inmate Request to Staff (BP-A0148) to the Records Office is the ordinary first step. Ask for the judgment and commitment order and the good time record at the same time — the computation cannot be checked without them.

2. Identify which number is in dispute. Computation disputes are almost always about one of four things: the date the sentence began, prior custody credit, a good conduct time award or forfeiture, or how multiple sentences were aggregated. Naming the number and the document that should support it is what turns a complaint into a records correction.

3. Use the administrative-remedy ladder, and start early. 28 C.F.R. § 542.10 provides that “The purpose of the Administrative Remedy Program is to allow an inmate to seek formal review of an issue relating to any aspect of his/her own confinement.” In practice: informal resolution (BP-8) with the Records Office, then BP-9 to the warden, then BP-10 to the region, then BP-11 to the Central Office. Because the computation is made and certified centrally rather than at the institution, a records-level correction often resolves the issue early — but the ladder still has to be climbed if it does not.

4. Know where the courts come in. A challenge to how the Bureau executes a sentence — as opposed to the sentence itself — is brought under 28 U.S.C. § 2241 in the district of confinement, after administrative remedies are exhausted. See Section 2241 petition.

Applied Insight — Christopher Zoukis, JD, MBA, Managing Director: The most common reason a computation looks wrong is not an arithmetic error — it is a document the DSCC never received: an amended judgment, a state jail-credit certification, a corrected date of offense. We build the paper trail first and only then compare it against the printout, because the Bureau corrects a computation when it receives a document, not when it receives an argument. The legal work on any § 2241 petition is handled by Elizabeth Franklin-Best and the firm’s attorneys.

Frequently Asked Questions About the Computation Sheet

Reviewed for legal accuracy by Elizabeth Franklin-Best, Esq., Principal Attorney·September 2026