Building a Simple Dealership Dashboard in a Spreadsheet

A used car manager who opens fourteen DMS reports on Monday and still cannot answer "what is aged, what is unlisted, and what sold" does not have a reporting problem. He has a dashboard problem. The data exists. It is scattered across export files, F&I logs, a Facebook activity screen, and a recon whiteboard. Nothing is wrong with a spreadsheet if it is the one place those answers live.

A simple dealership dashboard in a spreadsheet is not a substitute for a DMS. It is a one-screen operating tool: the numbers a general manager and a used car manager will actually look at every week, with a defined owner and a defined refresh. If it takes an hour to update, it will die. If it tries to replace accounting, it will lie.

This article walks through the tabs, the metrics, the update cadence, and the traps that turn a useful sheet into a museum of last quarter's formulas.

What a Simple Dealership Dashboard in a Spreadsheet Is For

The dashboard exists to force three conversations: inventory health, demand generation, and whether last week's activity produced sold units. Everything else belongs in the system of record.

One screen, not a second accounting close

If a number needs a journal entry to be true, it does not belong here. Use the spreadsheet for:

• Unit counts by status and aging bucket.
• Retail units sold this week and month-to-date.
• Front-end snapshot (a copy of a number you already trust, not a new formula).
• Online exposure: how many retail-ready units are live versus sitting.
• Lead handling: new inquiries, unanswered threads, appointments set.

Do not rebuild the general ledger in cells. Do not invent a "true gross" that disagrees with the controller.

Who the dashboard is for

Write the audience on the first tab:

• Used car manager: aging, buying, pricing, recon backlog.
• General manager: unit pace versus the month, coverage of the book, whether the floor is working the internet.
• Internet or BDC lead: response and appointments, not vehicle cost.

If a metric has no owner, delete it. Orphan metrics are how dashboards rot.

What "simple" actually means

Simple means:

• One workbook.
• A weekly snapshot tab plus a thin history tab.
• No macros that only one person understands.
• Colors used for status, not decoration.
• A refresh that a manager can finish before the first up.

A related meeting format is in a weekly inventory exposure meeting agenda. The spreadsheet is the packet for that meeting, not a replacement for walking the lot.

The Tabs That Earn Their Place

Resist the urge to add a tab for every question someone asked once. Start with four. Add a fifth only when the fourth is being used.

Tab 1: This week

This is the only tab that should be on the projector. Columns, not a wall of charts:

Last-week comparison is enough. Year-over-year on a 40-unit independent lot is noise until the process is stable.

Tab 2: Inventory snapshot

Paste or import a unit list once a week:

• Stock number, VIN, year, make, model.
• Days in stock.
• Status: recon, retail-ready, listed, sold, wholesale.
• Asking price.
• Whether a live Marketplace listing exists (yes/no). That one column will change behavior faster than a chart.

Filter views beat pivot tables that nobody refreshes. Teach the used car manager to sort by days in stock and by "not listed."

Tab 3: History

One row per week. Same metrics as Tab 1. This is how you see whether aged count is actually falling or just getting renamed. Do not chart every series. Chart aged units, unlisted retail-ready units, and retail sold. Three lines. If you cannot read those, more lines will not help.

Tab 4: Definitions

A short glossary so "listed" cannot mean "we took photos" to one person and "live on Marketplace" to another. Include the aging trigger your store uses (for example, action required at a 30/60/90 pattern — your policy, not a universal rule). Link out, in the notes cell, to five weekly numbers a used car manager should review if that checklist is how you train managers.

How to Build a Simple Dealership Dashboard in a Spreadsheet Without Creating a Second Job

The build is a half-day project. The maintenance is a 20-minute Monday routine. Design for the routine, not for the build.

Pull from systems you already have

1. DMS or book export: stock list, cost if you choose to show it to managers, days in stock. Clean it the same way you would before posting. Garbage VINs and sold units still sitting in "available" will wreck the dashboard. See cleaning a DMS inventory export.
2. Deal log: retail and wholesale counts for the week. A simple tally is better than a broken VLOOKUP into a 40-column F&I export.
3. Posting / inventory tool: listed versus not listed, sold versus still advertised.
4. Inbox or CRM: new leads and unanswered items. If Marketplace messages never enter the CRM, count them from the leads inbox you actually use. Do not pretend a blank CRM field is "zero internet."

