WebToolArcWhy assignment-level category math matters
A syllabus may say Homework 25%, Quizzes 20%, Midterms 35%, Projects 20%, but the category percentages themselves usually come from individual earned/possible points. Wave152 lets you audit that lower layer instead of requiring you to pre-compute every category average elsewhere.
Normalized standing is not the same as locked course contribution
If only 80% of a course has been represented so far, a 90% normalized standing does not mean 90 percentage points are already locked into the final course grade. The locked contribution is the sum of each category score multiplied by its syllabus weight. The target ladder uses that contribution plus an explicit remaining-course weight, and warns when the modeled weights do not reconcile to 100%.
Blank work and dropped work are policy choices
Some gradebooks exclude work that has not been graded yet; others temporarily display it as zero. Likewise, “drop the lowest” can mean different things across courses. This lab makes the blank-score choice explicit and, when requested, drops the lowest percentage inside each category while leaving the underlying row visible in the exported evidence. It does not claim that this matches every instructor policy.
Use the target ladder instead of checking one goal at a time
The target ladder reverse-solves the average needed on the remaining course weight for every active letter cutoff in your editable scale. A score can be labelled secured, reachable, or above your declared maximum possible future score. This makes the trade-off between an A, A-, B+ and other outcomes visible without repeatedly changing one target field.
Competitor-level workflow without hiding assumptions
The page supports the common top-result workflows—percentage or letter inputs, points, weighted grades, final-exam planning, editable cutoffs, drop-lowest what-ifs and repeat-use—while adding assignment-to-category evidence, separate normalized/locked views, a full target ladder, a remaining-score sweep, raw CSV, project JSON and explicit local gradebook saves. The broader workflow remains a planning aid, not an official school record.
Choose the calculation that matches your gradebook
Weighted course is for assignments or categories that each contribute a percentage of the course. Enter a percentage or a letter grade, keep the syllabus weights visible, and use the remaining-weight target only when the counted work plus the remaining work represents the full course. Final exam needed is the direct current-grade/target/final-weight workflow. Straight points is for courses where earned points divide by possible points. Test score converts wrong answers into percentage and letter outcomes on the same active scale.
Weighted grade and remaining-grade formulas
For counted course work, the Studio tracks each contribution as score × weight ÷ 100. When only part of the course has been graded, the displayed current grade is normalized across the counted weight: sum(score × weight) ÷ sum(weight). If the remaining work has weight r, the average needed on that work is (target − counted contribution) ÷ (r ÷ 100). The weight diagnostic warns when counted weight plus remaining weight does not reconcile to 100%.
Example: the built-in course sample contributes 70.7 percentage points across 80% of the course, so the normalized current grade is 88.375%. To finish with 90% when 20% remains, the required remaining average is 96.5%.
Final exam and straight-points formulas
For a final worth w of the course, the required final score is (target − current × (1 − w)) ÷ w, with w expressed as a decimal. In straight-points mode, current grade is earned ÷ possible × 100; the target solver computes how many of the future points must be earned to reach the requested overall percentage.
Letter scales, GPA reference and rounding
There is no universal percentage-to-letter scale. The common +/- and straight A–F presets are references, not school policy. You can edit every cutoff and optional GPA reference value, then choose whether classification uses the exact percentage, rounds to 0.1%, or rounds to a whole percent. That choice can change a boundary result, so match the syllabus or official gradebook.
Drop-lowest and scenario planning
The drop-lowest control is deliberately a what-if: it removes the lowest entered percentage from this model before recalculating. It does not infer whether your instructor drops a quiz, replaces an exam, renormalizes a category, caps extra credit, applies a curve, or rounds intermediate values. The 50–100% scenario cards show how plausible remaining/final scores would change the projected overall grade without overwriting your inputs.
Save, share and export without losing the assumptions
Course projects are saved locally in the browser when storage is available. A share link carries the calculator state in the URL hash; CSV exports preserve the entered score, interpreted percentage, weight and counted/dropped status, while JSON preserves the full project setup. Before relying on a result, copy or review the calculation audit so the target, remaining weight, scale and policy boundary travel with the number.
Accuracy boundary
WebToolArc performs the arithmetic shown above, but it cannot know an instructor's hidden gradebook rules. Category normalization, missing work, retakes, replacement tests, multi-part finals, extra credit, curves, late penalties and institution-specific GPA rules can change the official result. When the syllabus conflicts with a preset or this model, the syllabus wins.