Honor Roll Software · academic recognition for K–12, done right
Recognition earned from the record — published only with consent.
Honor Roll Software computes a school’s honor roll from the real record: the same posted term grades the transcript reads, credit-weighted into each student’s cumulative grade-point average, then banded against the floors the school configures. That much is ordinary. What is not ordinary is the disclosure boundary. A student’s name reaches a published honor roll ONLY through a consent chokepoint. A minor is default-DENY: their standing is computed and counts toward everyone’s rank, but their name does not appear on any list the school publishes unless the directory-information consent is on the record. Counting is not disclosure. The honor roll is honest recognition of what was actually earned — and it is published the way a school’s FERPA custodian should publish it.
This is the academic-recognition product page. The grading-and-reporting substrate it reads from — the gradebook-of-record, both grading models, and the transcript — is at its sibling reportcard.software. The plain-language catalog of all K–12 modules is at schoolsoftware.app. The full platform story is at homeroom.software. Recognition certificates and award assemblies are honest early access, named plainly below.
The five pillars: what is built and what is in early access
Academic recognition has five surfaces. The first three — computing the honor roll from the real record, banding it against configurable floors, and publishing it only through consent — are shipped and running. The recognition certificate and the award assembly are honest early access. Each is marked plainly.
Honor roll computed from the real record
The honor roll is not a separate data entry. The cohort-standing projection reads the same posted term grades the transcript reads, computes each student’s credit-weighted cumulative grade-point average through the one shared GPA core (no forked math), and bands the result. A student’s standing is the honest output of the grades that were actually recorded — there is no re-keying between the gradebook and the recognition list. Shipped
Configurable honor-roll floors, per school
A school sets its own honor-roll floors on its grade-scale configuration: a cumulative-GPA floor for honor roll, and a higher floor for high honor roll. The floors are stored in exact integer milli-points (a 3.500 floor is 3500) so there is no rounding drift at the band boundary. When both floors are left unset, there is NO honor-roll banding at all — the honest default until a school configures a scale. The school owns where the line sits. Shipped
Consent-gated publication (the differentiator)
A ranking or honor-roll list leaves the projection layer through ONE path, and that path re-resolves every student through the consent chokepoint before their name can be emitted. The disclosure purpose is directory information: opt-IN, default-DENY, with a do-not-publish kill-switch that overrides everything. A suppressed, do-not-publish, or no-consent-context student is withheld from the published body, fail-closed. Minors default to DENY. This is FERPA directory-information posture enforced in code, not a policy paragraph. Shipped
Recognition certificates
An honor-roll certificate composits a student’s recognition — the term, the band, the school’s crest and signature line — into a print-ready page through the same publications print pipeline and producibility gate the school’s other publications use. The certificate publication kind and the postal or framed-print fulfillment leg are honest early access. The generation rail is shared and built; the recognition-certificate binding and its print fulfillment are the early-access steps. Early access (certificate + print)
Award assemblies and recognition events
A recognition assembly — an event tied to an honor-roll term, with named recognition slots for the students being honored — rides the platform’s event-coordination structure. The named-slot event surface exists on the platform; the recognition-event binding that ties an assembly to a consent-cleared honor-roll list is honest early access. We name that plainly rather than presenting the assembly leg as available today. Early access (recognition event)
How the honor roll is computed and published
The recognition stack projects forward from the posted record. Nothing is re-keyed at the recognition stage, and the consent gate is the last thing that runs before a name can be published.
- The school configures its honor-roll floors. On the grade-scale configuration, the school sets a cumulative-GPA floor for honor roll and a higher floor for high honor roll, in exact integer milli-points. Both left unset means no honor-roll banding — a deliberate, honest default until the school decides where the line sits.
- The cohort standing is projected from posted term grades. The projection reads every student’s posted, GPA-counting term grades, computes each cumulative GPA through the one shared GPA core, and sorts the cohort with a deterministic tiebreak. A student with no GPA-counting rows is listed with a null standing — never silently dropped.
- Each student is banded against the floors. A cumulative GPA at or above the high-honor floor is banded high honor; at or above the honor floor, honor; below, no band. High honor wins over honor when both floors are met. The banding is a pure function of the GPA and the configured floors, so the same rows always band the same way.
- The whole cohort is counted first. Ranking runs over the entire cohort, including students who will not be published. Counting a student toward everyone’s rank is not a disclosure of that student — so the ranks stay correct even when some names will be withheld. This separation is the point: accuracy for everyone, disclosure only for the consented.
- Every student is re-resolved through the consent chokepoint. Before a name can be emitted, the list passes through the single emission path, which checks each student against the directory-information consent for the current time. The purpose is opt-IN and default-DENY; a do-not-publish flag on the record overrides everything. A suppressed, do-not-publish, or no-context student is withheld from the emitted body, fail-closed.
- The published list carries only consented names. What the school publishes — a printed honor roll, a page, a certificate run — contains only the students whose directory-information consent is on the record. A minor with no consent on file is not on the published list. The rank they contributed to is intact; their name is simply not disclosed.
- Recognition is delivered. A certificate generates through the publications print pipeline; an assembly recognizes the cleared list. The certificate publication kind, its print fulfillment, and the recognition-event binding are honest early access — named plainly, never presented as live today.
Consent-gated recognition: the FERPA directory-information posture
Publishing a minor’s name on an honor roll is a directory-information disclosure under FERPA. Honor Roll Software treats it as one — in code, at the emission boundary, not as a policy note bolted on afterward.
Publication is opt-IN, default-DENY
A student is published on an honor roll only when the directory-information consent is affirmatively on the record for that purpose. The default is DENY. A student with no consent context on file is treated as denied — the fail-closed direction — so a missing record can never become an accidental disclosure. Minors are protected by the default, not by a checkbox someone has to remember to set.
The do-not-publish kill-switch overrides everything
A student record can carry a do-not-publish flag that suppresses the name across every disclosure surface, regardless of any other consent state. When that flag is set, the student is withheld from the honor roll even if a directory-information consent otherwise exists. The kill-switch is the strongest signal in the chain and it wins outright.
Counting is not disclosure
A suppressed student still counts toward the cohort’s ranking — the ranks other students earned are computed against the whole class, so they stay correct. What the suppression controls is whether the suppressed student’s own NAME is emitted. The list is accurate for everyone and disclosed only for the consented. Accuracy and privacy are not in tension here; they are handled at two different steps.
One emission path, fail-closed
There is exactly one way a class rank or honor roll leaves the projection layer toward a disclosure surface, and it runs the consent check on every member. A surface that wanted to publish a list cannot reach the raw projection and skip the gate — the gated path is the only path. A student who is suppressed, do-not-publish, or missing a consent context is withheld. Fail-closed, by construction.
The record persists; the disclosure is what is gated
A consent withdrawal does not erase a student’s standing — the grades and the computed GPA remain in the record as internal FERPA education data. What the consent gate controls is the DISCLOSURE: whether the name may be published. Withdraw consent and the name drops off the next published list; the underlying academic record is untouched. Storage and disclosure are separate concerns.
The school stays the custodian
The consent decisions live on the student record the school already keeps, and the school’s FERPA custodian controls them. Honor Roll Software does not decide who is public; it enforces the school’s decisions at the boundary and defaults to the protective answer when a decision is absent. A commissioned rep or studio partner never sees a student’s grades or standing — the grade substrate returns zero rows to a rep-scoped session at the data layer.
How banding works, exactly
The honor-roll band is a pure function of a student’s cumulative grade-point average and the school’s two configured floors. There is no hidden weighting and no per-run variation.
The cumulative GPA is computed once, credit-weighted, in exact integer milli-points — a 3.667 GPA is carried as 3667 — so there is no floating-point accumulation error across a student’s full set of GPA-counting term grades. The floors the school configures are stored in the same milli-point unit, so a comparison at the boundary is an exact integer comparison, never a rounded one. A student sitting on the floor is on the correct side of it every time.
High honor wins over honor: a GPA at or above the high-honor floor bands high honor even though it also clears the honor floor. A GPA at or above the honor floor but below the high-honor floor bands honor. A GPA below the honor floor is unbanded. A student with no GPA-counting rows has a null GPA and is unbanded — not zero, not last, simply not eligible for a band until there is a GPA to band.
When a school leaves both floors unset, there is no banding surface at all. The honor roll is not fabricated with a guessed default cutoff; it does not exist until the school sets one. This is the honest default: the school decides where recognition begins, and until it does, the software does not invent a line.
Recognition certificates and assemblies (early access)
Recognition is more than a list. A certificate and an assembly turn a computed band into something a student and a family keep. Both ride shared platform rails; both have an honest early-access leg we name plainly.
Certificates through the publications pipeline
An honor-roll certificate composits the recognition — the term, the band, the school crest, the signature line — into a print-ready page through the same publications print pipeline and producibility gate that generate the school’s other publications. The generation rail is shared and built. Early access — certificate publication kind
Only consented names print
A certificate run draws from the consent-cleared list, not the raw projection. A student who is not eligible to be published on the honor roll is not printed on a public recognition sheet either — the same consent chokepoint governs the certificate emission. A certificate handed directly to a student and family is a separate, non-public disclosure and is handled as such.
Print and postal fulfillment
Once a certificate is generated, a framed-print or postal fulfillment leg carries it to the family. That fulfillment leg is honest early access. The print-ready generation is built on the shared rail; the recognition-certificate fulfillment is the early-access step. Early access — print fulfillment
Award assemblies
A recognition assembly ties an event to an honor-roll term with named recognition slots for the honored students. The named-slot event structure exists on the platform; the binding that ties an assembly to a consent-cleared honor-roll list is honest early access. Early access — recognition event
The sibling: where the grades come from
Honor Roll Software is the recognition face of the grading substrate; it does not own the gradebook. The gradebook-of-record, both grading models, the academic-integrity audit trail, and the cumulative transcript live at reportcard.software. The honor roll is a projection over that posted record — it reads the transcript-grade facts, it does not re-enter them.
That separation is deliberate. Grades are entered, scored, corrected, and audited in one product with one append-only trail. Recognition is computed and published in another, with the consent gate at the boundary. Neither product duplicates the other’s data; they share the same posted term grades. A change to a grade in the gradebook flows forward to the next honor-roll projection, because the projection reads the record rather than a copy of it.
The school keeps the authoritative enrollment record in its own student information system. The grading substrate imports the roster; the honor roll bands the students on that roster. The platform is SIS-adjacent by design and does not claim to replace the school’s system.
Common questions
Where does the honor roll get its data?
From the real record. The cohort-standing projection reads the same posted term grades the transcript reads, computes each student’s credit-weighted cumulative GPA through the one shared GPA core, and bands the result against the school’s configured floors. There is no separate honor-roll data entry — the recognition list is a projection over the grades that were actually recorded.
How does a student get onto a published honor roll?
Two things must both be true. First, the student’s cumulative GPA must meet the school’s configured honor or high-honor floor. Second, the directory-information consent must be on the record for that student. Publication is opt-IN and default-DENY: a minor with no consent on file is computed and counts toward everyone’s rank, but their name is not published. The default is the protective one.
Is a minor's name ever published automatically?
No. The default is DENY. A student’s name reaches a published honor roll only through the single consent-gated emission path, which checks the directory-information consent for every member and withholds anyone who is suppressed, marked do-not-publish, or missing a consent context. There is no automatic or default publication of a minor’s name.
What does 'counting is not disclosure' mean?
The ranking runs over the whole cohort, including students who will not be published, so the ranks every student earned are computed correctly against the full class. But a suppressed student’s own NAME is not emitted. Counting a student toward everyone’s rank does not disclose that student; publishing their name would. The two steps are separate, which is why the list can be both accurate for everyone and private for the unconsented.
Who sets the honor-roll cutoffs?
The school. On its grade-scale configuration, the school sets a cumulative-GPA floor for honor roll and a higher floor for high honor roll, in exact integer milli-points. When both are left unset, there is no honor-roll banding at all — the software does not invent a default cutoff. The school decides where recognition begins.
What happens if a family withdraws consent?
The name drops off the next published honor roll; the underlying academic record is untouched. Consent controls the DISCLOSURE, not the storage. The student’s grades and computed GPA remain in the record as internal FERPA education data, and the student still counts toward the cohort ranking. Only the publication of their name is gated by consent.
Are recognition certificates available today?
The print-ready certificate generation rides the shared publications print pipeline, which is built. The certificate publication kind and the postal or framed-print fulfillment leg are honest early access. We say so plainly. A certificate run draws only from the consent-cleared list, so a student not eligible to be published on the honor roll is not printed on a public recognition sheet either.
How is this different from reportcard.software?
reportcard.software is the grading-and-reporting product home: the gradebook-of-record, both grading models, the academic-integrity audit trail, and the cumulative transcript. Honor Roll Software is that substrate’s recognition face: it bands the posted record into an honor roll and publishes it only through the consent chokepoint. One product records and audits the grades; the other recognizes and publishes them, with the consent gate at the boundary.
Can a commissioned rep see a student's grades or standing?
No. The grade substrate the honor roll reads from is walled: a rep-scoped session reads zero grade rows at the database engine, enforced by a restrictive Row Level Security policy, not an application filter. A rep or studio partner never sees a student’s grades or honor-roll standing. Recognition is a school-custodian surface, not a rep surface.
Does anything here use AI over grade records?
No. The honor-roll banding and the consent gate are deterministic policy functions over the posted record — the same inputs always produce the same output. There is no model in the loop over grade records. Recognition is computed by exact arithmetic and gated by explicit consent, not inferred.
Related surfaces
Academic recognition connects to the rest of the platform through the shared posted record and the shared consent substrate. These destinations cover the adjacent surfaces.
reportcard.software
The sibling grading-and-reporting home: the gradebook-of-record, traditional and standards-based grading, the academic-integrity audit trail, and the cumulative transcript. The honor roll bands the posted record this product keeps.
schoolsoftware.app
The plain-language K–12 module catalog front door: all of the built school-software modules with honest per-module status. Academic recognition is one of them; this page is its full home.
homeroom.software
The flagship platform brand home: the full product story and the complete picture of the grading substrate and every other module on the platform.
Student Records
The student record the projection reads from: the roster, terms, and the consent substrate the directory-information gate consults before any name is published.
What is built and what is honest-off
Honor-roll computation from the real record — the cohort-standing projection that reads the posted term grades, computes each cumulative GPA through the one shared GPA core, and bands the result — is built and running today. Configurable honor-roll floors on the school’s grade-scale configuration, in exact integer milli-points, with no banding when unset, are built and running today. The consent-gated publication — the single emission path that re-resolves every student through the directory-information consent chokepoint, opt-IN and default-DENY, with the do-not-publish kill-switch, withholding anyone unconsented fail-closed — is built and running today. Minors default to DENY; counting is not disclosure. Recognition certificates as a print-gated publication kind and award assemblies as recognition events are honest early access — the shared print and event rails are built; the recognition-certificate and recognition-event bindings and their fulfillment are the early-access steps, named plainly. The grade substrate is walled: a rep-scoped session reads zero grade rows at the data layer. Nothing here uses AI over grade records. No competitor brand names appear here. Money, pricing, and checkout are not on this page.