A Weekly Draft Review: Clearing Units That Never Got Posted

A draft in inventory feels like a completed task. The VIN is in the system. Someone captured it, imported it, or typed it. The used-car manager glances at a long list and assumes those units are "in process." They are not. A draft that never reaches a queue is a unit the public cannot see, and days-to-turn still runs on it. The most expensive inventory on many lots is not the 90-day unit with a live listing. It is the 12-day unit that nobody posted because the record looked unfinished and nobody owned the finish.

Drafts accumulate for boring reasons: photos not shot, price not approved, recon not done, a rep who claimed the unit then took a day off, an import that created rows the desk never reviewed. None of those reasons is a strategy. They are leftovers. Leftovers become a second, invisible inventory unless a manager runs a weekly draft review.

This article is that review. It is written for used-car managers and internet directors who already have inventory in PostToMarket and want a one-meeting routine that clears units that never got posted, without dumping unverified cars onto Marketplace just to empty the list.

Why a Weekly Draft Review Beats an End-of-Month Surprise

Monthly close is the wrong time to discover that 18 units never left draft. By then the cars have been on the lot, the floor has been walking past them, and any Marketplace window you wanted in the first week of ownership is gone. A weekly pass is small enough to finish and frequent enough to catch stalls while they are still cheap.

What a draft actually means operationally

In a healthy workflow, draft is a waiting room, not a storage unit. A record belongs in draft when something real is missing:

• Photos of this VIN are not in the listing set yet.
• Retail price is not approved.
• The car is in transit or in recon and you have chosen not to advertise it yet.
• The row came from capture or import and has not been verified.

A record does not belong in draft because nobody decided. "We'll get to it" is how units that never got posted spend two weeks in the same status.

The hidden holding cost of unpublished inventory

Every unposted day is a day of floor-plan interest with zero chance of an inquiry. That relationship is the same math behind days-to-turn and online exposure: exposure is not the same as ownership. A car can be in your DMS, on your lot, and still commercially invisible. Draft is the status that makes that invisibility look organized.

Run the review on the same weekday every week. Friday afternoon works for stores that want a clean queue going into the weekend. Monday morning works for stores that want the used-car manager to assign work before the floor gets busy. Pick one and put it on the calendar as a 20-minute standing meeting, not a "when I have time" scan.

How to Run the Weekly Draft Review in Twenty Minutes

Open Inventory, filter to draft, and sort by oldest first. You are not reading every field. You are classifying each row into one of four buckets. Write the bucket on a notepad or in a shared note; the point is a decision, not a new report.

The four buckets

1. Post this week. Data is clean, photos exist or will exist today, price is approved, the car can be shown. Queue it before the meeting ends, or assign it to an associate during the meeting.
2. Hold with a reason and a date. In body, waiting on a part, in transit, title not in, photos scheduled for Tuesday. The reason must be specific and the date must be this week or next. "On hold" with no date is how drafts never get posted.
3. Fix then post. Wrong trim, blank mileage, wholesale price still in the field, duplicate VIN. These are not holds. They are data jobs. Assign the fix to a named person with a same-day due time.
4. Clear. Sold wholesale, deal fell through and the unit left, duplicate of a posted record, test row from a training import. Mark sold and archive, or remove it from the working inventory so it stops looking like a live problem.

A one-page checklist for the meeting

