Can Your Insurer Deny Overhead and Profit in Virginia?

Overhead and profit on a restoration estimate is the charge for general contractor coordination: sequencing separate trades, holding the schedule together and standing behind the finished result. It is not a markup applied to every task on the page. No Virginia statute, regulation or reported appellate decision we can locate decides whether a carrier must pay it, so an overhead and profit insurance claim argument turns on the loss settlement wording in the policy and on the facts of the loss.

On an estimate written in the industry's standard software, the line sits near the bottom of the summary page as two figures, general overhead and profit, shortened by restorers to O&P. Both are calculated against the job total rather than any single line item, which is why the number looks large on its own. Because the line prices coordination, the honest question is whether coordination was actually required, which is a factual question about your building rather than a legal question about your policy.

One note before the detail. Restoration Doctor is a restoration contractor. This post explains what the published rules say and what to ask for in writing. It is not legal or insurance advice, and nothing here describes what your own policy covers.

Three separate charges get confused with one another on a water loss, and the confusion is where most short payments start: general contractor overhead and profit; job-related overhead, meaning project-specific supervision and site costs; and sales tax. Striking one of them because of an objection to another produces a payment that does not reconcile to any document in the file.

The coordination line is also not a second charge for the work itself. If a reviewer removes coordination and leaves the other lines intact, the estimate still prices the physical work. What it stops pricing is the management of it.

Restoration Doctor does not add overhead and profit to the emergency service call line. That is a statement about how we write our own paperwork, not a claim about what any carrier owes anyone. We print it here because a post arguing that coordination is real work ought to say where we think it stops.

None that we can find, and that is the most useful sentence on this page. We searched CourtListener's published-opinion collection for every Supreme Court of Virginia and Court of Appeals of Virginia decision containing the phrase “overhead and profit.” The Supreme Court search returned seven results and the Court of Appeals search returned two. Every one of them is a construction or government-contract dispute. Not one is a first-party case, meaning a claim a policyholder makes on their own policy.

The case names are worth printing, because a negative finding is only as good as the method behind it. The first seven are Supreme Court results, the last two Court of Appeals results.

Two things that search does not prove, stated plainly. It covers published opinions inside CourtListener's collection, not unpublished circuit court rulings, and it is not a subscription-database sweep. And an absence of decisions is not a holding in either direction: it means no Virginia court has answered the question, so nobody can honestly tell you that Virginia law requires the payment, or permits the refusal.

The search does not come up empty because the collection is thin. The same corpus returns more than eight hundred Supreme Court of Virginia opinions containing the phrase “insurance policy.” This particular question simply has not been decided.

Virginia's rules govern the explanation rather than the coverage. 14VAC5-400-70 provides that “Any denial of a claim shall be given to a claimant in writing and the claim file of the insurer shall contain a copy of the denial.”

Read the trigger as carefully as the duty. The rule speaks to a denial of a claim. Whether a carrier that pays an invoice and removes one line from it has denied a claim within the meaning of the rule is not a question the rule answers, and we located no Virginia decision that answers it either. Ask for the written explanation on that footing rather than as a settled right.

The same section adds that an insurer “shall provide a reasonable written explanation of the basis for any claim denial.”

The next sentence is the one that gets misquoted, so read it closely. The written explanation “shall provide a specific reference to a policy provision, condition, or exclusion, if any.” Those last two words carry weight. Where the decision rests on policy language, the explanation has to point at that language. Where it does not, the rule requires nothing more specific than a reasonable written explanation.

Two further subsections of the same rule matter when coverage itself is not in dispute.

14VAC5-400-90 adds a standard for the carrier's own estimate: “the estimate shall be an amount for which the damage may reasonably be expected to be satisfactorily repaired.”

That rule continues: “The insurer shall give a copy of the estimate to the claimant.” Where the carrier prepared a repair estimate, the rule says you get a copy.

14VAC5-400-30 requires that “Detailed documentation shall be maintained for each claim file in order to permit reconstruction of the insurer's activities relating to each claim.”

There is an enforcement route, and it is narrower than it first looks. Va. Code § 38.2-510 lists the conduct that counts as an unfair claim settlement practice. Three items on that list bear on a struck coordination line.

Now the limits, which no honest page should leave out. The statute's own preamble reaches conduct performed “with such frequency as to indicate a general business practice,” so one decision on one file is usually not a violation of it.

Subsection B adds that “No violation of this section shall of itself be deemed to create any cause of action in favor of any person other than the Commission.”

The same subsection then preserves “the right of any person to seek redress at law or equity for any conduct for which action may be brought.”

The regulation is drawn a little differently. 14VAC5-400-25 makes it a violation if any person “Willfully violates any provision of this chapter” or commits a violation “with such frequency as to indicate a general business practice.” A willful single violation is reachable there. Either way the enforcer is the Bureau of Insurance, not the policyholder.

So the practical value of these rules is not a lawsuit. It is leverage of a duller kind: a written basis, a copy of the carrier's own estimate, a claim file that has to be reconstructable, and a regulator who accepts complaints. That is a real set of tools, and it is a different thing from a right to be paid.

With no Virginia authority, the reasoning has to be borrowed. The two decisions below are from the Superior Court of Pennsylvania, which makes them persuasive writing rather than binding law in Virginia. Both are also repair-loss holdback cases: each one concerns a carrier withholding a flat percentage from an advance payment on a repair loss. Neither involves an emergency water mitigation invoice.

