Evidence-aligned decision tools

Start with the decision—not the department.

Across the public dealership research DPL reviewed from 2021 through 2026, the same operating question appeared in different forms: the visible result is usually downstream of several connected conditions. That is DPL’s synthesis—not a finding from any single source. Choose the problem closest to today’s decision and build a private Dealer Operating Brief before reaching for a universal benchmark.

Private by designThe brief stays in the browser, requires no email, and produces an operating question, actions, a five-event observation, evidence context, and the relevant next path. It is not a score, diagnosis, compliance review, credit decision, valuation, or product recommendation.
FIELD TOOL · DPL-FI-001

Log five handoffs.

An abstract analytical composition of charts, reference lines, and layered research documents in navy and warm white.
Five real deals. One shared definition. A practical field log for seeing where time, context, and ownership start to break down.
FIVE-DEAL FIELD LOG · EXPLORATORY

Do not give us your averages. Show us five real transitions.

For five consecutive deals, capture the clock, readiness, rework, and ownership. The purpose is not to grade a person or store. It is to make the operating path visible.
OWNER-OPERATOR WORKFLOW

A handoff can happen inside one person.

Founding field instrument · Version 1.0
Five handoffs · Sales to F&I
A field log, not a performance score

Five real deals. One visible operating path.

The five-handoff log replaces the mythical average day with five specific transitions a dealership can inspect, compare, and discuss without assigning blame.

Status · Founding cohort open
DPL Field Instrument

Five-Handoff Field Log

DPL-FI-001 · Version 1.0
Question
What happens between deal-ready and F&I start?
Window
Five consecutive live deals
Evidence
Descriptive field observation
Moment
What changed?
What was upstream?
What would verify it?
Preparation
What changed?
Record the first task shortened, delayed, delegated, or skipped.
What was upstream?
Demand pattern, deal readiness, approvals, or staffing coverage.
What would verify it?
Compare three similar periods and note whether the same step changes.
Handoff
What changed?
Record context that is missing, repeated, or reinterpreted.
What was upstream?
Ownership, system fields, timing, or competing priorities.
What would verify it?
Observe five consecutive handoffs using one shared definition.
Customer conversation
What changed?
Record where waiting or urgency changes the exchange.
What was upstream?
Queue length, interruptions, prior expectations, or room readiness.
What would verify it?
Timestamp arrival, handoff, and conversation start for one busy window.
Follow-through
What changed?
Record exceptions, rework, or items that age after delivery.
What was upstream?
Documentation, funding complexity, product setup, or downstream load.
What would verify it?
Review exception age and the reason work returned to the queue.

Use the same definitions across five consecutive deals. The log organizes observation; it does not calculate a score, assign blame, or establish a benchmark.

A five-deal field run

Use five real transitions before trusting the average.

The goal is not instant certainty. It is five observations made with the same definitions—enough to see where the clock, readiness, rework, or ownership deserves a closer look.

01

Choose one real window

Use a recent busy period people can remember specifically. Avoid the mythical ‘average day.’

02

Name the first deviation

Document the earliest point where the intended process changed—not merely the last visible result.

03

Look one step upstream

Ask which condition made the deviation more likely: timing, information, ownership, access, or load.

04

Set the next observation

Define what to watch, for how long, and what evidence would strengthen or weaken the explanation.

What the brief does

Separates observation from inference, documents upstream conditions, and creates a reviewable next step.

What it does not do

It does not assign blame, produce a universal benchmark, or calculate the correct staffing level from a few prompts.

Begin the five-deal field log →

Operator tool · DPL-SL-001

Turn the visible symptom into a better operating question.

Choose the first condition you can actually see. The lens returns a sharper question and one disciplined five-deal observation—not a diagnosis.

First visible signal
Clock / elapsed timeObservation frame
Where does the customer’s clock begin—and which part of the wait has no clear owner?
Observe next

On five consecutive deals, record deal-ready, the first F&I conversation, and the first moment the work could not advance.

Do not conclude yet

Elapsed time alone does not establish a staffing problem or identify the root cause.

Deal 01
Deal 02
Deal 03
Deal 04
Deal 05