Precision or recall for the fraud queue
Decide whether a fraud flag feeding an investigations unit that opens 18 files a day is tuned for precision or recall, and set the operating point.
On this page
A fraud flag is the first output in this deployment whose errors land on two different groups: investigators who open the wrong files, and honest claimants whose payment waits. Which of the two the threshold protects is a decision, and the eval has to be built to inform it.
The situation
Phase 2 of the insurer's deployment, scoped after the triage pilot renewed; the pilot's scoping doc had ruled fraud scoring out. The sponsor wants a flag that refers suspicious claims to the special investigations unit (SIU). The floor handles 1,200 claims a working day, and the SIU estimates from claims later proved fraudulent that about 1% are fraud: 12 a day. Its three investigators open 6 referrals each a day, 18 in all. Today the floor routes about 5% of claims, 60 a day, to fraud review; supervisors pass 18 of them to the SIU by judgement, and 1 in 3 of those is confirmed, so 6 frauds a day are caught. A referred claim's payment is held until the SIU clears it, about 10 working days, and held honest claims are the complaints team's largest category. The team built a fraud eval from SIU outcomes, 100 confirmed frauds and 300 claims cleared on investigation, reweighted to the live 1%. It gives three operating points: refer 18 a day at 50% precision, 30 a day at 35%, or 45 a day at 24%.
The question
Decide whether the fraud flag is tuned for precision or for recall, choose its operating point, and say what you tell the head of the SIU.
A strong answer · Rubric · Where answers go wrong
Write your answer first, then open