A Quarterly CRM Audit for Dealership Lead Data
A quarterly CRM audit for dealership lead data is not a hunt for bad reps. It is a scheduled inspection of sources, statuses, duplicates, sold matches and fields that quietly went optional.
The monthly flash report says internet produced a solid month. The CRM says the top source is still "Other." Twelve sold deals have no lead record. Eight lead records are marked sold on units that never delivered. Two reps have conversion rates that look heroic until you notice they close files as sold when the customer only set an appointment. The numbers are not lying to you. They are describing a database nobody has inspected since the last software training.
A quarterly CRM audit for dealership lead data is a scheduled inspection of the data, not a performance review in disguise. You are looking for broken fields, duplicate people, source drift, status fiction and sold records that do not match the DMS. Coaching may follow. It is not the opening move. If you start with "who is sandbagging," reps will hide more files and the next quarter will be worse.
This guide is for general managers and internet directors. It assumes you already run a CRM and a DMS and that they do not magically agree. PostToMarket does not integrate with either. The audit still has to happen. Block a half-day on the calendar every quarter and treat it like a physical inventory of the lead book.
Why a Quarterly CRM Audit for Dealership Lead Data Beats Spot Checks
Spot checks catch a dummy phone number. They do not catch a source pick-list that three new hires never learned, a status called "hot" that means nothing, or a sold-match gap that has been growing since February.
Data decays on a calendar, not on a feeling
New portals, new Marketplace workflows, new associates, a BDC hire, a manager departure — each event changes how records get created. A quarter is long enough for those changes to show up in reports and short enough that you can still reconstruct what happened. Annual audits are archaeology.
Reports hide the same errors they are built on
If source is dirty, the source ROI report is theater. If status is dirty, the funnel report is theater. Auditing the report output without auditing the fields is how stores argue about "lead quality" for years. For a cleaner monthly picture after the audit, keep building a one-page lead source report for the GM in the same binder.
The audit is cheaper than another CRM
Stores buy new CRMs because they do not trust the old one. Often the old one is fine and the data is not. Prove that before you spend another implementation.
The Quarterly CRM Audit Scope: Five Areas, One Half-Day
Do not audit "the CRM." Audit five areas with an owner, a sample and a pass/fail. If you cannot finish five, finish four and schedule the fifth. An unfinished everything-audit becomes a slide deck.
1. Source integrity
- Pull a count of internet leads created in the quarter by source.
- List the distinct source values. If you still have free text, you will see FB, Facebook, Face Book, Marketplace, MP, Social and Other.
- Sample 20 records from "Other" or blank. Read the notes. Recode only when the note is clear. Leave unknown as unknown — do not guess a source to make the pie chart prettier.
- Confirm Marketplace, website and each portal are separate pick-list values, not one "internet" bucket. The method sits in tracking Marketplace lead source ROI in your CRM.
Pass: pick-list only, "Other" requires a note, and managers can name the top sources without squinting.
2. Status honesty
- List every status used in the quarter, including ones you thought you retired.
- Pull 15 records marked appointment and verify a date and time exist.
- Pull 15 marked sold and verify they match a DMS deal or a true delivery. Appointment-as-sold is a fail.
- Pull 15 marked new that are older than your stale window. Those should not still be new.
Pass: statuses match your written definitions, and sold is not a compliment.
3. Duplicate people
- Search the quarter for matching phones, matching emails and near-matching names plus vehicle.
- Count how many customers have two or more open records.
- Merge a sample in the room so the team sees the standard. Do not leave "we'll merge later" as the outcome.
Pass: a named merge rule exists, and the open duplicate count is known, not guessed.
4. Sold-match and up-log
- Take the quarter's delivered used deals from the DMS.
- Find each customer in the CRM. Missing records are the real leak — walk-ins who were actually Marketplace, or internet customers who were never entered.
- Reconcile with the up log if you keep one. The procedure belongs with reconciling the up log with your CRM lead records.
Pass: you can state how many deliveries had no CRM lead, and you have a rule for creating the missing ones going forward.
5. Field completeness on new records
- Sample 25 internet leads created in the last 30 days of the quarter.
- Check the required set: name, reachable contact, stock number, source, owner, status, next-step date.
- Count dummy values as empty.
Pass: the required set is still required in the software or still enforced in review. If a field quietly became optional after a CRM update, that is an audit find.
How to Run the Room
Who is in it
Internet director, used-car manager, and one person who can export from the CRM. The GM should see the findings, not sit through every merge. Do not invite the whole floor. This is a data inspection, not a public grading.
What you bring
- Written status definitions and source list.
- Last quarter's findings, if this is not the first audit.
- A sample of Messenger or web-chat threads for the sold-match misses, so you are not guessing origin.
- A clock. Half a day. Parking-lot items go on a list.
What you do not do in the room
- Recode hundreds of historical sources by hand. Fix the pick-list and the last 30 days. History can stay messy if the future is clean.
- Rank reps on conversion using dirty statuses.
- Decide to "look at this next quarter" for a broken required field. Fix the setting before people leave the room.
Illustrative agenda
Consider a store with one internet director and a used department of roughly 80 units:
- 20 minutes: export and distinct source list.
- 40 minutes: status sample (appointment, sold, aged-new).
- 40 minutes: duplicate hunt and two live merges.
- 40 minutes: DMS sold-match on a sample of deliveries, not necessarily every deal if volume is high — finish the rest the next morning if needed.
- 30 minutes: field completeness sample.
- 20 minutes: write findings and owners.
If volume is huge, sample on purpose and say so in the write-up. A complete fiction is worse than an honest sample.
Findings That Matter, and Findings That Do Not
Write findings as defects, not vibes
Bad: "Source data needs improvement."
Good: "17 distinct spellings of Marketplace in Q3. Pick-list not locked. Owner: internet director. Due: this week."
Bad: "Reps aren't using the CRM."
Good: "11 of 25 sampled new leads missing a next-step date. Required-field setting is off. Owner: internet director. Due: tomorrow."
Ignore vanity
Do not spend the audit celebrating who logged the most calls. Activity volume without field quality is how the database got here. Save scorecards for a different meeting.
Carry three numbers to the GM
- Distinct invalid source values found (and whether the pick-list is now locked).
- Deliveries with no CRM lead (count from the sample or the full set).
- Open duplicates still sitting in the book.
Those three tell a GM whether internet reporting is usable. Everything else is supporting detail.
After the Audit: 90 Days of Prevention
An audit with no prevention is a quarterly hobby.
- Lock pick-lists you found drifting.
- Restore required fields that software updates quietly dropped.
- Put duplicate merge on a weekly 15-minute slot, not on the next audit.
- Train anyone hired in the quarter on source and status, not only on how to log in.
- Schedule the next audit before people leave the room.
Filter junk out of metrics in the monthly rhythm so the quarterly audit is not the first time a fake lead hits a report. That monthly habit is filtering junk leads out of your lead metrics.
How PostToMarket Automates This
A quarterly CRM audit for dealership lead data keeps tripping on the same operational gaps: units posted from a shared login, sold cars still live, inquiries that never became CRM records, and source labels that do not match how the vehicle was actually listed. PostToMarket does not audit your CRM. It gives you a posting and inquiry trail you can sit next to the CRM during the half-day.
A trail of what was actually posted
- Team analytics by rep and source so you can compare CRM source values with posting activity by person, instead of arguing from memory.
- Inventory statuses and mark as sold so the sold-match conversation starts from what left the public list, not from a recap sheet.
- Import history and a row-level error log when inventory arrives by CSV or Excel, which is often the same week lead stock numbers start going wrong.
People you can name in the audit room
- Roles (admin, manager, sales rep, sales associate) with individual logins.
- Per-rep queues and a team queue view so "who owned this unit when the lead arrived" is visible.
- Leads inbox for managers so sold-match misses can be checked against real inquiries, not against folklore.
Limits of the tool, stated plainly
PostToMarket is not a CRM and does not claim a CRM or DMS integration. No tool can guarantee that every Marketplace inquiry is copied into your CRM. The audit still needs a human to open both systems. The product reduces the number of times the posting side of the story is missing.
Put the Audit on the Calendar Before the Next Flash Report
A quarterly CRM audit for dealership lead data inspects sources, statuses, duplicates, sold matches and required fields on a clock. It is how a GM knows whether the internet number is a fact or a mood. Run it in a half-day, write defects with owners, and lock the pick-lists before anyone goes back to the floor.
If the audit keeps finding inquiries that never became records, the leak is upstream of the CRM. PostToMarket holds unlimited inventory, queues, a leads inbox and human-paced AutoPost in one place so the posting story is at least complete when you sit down to inspect the lead story.
Starter is $59 per month for one login. Dealership is $299 per month for up to 13 logins and two managers. Both open with a 10-day free trial and secure Stripe checkout.
Start your 10-day free trial. Import the lot, assign queues, and walk into the next audit with inventory status you can actually check. Cancel anytime.