Tutorials › Exam PA - Predictive Analytics › Mapping Predictive Decisions to Potential Harms

Exam PA · Ethics, Bias, and Fairness · Tutorial 834 of 966

Mapping Predictive Decisions to Potential Harms

Learn to follow a prediction through the policy it triggers and identify the potential harms at each step.

Advanced 11 min read

What You'll Learn

  • Separate a model’s prediction from the rule and action that use it
  • Trace the path from data and prediction to consequences for people
  • Calculate an illustrative expected harm when outcomes and consequences are specified
  • Identify delayed access, financial loss, stigmatizing labels, and unsafe resource allocation
  • Distinguish an observed harm from a possible harm and state important assumptions
  • Communicate limitations without treating a model score as proof of an individual outcome

From Prediction to Consequence

A model prediction does not, by itself, deny a claim, change a premium, or assign a safety crew. Those consequences arise when an organization connects the prediction to a rule and then takes an action. To assess potential harm, trace that whole path rather than discussing model accuracy in isolation.

For example, a claim model might estimate the probability that a claim contains an error. A procedure could send claims above a threshold for manual review. A later decision-maker might delay payment while reviewing the claim. The prediction, referral rule, review, and payment delay are distinct steps. If the review is poorly designed, a person with a valid claim may experience financial strain even when the model’s output is technically within its intended range.

Definition: A predictive decision pathway is the sequence from the data used by a model, through its prediction and the rule applied to that prediction, to the resulting action and its consequences. A potential harm is an adverse consequence that could arise along this pathway for a person, organization, or community. It may be financial, practical, reputational, or related to safety or access.

A useful pathway description answers five questions: What was measured? What did the model predict? What rule used that prediction? What action followed? What consequence could the action create? The description should also say who or what is exposed to that consequence. This is a mapping exercise, not a conclusion that harm has occurred or that a model should necessarily be withdrawn.

1
Prediction.
State the predicted quantity and its meaning. A score of 0.70 might be an estimated probability of a specified event, not a finding that the event has occurred.
2
Rule.
Identify the threshold, ranking, or other policy that translates the prediction into a category or referral.
3
Action.
Describe what staff or an automated process actually does: request documents, delay a payment, change a price, or assign a service.
4
Consequence.
Identify plausible adverse outcomes, their duration or scale, and the people or assets that could experience them.

Describing and Estimating Harm

Some consequences can be counted or priced under explicit assumptions; others should be described rather than forced into dollars. Suppose an action can lead to one of several mutually exclusive outcomes. If outcome \(k\) has probability \(p_k\) and a specified monetary consequence \(h_k\), the expected monetary consequence is the probability-weighted average:

$$ E[H] = \sum_k p_k h_k, \qquad \sum_k p_k=1. $$

This expression follows from the definition of an expectation for a discrete outcome: each possible value of \(H\) contributes its value multiplied by the probability that it occurs. It applies when the outcomes and their probabilities are defined for the situation being assessed and \(h_k\) is a monetary amount. It does not automatically measure stigma, loss of trust, or safety risk. Those may need separate description, and combining different kinds of harm into one dollar total requires a defensible valuation method that may not be available.

Be precise about whether a consequence is an observed result, an estimated expected consequence, or a plausible scenario. A model’s estimated probability is not a guarantee about one person. Similarly, observing an adverse event after a decision does not by itself show that the decision caused it. The analysis should name its assumptions, such as the length of a delay, the cost per day, or the assumed effect of a safety intervention.

Worked Example: A Claim Review That Delays Payment

Method: Trace the referral rule, separate valid claims from claims with errors, and calculate the stated financial consequence for valid claimants who are delayed. A hypothetical income-protection insurer uses a model score as an estimated probability of a claim error. Claims with a score of at least 0.25 are referred for manual review. In a hypothetical batch of 100 claims, 30 are referred; later review establishes that 18 of those claims were valid and 12 contained errors. Each valid referred claimant waits six extra days for payment. Assume the delay creates an average financing cost of $18 per day for each affected claimant. The review costs $25 per referred claim.

Prediction and rule. The model score is compared with 0.25. A score at or above 0.25 triggers review; the rule does not itself establish that a claim is erroneous or authorize a denial.

Action and exposure. The 30 referred claims receive manual review. Of these, 18 are valid, so 18 people experience the specified six-day delay despite having valid claims.

Financial consequence of delay. For one valid claimant, the assumed financing cost is \(6 \times \$18=\$108\). Across the 18 valid referred claims, it is \(18 \times \$108=\$1{,}944\).

