Source synthesis, not an empirical claim-file study. Title and lien delay can be described with dated document events and mismatch categories; the review does not determine ownership, lien validity, or settlement entitlement.
Research question and scope
The review asks how long a total loss file takes to move from settlement authorization to a complete title and lien packet, and where documented mismatches add repeat work. The unit is a total loss file with a dated settlement event and a document checklist.
It does not decide who owns the vehicle, whether a lien is valid, or whether a settlement amount is correct. Those questions require legal or claims authority and are not answered by cycle-time data.
Population and event log
Define the population from a fixed total loss export with a stated authorization date range. Record the state of title, ownership type, lien status, and the checklist version used. Include files with electronic titles and files that required a paper title.
Build a dated event log for each file: authorization, first document request, document receipt, mismatch identified, corrected document received, and packet release. A status without a date cannot support a cycle-time measure.
Measures and mismatch categories
Measure days from authorization to first request and from request to complete packet. Count the number of requests per file and the number of mismatch cycles. Categorize mismatches as name, lien, signature, title form, payoff amount, or address.
Keep a separate count for files waiting on the customer and files waiting on an institution. A single elapsed-time figure mixes two different constraints and makes the queue look uniformly slow or uniformly fast.
Sampling and agreement
Stratify by state, title type, lien presence, and owner count. Oversample files with more than one request and files that closed without a release. Record the sample seed and any replacement.
Two reviewers should classify mismatch events from the same document set. Preserve the first-pass category and adjudicate differences against a written definition. A title that lists two owners but only one signature is a signature mismatch, not a customer delay, unless the record shows the request was never sent.
Analysis and limitations
Report medians, interquartile ranges, and counts by mismatch category. Inspect the longest files individually. A high cycle time may reflect a state processing delay, a missing lien release, or a request sent to the wrong servicer address.
The review cannot establish that a faster packet would produce a faster settlement, and it cannot determine legal title. State-processing rules, electronic-title availability, and ownership disputes are outside the data. Findings should be framed as process questions for the responsible owner.
Privacy and replication
Vehicle titles and lien documents contain names, addresses, and account numbers. Use a restricted working file, replace identifiers with a crosswalk, and report only aggregate categories.
Retain the export query, event-log definitions, checklist version, codebook, sample seed, and reviewer decisions. A qualified reviewer should be able to rebuild the cycle-time table without opening the original claim system.
Method note
We reviewed public title guidance, consumer insurance material, and internal-control principles, then defined document-event measures. No vehicle files or settlement records were used.
Sources
Common questions
Does a complete packet prove the vehicle title is valid?
No. It shows the documents the carrier requires are present. Legal title and lien validity are determined by the state and the parties.
How should a customer-caused delay be classified?
Only when the record shows a request was sent and the customer did not respond. Otherwise classify the waiting party from the documented event.
Can electronic titles be compared with paper titles?
Yes, if title type is a stratification variable and the event definitions account for verification steps that differ by state.
Apply the brief to a real queue
Bring the source records, current procedure, and known exceptions. We will help turn the evidence questions into a bounded support role and review plan.
Discuss your workflow