• How many drafts older than seven days?
• How many have no owner (not in any queue)?
• How many are in a queue but still draft because the rep never posted?
• How many arrived from last week's import or auction capture and were never verified?
• Which holds expired (the date on last week's note has passed)?

If you cannot answer those five questions in twenty minutes, the inventory list is too noisy. Archive the junk first, then rerun the counts.

Who sits in the meeting

The used-car manager runs it. Bring the person who owns photos and the person who owns pricing if those are the usual stall reasons. Do not bring the whole sales floor. A weekly draft review is a dispatch meeting, not a town hall. Associates do not decide what stays in draft; they receive the units you have already classified as "post this week."

Clearing Units That Never Got Posted: Decision Rules

The hard part is not identifying drafts. It is deciding that some of them should leave inventory instead of sitting there as a reminder. Managers keep dead rows because deleting feels like losing a unit. You are not losing the car. You are stopping a ghost record from hiding the real work.

When to keep a draft

Keep it when the physical unit is still yours and you intend to retail it, and the stall has a named blocker. Examples:

• Recon not complete, and you have a policy of not advertising units that cannot be shown.
• Photos scheduled, date on the calendar.
• Price waiting on a pack or a manager approval that will happen today.

When to archive or mark sold

• The unit sold and the listing never went up. Still mark it sold. You need the record of what happened more than you need a draft of a car that is gone.
• The unit went wholesale or back to auction. Same treatment.
• The row is a duplicate. Keep the record that matches the deal jacket. Clear the extra.
• The row was a training import or a test VIN. It should never have survived the week.

When a queued draft is actually a people problem

A unit that is in a rep's queue and still draft after several days is not an inventory problem. It is a claim problem. Either the rep is overloaded, the photos were never shot, or the rep does not know the unit is theirs. Use the team queue view to see who holds it. Release the claim if the owner is out. Reassign if you already know who should post it. Do not let "it's in someone's queue" count as a plan.

This is the same discipline you want in daily exception handling, just at a weekly cadence. If you later add a daily pass, keep this weekly review for the older tail so the morning meeting does not become an archaeology session.

Connect drafts to posting KPIs

A store that only tracks "how many we posted this week" will miss the draft pile. Add one line to the used-car manager's weekly numbers: count of drafts older than seven days, and count cleared. That pair belongs with the rest of the Marketplace posting KPIs a general manager should track. Volume without a draft-age number is how a team looks busy while units stay unpublished.

Pitfalls That Make the Review Useless

A weekly ritual can still fail. These are the failure modes that show up after a month of "we already do that."

Rubber-stamping holds

If every aged draft is marked "recon" with no date, you have renamed the problem. Require a date. When the date passes, the unit is either queued or the hold is rewritten with a new reason. Third rewrite in a row goes to the GM: the car may not belong in retail inventory.

Posting to empty the list

The review is not a license to dump unverified rows onto Marketplace so the draft count hits zero. That creates failed posts, bad copy, and buyer messages about cars that are in paint. Clearing means deciding. It does not mean posting garbage.

No owner after the meeting

Every "post this week" unit needs a name before people stand up. Manager assigns it to an associate, or a sales rep self-queues it in the room. A list of "we should post these" that returns to draft by Wednesday is a meeting that did not happen.

Ignoring failed alongside draft

Failed is not draft, but it is the same commercial outcome: the public cannot see the car. Glance at failed in the same twenty minutes. A unit that attempted to post and lost should not wait for next month's audit.

Treating import leftovers as inventory

A bulk import can create dozens of drafts in one afternoon. If the import included sold, wholesale, or incomplete rows, those drafts will haunt the weekly review forever. Fix the file and the error log at import time so the weekly meeting is about real cars.

How PostToMarket Automates This

A weekly draft review only works if every unit has a status the whole store trusts, and if stalled work is visible without asking each rep what they meant to do. PostToMarket keeps inventory, queues, and posting state in one place so the meeting is a filter-and-decide exercise instead of a scavenger hunt.

Statuses that make the pile visible

• Inventory statuses: draft, posting, posted, sold, failed. Filter to draft and you are looking at unpublished inventory, not a mixed spreadsheet.
• Mark as sold and archive from inventory or the queue when the weekly review finds units that already moved.
• Unlimited vehicles in inventory, so drafts can sit for a legitimate hold without being deleted to "make room."

Getting units into a clean draft state in the first place

• Bulk CSV and Excel import with import history and a row-level error log, so bad rows are fixed at upload instead of lingering as mystery drafts.
• Capture from auction and wholesale sites into inventory, then leave those records in draft until photos and price exist.
• AI-generated titles and descriptions, editable before posting, so "the copy isn't written" is not a reason a unit sits unpublished for a week.

Turning "post this week" into assigned work

• Personal posting queues and per-rep queues.
• Managers assign vehicles to associate queues; sales reps self-queue from shared inventory during or right after the meeting.
• Team queue view: see and release any claim that is blocking a draft from moving.
• Chrome extension posts one vehicle at a time with human-like delays and server-enforced daily limits, so the units you cleared into queue actually go out over the following days instead of in one burst.
• Mobile dashboard so a rep can reorder that newly assigned queue between customers.

The review stays a manager conversation. The product keeps the list honest so the conversation is about cars, not about who has a screenshot of a spreadsheet.

Stop Letting Drafts Pretend They Are Posted

If your inventory screen is full of drafts older than a week, you do not have a posting volume problem. You have a decision problem. Run the weekly draft review, put a name and a date on every hold, and clear the rows that will never go live. Units that never got posted are still costing you; they are just doing it quietly.

PostToMarket is built for that operating rhythm: unlimited inventory, statuses the floor can filter, queues managers can assign, and AutoPost that works the queue without depending on a rep to remember the leftover list. Starter runs $59 per month for a solo seller with one login who needs the draft pile visible. Dealership runs $299 per month for up to 13 logins, so the used-car manager and the floor can share the same statuses.

Start your 10-day free trial with secure Stripe checkout. Import or capture this week's buys, leave them in draft on purpose, then run this review once. Cancel anytime. Questions on statuses or queues go to info@posttomarket.com.