A Weekly Manager Review: Statuses Analytics and Leads

A used-car manager can walk the lot every morning and still have no idea whether Marketplace posting is working. Reps say they "got a lot up." Associates say their queues were light. The internet director heard that one truck "blew up with messages." None of that is a review. A review is a standing look at three boards that do not lie: inventory statuses, posting analytics, and leads.

A weekly manager review of statuses, analytics, and leads is how you catch stalled drafts, uneven posting, and slow follow-up before they become a month of aged inventory. This article is written for used-car managers, internet directors, and GMs who already know days-to-turn and recon. It is a meeting agenda and a reading order, not a dashboard tour of invented buttons. It does not claim that any number on a report guarantees sales. It does claim that a store which never looks at statuses, analytics, and leads together is managing by story.

Why a Weekly Manager Review of Statuses, Analytics, and Leads Beats Daily Anecdotes

Daily huddles are for today's queue. Weekly review is for patterns. If you only manage day to day, you will miss the associate whose failed posts accumulate every Thursday, the rep who claims units and never posts them, and the source of inventory that always arrives with missing photos.

The three questions the week must answer

1. Is the inventory honest? Statuses tell you what is draft, posting, posted, sold, or failed. A growing draft pile, a cluster of failed units, or posted cars that should have been archived are process failures, not market failures.
2. Who posted what, and from where? Analytics by rep and by source tell you whether work is concentrated on two people, whether auction captures are sitting idle, and whether one rep's volume is empty calories.
3. Did inquiries get handled? The leads inbox is where posting turns into appointments. Volume without response is a marketing expense with no close.

If you cannot answer those three from the board in a short sitting, the week did not have a manager. It had activity.

Keep the meeting short on purpose

Thirty minutes is enough if the agenda is fixed. Longer meetings become deal discussions. This review is not a pricing meeting and not a recon meeting. Those can follow. Start with the boards.

Part One: Statuses as the Inventory Truth Set

Start with statuses. Analytics without an honest inventory will praise people for posting cars that were not available.

What to count, without inventing targets

Do not create fake KPIs. Count what is on the board and ask why:

• Drafts older than a few days. Either data is blocked (price, photos, import errors) or nobody is assigning work.
• Failed units still sitting. Failed means the post did not complete. A failed unit that is a week old is an owned problem that nobody owned.
• Posting leftovers. A vehicle should not live in posting from last week. That is a stuck session, not a status you manage around.
• Posted vs. actually on the lot. Spot-check a sample against the deal board and the recon list.
• Sold and archived lag. If sold in the DMS and still posted here, the daily close is broken.

The weekly review only needs the five status labels and the owners. Do not invent extra statuses.

Status exceptions worth a name in the notes

Write names, not vibes:

• Who has the oldest failed unit?
• Who claimed drafts that never moved?
• Which import file created a cluster of drafts with row-level errors?

Import history with a row-level error log is the audit trail for the third question. If the same columns fail every week, the problem is the file, not the floor.

Part Two: Analytics by Rep and by Source

Once statuses are clean enough to trust, read posting analytics. The point is coaching and load, not a leaderboard.

Read by rep first

Ask questions the numbers can actually support:

• Who posted this week, and who only claimed?
• Is one person carrying the store while others live in "busy on the floor"?
• Are associates finishing assigned queues, or are they accumulating unfinished claims?
• Did anyone's volume spike in a way that looks like a burst rather than a paced day?

PostToMarket enforces daily post limits and human-like delays on the server. A week of healthy work looks like steady days, not one hero afternoon. For how to read the report without fooling yourself, see Reading Posting Analytics by Rep and Source.

Then read by source

Source is how inventory entered the system: bulk CSV or Excel import, capture from auction and wholesale sites, or other entry into inventory. A weekly manager review of statuses, analytics, and leads should notice:

• Auction captures that stay in draft because photos were never shot on the lot.
• A DMS export that always needs cleanup, which shows up as import errors then delayed posts.
• A source that produces units which fail more often, which is usually data quality, not "Facebook being Facebook."

Do not invent a conversion rate. You do not have a study. You have a board. If a source creates work that never posts, stop congratulating the importer.

