Almost every dealership already has a place to track claims. It is the notes field in the DMS - a scrolling wall of free text stapled to the deal, the RO, or the customer. It is right there, everyone can type in it, and it costs nothing extra. So it becomes the default. The trouble is that a note field was built to record what happened, not to make sure the next thing happens. Here is the honest comparison of DMS notes claims tracking versus dedicated claims software, and where the note field quietly costs you money.
What does it mean to track claims in DMS notes?
Tracking claims in DMS notes means recording each incident as free-text comments attached to a deal, repair order, or customer record inside your dealer management system. The note captures what was said, but it does not own the claim, hold a deadline, or produce an audit trail.
Every DMS - CDK, Tekion, Reynolds, Dealertrack - has a notes or comments area. A porter dents a unit, someone types “left rear door, backed into bollard, will get estimate” into the RO notes, and the claim is now “tracked.” The next person adds a line. Then another. Three weeks later the claim is a paragraph of timestamps and initials that you have to read top to bottom to understand, assuming you can find the right RO at all.
This is not a knock on the DMS. A DMS is excellent at what it was built for - deals, inventory, service, accounting. Claims tracking simply is not one of those jobs, and the notes field is where that gap shows up.
DMS notes vs claims software: what is really being compared?
It is a passive log versus an active system. A DMS note is a place to write down a claim; dedicated claims software is a place where the claim has an owner, a status, a deadline, and a record of every change - so the work gets done, not just described.
This is the same distinction we draw in claims software vs spreadsheets, and the answer rhymes. A spreadsheet at least gives you columns and filters. A DMS note gives you a paragraph. Both are passive: they hold text, and they wait for a human to remember to act on it. Dedicated software flips that - the claim itself carries the obligation to move forward.
A note tells you a claim existed. It never tells you a claim is late.
The three things a note field structurally cannot do are the three things that decide whether a claim costs you money: assign an owner, enforce a deadline, and produce a defensible audit trail. Take them one at a time.
Why can't a DMS note assign or own a claim?
A note is text, not a task. It has no owner field, no status, and no queue, so a claim recorded in notes belongs to everyone and therefore no one. It sits until someone happens to re-read it.
Ownership is the first thing that decides whether a claim moves. In a note field there is nowhere to put it. You can type “Maria to follow up,” but nothing routes the claim to Maria, nothing shows Maria her open claims, and nothing tells a manager that Maria has twelve of them aging past thirty days. The assignment is a sentence, not a system.
The practical failures are always the same:
- No open-claims list, so no one can see their own workload at a glance.
- No status, so “done” and “forgotten” look identical from the outside.
- No hand-off, so when the person who wrote the note is out, the claim stops.
- No roll-up, so a group leader cannot see open claims across rooftops at all.
That last one is the killer for a group. A note lives inside one store’s DMS instance and is invisible everywhere else. This is exactly how multi-rooftop groups lose money on claims: the losses are real, but no single view ever sums them, so nobody feels the total.
Why can't DMS notes enforce a claim deadline?
Because a note is inert. You can write a deadline into it, but the field does nothing when that date arrives - it will not remind anyone, change color, or surface the claim. The deadline passes in silence.
Most of what a dealership loses on claims is lost to deadlines nobody was watching - a demand response window, a subrogation recovery window, an impound meter running every day a vehicle sits. We break those clocks down in claims SLA management. The point here is narrower: a note field cannot watch any of them.
Typing “demand due 8/15” into an RO comment feels like tracking a deadline. It is not. On 8/15 the note does not move to the top of anything. No alert fires. The only way that deadline gets honored is if a human remembers to scroll back through the notes and find it, which is precisely the thing that does not happen on a busy service drive. The deadline was recorded. It was never enforced. Those are different verbs, and the gap between them is where the recovery dies.
Why do DMS notes fail as an audit trail?
Because free-text notes are editable, unstructured, and scattered. There is no guaranteed record of who changed what and when, so when a claim is disputed the note field cannot prove your version of events.
An audit trail is what wins a dispute months later. It answers three questions cleanly: what happened, when, and who recorded it. A note field answers none of them reliably. Entries can be edited or deleted, the timestamps depend on who typed and when, and the evidence - the photos, the insurance card, the estimate - lives in someone’s email or on a phone, not on the record.
A real audit trail is append-only: every entry is stamped as it is added and cannot be quietly rewritten later. That property is what makes a claim defensible in a subrogation demand or a legal matter. A paragraph of notes that anyone with DMS access can overwrite has the opposite property - it is exactly the record an opposing adjuster wants you to be relying on.
Do CDK, Tekion, or other DMS notes fix this?
No. CDK notes, Tekion claims comments, and every other DMS notes field share the same limitation - they are general-purpose text attached to a deal or RO, not a claims workflow. A newer or cleaner interface does not add ownership, deadlines, or an audit trail.
It is worth being specific, because dealers often assume the answer is a better DMS. CDK notes are fine for their purpose; so are Tekion’s. Neither was designed to route a claim to an owner, fire an alert before a subrogation window closes, or hold an append-only history tied to a VIN across every rooftop. Those are not features you are missing in your DMS configuration - they are outside what a note field is for.
The DMS limitations that matter for claims are structural:
- Notes attach to a deal, customer, or RO - not to a claim that spans a loaner, a body shop, and a recovery.
- No cross-rooftop view: each store’s notes are trapped in its own instance.
- No deadline engine, so nothing surfaces a claim before its clock runs out.
- No structured recovery pipeline, so subrogation lives as a sentence instead of a tracked opportunity.
When should a dealer group move off DMS notes?
When claims carry real money - subrogation to recover, deadlines to hit, loaner and lot damage to chase - and when more than one store is involved. At that point the note field stops being free and starts costing you the recoveries it cannot enforce.
A single, low-volume store with one disciplined manager can limp along on DMS notes the same way it can limp along on a spreadsheet. The break point is the same in both cases: recovery stakes and scale. Once you have subrogation worth pursuing, deadlines that bite, and several rooftops that need to roll up into one number, a note field is no longer a shortcut - it is a leak.
Dedicated claims software is not a bigger note field. It is the layer that turns each incident into a claim with an owner, a status, a deadline, and an audit trail, tagged to its rooftop and its VIN, feeding straight into a recovery pipeline. That is the difference between a record of what happened and a system that makes the next thing happen - and it is what cut claim cycle time in half at VIP Auto Group across their ten rooftops.
If your claims currently live in DMS notes, the fastest way to see the gap is to look at your own open claims and ask which ones have an owner, a deadline, and a recovery in motion. To see how a structured claim replaces the note field, look at ClaimsPointe claim tracking or request a demo and bring a few claims from your DMS - we will show you what the note field was hiding.
Frequently asked questions
Dana Whitfield
Head of Claims Operations, ClaimsPointe
Dana spent over a decade running claims and fixed-operations desks across multi-rooftop dealer groups before joining ClaimsPointe. She writes about the operational side of dealership claims - the deadlines, recoveries, and hand-offs that decide whether a claim costs you money or earns it back.