Writing Dealership SOPs From Scratch: A Simple Method

Ask a floor rep how to mark a car sold and you will get three answers, two of which skip Marketplace. Ask where the intake VIN photo lives and you will get a shrug toward a shared drive nobody has opened since the last internet manager left. The store has procedures. They live in people. When those people take a Saturday off, the procedure vanishes.

Writing dealership SOPs from scratch is not a documentation project for its own sake. It is how a used-car department survives turnover, weekend staff, and the gap between what the general manager thinks happens and what actually happens at 5:50 p.m. The method below is deliberately small: one job per page, tested on the floor, dated, and short enough that a new associate can run it without a lecture.

This guide is for general managers, used-car managers, and internet directors who do not have a corporate playbook and should not wait for one. It is operational. It is not legal advice, HR policy, or a substitute for your counsel on employment, advertising, or F&I.

Start With Jobs, Not Binders, When Writing Dealership SOPs From Scratch

A three-inch binder titled "Operations" is where procedures go to die. Start with the jobs that already fail when one person is absent.

Pick the ten jobs that hurt when they fail

Illustrative list for a used department — cut or add to match your lot:

1. Vehicle intake from purchase to lot (keys, VIN, packet).
2. Recon request and "ready for photos" handoff.
3. Photo day or contractor shoot.
4. Inventory data cleanup before any public listing.
5. Marketplace posting for a single unit.
6. Lead response on Messenger and after hours.
7. Appointment confirm the morning of the visit.
8. Pending and sold status, including pulling the listing.
9. Shift-change handoff of hot deals.
10. Delivery-day packet and walkaround.

If a job is not on a list like this, it is not an SOP candidate yet. You are not writing a novel of "how we do business." You are writing the steps that, if skipped, cost money or create a buyer complaint.

One owner per SOP

Every page has a role that owns the document (usually a manager) and a role that executes it (rep, associate, porter, recon). Ownership is not "the team." When two roles share a step, name who does it first and who verifies.

What an SOP is not

• Not a training lecture. Training uses the SOP; the SOP is the steps.
• Not a mission statement.
• Not a paste of a manufacturer's or platform's policy. Point people to the current source instead of quoting rules you will not update.
• Not a place to invent statistics or "best practice" percentages. Write what this store does.

The One-Page Template for Writing Dealership SOPs From Scratch

If it will not fit on one page (or two if the job is truly a sequence of checklists), you are mixing jobs. Split it.

Required blocks

Title and job — "Mark a unit sold and remove public listings," not "Inventory excellence."

When it starts / when it ends — Start: deal written or cash taken. End: inventory status is sold, listing is down, keys tagged.

Who — Primary role, backup role, manager who can override.

Tools — DMS screen, key board, PostToMarket inventory, Messenger, whatever is real. Do not list tools you do not use.

Steps — Numbered. Each step is an action a person can do without interpretation.

If this fails — Two or three exception paths (unit already pending, buyer walked, listing already removed).

Version — Date and initials. Old copies in drawers do not count.

Example skeleton (illustrative)

SOP-07  Mark unit sold and pull listings
Starts: deal written or funds received
Ends:   status sold, Marketplace listing gone, keys tagged
Owner:  sales manager    Does: closer or associate on duty

1. Confirm stock number and VIN on the deal match the unit.
2. Change inventory status to sold in the system of record.
3. Remove or archive the Marketplace listing the same day.
4. Tag keys and move the hook off "available."
5. Note the CRM / desk log: buyer name, stock, who pulled the listing.
If the listing cannot be removed immediately: notify the manager on duty
and log the blocker. Do not leave it for "tomorrow" with no name.
Version: 2026-10-15  J.R.

That is enough. The sold-unit hygiene process is a full article on why this job matters; the SOP is the store's actual clicks and tags.

Language rules

• Use the words your floor uses (stock, recon, up, pending).
• Write verbs: confirm, change, tag, notify.
• Ban "ensure," "appropriate," and "as needed" unless you immediately define them.
• If a step depends on state paperwork or advertising rules, write "confirm with the desk / counsel" rather than citing a statute you will not maintain.

Checklists vs procedures

Use a numbered procedure when order matters (intake, delivery). Use a bulleted checklist when items can be done in any order (lot walk observations). Mixing them on one page is how people skip the ordered part.

Test, Version, and Kill Dead Pages

An untested SOP is fiction. A never-revised SOP is archaeology.

