Job Displacement Risk Calculator

The formula

gross = likelihood × impact (1–25); net = gross × (1 − controls)

What the job displacement risk tells you

The 5×5 matrix the risk industry actually uses, for job displacement risk: gross likelihood × impact, discounted by how well your controls actually work.

Calculation: gross = likelihood × impact (1–25); net = gross × (1 − controls). Enter your inputs and every substitution is shown below the result.

Reading the result

Scores rank attention; they do not price losses. Anything 15+ gets a treatment plan with a named owner.

Rules of thumb: Most organisations carry 3–5 reds; more usually means likelihood inflation, not danger.

Limitations and best practice

Control ratings drift optimistic — audit one control’s evidence and re-mark the rest against it.

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

Why discount by controls?
A 20-score hazard half-mitigated is a 10, and 10s behave like a different risk class.
Do these scores compare across teams?
Only if the likelihood and impact scales are calibrated to the same definitions — the matrix is shared, the calibration is organisational.

Source & methodology

ISO 31000-aligned qualitative risk matrices.

Job Displacement Risk: what this tool answers

You are here because you need a specific number, and you want to see how it was produced before you rely on it. There are plenty of pages about Job Displacement Risk; almost none of them show the working. This one does: the formula, every input, a fully computed example, and a sensitivity analysis calculated live from this engine’s own defaults.

Like most useful measures, Job Displacement Risk is a summary, and summaries hide as much as they reveal. The companion outputs and the input table are here to reopen what the headline compressed.

Systems math in Technology & Computing has a peculiar property: it feels precise until an assumption breaks silently. Job Displacement Risk is exact arithmetic over gross = likelihood × impact (1–25); net = gross × (1 − controls) — but only as truthful as the model. A wrong assumption about Likelihood (1 = rare … 5 = almost certain) will not throw an error; it will just quietly produce the wrong 9.1 / 25.

What makes a calculation page trustworthy is that its copy is derived from its own arithmetic: here net risk score = 9.1 / 25, recomputed every time a field changes, and the sensitivity section ranks the inputs that move the result — Likelihood (1 = rare … 5 = almost certain) first, at ≈10.0 % of the headline for a ten-percent error either way in that input. Read the sections in order and you will be able to reproduce every figure by hand.

How Job Displacement Risk is computed, line by line

One formula, published in full: gross = likelihood × impact (1–25); net = gross × (1 − controls). Anything you can read, you can reproduce in a spreadsheet, and that reproducibility is the whole point of printing it rather than hiding it behind a button.

Likelihood (1 = rare … 5 = almost certain) (example value 4) is a quantity rather than a category — precision here is cheap and worth having. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.

Impact (1 = negligible … 5 = severe) (example value 4) 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.

Control effectiveness (0–100 %) (example value 43) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Check the convention first: if the source says “6.5 % per year”, type 6.5 and let the formula do the rest.

Job Displacement Risk on the example inputs: the complete substitution

The tool prints its own working; this is the same arithmetic on the example values, reproduced so you can follow it by hand. Starting figures: Likelihood (1 = rare … 5 = almost certain), Impact (1 = negligible … 5 = severe), Control effectiveness (0–100 %). The computed net risk score comes out at 9.1 / 25, which the interpretation band labels “Amber — needs an owner and a date”.

  1. Gross = 4 × 4 = 16
  2. Net = 16 × (1 − 43 %) = 9.1

Gross score — 16 / 25. Read next to the headline, this is the figure that shows the shape of the trade-off.

Control credit — 6.9 pts. Compare it against the main result of 9.1 / 25 before drawing conclusions.

Likelihood × impact band — High×High. Compare it against the main result of 9.1 / 25 before drawing conclusions.

Keep this worked example open while you enter your own figures: matching the shape of the substitution is the fastest way to spot a unit or convention mistake.

Scenario table: Job Displacement Risk at ±10 % and ±20 % of the key input

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 Job Displacement Risk, not an interpolation.

Likelihood (1 = rare … 5 = almost certain) settingNet risk score
80 % of the example value7.3 / 25
90 % of the example value8.2 / 25
example inputs9.1 / 25
110 % of the example value10.0 / 25
120 % of the example value10.9 / 25

The corridor runs from 7.3 / 25 to 10.9 / 25 across that band — which is the range worth planning inside rather than the single 9.1 / 25 point estimate. Reproduce it in the form above by editing Likelihood (1 = rare … 5 = almost certain) alone; the substitution steps will follow your figures exactly.

