Using Statuses to Build a Daily Exception List

Open Inventory at 10:15 a.m. and you can drown. Unlimited vehicles means the grid is large on purpose. The useful question is not "how many units do we have?" It is "which records are in a state that requires a human this morning?" That is an exception list. If you do not build one, you will manage by whoever yells, and the quiet failures — a draft from last week's import, a failed post, a sold car still marked posted — will sit until a buyer messages you about a car that is gone.

Using statuses to build a daily exception list is a manager habit: filter the day through draft, posting, posted, sold, and failed, write down only the rows that break the expected path, and assign an owner before lunch. It is narrower than a monthly audit and slower than a five-minute stand-up. It is the written work those meetings should produce.

This article is for used-car managers, internet directors, and admins who can see the whole inventory. Associates should not be asked to build the store's exception list; they should receive the pieces that belong in their queue.

Using Statuses to Build a Daily Exception List: What Counts

An exception is a record whose status does not match the story the floor believes, or a record that has stayed in a transitional or unfinished state longer than your operating standard.

The five statuses, used as exception detectors

For definitions and movement between states, keep PostToMarket inventory statuses explained next to this workflow. This article assumes you already know the words.

What does not belong on the daily list

• Every draft in a 200-unit store. That is inventory, not an exception.
• Every posted unit. Posted is the success state.
• Pricing strategy debates that are not tied to a wrong status.
• Facebook reach complaints. Status is not a distribution report, and no tool can guarantee Facebook will show every listing.

If a row is doing what the status says it should, leave it off the page.

How to Build a Daily Exception List From Statuses Each Morning

Same order every day so your eye does not wander into the pretty SUVs.

Pass 1: Failed

Failed is always first. Each failed VIN goes on the list with a cause bucket:

• Data (VIN, price, mileage, required field).
• Media (no usable photos, wrong gallery).
• Session (extension not signed in, browser closed mid-post).
• Unknown (needs a manager, possibly a Facebook-side block).

Unknown does not stay unknown for a week. If you cannot classify it today, it still gets an owner. Retrying without a cause is how failed becomes a personality trait of that VIN.

Pass 2: Posting that is still posting

Posting should be brief. PostToMarket submits one vehicle at a time with delays; a unit should not live in posting while the poster is at lunch and the laptop is closed. If it does, the exception is "session interrupted," and the owner is the person whose queue it sits in. Do not create a second queue item for the same VIN while the first is still posting.

Pass 3: Sold that is not clean

Look for sold units that are still claimed, still in a posting queue, or still treated as live work. The action is mark sold and archive, plus release the claim if needed. If this pass is long, you do not have an exception problem. You have a sold-unit SOP problem. See handling a sold unit that is still in a rep queue.

Pass 4: Drafts that should have moved

You will not list every draft. You will list drafts that violate a rule you already set, for example:

• Imported before yesterday and still unqueued, if they are available.
• Captured from auction yesterday, verified, and still sitting.
• Units on the aging report with photos and a current price.

A growing draft pile after a clean import is a queue-ownership exception, not an import exception. Send those VINs to the stand-up or assign them to associates the same morning.

Pass 5: Posted records the floor knows are wrong

This pass is qualitative and should stay short. Examples: a posted unit whose price changed on the window, a posted unit that went into recon overnight, a posted unit with the twin's photos. Status is "posted" and still an exception because the commercial story is false. Fix the record, then fix the live listing. Do not pretend a dashboard edit rewrites Facebook by magic.

Turn the List Into Owners, Not Into a Newsletter

A list without names is a blog post. Use a simple table.

Assignment rules that keep the list honest

• Associates receive work only through manager assignment. Do not email them a VIN and hope.
• Reps can take self-queued drafts from the list if they have capacity under your conservative daily ceiling.
• Failed-unknown stays with a manager until it is classified.
• The person who imported a bad file owns the data exceptions from that file for the day, even if someone else will post the unit later.

Cap the list. If you have more exceptions than the floor can clear by early afternoon, you are looking at a process failure (import quality, last look, sold hygiene) and the daily list is only triage. Put the pattern on the weekly manager review instead of pretending thirty failed rows are a normal Tuesday.

When to stop building and start walking

The list is finished when each line has an owner and a definition of done. It is not finished when you have explained every VIN to yourself. Walk the first three items. Managers who polish the spreadsheet until 11:40 a.m. have built a report, not an exception list.

For a slower, deeper pass, the monthly inventory audit using PostToMarket statuses exists. Do not run a monthly audit every morning.

Connect Exceptions to the Rest of the Day

Statuses are shared language. The exception list is how that language becomes a work order.

After stand-up, not instead of it

The five-minute daily stand-up built on queue status assigns people. The exception list captures what the stand-up did not have time to write down. If you only do the meeting, you will forget the fourth failed VIN. If you only do the list, nobody will release a claim before the lot gets busy.

Feed yesterday's leftovers first

Exceptions that repeat from yesterday go to the top of today's list. A failed unit that failed twice is not "still in the flow." It is blocked. Pull it from retry loops until the cause is real.

Close the list at end of day

At close, mark each line cleared, carried, or escalated. Carried items that survive three closes become SOP work: import checklist, last look, or offboarding. Escalated items can go to PostToMarket support with VIN, timestamp, status, and login — not as a substitute for cleaning your own data.

How PostToMarket Automates This

Using statuses to build a daily exception list is possible because every vehicle already carries one of five states. The work is filtering and ownership, not inventing a coding system in a spreadsheet.

• Draft, posting, posted, sold, failed on every inventory record, visible to the people whose roles can see inventory.
• Team queue view to see whether an exception is also a stuck claim, and to release it.
• Import history and row-level error logs to explain a cluster of draft or failed data problems after an upload.
• Mark as sold and archive as the standard exit for sold exceptions.
• Team analytics by rep and source when the exception pattern is "one login never completes posting," which is a coaching issue rather than a VIN issue.

PostToMarket is independent and not affiliated with Meta. Statuses describe your inventory workflow. They are not a promise about listing distribution.

Build Tomorrow's List From Live Statuses, Then Keep the Habit

Using statuses to build a daily exception list turns a large inventory grid into a short work order: failed first, hanging posting second, dirty sold third, stale drafts fourth, known-wrong posted units last. Assign owners the same morning.

PostToMarket gives you those statuses, queues, and import logs on every plan. A solo lot can run the list on Starter at $59 per month with one login. A store that needs managers assigning around a full floor uses Dealership at $299 per month, up to 13 logins.

Start your 10-day free trial with secure Stripe checkout. On the first weekday of the trial, write this list from real statuses and clear it before lunch. That exercise tells you more than a feature tour. Cancel anytime.