The fixture preserves both S1 observations without averaging or choosing the latest. S2 has separate not-assessed, insufficient-evidence and demonstrated-low cases. The local viewer switches those cases while keeping the teacher judgment pending; it never creates a student grade.
Work through the example
Select Not assessed to see practice code NA. Select Insufficient evidence to see IE. Select Demonstrated low to see a criterion-linked teacher review request, not an automatic IE or numeric score. The fictional “Entered late” habit note remains separate throughout and does not deduct proficiency under this exercise policy.
Ask what the evidence actually demonstrates against the approved criterion before choosing a reported judgment. Insufficient evidence differs from demonstrated difficulty. The habit note has its own purpose and cannot silently alter the academic field under this exercise policy. Preserve earlier observations and document the evidence selection, sufficiency decision and rationale whenever a teacher makes a real judgment.
Begin with the approved standard and criteria
Boise School District describes reporting around defined learning goals and separately communicating habits of work. That provides one US district's context for organizing a record; it is not a national formula or proof of improved outcomes. Boise standards-based reporting.
Before real use, confirm the school's current standards, rubric, reporting codes, and judgment policy. The original exercise below uses two fictional practice targets:
| Standard ID | Original practice target | Record requirement |
|---|---|---|
| S1 | Identify the given label | Evidence linked to the label-identification criterion |
| S2 | Explain the sorting rule | Evidence linked to the explanation criterion |
These targets are not adopted curriculum standards. Keep a standard revision and criterion revision beside each evidence record. A response evaluated against yesterday's task cannot automatically satisfy a revised target.
Preserve the two dated evidence entries
Use this supplied fictional timeline. Its dates are authored scenario dates, not observations of actual learner work.
| Evidence ID | Scenario date | Standard | Supplied evidence-level interpretation |
|---|---|---|---|
| E1 | October 14 | S1 | Approaching |
| E2 | October 18 | S1 | Meets |
The current teacher-judgment field starts blank with status Pending review. E2's later date does not fill it. Nor should a numeric average of invented scale values create a result when this packet has no approved conversion or aggregation rule.
Document the judgment that is actually made
If a teacher later chooses Meets for S1, record the evidence IDs considered, the criterion used, the sufficiency decision, rationale, review date, and judgment revision. If only selected evidence supports that decision, identify the selection and explain it under the local policy.
For example, a review might ask whether E2 demonstrates the stated label-identification criterion under the required conditions and whether the available evidence is sufficient. The fixture does not include the learner's work, so a teacher cannot make that judgment from these entries alone.
Keep the evidence-level interpretations distinct from the reported standard judgment. The record should explain how the teacher reached the latter, not replace that explanation with “latest wins.” Preserve earlier observations even when the judgment changes.
Separate NA, IE, and demonstrated low proficiency
For this original exercise, test separate S2 cases:
| Case | Supplied circumstance | Practice-record treatment |
|---|---|---|
| S2-N | S2 not assessed in this period | NA under the declared exercise coding |
| S2-I | S2 assessed or assigned, but available product insufficient for a judgment | IE under the declared exercise coding |
| S2-D | Adequate assessable evidence demonstrates a low level against the criterion | Record the evidence and a teacher-reviewed proficiency judgment |
Recreate this example
Build one self-contained responsive HTML example titled “Standards-based gradebook: evidence before judgment” for readers completing the stated task. Return the complete HTML with embedded CSS and JavaScript. Use no remote fonts, libraries, images, requests, account connections, or saved-state claims.
Fictional S1 Identify given label, S2 Explain sorting rule. S1 E1 October14 Approaching and E2 October18 Meets, preserve both. Teacher judgment blank/pending, no latest-wins/average. Buttons S2 Not assessed => NA, Insufficient evidence => IE, Demonstrated low => criterion-linked teacher review, not missing-evidence code. Codes are declared exercise policy inspired by local reporting, not universal. Keep Entered late habit note separate from academic judgment. Show required rationale/evidence/criteria revision fields as pending. No real learner identifiers, grades, storage or school-system integration.
Use a school evidence ledger with dated records and separate assessment-status cases design with a compact header. Keep the actual sample data, controls, and useful default result visible early on a 360px-wide screen. Use readable text at least 16px, generous paragraph spacing, strong contrast, semantic labels, visible keyboard focus, and wrapping source blocks. Stack records on narrow screens rather than forcing a wide table.
Wire each action to an explicit type=button click handler using element selectors; the host permits scripts but blocks form submission. Update the visible result when the described action occurs. Show specific error feedback for invalid or missing input and clear stale feedback after dependent inputs change. Use plain text when displaying user values.
Fictional practice codes and evidence records are not real student grades or a universal reporting policy. Keep the source fixture and worked teacher or developer example distinct from actual user records. Include the domain-specific explanation and next check beside the result. Provide no fake download, send, deployment, approval, or persistence button. Everything operates locally for the current page session.
Review the prepared copy in NOS
Use the fictional cases to agree on the school’s code legend before entering actual grades. NOS can render a sanitized HTML explanation and let eligible static policy notes be revised visually. Actual learner evidence and teacher judgments belong in the approved school record.