Gilderman v. State Farm Insurance, 649 A.2d 941 (Pa. Super. Ct. 1994), framed the issue as whether an insurer paying repair cost less depreciation in advance “may automatically withhold both depreciation and a flat twenty percent representing contractor overhead and profit from its advance payment.”

The court concluded “that it may not.” Its holding was that “repair or replacement costs include any cost that an insured is reasonably likely to incur in repairing or replacing a covered loss.”

Read whole, Gilderman sets out a reasonableness test rather than an entitlement, and the same opinion refuses the opposite overreach. It states that “there clearly are certain types of property damage claims which will not require the services of a general contractor,” and offers the example of a loss involving “only a damaged pipe, and a plumber alone.”

Mee v. Safeco Insurance Co. of America, 908 A.2d 344 (Pa. Super. Ct. 2006), tightened it. The court held that “The answer to that question depends on whether use of a general contractor was reasonably likely,” and that “Whether use of a general contractor was reasonably likely is a question of fact for the jury.”

The three-trade rule is the phrase most property owners hear, usually secondhand: the idea that three or more trades automatically earns a coordination charge and that fewer than three never does. We could not locate a source for it in any Virginia statute, regulation, bureau bulletin or reported decision. It is industry shorthand rather than authority, and calling it either a legal right or a legal prohibition would be wrong.

Mee is often cited as though it settled trade counting. Read carefully, it rejects counting in both directions. The trial court there had held that no general contractor was hired, so coordination was never reasonably likely. The policyholder argued the reverse from custom and usage: that “whenever more than one trade is reasonably required to make repairs, a general contractor's services (with the contractor's overhead and profit) are reasonably required.”

The court's answer to both was that “Both these interpretations miss the mark.” No court we can find has examined a three-trade rule at all. What a Pennsylvania appellate court rejected, in the one decision on trade counting we could locate, was a more-than-one-trade trigger on one side and a no-contractor-hired bar on the other, in favor of a question of fact.

The practical consequence is unglamorous. Neither a property owner nor a reviewer wins this by counting to three. What moves a reasonably-likely question is a record: which trades the scope calls for, in what order they run, who was responsible for sequencing them, and what that sequencing involved.

Every case above is about a rebuild. Mitigation is the emergency phase: stopping the spread, extracting water, removing unsalvageable material and drying the structure. It often runs before anyone has written a repair estimate, sometimes before an adjuster has seen the building. Borrowing a rebuild holdback case to argue a mitigation line is an analogy, and should be labeled as one.

Said against our own interest: an extraction-only job is the weakest place to argue coordination. One crew, one trade, a few days of equipment and no sequencing of separate specialties is close to the fact pattern Gilderman described as not requiring a general contractor. A carrier reviewing that invoice has the stronger argument, and a contractor who claims otherwise is not helping the property owner.

Larger mitigation projects look different. A loss that needs hazardous-material testing before demolition, a licensed plumber for the source, an electrician to isolate circuits and a drying plan re-sequenced around each of them is a coordination problem whether or not anyone calls it a rebuild. The record either shows that or it does not.

This is also why the invoice itself matters more than any citation. Our guide on how to read a water mitigation invoice walks the anatomy, including how equipment is counted in unit-days, meaning one machine for one day. For the clocks a Virginia carrier works to, see insurance claim response deadlines; no day counts are printed here.

Put every request in writing and keep the replies. That habit is worth more than any clever phrasing, because it turns a phone conversation into a document that survives a file being reassigned. There is no template on this page, and there should not be. A fill-in paragraph you send your carrier starts to look like preparing a claim, which a restoration contractor in Virginia is not licensed to do.

What follows is a list of documents and questions rather than a script. Put the claim number on every message and give the carrier a reasonable window to answer before escalating.

Then the escalation ladder, roughly in order of how disruptive each step is. Ask for a re-inspection. Submit documentation that speaks directly to the stated basis for the reduction. If the disagreement is about amount rather than coverage, ask whether your policy contains an appraisal provision, a process for settling a disagreement over amount, and what it requires. If it is about coverage, that is a question for a licensed public adjuster or an attorney.

A complaint to the Virginia State Corporation Commission's Bureau of Insurance is available at any point. It is regulatory rather than a collection mechanism: the Bureau reviews claim handling, and no complaint obliges a carrier to pay a particular line. The Commission's file a complaint page explains what it needs.

The boundary is statutory. Virginia licenses public adjusting, and Va. Code § 38.2-1845.3 lists who is exempt from that requirement. The exemption covers “a person employed only for the purpose of obtaining facts surrounding a loss or furnishing technical assistance to a licensed public adjuster, including photographers, estimators, private investigators, engineers, and handwriting experts.” Restoration contractors are not on the list.

What a restoration contractor can properly do is document and price its own work, then explain the documents it wrote. Restoration Doctor writes the scope, records the moisture and equipment data behind it, and hands you a file you can give your carrier. We invoice the property owner rather than the carrier, so a struck coordination line does not change what the contract says is owed, and seeking reimbursement for it is between you and your insurer. We do not negotiate or settle your claim, and we do not tell you what your policy covers, because that answer belongs to your carrier, and after that to a licensed public adjuster or an attorney.

For the same reason this post stops at what the published rules say. It does not tell you whether your carrier owes the coordination line on your loss. What it can tell you is that nobody in Virginia can point to a statute or a decision that settles the question, and that the written explanation Virginia's rules require of the insurer is where the argument actually starts. Our note on what a carrier-ready drying file contains lists what belongs in the record before anyone argues about a line.