A Month-End Reporting Checklist for Used Car Managers

Month-end in a used-car department is a stack of reports the GM already expects: turns, aged units, gross, recon aging, maybe a website lead source dump. Marketplace posting is usually missing, or it shows up as a single brag ("we listed a lot of cars") that cannot survive a follow-up question. A month-end reporting checklist for used car managers exists so you walk into that meeting with operational facts: what was available to post, what actually went live, what stalled, who did the work, and whether sold cars left the advertising set.

You do not need a new business-intelligence project. You need a repeatable packet assembled from inventory statuses, posting analytics, the leads inbox, and a short reconciliation to the desk. If a number cannot be explained in one sentence, leave it out. Invented conversion rates and "reach" figures do not belong in this packet. No tool can guarantee Facebook distribution, and you should not report a guarantee you do not have.

This checklist is for used-car managers and internet directors who already run inventory through PostToMarket. It is complementary to listing-quality writeups and to store-level Marketplace posting KPIs. Here the audience is the monthly GM meeting, not a daily huddle.

What Belongs in a Month-End Reporting Checklist

A useful packet answers five questions. If it answers twenty, nobody will read it.

1. Coverage: Of units we intended to retail, how many had a live listing at some point, and how many never left draft or failed?
2. Hygiene: Did sold units leave posted/queue the same day, or are we still advertising ghosts?
3. Work: Who posted, from which source (import, capture, manual), and where did volume cluster?
4. Response: Are Marketplace inquiries visible, and is anyone looking at them besides the rep who happened to get the ping?
5. Exceptions: What will we change next month, named, with an owner?

What to leave out

• Percentages you cannot define (open rate, "engagement," shadowban scores).
• Rankings of reps by raw post count with no context for queue size or days off.
• Promises about next month's lead volume.
• Customer names, testimonials, or cherry-picked message screenshots.

If the GM wants days-to-turn, use the DMS. This packet explains online exposure operations, not accounting.

Assembling the Month-End Reporting Checklist in One Sitting

Set a recurring calendar block on the last business day, or the first morning after close. Forty minutes is enough if statuses were kept honest all month.

A. Inventory status snapshot (10 minutes)

Record counts for draft, posting, posted, sold, failed. Save them next to last month. Then add two derived lines:

• Unpublished owned inventory: draft + failed on units you still have. That is the coverage gap.
• Aged drafts: drafts older than seven days.

If unpublished owned inventory grew while you "had a good posting month," you imported or captured faster than you queued. Say that plainly.

B. Sold-unit reconciliation (10 minutes)

Compare desk retail sold count (from whatever the desk trusts) to units marked sold in PostToMarket. You want them in the same neighborhood, not identical to the unit.

• Desk much higher: mark-as-sold is lagging. Ghost listings are likely.
• PostToMarket much higher: pending deals marked sold, or fall-throughs never returned to stock.

Pull three examples either way. Examples teach; a variance number alone starts an argument.

C. Posting analytics by rep and source (10 minutes)

Read posting analytics by rep and source with two questions only:

• Did any login do almost all the posting while others had full queues? That is an assignment problem or a shared-login problem.
• Did one source (for example a messy import) dominate failures? That is a file problem, not a motivation problem.

Do not publish a leaderboard in the GM packet. Publish two observations and one coaching action.

D. Leads inbox glance (5 minutes)

Managers should know whether inquiries are landing in a place they can see. You are not reporting a response-time SLA you did not measure with a defined clock. You are reporting:

• Whether the inbox was used at all.
• Whether unanswered threads piled up on one or two vehicles (often a listing problem, not a staffing problem).
• Whether sold units were still collecting "is this available" messages (hygiene again).

E. Exception log (5 minutes)

Five lines maximum. Each line: problem, example VIN or pattern, owner, done-by date. Examples: aged photo backlog on dark paint, import rows with blank prices, associate queue empty by Wednesday, sold cars remaining in queues overnight.

A One-Page Template You Can Reuse

Copy this structure into a note. Fill it; do not decorate it.

Month: ____
Retail units intended for Marketplace (desk): ____

Status snapshot: draft __ | posting __ | posted __ | sold __ | failed __
Unpublished owned (draft+failed still in stock): ____
Drafts > 7 days: ____

Desk retail sold vs marked sold: ____ vs ____
Hygiene note (1 sentence): ____

Posting observations (rep / source): 
1. ____
2. ____

