For the past six months, I decided to try out Progressive’s Snapshot Discount program. This program involves using a device that plugs into your car and tracks your driving habits to potentially lower your insurance rates. As a car expert and content creator for carw.store, I wanted to delve into how this “Progressive Car Scanner” really works and if it’s beneficial for drivers. My experience with Snapshot has been enlightening, and in this review, I’ll share my findings to help you decide if participating in this monitoring program is the right choice for you.
When I first signed up, I didn’t fully grasp the intricacies of the program. However, after several months of use, I’ve gained valuable insights about these devices that every car owner considering usage-based insurance should understand.
UPDATE: For more recent reflections, check out my follow-up thoughts on Progressive Snapshot, which expands on this initial review.
Progressive Snapshot: Unpacking the Claims
“Save up to 30 percent!” That’s the catchy slogan from Progressive’s ads, often featuring their memorable character, Flo, promoting the Snapshot Discount. Intrigued by the potential savings, I decided to test it out myself to see if the promised discounts lived up to the hype. When I was quickly purchasing insurance for my new 2014 Mustang straight off the dealer’s lot, opting for the Snapshot program seemed like a good idea without much initial research.
I reasoned, what’s the downside? Even a small percentage discount would be worthwhile, given my typical driving habits. However, a thought lingered: was I putting a price on my privacy? How much was that really worth? The answer, as you’ll see later, might be surprising.
After just a week with the Snapshot device plugged into my car, my feelings were mixed. While the constant beeping (more on that later) was initially annoying, the access to data about my driving activity sparked my curiosity. Once you commit to the program, it’s generally recommended to complete the full term. Ending it prematurely could potentially lead to rate increases based on a limited data sample. To help you understand the program better, I’m going to share the data Snapshot collected from my driving.
Ask anyone who has used the Snapshot device what their biggest frustration is, and you’ll likely hear about the “BEEP-BEEP-BEEP” sound. This sound is the device’s way of signaling that it has recorded an instance of what it considers “hard braking.” It’s a direct feedback mechanism, letting you know you’ve been “flagged” for slowing down a bit too abruptly.
Understanding the Progressive Snapshot Device: More Than Just a Simple Scanner
The Progressive Snapshot device is a compact module designed to connect to your car’s On-Board Diagnostics Type 2 (OBD-II) port. The OBD-II system is a standard in modern vehicles, primarily used by mechanics to diagnose vehicle issues. It offers access to a vast array of your car’s systems, from the engine and transmission to brakes and electronics. Essentially, if your car monitors it, the OBD-II system can access it.
The Snapshot device packs considerable technology into its small, roughly 2” x 3” frame. Inside, you’ll find a memory chip for data storage, a cellular radio for transmitting data, and a GPS radio for location tracking. For those technically inclined, you can explore the patent for a deeper dive into its internal components. While you drive, the Snapshot device is continuously sending your vehicle’s data to Progressive’s servers. My device utilized a quad-band GSM module (datasheet available), which is logical considering Progressive’s partnership with AT&T for data services.
Progressive states on their website that they monitor vehicle speed but not location data. This is a deliberate choice, not a technical limitation. The device is technically capable of tracking location, similar to a smartphone connected via the AT&T network. However, they are less transparent about the full range of vehicle data they collect. Are they also tracking RPMs, throttle position, or other metrics? While the specifics remain undisclosed, it’s reasonable to assume they could access a wide range of data through the OBD-II connection.
Since I initially enrolled, Progressive has refined their guidance on who benefits most from the Snapshot program. Interestingly, this detailed information is only accessible to existing customers once they log into their account portal, not to the general public. Their publicly available FAQs regarding the program certainly present a more optimistic view.
A screenshot from Progressive’s website, titled “Is Snapshot Right For Me?”, outlines factors that make drivers ideal candidates for their usage-based insurance program.
Furthermore, the complete terms and conditions of the Snapshot Discount program are not readily available until you agree to participate. To save you the trouble of searching, as it’s not visible to non-customers, here’s a direct link to the Snapshot Terms & Conditions. It’s worthwhile to review these terms carefully before opting in.
As part of the program agreement, there’s a strict warning against reverse-engineering, disassembling, or otherwise tampering with the device. While I respected this, from a technical standpoint, it wouldn’t be overly complicated to investigate the exact data transmitted. One could even imagine using sophisticated tools, though perhaps that’s an unnecessary level of scrutiny. More simply, the OBD-II protocol itself is fairly open, potentially allowing for monitoring of data flow between the port and the device – a classic man-in-the-middle approach. But I digress; such technical explorations are beyond the scope of a typical user.
How Progressive Snapshot Evaluates Your Driving: Braking and Time of Day
Based on my experience, the Snapshot device primarily focuses on two types of driving data to assess your driving behavior. The first is deceleration rate, specifically instances of “hard braking,” which I’ll explain in detail shortly. The second is the time of day when you drive. The device logs the time your car starts, regardless of whether the vehicle is immediately in motion. (For instance, one evening, while working on my car, I started it briefly late at night; the Snapshot registered this as “driving” during a high-risk period, even though the car barely moved.)
Surprisingly, the device doesn’t seem to flag rapid acceleration or high velocity directly. In theory, aggressive acceleration wouldn’t negatively impact your score. However, abrupt deceleration will trigger a “hard braking” event. This brings up the issue of potential false positives.
Consider situations where your tires lose traction, such as driving on ice, unpaved roads, or even wet surfaces. When tires spin, they rotate faster than the vehicle’s actual speed. When traction is regained, they rapidly decelerate to match the vehicle speed. The Snapshot device can misinterpret this as hard braking, even if you haven’t applied the brakes. This is because the vehicle speed sensor is often located in the transmission, so spinning tires cause the driveshaft and sensor to rotate faster, leading to a false reading of rapid deceleration. Your speedometer might even indicate movement while the car is stationary, further illustrating this point.
The Subjectivity of “Hard Braking”: Is 7 MPH/Second Realistic?
Progressive defines a “hard brake” as any deceleration exceeding 7 miles per hour per second. This can be triggered not only by braking but also by engine braking or even coasting downhill rapidly. While I can’t confirm specific speed thresholds that might influence this, my experience suggests this 7 mph/second threshold is consistently applied across different speeds.
In my opinion, the 7 MPH/second threshold is overly simplistic and doesn’t realistically account for diverse driving conditions. It’s a rigid rule that overlooks factors like vehicle inertia and basic physics. If you drive regularly in an urban environment – good luck avoiding hard brakes! After understanding this sensitivity, I consciously tried to limit my deceleration to no more than 10 MPH per second, constantly monitoring my speedometer. This strategy was somewhat effective in reducing hard brake events.
To illustrate why I believe 7 MPH/second (approximately 10.27 feet per second) is an inadequate measure of “safe” braking, consider these common driving scenarios:
- Scenario 1: High-Speed Deceleration. Reducing speed from 75MPH (110 feet per second) to 25MPH (36.67 feet per second) requires a minimum of 7.1 seconds to stay within the 7 MPH/second deceleration limit.
- Scenario 2: Emergency Stop from Highway Speed. Coming to a complete stop from 75 MPH (110 feet per second) necessitates at least 11 seconds to avoid exceeding the hard braking threshold.
- Scenario 3: City Stop from Moderate Speed. Slowing to a complete stop from 45MPH (66 feet per second), such as when making a left turn, still requires 6.4 seconds to remain under the 7 MPH/second limit.
These examples highlight that safe deceleration time is heavily dependent on initial speed. The crucial factor is maintaining adequate distance from potential hazards. In city driving, hazards might be more frequent but less severe, while highway driving can present less frequent but potentially more dangerous, less predictable situations.
The counterargument is that by maintaining a larger following distance, drivers can generally stay within the Snapshot’s braking parameters while still driving effectively. However, in real-world traffic, adhering strictly to this might occasionally lead to missed turns or other inconveniences to avoid triggering a hard brake. On the other hand, the program might subtly encourage more attentive driving habits and increased awareness of road conditions, as drivers become more mindful of their braking.
This leads to the question of how to “game” or strategically use the system to your advantage.
Strategies for Optimizing Your Snapshot Score: Playing the Game
Now that you understand what data Snapshot tracks and the challenges of avoiding penalties, you might be interested in how to maximize your discount. As the saying goes, “don’t hate the player, hate the game,” or in this case, play the game effectively.
Progressive’s discount calculation considers hard braking events, nighttime driving, and total miles driven. Of these, mileage is arguably the most controllable factor to influence your discount. The core metric seems to be the ratio of hard brakes to miles driven.
Therefore, you have two primary strategies: either modify your braking habits to minimize hard brakes, or increase your mileage to dilute the impact of unavoidable hard brakes.
The Double-Edged Sword: Snapshot Data in Claims and Liability
It’s crucial to understand that by participating in the Snapshot program, you’re also allowing Progressive to use the collected data in the event of an insurance claim. While this might not be a concern for most drivers, it’s worth considering that your driving data could potentially be used against you when determining fault or setting premiums. For example, if an accident occurs and Snapshot data shows you were speeding, it could negatively affect your claim outcome. Conversely, the data could also support your claim if it demonstrates you were driving safely.
The intention behind this policy likely aims to reduce fraudulent claims and fairly assign responsibility in accidents. However, if I were ever involved in an at-fault accident, my first instinct might be to discreetly remove the Snapshot device to avoid the other party becoming aware of its presence and potentially subpoenaing the data. The data, in this context, feels like it’s primarily for my insurance company’s use.
However, the data’s use isn’t always negative. In a notable case in Cleveland, Snapshot data was instrumental in proving a man’s innocence in a murder case, demonstrating the potential for this data to be beneficial in unexpected situations.
Snapshot as a Behavior Modification Tool: Reshaping Driving Habits
After six months of using Snapshot, I concluded that its most significant impact is in raising driver awareness. It encourages drivers to be more conscious of their vehicle dynamics, road conditions, and the importance of smooth, gradual deceleration. It took me about two months to consciously adjust my driving habits.
And it worked. After that initial period, I no longer consciously worried about triggering the Snapshot beep because my braking naturally became smoother and more anticipatory. While I might have occasionally accelerated quickly through a yellow light when safe, the general tendency to be more decisive and less hesitant in such situations diminished.
The device’s audible beep serves as a negative stimulus, immediately signaling a “penalty.” The potential insurance discount acts as a positive reinforcement. The system, in essence, is a form of Pavlovian conditioning, subtly shaping driving behavior through feedback.
Snapshot Savings: Did I Actually Get a Discount? (Spoiler: Not Really)
During my first month, Snapshot categorized me as a “terrible” driver. This is significant because Progressive uses the first 30 days as a probationary period to assess your driving and set your initial discount for the remaining five months.
My initial “discount”? A mere one percent, or $5.46. That was the calculated value of my privacy in the first month. After the full six-month period, my discount increased to 12 percent, around $96. However, closer inspection of my policy revealed a less straightforward picture.
Did I truly “save” $96? Examining my policy declarations pages revealed a more nuanced reality.
My insurance rates actually increased. It’s unclear if this increase was directly related to Snapshot data, but my base premiums rose while the Snapshot discount was applied. While insurance premiums can fluctuate due to various factors, the timing of this increase, coinciding with the Snapshot program, is concerning. One would expect premiums to decrease with vehicle depreciation, but Progressive’s actions suggested otherwise.
Original Premiums with Progressive ($741)
Six-month Renewal Premiums with Progressive ($836)
A side-by-side comparison shows an increase in the six-month renewal premium from $741 to $836, despite a Snapshot discount being applied.
As I discovered, Progressive increased my premiums by $95 – almost exactly offsetting the $96 Snapshot discount. While I received other discounts, the base policy premium increased. Effectively, my privacy cost me roughly one dollar for the six-month period, or about 16 cents per month.
In conclusion, with Snapshot, you might see a nominal discount on your insurance, but it could be negated by an increase in your base premium at renewal. It’s essential to carefully scrutinize your policy details to understand the true financial impact.
Progressive Snapshot Data: A Glimpse into Your Driving Habits
Progressive provides customers with reports on their Snapshot data through their website. This information isn’t part of their public marketing, so here’s a preview of what you can expect to see as a Snapshot participant.
Snapshot Program Discounts: (This section likely details the overall discount percentage earned.)
Weekly Trip Averages Report: This report compares your driving for the current week against your overall average performance. (Note: Data for my last seven days is unavailable since I completed the Snapshot program.)
A graph titled “Weekly Trip Averages Log” displays weekly driving performance compared to the overall average across various metrics.
Daily Trip Details Log (Final week of Snapshot): (This would show detailed data for each trip in the final week of the program.)
Daily Trip Details Log (First Week of Snapshot):
A “Daily Trip Details Log” shows driving data from the first week of using Progressive Snapshot, breaking down performance by individual days.
Trip Detail Report (Example: Driving from Tucson to Phoenix): (This would provide granular data for specific trips, like the example route mentioned.)
Key Insights from My Snapshot Data Analysis
Progressive’s reports are somewhat basic in explaining the data’s significance. It’s largely up to you and their underwriters to interpret the implications. So, I exported my data (a somewhat cumbersome process) and performed some analysis in Excel, looking at my six months of data from January to June.
Key Findings:
- Behavior Adaptation: It took approximately 70 days to noticeably improve my driving behavior in response to the Snapshot feedback.
- Mileage Offset: “Good” miles driven could compensate for hard braking events in the discount calculation.
- Commute Impact: Switching from city street commutes to highway driving significantly reduced hard brake occurrences.
- Discount Achieved: I ultimately earned an 11% discount at the end of the six-month term.
Hard Brakes (Aggregated):
A bar graph titled “Hard Brakes (Aggregated)” visually presents the total number of hard braking events recorded over the six-month Snapshot program period.
Mileage (Aggregated): (Graph showing total mileage driven over the six months)
Trips (Aggregated):
A bar graph titled “Total Trips (Aggregated)” displays the number of trips taken each month during the Snapshot program.
Hard Brake to Mileage Ratio: (Graph showing the ratio of hard brakes to miles driven over time)
February 4th Anomaly: The data spike on February 4th? That was me experimenting with burnouts and figuring out how to disable traction control on my 2014 Mustang. 😉 (Purely for research purposes, of course!)
Final Verdict: Progressive Snapshot – Helpful Tool or Privacy Concern?
It’s clear that the initial 30 days of using Snapshot can be challenging, at least it was for me. Knowing the precise impact of each hard brake event from the start would have helped me adapt even faster. Now, with this understanding, adapting to these driving monitoring devices becomes more manageable.
My primary lingering concern is the voluntary nature of these devices currently. Progressive and State Farm offer discounts as incentives for participation. However, the value of the collected driving data likely far exceeds the discounts offered. I anticipate a future where such monitoring becomes mandatory, with penalties for drivers who opt out.
For privacy advocates, this system raises valid concerns. Especially in light of NSA surveillance controversies, this technology adds another layer of potential tracking of citizens. With legal processes like subpoenas, insurance companies and data providers could be compelled to share vehicle location and driving data with law enforcement. Furthermore, local law enforcement agencies already utilize tools like Stingrays to monitor cellular traffic without explicit consent. (Remember, the Snapshot device includes a cellular modem and SIM card for device identification. Review the patent for details!)
Overall, the Progressive Snapshot program achieved its stated goal: it made me a more conscious and safer driver. While I have reservations about certain aspects, especially concerning privacy and the actual financial benefits, the program is still relatively new, and likely evolving.
In the future, I’d like to see Progressive provide more insightful comparisons, perhaps benchmarking driving performance against other drivers in the same state or with similar vehicles, similar to how Nest provides energy consumption comparisons. This type of data utilization could further encourage positive driving behavior. Transparency regarding the specific data collected, retained, and discarded would also be appreciated, even if presented in technical detail.
If you are a driver who typically drives cautiously, avoids aggressive maneuvers, and primarily drives in favorable conditions, Snapshot might be beneficial for you. Otherwise, the tempting discount might not be worth the trade-off in privacy and potential premium adjustments.
UPDATE (2018): For a more current perspective, read my recent thoughts on Progressive Snapshot, a follow-up to this initial review.
Photo credit: robertnelson