Review expense. The review cost is \(30 \times \$25=\$750\). This is an administrative cost, not the same thing as the claimants’ financing cost. Under the stated assumptions, the two monetary amounts total \(\$1{,}944+\$750=\$2{,}694\), but they fall on different parties and should normally be reported separately.

Check. There are \(18+12=30\) referred claims, matching the stated total. The calculated claimant delay cost applies only to the 18 valid claims. Common mistake avoided: multiplying the delay cost by all 30 referred claims would incorrectly treat the 12 claims with errors as valid claimants experiencing the specified harm. The calculation also does not imply that every valid claimant faces the same actual financing cost; $18 per day is an assumption for this illustration.

Common Pathways to Harm

A decision pathway can create different kinds of harm at different stages. Naming the mechanism is more informative than simply calling a model “risky” or “unfair.”

Potential harmPossible pathwayQuestion to make the concern specific
Denied or delayed accessA score triggers a rejection, extra evidence request, or queue priority.Which service, payment, or coverage is withheld, and for how long?
Financial lossA prediction changes a price, benefit, credit, or claim payment.Who pays or loses money, and what amount or time period is involved?
StigmatizationA label is recorded, displayed, or passed to later decision-makers.Could the label affect later treatment even when the initial concern is unconfirmed?
Unsafe service allocationA ranking assigns limited inspections, maintenance, or assistance to some sites and not others.What safety protection is reduced for sites that receive less service?

The same model output can create multiple effects. A referral may first delay a payment, then place a “suspected error” label in a case record, and later prompt additional scrutiny. Record retention, access to the label, appeal procedures, and review time can therefore matter as much as the original threshold. Conversely, a high score used only to offer additional support may have a different consequence from the same score used to impose a penalty.

Worked Example: A Label During Claim Investigation

Method: Follow the output through the investigation policy, calculate the stated costs for people whose claims prove valid, and distinguish measurable expense from reputational risk. In a hypothetical travel-insurance operation, a model produces an estimated claim-irregularity score from 0 to 1. A score of at least 0.65 triggers investigation and adds a “suspected irregularity” label to the case system until review is complete. Of 40 investigated claims, 10 are eventually found to contain an irregularity and 30 are valid. Each valid claimant’s payment is delayed by 14 days. Assume each such delay creates a financing cost of $22 per day and that each investigation costs $90.

Decision pathway. The score threshold triggers investigation; investigation, not the score alone, results in the temporary label and payment delay. The later finding distinguishes the 10 claims with irregularities from the 30 valid claims.

Cost per valid claimant. The assumed delay cost is \(14 \times \$22=\$308\). Adding the $90 investigation cost gives \(\$308+\$90=\$398\) per valid investigated claim.

Total stated costs for valid claims. Across 30 valid claims, the delay-related cost is \(30 \times \$308=\$9{,}240\), and the investigation cost is \(30 \times \$90=\$2{,}700\). Together, these specified costs are \(\$9{,}240+\$2{,}700=\$11{,}940\). Investigation expenses for the 10 claims found to contain irregularities are not included in this total.

Additional potential harm. The temporary label may lead staff to view a valid claimant with suspicion or may influence a later review if the label remains visible. No dollar amount for that potential stigma is supplied, so it should be described separately rather than included in the $11,940.

Check. The valid and irregularity-containing claims sum to \(30+10=40\), the number investigated. Common mistake avoided: treating a model score as proof of irregularity would collapse prediction and finding into one step. The label’s possible downstream effect also depends on who can see it, how long it remains, and whether it can be corrected.

Worked Example: Ranking Sites for a Safety Crew

Method: Calculate the expected loss used by the allocation rule, then compare the selected site with an excluded site while keeping an individual realized loss distinct from an expected loss. A hypothetical insurer has one inspection crew to reduce fire losses at commercial properties. Its model estimates annual fire probabilities and potential losses. The rule sends the crew to the property with the greatest estimated annual loss. For property B, the estimates are probability 0.10 and loss $120,000. For property C, they are probability 0.04 and loss $250,000. Assume an inspection halves the estimated fire probability for one year and does not change the potential loss if a fire occurs.

Estimated annual losses before inspection. For B, the expected loss is \(0.10 \times \$120{,}000=\$12{,}000\). For C, it is \(0.04 \times \$250{,}000=\$10{,}000\). The rule selects B because \(\$12{,}000>\$10{,}000\).

