The short answer
A deductible attaches to an occurrence, not to a repair order. Two impacts a week apart are almost always two occurrences and two deductibles, even if one shop fixes both at once. The money you save by timing them together comes from shared setup, shared refinish work and a single stretch of downtime, not from the deductible column. Decide the sequence with that distinction in front of you.
One loss or two? The question that sets the count
Owners often assume that because both dents get fixed in the same bay during the same two weeks, the carrier will treat the work as one job. The carrier is not looking at the bay. It is looking at the loss notice.
Each first notice of loss creates a claim file with its own date, its own cause of loss code and its own reserve. A deductible is applied per file. So the question that determines whether you write one check or two is not "can these be repaired together" but "did these arise from one occurrence".
That question has a real answer, and it is usually obvious. A hail event that damages the roof and then a branch that falls from the same storm onto the same unit an hour later is one occurrence. Backing into a bollard in a Hamner Avenue lot on Tuesday and getting sideswiped on SR-91 on Friday is two. The gray zone is narrow, and it lives in continuous events: a single trip where the same object contacts the unit twice, or a chain reaction collision. Our page on how a claim moves from notice to payment walks through the file structure that makes this concrete.
How carriers separate incidents in practice
Adjusters use a small set of factors, and they use them consistently across the carriers we handle claims for, including Progressive, GEICO, State Farm, AAA SoCal, Mercury, Allstate, Wawanesa, Liberty Mutual and Foremost. Naming those carriers describes claim handling experience, not any affiliation.
The factors:
- Date and time. Different calendar days is the strongest single signal for separation.
- Cause of loss. Collision, comprehensive and falling object are separate codes. Two different codes almost never merge.
- Location. Same parking structure on the same afternoon reads differently than two cities on two days.
- Continuity of the proximate cause. One unbroken chain of events, one occurrence. A break in the chain, two.
- What you reported. If you described them as two events on the phone, the file reflects two events.
There is one further factor that shows up on comprehensive files: whether the same peril caused both. Two separate incidents of vandalism in the same week at the same location will sometimes be treated as one occurrence and sometimes as two, and the deciding detail is usually whether the second was discovered before or after the first was reported.
That last one matters more than people expect. The narrative captured at first notice tends to stick. If two impacts genuinely came from one continuous event, say so plainly at the outset rather than trying to consolidate the files later.
Sequencing two repairs through one shop visit
Once you know the deductible count, the sequencing decision becomes purely operational. Running both repairs in one visit is usually correct, and here is why.
A collision repair carries fixed overhead that does not double when the damage doubles. Setup and measure happens once. The unit gets masked once. The booth cycle covers all panels going in at the same time. Blend into adjacent panels overlaps if the two damage areas are on the same side. Reassembly labor consolidates. On a unit where both losses touch the same quarter or the same side, the combined estimate can land meaningfully below the sum of two standalone estimates.
The other half is downtime. Two separate visits means two intake cycles, two teardowns, two approval waits and two release inspections. For an Eastvale owner making the drive to Yorba Linda, roughly twenty miles via SR-71 to SR-91, that is two round trips instead of one. For a working unit, it is two outages instead of one.
What combining work does and does not save
Be precise about this with your adjusters, because vague claims of savings invite pushback.
Combining does save:
- One setup and measure operation instead of two
- One cover and mask operation
- Shared booth and cure time where panels are refinished together
- Overlapping blend where the damage areas are adjacent
- A single teardown on shared assemblies
- One period of loss of use rather than two
Combining does not save:
- The deductible on either file
- The parts cost on either file
- Supplement time, which still gets written per file
- Any operation unique to one damage area
The practical consequence is that the shop must write the estimate so the overlap is visible and attributed. If a blend operation serves both losses, it belongs on one file with a note, not billed twice. Estimators who understand this write cleaner files and get faster approvals. Our labor rate structure is published so you can check how the hours on each file were priced.
The policy period wrinkle nobody reads
Two events that straddle a renewal date sit in two policy periods. That has consequences beyond the deductible.
If your deductible changed at renewal, each loss carries the deductible in force on its own date of loss, not the one currently on the declarations page. If a coverage was added or dropped at renewal, the same logic applies. And if your policy carries an aggregate limit on any coverage, the two losses draw from different aggregates.
There is a second wrinkle on specialty units: some policies apply a percentage deductible to certain causes of loss rather than a flat dollar figure. Two losses under a percentage deductible can produce two very different numbers even when the repair costs are similar. Read the declarations page for the period each loss fell in, not the current one. The background on how deductibles and depreciation interact is worth reviewing before you make the call.
Documenting each incident so the file stays clean
The single most useful thing you can do is keep the two events physically separate in your records from the first day.
Shoot a separate photo set for each incident, on the day it happened, and do not mix them into one folder. Write a short dated note for each: what happened, where, direction of travel, weather, other parties. Keep any police exchange, dashcam clip or witness contact attached to the correct event.
Then ask the shop to segregate operations by incident on the estimate. A line item that says "repair left quarter" is ambiguous when two losses touched the left side. A line that says "repair left quarter, lower crease, loss of the fourteenth" is not. Segregation protects you if one file gets scrutinized and the other does not, and it prevents an adjuster from arguing that damage from the second event was already paid on the first.
If either estimate is likely to grow after teardown, flag that at intake on both files rather than one. And if you want a sense of the range before either conversation starts, the repair range estimator gives you a bracket to plan around.