What an up log is, and why the software version never matches the floor
In short
An up log is the floor-traffic record a store keeps of everyone who walks in: who arrived, when, who greeted them and what happened. It does 2 jobs that pull against each other — settling whose turn it is, and counting traffic — and because it is completed voluntarily, after the fact, usually by the person who just lost the sale, its count is a lower bound rather than a total.
Key takeaways
- An up log records visits to the sales floor; a CRM record records people. Most ups never become CRM records.
- Its 2 jobs — rotation fairness and traffic measurement — want the row written at opposite ends of the visit.
- Whoever logs the up pays the cost of logging it, and on unsold traffic that is the person who just lost the sale.
- The missing rows are not random: they concentrate in unsold traffic, the population the log exists to count.
- Digitising the sheet fixes legibility, timestamps and rotation disputes, and inherits the undercount unchanged.
An up log is the record of everyone who reaches a dealership's sales floor: when they arrived, who greeted them, what they came to look at and what happened. It is a floor-traffic artefact, not a CRM record. A CRM record is created about a person whose contact details you captured; an up row exists whether or not anyone learned the visitor's surname, and most rows never get that far.
The name comes from the rotation — the salesperson who is "up" takes the next customer through the door, and the log is the referee. At month end the same log becomes the denominator in every closing-ratio conversation the store has. That second career is where the trouble starts.
Two jobs on one sheet, and they want opposite things
Rotation fairness needs the row created at arrival, before the greeting, with almost nothing in it. Traffic measurement needs it completed afterwards, once the outcome is known. Nearly every argument about the up log is an argument about which of those 2 jobs is being served this week.
| Job | Written when | Who needs it accurate | What it degrades into |
|---|---|---|---|
| Rotation fairness | At arrival, before the greeting | The sales floor | A queue log with no outcomes: you know whose turn it was, never what happened |
| Traffic measurement | After the visit, outcome known | The desk and the GM | Every sale is in it and the walkouts are thin |
| Follow-up on unsold visits | During the visit, with contact details | Whoever owns the cadence | A list of first names and no phone numbers |
A store that decides which of the 3 it is optimising for gets a usable artefact. One that leaves it implicit gets a sheet the floor defends as a fairness device and the desk quotes as a measurement.
The 7 fields that decide whether the log is worth keeping
- Arrival timestamp. Written at arrival, not reconstructed at close of day — reconstructed times cluster on the hour and destroy any hour-of-day view of showroom traffic.
- Up type. A walk-in, be-back, booked appointment, phone-up and internet lead arriving in person are 5 different denominators.
- Greeter, and current owner if it changed. Turnovers are where accountability for the row transfers and nobody writes it down.
- Vehicle of interest as a stock number. Free text like "blue SUV" cannot be joined to inventory — the same failure that makes a parts lookup return a part for the wrong engine.
- Stage markers: demo, write-up, desk, turnover. A visit that reached a write-up is a different animal from one that lasted 90 seconds.
- Outcome and disposition. Sold, be-back, not now and not a buyer are 4 different next actions; a free-text note is none of them.
- Whether contact details were captured, and which. This flag decides whether the visit is followable at all.
Why the count is always a floor, never a total
The person who logs the up pays the cost of logging it, and on unsold traffic that person has just lost the sale. Nobody designed that incentive; it falls out of who is standing there. It guarantees a voluntary log undercounts, and it predicts which rows go missing.
- The visitor nobody greeted. Busy floor, left after 4 minutes, and no salesperson has a reason to create the row.
- The 90-second up, logged as "just looking" if at all, because writing it feels like admitting to it.
- The turnover that went nowhere: 2 people touched the customer and each assumes the other wrote it up.
- The last hour of a Saturday. The rows that survive a hard day are the ones attached to a deal.
- The be-back logged as a fresh up — the one error running the other way, inflating the denominator with a duplicate visit.
Those absences concentrate in unsold traffic, precisely the population the measurement exists to count, so the direction of the error is knowable even when its size is not.
A closing ratio computed on a voluntary log is a ratio of sales to remembered visits, and people remember the ones they won.
Digitising the sheet fixes real problems: legible rows, honest timestamps, rotation disputes settled by a record, and a row that joins to a CRM record. It does not touch the incentive, and a tablet form with 20 fields where the clipboard had 8 makes completion worse. The only structural fix is to move capture off the closer — a receptionist or duty manager opens the row at the door in one tap and the salesperson completes it. Settle that before commissioning any lead-response and follow-up automation on top.
For a denominator you can defend, use a door counter or a people-count feed from cameras already on site, then be honest that it counts bodies: service customers crossing the showroom and one shopper stepping out for a call are both in it. Two imperfect counts that disagree in known directions beat one count whose error nobody will name — the argument for treating operational logs as instruments rather than paperwork that runs through our note on AI in logistics operations.
Up log or CRM record: not two views of one object
| Property | Up log row | CRM record |
|---|---|---|
| Identity | May be anonymous | Must resolve to a contactable person |
| Lifetime | One visit; 2 visits are 2 rows, permanently | The person, across years of visits and enquiries |
| Deduplication | Never merged — merging destroys the count | Merged deliberately, and getting it wrong causes its own damage |
| Owner | The floor or duty manager | The assigned salesperson or the BDC |
| Cost of a missing one | An undercounted denominator | A customer nobody contacts again |
The deduplication row catches people. Merging is right in the CRM and wrong in the log, and one rule applied to both either loses visits or creates the mess set out in three salespeople texting the same shopper. The join is one nullable field: the up row carries a CRM record id when contact details were captured, which is also the cleanest capture-rate measure the store will get.
Two limits belong on the record before anyone quotes an up count. It covers only the hours the doors are open, so it says nothing about the overnight population measured the way half your enquiries arriving when the store is shut sets out. And when 2 systems count the same thing they disagree, so the work is naming which hop lost the rows rather than picking the number you prefer, exactly as when the marketplace says it sent 40 leads and the CRM has 31. What happens to those rows next is the rest of the lead response and follow-up cluster, inside our automotive retail and aftermarket work.
Frequently asked questions
Short answers to the follow-ups this page tends to raise.
What is an up log at a dealership?
It is the running record of every visitor who reaches the sales floor — arrival time, who greeted them, what they came to see and how the visit ended. It settles whose turn it is to take the next customer and gives the store a traffic count. It is kept per visit, not per person, so the same shopper returning next weekend is a second row.
Is an up sheet the same thing as an up log?
Yes — the up sheet is the form and the up log is the record it produces. The distinction that matters is not paper versus digital but voluntary versus captured: a sheet completed by the salesperson after the visit and a row opened at the door by someone not selling anything produce very different numbers from the same day.
Can you trust a closing ratio from showroom traffic log software?
Treat it as a ceiling on performance rather than a measurement of it, because the denominator is a floor. Unlogged visits concentrate in unsold traffic, so the ratio is biased upward by an amount nobody can size. It stays useful for comparing one store against itself week to week, and is close to useless for comparing 2 stores.
Should the salesperson log the up, or someone else?
Someone else opens the row and the salesperson completes it. Capture at the door removes the conflict that makes the log undercount and leaves a much smaller job: adding outcome, stage and capture flags to a row that exists. Where there is nobody at the door, a manager sweeping the floor at fixed points is the next best option.
- up log
- showroom traffic
- dealership operations
- sales floor
The work behind this page
Builds from our portfolio that this page draws on.
Read next
- The marketplace says it sent 40 leads and your CRM has 31A vendor's lead count and your CRM's lead count disagree for four different reasons, and from inside the CRM all four look identical. Here is the reconciliation that tells them apart.diagnostic
- Disposition codes: 'no answer', 'not now' and 'not a buyer' differA disposition is not a note about the call. It is the instruction for what happens next, and a value naming no single action and owner cannot be automated.definition
- Lead source codes: why 3 systems give 3 answers on where a lead came fromSource in the CRM, in analytics and on the vendor invoice answer 3 different questions. Nominate one as the operational answer and stop reconciling the other two.definition
- The ADF lead: every field a CRM receives, and the three that decide routingADF is the XML format most third-party enquiries arrive in. The spec is old and loosely honoured, so a parser has to treat almost every element as optional — except three.definition
Working on something in this space?
Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.
Start the conversation