Paste values. Do not live-link five workbooks across a shared drive unless someone is paid to keep those links alive.

A Monday update checklist

• Export current inventory. Remove sold and wholesale-in-transit if they still appear as live.
• Recount retail sold and wholesale exits from the deal log, not from memory.
• Mark listed / not listed from the posting system, not from "I think we got to those."
• Count new inquiries and unanswered threads.
• Copy this week's row down to History.
• Write three sentences at the top of This Week: what got better, what got worse, what we will do by Friday.

The three sentences are the dashboard. The numbers only exist to support them.

Guardrails so the sheet stays honest

• Date-stamp every refresh in cell A1.
• Protect the Definitions tab.
• One person owns the file. Others can view. If five people edit, you will get five truths.
• Never hide rows to make aged look better. If a unit is on the lot, it is on the sheet.

Metrics That Belong — and Vanity That Does Not

A simple dealership dashboard in a spreadsheet fails when it fills up with activity that feels like work.

Keep these

• Aged unit count at your store's trigger, not an industry "best practice" you cannot defend.
• Unlisted retail-ready count. This is the cheapest problem to fix and the one most stores ignore.
• Retail units sold and a separate wholesale line.
• Lead response gap: threads with no first reply. Response time is a process metric; see how to measure Marketplace lead response time.
• Month-to-date unit pace versus your plan, if you have a plan. If you do not, the dashboard will not invent one.

Drop these

• Total Facebook page likes.
• Raw post counts with no inventory coverage.
• "Website hits" with no lead or appointment attached.
• Average gross to the penny copied from a report the controller will replace on the 10th.

Posting volume is useful only as a coverage check: did we list the cars that needed listing, at a conservative daily pace, without a Friday dump. It is not a success metric by itself. For a fuller GM view, use Marketplace posting KPIs for general managers as the qualitative companion to this sheet.

A 15-minute read, not a 15-tab novel

If the used car manager cannot brief the GM from Tab 1 in fifteen minutes, you added too much. Cut until the briefing is possible. Then, and only then, consider a single chart of aged units over the last twelve weeks.

How PostToMarket Automates This

A spreadsheet dashboard collapses when "listed" is a rumor and sold cars still look live. PostToMarket feeds the two columns that usually rot first: inventory status and posting ownership.

Statuses you can paste without arguing

• Inventory of draft, posting, posted, sold, failed.
• Mark as sold and archive from inventory or the queue, so the dashboard's sold line and the public listings agree.
• Unlimited vehicles in inventory, which means the snapshot can be the whole book, not the cars someone remembered to type.

The weekly numbers that are painful to collect by hand

• Team analytics by rep and source so "who posted" and "which source" are not reconstructed from screenshots.
• Leads inbox for managers, which gives you a countable inquiry pile instead of a Messenger scavenger hunt.
• Import history and row-level errors on CSV and Excel uploads, so the unit list you paste into Tab 2 is not full of blank prices and bad VINs.

Work that happens between dashboard Mondays

• Personal and per-rep queues, manager assignment to associates, reps self-queuing from shared inventory.
• Team queue view to release stuck claims.
• Chrome extension posting to Marketplace, profile, and groups, one at a time, with human-like delays and server-enforced daily limits.
• AI listing copy from specs and a Facebook photo picker.

PostToMarket is not a BI tool and does not replace your DMS. It is the operational feed that keeps a simple spreadsheet from lying about what is actually for sale.

Build the Sheet This Week. Then Stop Updating It by Memory.

A simple dealership dashboard in a spreadsheet works when it is short, owned, and refreshed on a clock. Four tabs, a Monday checklist, and three sentences at the top will outperform a wall of unused DMS reports. The sheet will still fail if listed-versus-not-listed is a guess.

PostToMarket is the system that makes that column true: one inventory, queues, paced posting, and sold units taken down the same day. Put the dashboard on Monday. Put the posting workflow underneath it every day.

Starter at $59 a month fits a solo seller or independent lot with one login. Dealership at $299 a month gives you up to 13 logins so managers and floor staff share the same statuses the spreadsheet is trying to report. Start your 10-day free trial on secure Stripe checkout. Cancel anytime. Use the trial week to fill Tab 2 with live statuses instead of hope.