Pool Defined Technical Terms Across Chapters to Audit Glossary Coverage — Free
Averaging chapter glossary percentages treats a twenty-term safety primer the same as an eighty-term chemistry module. Pool total defined terms over total introduced terms to calculate true course-wide glossary coverage.
The proof surface
Cloze-density tools check deleted words in language passages. This audits study glossaries by pooling defined technical terms across modules and flagging chapters below your coverage threshold.
Why the flat version breaks
Averaging module percentages equally
A small 100-percent module hides a large 75-percent module unless denominators are pooled.
Counting undefined headings as glossary entries
Only count terms whose definition is actually written and checked.
Leaving foundational modules under-defined
Early terminology gaps compound when later chapters reuse the same vocabulary.
How to work the glossary coverage register
List each chapter or lecture module and the total number of distinct technical terms it introduces.
Record how many of those introduced terms already have a clear definition and example in your study glossary.
Enter the percentage of terms each module should define before exam revision begins (for example, 85 percent).
In the alternate sample, 60 of 80 chemistry terms (75 percent, flagged) and 20 of 20 safety terms (100 percent) pool to 80 defined out of 100 total terms — 80 percent, not an unweighted 87.5 percent average.
What the glossary coverage register replaces
| Question | Before | Visible working |
|---|---|---|
| Averaging module percentages equally | A small 100-percent module hides a large 75-percent module unless denominators are pooled. | Count terms with completed glossary definitions |
| Counting undefined headings as glossary entries | Only count terms whose definition is actually written and checked. | Set your minimum coverage threshold |
| Leaving foundational modules under-defined | Early terminology gaps compound when later chapters reuse the same vocabulary. | Read the pooled percentage and flagged modules |
A local arithmetic aid replaces hand calculation, not expert review. No paid AI service is needed.
Run it on the samples, right here
FIRST-LOAD
Input is processed locally and a draft is saved automatically in this browser profile when storage is available. Reset to sample clears that draft; Pro history has its own clear button. A state link encodes your inputs in its URL: share only non-sensitive rows. Browser history, clipboard and anyone receiving the link may retain it. Optional AI use below leaves this device; it is not required.
Pooled proportion arithmetic on term counts you enter. Not curriculum accreditation or exam-readiness certification; verify definitions against authoritative course textbooks.
Data note: Everything runs in this browser tab on the glossary coverage register: your course module | technical terms introduced | terms defined in glossary stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Go deeper: the companion app files the same reading as a bound register page
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the glossary coverage register reading, and holds your drafts on this device — one free run, then $ 4 one-time for the layer that keeps filing.
The glossary coverage register reading is complete for free. The optional $4 layer adds print, row CSV and the last five local reading summaries; it does not add hidden answers. Checkout is not configured yet; the article demo remains unlimited.
Open the pool defined technical terms across chapters to audit glossary coverage companionBoundary
Pooled proportion arithmetic on term counts you enter. Not curriculum accreditation or exam-readiness certification; verify definitions against authoritative course textbooks.
What this is built on
- Method: Enter the percentage of terms each module should define before exam revision begins (for example, 85 percent).
- All sample records are invented examples. The app does not fetch measurements, policies, files or personal records.
- Google’s official pricing page, fetched 2026-09-29, lists free-tier access including AI Studio. Optional formatting only; limits and availability can change. Free-tier content may be used to improve products. Never paste private records there.
Before: A small 100-percent module hides a large 75-percent module unless denominators are pooled. After: the glossary coverage register shows the working beside each named row so the reader can change the assumption and inspect the consequence.
Optional AI formatting, not calculation
For this glossary coverage register, use the free AI Studio interface only if available to you, with no paid API key. Manual entry completes the same workflow for free. Supply only fictional or non-sensitive notes. Review its output against the source; never paste unresolved questions into the numeric rows.
Format my non-sensitive notes for a glossary coverage register. Return plain rows only: course module | technical terms introduced | terms defined in glossary. Preserve supplied quantities exactly. Do not guess missing values; list questions separately. Do not calculate or add advice. I will check every row before pasting into the local tool.
Accepted schema: course module | technical terms introduced | terms defined in glossary. No AI response is executed as code.