Floor test in one shift

1. Hand the draft to someone who did not write it.
2. Watch them run the job on a real unit (or a supervised dry run).
3. Mark every pause, question, and workaround.
4. Edit the page the same day. Do not schedule a "documentation meeting" next month.

If the tester needs a sidebar explanation, the page is incomplete. Put the missing decision on the page or into a separate SOP.

Versioning without software theater

• Filename or header includes the date.
• One official copy in a known place (shared drive folder, binder at the desk, both if you print).
• When you change a step, change the date. Tell the people who execute it. A Slack message with the new page attached is enough.
• Archive the old page. Do not leave two versions in the same folder named SOP sold FINAL and SOP sold FINAL v2 REAL.

Kill or split

If a page grows past two pages, split the job. If nobody has used it in ninety days, it was not a job; it was a wish. Delete it from the working set so the working set stays small enough to train.

Connect SOPs to meetings you already run

The weekly inventory exposure meeting is a natural place to notice that recon handoff or posting coverage has no page. Do not add SOP writing as a standing agenda item that produces guilt. Add a page only when a failure repeats.

Train From the Page, Then Audit Lightly

SOPs fail in training when managers still onboard by "follow Maria around." Shadowing is fine. Shadowing without a page means Maria's shortcuts become the store.

Onboarding use

• Day one: the new hire runs two SOPs with a trainer watching (keys, greets, or posting a prepared unit).
• They initial that they ran them, not that they "read the binder."
• Marketplace posting onboarding can follow a one-day plan; the SOP is the posting steps inside that plan. See onboarding new sales reps on Marketplace posting.

Light audit

Once a week, pick one SOP and look for evidence it ran:

• Intake: VIN photo and packet complete on the last three arrivals.
• Sold: Saturday deliveries not still live online Monday.
• Handoff: shift log has next actions, not "talked to guy about truck."

Coach the miss against the page. If the page is wrong, edit the page. If the person skipped it, that is a performance conversation. Mixing those two responses is how staff learn to ignore documentation.

Internet sales process as a set, not one mega-SOP

An internet sales process around Marketplace is several jobs: post, reply, qualify, appoint, hand off, mark sold. Write each as its own page. A single "internet SOP" will be skipped.

How PostToMarket Automates This

SOPs describe the job. They still fail when the tools make the job optional — when status lives in a spreadsheet, queues live in a group chat, and sold units depend on someone remembering Facebook. PostToMarket makes the inventory and posting steps checkable, which is what a one-page SOP needs.

Steps you can actually point to

• Inventory statuses (draft, posting, posted, sold, failed) give the sold and pending SOPs a system of record besides the key board.
• Mark as sold and archive from inventory or the queue so "pull the listing" is a named action, not a hope.
• Import history and row-level error logs support an intake or DMS-export SOP: bad rows are visible instead of becoming live listings.

Roles that match the page

• Admin, manager, sales rep, and sales associate roles so the SOP's "who" is a permission, not a suggestion.
• Managers assign vehicles to associate queues; sales reps self-queue; associates work only what they are given. That is an SOP for posting ownership without a speech.
• Team queue view to release stuck claims when the person named in the SOP is out.

Evidence for the light audit

• Team analytics by rep and source, so posting SOPs can be checked without asking who "thinks" they posted.
• Leads inbox for managers reviewing response SOPs.
• Mobile dashboard so a floor SOP that says "reorder the queue between customers" is possible on a phone.
• Chrome extension posting one vehicle at a time with human-like delays and server-enforced daily limits, which belongs in the posting SOP as the actual method rather than "post the cars."

PostToMarket is not affiliated with Meta. It does not replace your written pages. It is the dashboard those pages should name: Inventory, Import, Queue, Team, Leads, Analytics, Billing, and Settings.

Write Five Pages This Week, Then Run Them Live

If writing dealership SOPs from scratch still sounds like a winter project, you will still be explaining sold-unit steps verbally in June. Five jobs, five pages, one floor test each, is a better store than a planned binder.

PostToMarket is the system those pages can reference for inventory, queues, and Marketplace posting. Starter is $59 per month with one login if you are documenting a solo lot. Dealership is $299 per month with up to 13 logins when managers, reps, and associates each have a role on the page.

Start your 10-day free trial with secure Stripe checkout. Import inventory, assign a queue, and write the posting SOP against the real screens. Cancel anytime.