Dealer Performance Lab · Field Instrument
DPL-FI-001 · Version 1.0
Founding handoff cohort

Log five handoffs.

Use five consecutive live deals to document what happened between deal-ready and the start of F&I. This is a field record—not a performance score.

What to expect

Five consecutive handoffs. One short submission after the fifth.

Observe five consecutive live deals—do not select the best or worst.
Set aside one short session after the fifth handoff to enter the record.
No customer names, VINs, credit or DMS data, employee grading, or public rankings.
01
Choose a private participant ID
02
Observe five consecutive handoffs
03
Submit the record and optionally compare notes

Five deals. One honest operating record.

You leave with a shared language for clock, readiness, rework, and ownership. DPL receives one clearly labeled exploratory record—not a score or benchmark.

Start with an alias—not a customer record.

Contact information is optional and is not used as an observation field.

Record the handoff—not the person.

Use the same definitions for each consecutive live deal.

Record the handoff—not the person.

Use the same definitions for each consecutive live deal.

Record the handoff—not the person.

Use the same definitions for each consecutive live deal.

Record the handoff—not the person.

Use the same definitions for each consecutive live deal.

Record the handoff—not the person.

Use the same definitions for each consecutive live deal.

One last integrity check.

Exploratory fieldwork is useful only when the collection rule is followed.

Send the five-handoff field record.

Submitting does not enroll you in marketing or create a performance score. DPL may compare these observations only within the stated exploratory scope.

Five handoffs received.

Thank you. Your field record is now part of the founding pilot. It will be reviewed as exploratory evidence—not as a store or employee score.

Return to the Handoff Observatory →

Want to compare notes? Send the Lab the situation as it actually exists. No polished story required.

Compare notes with the Lab →

Your private operator record

Five-handoff summary

Prepared from the five handoffs entered in this browser.

Fastest handoff—
Median handoff—
Longest handoff—

The five observations

Response patterns

Readiness
Rework
Ownership
Customer wait signal

Observation notes

No optional notes were entered.

This is a descriptive field record, not a performance score or benchmark. It remains in this page view unless it is copied or printed.

That record did not make it through.

Your entries may still be on this page. Try submitting again. If the problem continues, copy any longer notes before refreshing.

Tell the Lab what happened →
Shared definitions

What counts as deal-ready?

Use the moment your store believes the deal can move toward F&I—not necessarily when every downstream condition is actually ready.

Review the full instrument →
Participant protection

No names. No rankings. No sales sequence.

Participation is not treated as a lead. Identifying details and quotations are never published without permission.

Ask the Lab a question →
Evidence level

Exploratory field observation.

This founding pilot tests definitions and collection behavior. It does not establish a national benchmark or causal claim.

Read the research standard →
After the field log
Research signal · not a score
What happens next

Your five handoffs do not disappear into a dashboard.

The value is not the form submission. It is the honest operating conversation that can follow when a repeated condition becomes visible.

01
The entry is received

You get an on-screen confirmation. Send operational context only—never customer names or personally identifying information.

02
The signal is read

The log is treated as research input: a clue about clock, readiness, rework, or ownership—not an employee score.

03
The relationship stays human

If you want to compare notes, bring the Lab the situation as it actually exists. No pitch deck is required.

A necessary boundary
DPL may describe de-identified operating patterns in aggregate. A submitted field log is not permission to publish a store name, a customer detail, or a public case study.