Sensitivity Calculator
The formula
What the sensitivity tells you
The scaling law behind sensitivity executed with its exponent printed: a·x^n, plus the sensitivity that makes power laws unforgiving.
Calculation: Sensitivity = a × x^3.5 (empirical power law). Enter your inputs and every substitution is shown below the result.
Reading the result
The elasticity line is the point: with exponent 3.5 a 10 % measurement error costs 40 % of the answer.
Limitations and best practice
Power laws hold within a fitted range — extrapolating far outside it silently misleads.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Where does the exponent come from?
Why log scales?
Source & methodology
Published empirical scaling relation.
Sensitivity explained: formula, worked example and honest limits
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. Sensitivity is the kind of number people argue about from memory. This page ends that argument with arithmetic you can watch happen: enter your figures, get Sensitivity in real time, and see every substitution printed below.
It helps to separate the mechanics from the interpretation. The mechanics are fixed: Sensitivity = a × x^3.5 (empirical power law). Anyone, anywhere, entering the same inputs will get the same 46.765. The interpretation is where experience counts: whether 46.765 is good, normal or alarming depends on comparisons covered below, and that is the part most articles about Sensitivity never explain.
Research arithmetic demands traceability, and Sensitivity delivers it: every substitution of Sensitivity = a × x^3.5 (empirical power law) is printed, so 46.765 can be reproduced, cited and defended — the three things a bare calculator output cannot promise.
What makes a calculation page trustworthy is that its copy is derived from its own arithmetic: here sensitivity = 46.765, recomputed every time a field changes, and the sensitivity section ranks the inputs that move the result — Input quantity first, at ≈39.6 % of the headline for a ten-percent error either way in that input — which is the thread the rest of this guide pulls on.
The Sensitivity formula, explained
The engine implements a single stated model: Sensitivity = a × x^3.5 (empirical power law). There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Input quantity (example value 3) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Quantities scale everything downstream — a one-unit error here is multiplied across the whole result.
Scaling constant a (example value 1) is a quantity rather than a category — precision here is cheap and worth having. This input feeds the formula directly; a defensible figure here is worth more than false precision anywhere else.
Reference/output unit scale (example value 1) is a measured number in the unit named by the label; the formula does not convert for you. If the true figure falls between counts, run both and read the spread as your uncertainty.
Sensitivity on the example inputs: the complete substitution
Abstract formulas are hard to trust, so here is the complete substitution using the default inputs, written the way an examiner would want it. Starting figures: Input quantity, Scaling constant a, Reference/output unit scale. Run to the end, the sensitivity resolves to 46.765 — Steep exponent — small input errors blow up the output; measure x carefully on the bands this tool uses.
- x^3.5 = 46.7654
- Result = 1.00 × 46.7654 = 46.7654
- Elasticity: +1 % in x moves the result 3.5 %
Log₁₀ result — 1.67. If your inputs change, this is usually the first companion figure to move.
Sensitivity (Δ% per +1 % x) — 3.5 %. Compare it against the main result of 46.765 before drawing conclusions.
Double x gives — 529.090. Read next to the headline, this is the figure that shows the shape of the trade-off.
Overwrite any input above and every line of this example updates with it — the substitution is live, not a screenshot of somebody else’s numbers.
The Sensitivity corridor: your result across a realistic band
Single-point answers invite false confidence, so the same engine was run across a band around the input that matters most here. Each row is a full recalculation of Sensitivity, not an interpolation.
| Input quantity setting | Sensitivity |
|---|---|
| 80 % of the example value | 21.416 |
| 90 % of the example value | 32.342 |
| example inputs | 46.765 |
| 110 % of the example value | 65.283 |
| 120 % of the example value | 88.524 |
Across 5 settings of Input quantity, the result spans 21.416 to 88.524. A decision that only works at one row of this table is a decision waiting for an input to move. Reproduce it in the form above by editing Input quantity alone; the substitution steps will follow your figures exactly.
What actually moves your Sensitivity
Nobody should have to guess which input matters. The engine was re-run once per field below — ten percent up, ten percent down, everything else frozen — and the results ranked by how far they moved the sensitivity. It is the fastest honest answer to “what matters most in Sensitivity?” — and it is specific to these defaults, because sensitivity moves with the starting point.
- Input quantity: ten percent up gives 65.283, ten percent down gives 32.342 — ≈39.6 % of the sensitivity either way
- Scaling constant a +10 % → Sensitivity = 51.442 · −10 % → 42.089 (the sensitivity shifts ≈10.0 %)
- Nudge Reference/output unit scale by ±10 % and Sensitivity lands between 42.089 and 51.442 (sensitivity ≈10.0 %)
Input quantity is the dominant lever here: ten percent either way moves the result by about 39.6 %, from 32.342 to 65.283. Spend your verification effort there first, and treat Scaling constant a as the second priority (≈10.0 % per ten percent). The rest of the inputs earn only a rounding-error of attention, and that asymmetry is the practical payoff of measuring rather than asserting.
What a Sensitivity of 46.765 means in practice
The value above only becomes useful the moment you know what it is being measured against. The verdict attached to the default calculation — “Steep exponent — small input errors blow up the output; measure x carefully” — is one band on a ladder your own figure may sit somewhere else on. The sensitivity list shows how far a modest input error moves you along that ladder: for Input quantity, ±10 % covers 32.342 to 65.283. The practical reading rules: compare against your own history before comparing against other people; treat band boundaries as zones, not walls — one point on the wrong side of a threshold rarely changes a real outcome; and when a companion output contradicts the headline, believe the pair.
The comparison worth making is not with somebody else’s Sensitivity but with the version of your own situation measured last quarter — same formula, same conventions, different inputs.
Why Sensitivity results go wrong — and how to prevent it
Power laws hold within a fitted range — extrapolating far outside it silently misleads. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Stopping at the first plausible answer. If the result surprises you, the productive question is which input would have to be wrong for the surprise to disappear — then go check that input.
This model has its own particular trap: Input quantity carries ≈39.6 % of the response per ten percent of error, so effort spent elsewhere is largely decorative.
A final trap is presentation: reporting Sensitivity to more decimal places than the inputs support. The tool prints what the arithmetic gives; you should quote only what your least precise field justifies.
Sensitivity verification checklist
- Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
- Confirm the example values are plausible for your own situation before replacing them.
- Put Input quantity under a magnifier; the sensitivity table above is the reason why.
- State, in one sentence, which convention each rate, unit or period in the form is using.
- Recompute once with the dominant input deliberately set low, and see whether the decision changes.
- Confirm the answer against one independent method or published benchmark for Sensitivity.
Five steps from raw inputs to a figure you can defend
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — gather before you type. Sensitivity depends on input quantity, scaling constant a, reference/output unit scale. Collect them from a source document — a statement, a report, an invoice, a log — rather than from memory, because recalled inputs are the single largest cause of wrong results. A calculation you cannot explain to somebody else is a calculation you cannot defend.
Step 2 — compute the version you would not be embarrassed by. If a stranger audited your inputs, which set would you hand over? Enter that set, read the result, and treat everything else as upside. Note the assumption you are least sure about; that is where the real risk lives.
Step 3 — change one input at a time. Nudge a single field by ten percent, watch the headline and its companions move, then undo it. Two or three fields will dominate — the sensitivity table above already ranks them for this engine. Comparisons are cheap: run the identical calculation for the alternative and look at the gap.
Step 4 — run the scenario trio. Expected, pessimistic, optimistic. The gap between pessimistic and expected is the number to plan against; the optimistic result is useful only as a ceiling. A figure with a date beside it becomes evidence; without one it stays an anecdote.
Step 5 — write the one-line memo. “Sensitivity = 46.765 on this date, from these inputs.” That line is the entire deliverable; everything else on this page is how you earned the right to write it. Write the assumptions in the same file as the result, and future arguments take minutes instead of meetings.
Who actually uses Sensitivity — and when
Science & Research arguments end at arithmetic or they do not end. Sensitivity is the arithmetic: 46.765 on the example inputs, reproducible by anyone who types the same numbers. If the answer changes your behaviour, it deserves a second run with different assumptions.
Professionals in Physics Laboratory use this style of calculation as a screening filter before spending real money or effort: a quick Sensitivity check eliminates weak options in minutes, and the survivors earn the deeper, slower analysis. Rounding early is the quietest way to introduce a permanent error.
There is a personal-administration use people overlook: periodic self-checking. Sensitivity quietly drifts as life changes — rates move, bodies change, costs compound — and re-running it a few times a year catches drift while correction is still cheap. A result worth acting on survives having its two shakiest inputs halved.
People also ask about Sensitivity
What affects Sensitivity the most?
The short answer: Input quantity. The longer answer is the sensitivity table on this page, where every numeric input was probed by ten percent and the sensitivity recalculated — Input quantity moved it furthest, by roughly 39.6 % (32.342 to 65.283).
Which matters more: scaling constant a or input quantity?
For Sensitivity, Input quantity wins the head-to-head (≈39.6 % against ≈10.0 % per ten-percent change). Knowing which input dominates is the difference between careful work and merely slow work.
What is a typical Sensitivity?
On the worked example above Sensitivity comes out at 46.765. Treat that as one point on a distribution rather than a norm: the bands, the companion outputs and the sensitivity ranking tell you how wide the plausible range really is.
How do I calculate Sensitivity by hand?
Three steps: write the formula (Sensitivity = a × x^3.5 (empirical power law)), insert your values, and simplify. The worked example section shows exactly that chain for the default inputs; replicating it once on paper teaches you more about Sensitivity than any number of calculator runs.
What happens to Sensitivity if input quantity changes by 10 %?
Try it in the form above and the printed substitution will follow you; the pre-computed answer for the defaults is 32.342 to 65.283 across the ten-percent probe, i.e. ≈39.6 % sensitivity on the sensitivity.
Is the Sensitivity result of 46.765 good or bad?
The tool answers “what”, not “whether”: 46.765 carries the verdict “Steep exponent — small input errors blow up the output; measure x carefully” for the default case, which is a starting interpretation rather than a verdict on your situation. Re-run with your own figures and compare the bands.
Is Sensitivity accurate?
The arithmetic is exact: Sensitivity = a × x^3.5 (empirical power law) is evaluated with full floating-point precision and every substitution is printed in the worked example. What limits accuracy is input quality and the model’s assumptions, so treat the 46.765 result as the correct answer to the question you typed — and check the assumptions section before acting on it.
How often should I check Sensitivity?
Whenever an input changes by more than a few percent, and otherwise on the rhythm of your decisions — before a purchase, a review, a renewal. Sensitivity is a snapshot, not a subscription; stale snapshots are the most common silent error in Science & Research planning.
Where does the exponent come from?
Empirical fits to observations or physics (homology relations); cite the range of validity when reporting.
Why log scales?
Quantities spanning many orders of magnitude compare as straight lines on log axes.
Can this tool see the numbers I type?
It cannot. There is no submission step: the calculation happens in your browser and the result disappears when you close the page. Treat the fields above as a scratchpad rather than a form.
What the labels on this page mean
- Log₁₀ result
- 1.67 for the Sensitivity worked case; it sits next to the main result because it carries context the headline leaves out.
- Sensitivity (Δ% per +1 % x)
- 3.5 % in the default Sensitivity calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Double x gives
- 529.090 for the Sensitivity worked case; it sits next to the main result because it carries context the headline leaves out.
- Sensitivity
- The primary output of this tool: 46.765 for the default inputs, computed exactly from Sensitivity = a × x^3.5 (empirical power law).
- Worked example
- The step-by-step substitution printed above, so the arithmetic can be re-derived by hand or in a spreadsheet.
- Verdict band
- The interpretation attached to a result (“Steep exponent — small input errors blow up the output; measure x carefully” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the Sensitivity moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Methodology, sources and limits
The model is published arithmetic implemented exactly as written: Sensitivity = a × x^3.5 (empirical power law). Source of record: Published empirical scaling relation. Specialist software layers extra coefficients on top of the same algebra; none are hidden here, and that transparency is what makes a disagreement traceable to a specific input instead of a black box.
Nothing here replaces a qualified professional, and nothing here is approximate either — the arithmetic is exact, and the honesty is in the inputs you supply. The design constraint was set by usefulness rather than by comfort: an estimate you can interrogate beats an answer you have to trust.
After the number: what to do with it
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
This page was written for people who need one trustworthy number before their next decision, and the promise is that nothing above required trust. Bookmark the tool, re-run it whenever an input moves by more than a few percent, and keep the date with the number.