Assess whether to refer to law enforcement or keep civil (dc82cc)
August 31, 2026
SITUATION A credit-card issuer during a holiday-authorization spike cannot treat a 400% utilization jump in 11 days as incidental context on first-party friendly-fraud dispute pack. Synthetic-identity detection manager must close to refer to law from that extract under Fraud Detection / Mortgage Fraud.
DECISION Synthetic-identity detection manager in a credit-card issuer during a holiday-authorization spike must choose To refer to law enforcement / Keep civil using first-party friendly-fraud dispute pack after a 400% utilization jump in 11 days.
HYPOTHESES TO TEST 1. A 400% utilization jump in 11 days is noise around an already-controlled Mortgage Fraud process in a credit-card issuer during a holiday-authorization spike, given first-party friendly-fraud dispute pack. 2. A 400% utilization jump in 11 days is the event in first-party friendly-fraud dispute pack that forces To refer to law enforcement for synthetic-identity detection manager under Fraud Detection. 3. First-party friendly-fraud dispute pack shows a one-file miss after a 400% utilization jump in 11 days, not a Mortgage Fraud program failure. 4. First-party friendly-fraud dispute pack cannot decide to refer to law yet after a 400% utilization jump in 11 days; hold is the only Fraud Detection close a credit-card issuer during a holiday-authorization spike can defend.
ANALYSIS REQUIRED 1. Quantify loss if the hold is released before first-party friendly-fraud dispute pack is complete. 2. Test a one-off dispute against the first edge of a scheme around to refer to law. 3. Check mule or round-trip markers in first-party friendly-fraud dispute pack. 4. For this Fraud Detection Mortgage Fraud file, read first-party friendly-fraud dispute pack against a 400% utilization jump in 11 days and write the one fact that would move to refer to law for synthetic-identity detection manager.
RECOMMENDATION Choose To refer to law enforcement / Keep civil on this Fraud Detection / Mortgage Fraud packet (first-party friendly-fraud dispute pack after a 400% utilization jump in 11 days). Lead with the Fraud Detection option first-party friendly-fraud dispute pack can support after a 400% utilization jump in 11 days, then the two facts that force it, then the Monday action for synthetic-identity detection manager in a credit-card issuer during a holiday-authorization spike.
COMMAND RETURNS - Bottom-line Fraud Detection option on to refer to law, then the evidence in first-party friendly-fraud dispute pack, then the action for synthetic-identity detection manager - Hypothesis scorecard against first-party friendly-fraud dispute pack: supported / rejected / untestable - Mortgage Fraud finding in first-party friendly-fraud dispute pack that a second reviewer can re-perform - Missing page in first-party friendly-fraud dispute pack after a 400% utilization jump in 11 days, if any
Explore more
More Fraud Detection prompts
- Assess whether a claims ring exists or is coincidental overlap (2dc14c)
- Assess whether linked accounts should be treated as one case (c020ab)
- Assess whether the model score is a false positive from a life event (b7cd79)
- Assess whether a payment hold survives a customer complaint (17df74)
- Assess whether a claims ring exists or is coincidental overlap (65bac1)
Explore related decision areas
- Assess whether bonus triggers were gamed by cutoff (0d9cb8)Forensic Accounting
- Assess whether notices match the actual decisioning reasons (4050f3)Fair Lending
- Cyber underwriter must resolve whether to non-renew a deteriorating bookInsurance Underwriting
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