Where Job Displacement Risk is fragile — and where it is not

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 net risk score. For Job Displacement Risk the ranking is measured rather than guessed, and it belongs to these defaults: shift the starting point and the order can shift with it.

  • Likelihood (1 = rare … 5 = almost certain): ten percent up gives 10.0 / 25, ten percent down gives 8.2 / 25 — ≈10.0 % of the net risk score either way
  • Impact (1 = negligible … 5 = severe): ten percent up gives 10.0 / 25, ten percent down gives 8.2 / 25 — ≈10.0 % of the net risk score either way
  • Control effectiveness +10 % → Job Displacement Risk = 8.4 / 25 · −10 % → 9.8 / 25 (the net risk score shifts ≈7.5 %)

Likelihood (1 = rare … 5 = almost certain) is the dominant lever here: ten percent either way moves the result by about 10.0 %, from 8.2 / 25 to 10.0 / 25. That is where a careless figure does the most damage, so check it against a source, and Impact (1 = negligible … 5 = severe) is effectively tied with it (≈10.0 % for the same nudge), so verify the pair together. The remaining fields can sit at safe defaults without materially changing the answer — knowing which is which is what separates a careful calculation from an anxious one.

What a Job Displacement Risk of 9.1 / 25 means in practice

The value above only becomes useful the moment you know what it is being measured against. On the example inputs the band reads “Amber — needs an owner and a date”; your own figures place you on a different rung of the same ladder. The sensitivity list shows how far a modest input error moves you along that ladder: for Likelihood (1 = rare … 5 = almost certain), ±10 % covers 8.2 / 25 to 10.0 / 25. The practical reading rules: read the band as a starting hypothesis, then test it: change the two dominant inputs by ten percent and see whether the verdict survives. Verdicts that survive stress are the ones worth acting on.

Related measures answer related questions, and the distinctions matter: Job Displacement Risk is the quantity, Net risk score is this tool’s reading of it, and the decision that follows belongs to neither of them separately.

How people get Job Displacement Risk wrong

Control ratings drift optimistic — audit one control’s evidence and re-mark the rest against it. 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.

Comparing a Job Displacement Risk computed here with a figure from another source that uses different conventions. Same name, different denominator — the disagreement is usually in the definitions, not the data.

This model has its own particular trap: Likelihood (1 = rare … 5 = almost certain) carries ≈10.0 % of the response per ten percent of error, so effort spent elsewhere is largely decorative.

The subtlest error is answering the wrong question precisely. Confirm that net risk score is actually the quantity your decision needs — the arithmetic is flawless either way, which is what makes the mistake invisible.

Six things to confirm before acting on Job Displacement Risk

  • Record the date and the inputs alongside the number so future-you knows what was assumed.
  • Confirm the example values are plausible for your own situation before replacing them.
  • Put Likelihood (1 = rare … 5 = almost certain) under a magnifier; the sensitivity table above is the reason why.
  • Compare the output against one published benchmark or a colleague’s independent estimate.
  • Re-run the calculation with a ±10 % stress on the two most sensitive inputs.
  • Confirm the answer against one independent method or published benchmark for Job Displacement Risk.

Step by step: getting a trustworthy Job Displacement Risk out of this tool

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 — collect, then type. Everything this tool asks for is listed above (likelihood (1 = rare … 5 = almost certain), impact (1 = negligible … 5 = severe), control effectiveness (0–100 %)). Pull each figure from something you can point at — paperwork, a dashboard, a label — before touching a field. Guesswork at the input stage cannot be repaired at the interpretation stage. One decimal place more than your data supports is one decimal place of fiction.

Step 2 — baseline before exploration. Get one defensible Net risk score on screen before you start nudging numbers. Without a baseline, every variation looks interesting and none of them means anything. Note the assumption you are least sure about; that is where the real risk lives.

Step 3 — play with the inputs on purpose. Ten percent up, ten percent down, one field at a time. Within a few minutes you will know this calculation better than most people who quote its results. Repeating a calculation with the same numbers proves only that the arithmetic is reliable — which is worth knowing.

Step 4 — stress before you commit. A decision that survives a ten-percent squeeze on its two biggest inputs needs no luck to be sound. One that does not survive is a decision about hope, not about arithmetic. Compare the calculation to the rough guess you arrived with, and ask why they differ.

Step 5 — save the story with the figure. A number without its inputs and its date is unusable within a quarter. Record 9.1 / 25, the assumptions behind it, and today’s date; your future self will be auditing a stranger’s arithmetic. A figure nobody can reproduce is a figure nobody will act on twice.

Who actually uses Job Displacement Risk — and when

In AI & Machine Learning the figure computed here is usually the first one somebody asks to see. Having it — with the formula behind it — changes your position in the conversation from participant to reference. Write the figure down before moving on; memory flatters whichever number you saw last.

