A free fraud case tracker, and how to tell when you've outgrown it
A spreadsheet is a perfectly good place to run fraud cases. It's free, it's fast, everyone on the team already knows how to use one, and when you're a team of one to three working a manageable number of cases, it does the job without asking anyone for budget.
Most trackers stop at the cases, though, and that's where the real cost hides. You close a case, the row scrolls out of view, and six months later someone works the same pattern from scratch because the first write-up lived in a cell nobody thought to search. So we built the tracker we'd have wanted on our first fraud team, with a tab for the patterns behind the cases, not just the cases themselves.
It's free, it's yours to change, and you can see every tab below before you download anything.
The download sits behind a short form on steal.stingrayfraud.com: a name, any email and a tick to say we can email you, then the file.
what's in the tracker
One .xlsx file with six tabs. No macros, no external links, nothing your security team has to think twice about before opening.
The official file is .xlsx only, with no macros. If you got an .xlsm, a .zip or anything that asks you to enable content, it isn't from us.
SHA-256777dcf329df708e25a8ccb0ce05bd15f031d52944fa013d48dccddea80052695
Start here
What each tab is for, what every column means, and a plain list of what to keep out of a file your team shares.
Cases
One row per case, from the moment it's opened to the decision and the money, with the columns in the order you work a case. The due date and dispute columns are grouped, so a team that never works disputes can fold them away with one click, but keep them open if anything you handle has a response deadline. The columns:
who, what and when
- Case ID
- Opened date
- Source alert, chargeback, customer report, manual review, internal referral
- Fraud type stolen card (third-party), account takeover, card testing, friendly or first-party fraud, triangulation, promo abuse, refund abuse, marketplace seller fraud, ACH or bank fraud, other
- Priority
- Owner
- Status new, investigating, waiting, escalated, closed
- Escalated to legal, payments, law enforcement, a senior analyst
links and signals
- Order or account reference your internal ID
- Amount at risk
- Linked signals email domain, device, IP or shipping address, by internal reference, not the raw value
- Related case IDs cases that look like the same person or ring
- Linked pattern ID a dropdown of your Pattern IDs, or NONE if you checked and it isn't one
- Pattern check asks whether a fraud case with related cases belongs to a pattern, and catches a mistyped Pattern ID
- Evidence location a ticket or folder reference, not the evidence itself
due date and disputes, optional
- Due date the date you must respond by, coral from 3 days out until the case closes
- Dispute reason code
- Dispute stage inquiry through arbitration, then won, lost or accepted
- Customer contacted yes or no
decision and money
- Decision confirmed fraud, likely fraud, not fraud, inconclusive
- Action taken
- Loss gross, before anything comes back
- Recovered money back after a loss
- Prevented loss stopped before it happened
- Closed date
- Days open
- Next step and notes
Patterns the heart of it
This is the tab most trackers don't have, and the one we'd keep if we could only keep one. Each row is a pattern your team has worked out: when you first and last saw it, the signals that identify it, how it was confirmed, the steps that worked, and who figured it out. A linked case count pulls from the Cases tab, so you can see which patterns keep coming back, and a status column marks each one active or dormant. When a new analyst asks "have we seen this before?", this is where the answer should live.
Each pattern also gets its legit look-alikes, the innocent customers who can look like it and how to tell them apart, and a last reviewed date that turns yellow when an active playbook hasn't been checked in 90 days. First seen and last seen fill themselves in from the linked cases. Cases you cleared as not fraud don't count toward a pattern; they show up as cleared look-alikes instead, a nudge to write down how to tell them apart.
| Pattern ID | Pattern name | Identifying signals | Legit look-alikes | Playbook | Linked cases | Status |
|---|---|---|---|---|---|---|
| SAMPLE-P-001 | New accounts, shared reshipper address | Several new accounts ship to the same forwarding address. | A college dorm, a family or an office sharing one address. Older accounts with normal order history point that way. | Link the accounts, review open orders, record the outcome on each case. | 1 | active |
| SAMPLE-P-002 | Repeat "item not received" claims | Same customer, repeated not-received claims across orders. | Real porch theft in one area. Check the carrier's delivery scan and photo before deciding. | Pull delivery evidence, check claim history, decide and log the reason. | 2 | active |
| SAMPLE-P-003 | Promo code reused across linked accounts | One promo redeemed by accounts that share a device or payment reference. | Family members sharing one laptop, each with a single normal order. | Link the accounts, review the redemptions, note the action taken. | 1 | dormant |
The Patterns tab with the template's sample rows. The file also has fraud type, first seen, last seen, how it was confirmed, worked out by and last reviewed. Grey cells calculate themselves.
Decision log
Timestamp, case ID, who decided, the decision before and after, why, the evidence it was based on, and who signed it off if your team wants a second pair of eyes. The first decision gets logged too, not just later changes, and status changes stay on the case. In a spreadsheet you fill this in by hand, and we'll be honest that it only works if everyone remembers to do it, but a team that keeps it can answer "why did we close this?" months later.
Weekly view
Formulas only, nothing to type: what's due in the next 7 days and what's already past due, open cases by status and fraud type, average days open, gross loss, recovered, net loss and prevented on confirmed fraud, this month's not-fraud decisions by source (your false positives), the patterns with the most linked cases, and the clusters worth talking through: fraud cases this week that share something with other cases but aren't tied to a pattern yet. It's the page you'd screenshot for a Monday check-in.
Lists
Every dropdown value in one place, so you can rename statuses or add a fraud type that fits your business without touching a formula.
sample rows
The sample rows are clearly fictional (example.com addresses, IDs marked SAMPLE), so delete them and start fresh.
a note on what goes in the sheet
A shared spreadsheet is the wrong place for card numbers, government IDs or a customer's contact details, even one email at a time. The tracker is built around your internal order and account IDs, so the detail stays in the systems designed to protect it and the sheet holds the investigation. The Start here tab spells it out:
keep sensitive data out of the file
- never
- Full card numbers, CVV, bank account numbers, government IDs, passwords, one-time codes or reset links.
- avoid
- Names, emails, phone numbers, full addresses and raw IPs. Use your internal order, account and reference IDs.
- fine
- Your internal IDs, an email domain, a card's last 4 digits, a country or city.
- watch out for
- Version history: deleting a pasted card number doesn't remove it, because Google Sheets and OneDrive keep old versions. Suspicious links: write them defanged (hxxps://example[.]com), so nobody clicks one by accident. Pasted exports: paste as values only, because fraudsters plant formulas (starting with =, +, - or @) in names and notes on purpose.
- the Patterns tab
- It describes how you catch fraud. Treat the file as confidential, share it with your team only, and leave out exact rule thresholds, score cut-offs and rule IDs.
signs you've outgrown it
None of these mean you did anything wrong, they just mean the team grew faster than the file did. Count how many are true for you:
When three of these are true, that's what Stingray was built for.
Take the tracker and change whatever you like, just keep the Patterns tab, because that's where a closed case stops getting forgotten.