Estimated reduction from inspection. At B, halving the probability gives \(0.10/2=0.05\), so the post-inspection expected loss is \(0.05 \times \$120{,}000=\$6{,}000\). The estimated reduction is \(\$12{,}000-\$6{,}000=\$6{,}000\). At C, the probability would fall from 0.04 to 0.02, giving post-inspection expected loss \(0.02 \times \$250{,}000=\$5{,}000\) and an estimated reduction of \(\$10{,}000-\$5{,}000=\$5{,}000\).

Potential consequence. The rule directs a limited safety service to B, leaving C without this inspection. If a fire occurs at C, the potential loss is $250,000 under the scenario; that severe possible outcome explains why allocation decisions have safety consequences. It does not mean that C was more favorable under the stated expected-loss rule, nor that a fire at C is certain.

Check. The estimated reductions are $6,000 for B and $5,000 for C, consistent with the assumed one-half reduction in probability. Common mistake avoided: comparing only the probabilities would rank B as riskier, while ignoring the larger loss at C. The pathway still depends on the quality of both probability and severity estimates and on whether an inspection actually has the assumed effect.

Making the Mapping Useful

A clear account of potential harm helps decision-makers see where safeguards could matter. It can reveal that a threshold sends too many people into a slow process, that a label remains in a record after it is no longer justified, or that a ranking leaves some locations without a safety service. The mapping should be specific enough to support follow-up, but it should not claim more than the available information supports.

When documenting a pathway, distinguish among model output, policy, human judgment, and operational capacity. A referral rule may be reasonable on paper but cause long delays if review staff are unavailable. A premium change may be applied automatically, while an employee can reverse it only after an appeal. A service allocation may be based on expected loss even though the worst-case consequence at an unserved site is large. These are different mechanisms and call for different evidence.

A concise harm statement can follow this pattern: “When [prediction and rule] lead to [action], [person or asset] could experience [specific consequence] over [time or scope], under [assumptions].” For example: “When a score above the stated threshold leads to manual review, a valid claimant could wait six additional days for payment, assuming the review queue produces the specified delay.” This form avoids presenting a possibility as a proven outcome and makes the causal steps available for examination.

  • Do not equate a predicted probability with proof about an individual case.
  • Do not attribute every downstream consequence to the model alone; identify the rule and operational action.
  • Do not combine financial, reputational, and safety harms into one total unless the valuation is justified.
  • Do state uncertainty, assumptions, who may be affected, and whether the consequence is observed or only plausible.
Key takeaway: Potential harm is found by tracing the complete route from prediction to policy, action, and consequence. A numerical score matters because of how it is used; a careful account keeps those stages separate and states what is known, assumed, and still uncertain. This approach is aligned with the SOA Exam PA (Predictive Analytics) syllabus.

Check Your Understanding

For each situation, trace the action and calculate only the consequence specified. Treat all data as hypothetical.

  1. A claim model estimates an irregularity probability of 0.38. The review threshold is 0.35, and a referral delays payment by five days. Assume one valid claimant incurs $24 per day in financing cost. State the action and that claimant’s estimated cost. (Answer: Referred for review; $120 estimated financing cost.)
  2. A travel-insurance investigation rule refers scores of at least 0.60. Of 20 referred claims, eight are valid. Each valid claimant incurs $75 in investigation-related expense and a three-day delay costing $30 per day. Calculate the stated total for valid claimants. (Answer: $1,320.)
  3. A safety model estimates annual loss of $300,000 with probability 0.03 at site X, and loss of $70,000 with probability 0.10 at site Y. One crew can halve the selected site’s estimated probability. Which site has the larger estimated loss reduction, and by how much? (Answer: X; $4,500 reduction at X versus $3,500 at Y, a $1,000 greater estimated reduction.)
  4. A threshold sends 40 applications to manual review. Fifteen applicants are valid, and for each valid applicant the process costs $80 and causes a ten-day delay at an assumed $12 per day. Calculate the stated total for the valid applicants and name one possible nonfinancial harm from a recorded suspicion label. (Answer: $3,000; possible stigma or later scrutiny.)
  5. A model predicts a 0.22 probability for an event, and a policy at 0.20 automatically denies a service. In a hypothetical set of 50 applicants, 12 are denied and later found eligible. If each eligible applicant loses a $400 deposit because of the denial, calculate the stated loss and identify which step directly denies access. (Answer: $4,800; the policy’s denial action, not the prediction alone, directly denies access.)
Clinical Biostats