Coaching that follows from the analytics

Keep the conversation operational. Do not use analytics as a public ranking in the sales meeting unless you are ready for people to game volume.

Part Three: Leads as the Test of Whether Posting Mattered

The last board is the leads inbox. Managers can see inquiries in one place. The weekly pass is about response discipline and inventory signals, not about writing a CRM novel. PostToMarket does not claim a CRM integration; this inbox is its own workflow.

What a manager should look at weekly

• Inquiries that sat unanswered into the next day.
• Repeat messages on units that were already sold (a status problem, not a sales problem).
• Units that draw questions about missing facts: mileage, price, accident history, or "is this still available?" Those are listing-quality issues.
• Uneven handling across reps, if you can see it from who owns follow-up.

A daily habit still matters. The weekly review is where you notice the pattern the daily glance missed. Pair this section with Using the PostToMarket Leads Inbox to Track Response Times.

Do not confuse a quiet inbox with a shadowban

A week of few inquiries can be price, photos, segment, or distribution. Meta does not publish a "shadowban" status. If listings are live and views look thin, diagnose like an operator: check current Marketplace and commerce policies, confirm the unit is actually posted, confirm it is priced like a real car, and avoid burst posting. No tool can guarantee Facebook will distribute every listing. The weekly review should record what you checked, not a story about an algorithm.

A Weekly Manager Review Agenda You Can Reuse Every Week

Use the same order every time so the meeting cannot wander.

1. Statuses (10 minutes). Counts for draft, failed, posting, posted, sold lag. Name owners for exceptions.
2. Analytics (10 minutes). Rep load, source delays, any burst-looking days. Decide queue sizes for next week.
3. Leads (8 minutes). Unanswered, sold-unit messages, listing-quality complaints.
4. Decisions (2 minutes). Who gets more assigned inventory, who gets less, which import file needs a fix, which units get pulled from posting until recon is done.

What to write down

A useful note is one page:

• Three exceptions with names.
• One process change (queue size, close discipline, import checklist).
• One listing-quality theme (lead photos, mileage in copy, sold hygiene).

If the note is a paragraph of feelings about "the market," the review did not happen.

How this differs from the admin's weekly pass

The manager review is operational: statuses, load, leads. The admin still needs a wider weekly look at team access, billing, and settings. That is a different hat. See Admin Guide: What to Review in PostToMarket Every Week and do not merge the two meetings into one rambling hour.

How PostToMarket Automates This

A weekly manager review of statuses, analytics, and leads fails when those three pictures live in chat, spreadsheets, and memory. PostToMarket keeps them in the dashboard areas that already exist — Inventory, Queue, Analytics, Leads — so the meeting is a reading of the same board the floor used all week. The product does not guarantee leads or sales. It makes the operational mistakes visible.

• Inventory statuses (draft, posting, posted, sold, failed) are the truth set for the first agenda block.
• Team queue view shows claims that analytics will later explain as "high claims, low posts."
• Posting analytics by rep and source support load and coaching without a homemade tracker.
• Leads inbox for managers is the third board.
• Import history and row-level error logs explain draft piles that came from a bad file, not from lazy reps.
• Mark as sold and archive is the control you inspect when sold-unit messages show up in the inbox.
• Roles (admin, manager, sales rep, sales associate) tell you who should have been assigning, self-queueing, or working only what they were given.

The weekly review becomes a short meeting because the system already captured the week.

Put the Week on a Board, Not on a Story

If your only Marketplace conversation is "we posted a lot," you are not managing the channel. You are narrating it. A weekly manager review of statuses, analytics, and leads is how a used-car manager coaches the floor, fixes imports, and stops sold cars from collecting messages.

PostToMarket includes unlimited vehicles in inventory, team queues, analytics, and a leads inbox on the Dealership plan at $299 per month, with up to 13 logins so the people in the meeting are the people in the product. A one-person lot can still run a lighter version of this review on Starter at $59 per month with a single login.

Start your 10-day free trial and check out through secure Stripe. Run one week against the three boards, then decide whether you still want to manage posting from hallway talk. Cancel anytime.