A percent of percent calculator multiplies the two decimal rates. To interpret the result, you must also know what each rate is a percentage of. The worked record below keeps that connection visible and distinguishes supplied counts from a modeled quantity.
Follow the same assignments through both stages
Use this original fictional record, dated October 13, 2026. All stages use the same assignment-ID basis:
| Group | Supplied count | Denominator | Share |
|---|---|---|---|
| D01: whole assignment set | 50 | Whole set | 100% |
| E01: eligible assignments within D01 | 40 | 50 in D01 | 80% |
| C01: completed assignments within E01 | 30 | 40 in E01 | 75% |
C01 is contained in E01, and E01 is contained in D01. These are supplied fictional counts, not measured student or team outcomes.
The 75% uses 40 as its denominator. It does not say that 75% of all 50 assignments are complete. To recover the overall share, multiply the fraction eligible by the fraction complete within that eligible group:
Overall fraction = (80 / 100) × (75 / 100)
= 0.80 × 0.75
= 0.60
Overall percentage = 0.60 × 100% = 60%
Inch Calculator explains the same basic operation: convert both percentages to decimals, multiply, then convert the result back to a percentage. Percent of a Percent formula
Check the result directly against the supplied record: 30 / 50 × 100% = 60%. You can also see the denominator connection in (40/50) × (30/40) = 30/50. Adding 80 + 75 gives 155, but it combines rates with different denominators and does not answer the overall-share question.
Label both rates before entering them
Read the first input as p: eligible share of the whole, and the second as q: completed share within the eligible subset. The output is the completed share of the original whole.
The numeric product is unchanged if you swap 80 and 75. The story is not unchanged: 75% eligible with 80% complete within that group describes a different denominator chain. Do not swap the labels simply because multiplication is commutative.
Likewise, two rates from different dates, cohorts or quantity bases cannot automatically be combined. If 80% of one group meets a condition and 75% of another meets a different condition, multiplying them does not establish the size of an intersection. You need the appropriate conditional rate or separately justified assumptions; this tool does not assume independence.
Separate a modeled amount from a counted record
If you apply the same rates to a hypothetical base of 12 units:
Modeled amount = 12 × 0.80 × 0.75 = 7.2 units
Label 7.2 units as a modeled amount under the entered rates. It is not an observed count of completed assignments. Do not round it to seven and present that number as something counted.
The original 50/40/30 record has whole-number counts supplied at each stage. The base-12 example instead applies rates to a hypothetical base. Keep these two evidence types in separate ledger rows.
Check the product and the meaning of zero
| Calculation | Arithmetic result | Interpretation check |
|---|---|---|
| 75% of an 80% subset | 60% of the whole | Both denominators must connect. |
| 25% of a 40% subset | 10% of the whole | Multiply 0.25 by 0.40. |
| 100% of an 80% subset | 80% of the whole | All of the subset stays 80% of the whole. |
| 0% of an 80% subset | 0% of the whole | None of a nonempty eligible group is complete. |
| 75% of a 0% subset | Numeric product 0% | A measured 75% within an empty group is undefined. |
The final row needs two messages. As a pure multiplication exercise, 0 × 0.75 = 0. But if the eligible count is zero, “75% complete within eligible assignments” would require dividing a count by zero. Do not present the numeric product as evidence that a 75% conditional rate was observed in an empty set.
The example's rate scope is finite inputs from 0% to 100% inclusive, with at most six decimal places using a US decimal point. Blank input is not zero. Missing, negative, above-100, nonfinite or excessive-decimal inputs need a clear error, and changing an input to an invalid value must clear the old answer. A hypothetical base is optional; it must never silently replace supplied counts.
Copy this prompt for the comparison specification
Prepare an original US-English specification and worked ledger for a local percent of percent calculator. Do not implement a tool, claim runtime tests or produce grading/performance conclusions.
Keep the denominator chain visible. Fictional record dated October 13, 2026: D01 contains 50 assignments, E01 contains 40 eligible assignments within D01, C01 contains 30 completed assignments within E01. All use the same assignment-ID basis; C01 is within E01 within D01. p = 40/50 = 80% of the whole; q = 30/40 = 75% within eligible. Compute (p/100)*(q/100)*100% = 60% of the whole and audit against 30/50 = 60%. These supplied counts are fictional, not actual student/team outcomes. Explain why 80+75 is not the operation.
Inputs are finite rates 0..100 inclusive, up to six decimal places, US dot decimal. Missing, negative, above-100, nonfinite or overly precise inputs are invalid and clear stale output. Explicit labels: p eligible/whole; q complete/eligible; output complete/whole. Swapping numeric factors preserves product but changes the denominator story; do not swap labels silently.
Audit 25% of 40% = 10%; 100% of 80% = 80%; 0% of 80% = 0%. For a 0% eligible subset and entered 75% conditional rate, show pure product 0 but flag that an observed conditional rate within an empty set is undefined. Do not infer intersections from independent marginal rates or different cohorts/dates/bases.
Optional hypothetical base 12 with 80% and 75% yields modeled 7.2 units. Preserve the fractional modeled label; do not round it into an actual count. Keep modeled rows separate from the supplied 50/40/30 count record. Provide denominator/group record, formula, audit cases, error states and basis flags. No financial/medical use, actual learning results, persistence or integration claimed. Native maintained ledger remains authoritative; HTML/keyboard/boundary testing is later work.
Review the denominator chain with the result
The local HTML example shows D01 → E01 → C01 beside the calculation. NOS supports saving and rendering prepared HTML. Keep the maintained group record and comparison ledger authoritative.
Explore NOS to present a prepared calculation. Report 60% together with its denominator chain, and keep modeled amounts separate from what was actually counted.