Leads inbox note (1 sentence): ____

Next month (max 5):
- ____ (owner, date)

Illustrative fill (not a benchmark)

Consider a lot that aimed to retail about 60 units. Snapshot shows 9 drafts, 4 failed, 40 posted, and sold-status well below the desk. The one-page says: coverage gap of 13 owned unpublished, sold hygiene lagging, import source produced the failed four, next month the used-car manager owns same-day mark-sold and a photo day on Tuesday. That is a report a GM can manage. "We posted a lot" is not.

How to Present It Without Getting Dragged Into Vanity Metrics

Lead with coverage, not volume

Volume is what reps did. Coverage is whether the inventory was advertised. GMs already know how to over-index on activity. Start with unpublished owned inventory and aged drafts.

Use ranges and stories, not fake precision

"Sold-status is materially below the desk; here are two VINs that stayed posted over a weekend" is better than a made-up percentage of "listing accuracy."

Separate people problems from system problems

Empty associate queues are a manager assignment issue. Repeated failed rows from one spreadsheet are an import issue. A rep with low posts and an empty queue is not "lazy" in this report; they were not given work, or they were given work that was not ready.

Do not blame Facebook in the packet

If listings were posted and quiet, say they were posted and quiet. Do not diagnose a shadowban in month-end. That is a different, careful test, and Meta does not publish a status by that name. Check current commerce policies if you had removals; report removals as removals, not as folklore.

Carry the exception list into next month's first week

The packet dies if the five next-month lines are rewritten from scratch every close. Start next month's first used-car meeting by reading last month's five lines out loud.

Pitfalls That Ruin Month-End Marketplace Reporting

• Counting posts, ignoring failed. Failed is unpublished. Include it in the gap.
• Changing definitions mid-year. If "posted" means completed listing this month, it cannot mean "we intended to post" next month.
• Shared logins. Analytics by rep become fiction. Fix logins before you report people.
• Importing sold units and calling it volume. Source analytics exist so you can see this. Do not congratulate the store for uploading ghosts.
• No trial of the process during the month. If statuses are dirty all month, month-end cannot be clean. The checklist is a readout of habits, not a cleanup party.

How PostToMarket Automates This

A month-end reporting checklist falls apart when the used-car manager has to reconstruct the month from screenshots and hallway memory. PostToMarket already stores the inputs: statuses, posting analytics by rep and source, queues, import history, and a leads inbox. The manager's job is to snapshot and interpret, not to invent a parallel tracking sheet.

Numbers you can snapshot without a side spreadsheet

• Inventory statuses (draft, posting, posted, sold, failed) as the coverage skeleton.
• Team analytics: posting analytics by rep and source.
• Import history and row-level error log, so "failed because of the file" is a documented claim.
• Leads inbox for managers, as a qualitative check on whether inquiries are being seen.

Operations behind the numbers

• Unlimited vehicles in inventory, so the snapshot is the real book of posting records, not a truncated list.
• Bulk CSV/Excel import and capture from auction and wholesale sites — the sources you will mention in the analytics section.
• Mark as sold and archive from inventory or the queue, which is the hygiene number you are reconciling to the desk.
• Personal and per-rep queues, manager assignment, team queue view: the assignment story behind uneven rep analytics.
• Chrome extension posting one vehicle at a time with human-like delays and server-enforced daily limits: context for why "we did not dump 80 cars on the last day of the month" is a feature of the process, not a failure to hustle.

Put the one-page template next to the dashboard. Fill it from live filters. That is the automation: one system of record for posting operations when the GM asks what happened online.

Walk Into Month-End With Coverage, Not a Brag

Used-car month-end already has enough fiction. Use this month-end reporting checklist: status snapshot, sold reconciliation, two analytics observations, a leads note, and five owned actions. If you cannot fill the one-page, you do not have a reporting problem. You have a status-discipline problem, and that is fixable during the month, not on the last afternoon.

PostToMarket is where those statuses, analytics, queues, and the leads inbox live. Starter is $59 per month for a solo used-car operator who still owes themselves an honest close. Dealership is $299 per month for up to 13 logins so the used-car manager, a second manager, and the floor share the same month.

Start your 10-day free trial with secure Stripe checkout. Run one mid-month snapshot as practice, then use this checklist at close. Cancel anytime. If you want a second set of eyes on what to include, email info@posttomarket.com.