Used properly this is a five-minute filter that saves weeks. Compute Job Displacement Risk, reject what fails, and only then bring in the expensive analysis for the survivors. If the answer changes your behaviour, it deserves a second run with different assumptions.

Re-running this page costs nothing and catches the slow drifts that never announce themselves. In Technology & Computing the expensive mistakes are rarely sudden; they are small changes in Likelihood (1 = rare … 5 = almost certain) that nobody recalculated for a year. Rounding early is the quietest way to introduce a permanent error.

People also ask about Job Displacement Risk

What affects Job Displacement Risk the most?

Measured on this engine, Likelihood (1 = rare … 5 = almost certain) is the dominant lever: moving it ±10 % shifts the net risk score across 8.2 / 25 to 10.0 / 25 — about 10.0 % of the headline, with Impact (1 = negligible … 5 = severe) next at ≈10.0 %. The ranked list in the sensitivity section is computed live, not asserted from a template.

Do impact (1 = negligible … 5 = severe) and likelihood (1 = rare … 5 = almost certain) matter equally?

Effectively. Measured on this engine they land at ≈10.0 % and ≈10.0 % for the same ten-percent nudge, so the honest advice is to get both right; chasing precision in only one of them buys almost nothing.

What is a typical Job Displacement Risk?

With the example inputs on this page the result is 9.1 / 25, labelled “Amber — needs an owner and a date”. “Typical” varies with situation, which is why every result here ships with its verdict band and its sensitivity list: they turn one figure into a range you can locate yourself inside.

How do I calculate Job Displacement Risk by hand?

Three steps: write the formula (gross = likelihood × impact (1–25); net = gross × (1 − controls)), 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 Job Displacement Risk than any number of calculator runs.

What happens to Job Displacement Risk if likelihood (1 = rare … 5 = almost certain) changes by 10 %?

On these inputs a ±10 % change in likelihood (1 = rare … 5 = almost certain) takes Job Displacement Risk to 10.0 / 25 against the 9.1 / 25 example — around 10.0 % of the headline. The same test on every other field is in the sensitivity section.

Is the Job Displacement Risk result of 9.1 / 25 good or bad?

Good and bad are comparisons, so the honest test is three questions: where does your own Job Displacement Risk sit against the 9.1 / 25 reference above, how far would a plausible input error move it (≈10.0 % per ten percent on Likelihood (1 = rare … 5 = almost certain)), and what does the alternative option compute to?

How do I calculate Job Displacement Risk manually?

Write down the inputs, then follow the printed steps in order — gross = likelihood × impact (1–25); net = gross × (1 − controls). A spreadsheet replicates it with two or three cells. The manual route is worth doing once to build intuition; after that the calculator saves time and eliminates transcription slips.

How often should I check Job Displacement Risk?

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. Job Displacement Risk is a snapshot, not a subscription; stale snapshots are the most common silent error in Technology & Computing planning.

Why discount by controls?

A 20-score hazard half-mitigated is a 10, and 10s behave like a different risk class.

Do these scores compare across teams?

Only if the likelihood and impact scales are calibrated to the same definitions — the matrix is shared, the calibration is organisational.

Does this Job Displacement Risk tool store my numbers?

No. The entire calculation runs in your browser session; nothing entered above is transmitted or saved, which is the correct behaviour for sensitive Technology & Computing figures and the reason you can re-run this page as often as you like.

Glossary for Job Displacement Risk

Gross score
16 / 25 for the Job Displacement Risk worked case; it sits next to the main result because it carries context the headline leaves out.
Control credit
6.9 pts for the Job Displacement Risk worked case; it sits next to the main result because it carries context the headline leaves out.
Likelihood × impact band
High×High in the default Job Displacement Risk calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
Net risk score
The primary output of this tool: 9.1 / 25 for the default inputs, computed exactly from gross = likelihood × impact (1–25); net = gross × (1 − controls).
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 plain-language label — here “Amber — needs an owner and a date” — mapping the computed figure onto experience-based ranges for Technology & Computing.
Sensitivity (±10 %)
How far the Job Displacement Risk 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: gross = likelihood × impact (1–25); net = gross × (1 − controls). Source of record: ISO 31000-aligned qualitative risk matrices. Where a professional version of this calculation differs, it differs in inputs and jurisdiction-specific coefficients, not in the algebra — which is why re-checking your inputs beats hunting for a second calculator.

This page is an estimation aid, not professional advice. The design rule is simple: two people entering identical figures must get identical answers. The design constraint was set by usefulness rather than by comfort: an estimate you can interrogate beats an answer you have to trust.

Turning this Job Displacement Risk into a decision

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.