You already run one business, and you've spotted a second opportunity next to it. Same trucks, same crew, maybe the same customers, so you file a DBA, print new business cards, and start booking jobs under the new name. It feels like a branding decision. For your insurance, it's a much bigger one.
A DBA is a name, not a new company
DBA stands for "doing business as." Depending on your state it's called an assumed name, fictitious name, or trade name, and it may be filed with the state, the county, or the city. What it is not, anywhere, is a separate legal entity. The SBA notes that registering a DBA "doesn't provide legal protection by itself."
That means the new operation is your existing company wearing a different sign:
- Same legal entity. Contracts signed under the DBA bind the business that registered it.
- Same assets. A lawsuit over the new operation reaches everything the existing business owns.
- Same tax identity. The IRS generally doesn't require a new EIN just because a business operates under a different name.
So the claim from the new operation lands on the balance sheet you've spent years building. The only question is whether your policies are set up to answer it.
Your policies cover what you told them about
Commercial policies are written around the operations you disclosed on the application and the classifications the insurer assigned. Add a different kind of work without telling anyone and one of three things tends to happen: the work is covered but priced wrong, the difference shows up as a charge at audit, or the work isn't covered at all. Which one depends on the line of coverage.
- General liability. Your GL is rated by classification. On many standard forms that's mainly a pricing issue settled at audit. But plenty of policies carry a classification limitation or designated-operations endorsement that limits coverage to the operations listed. On those, an unlisted operation can simply be outside the policy.
- Workers' comp. The standard policy says that if your actual exposures aren't properly described by the classifications on it, the insurer will assign the proper classifications and rates, and the final premium is figured after the policy ends using actual payroll and the classes that apply. Your crew is usually still covered as your employees, but the new work gets charged at its own class at audit, often at a higher rate than you budgeted. And remember GL excludes injuries to your own employees, so comp is the policy that answers when your crew gets hurt.
- Commercial auto. Auto is rated on the vehicles you've listed, how they're used, and how far they travel. A truck bought for the new operation may need to be added before it's covered, and a shift to hauling, towing, or carrying equipment the policy wasn't rated for is exactly the undisclosed business use that causes disputes.
- Professional liability. If the new operation gives advice, designs, or manages something for others, your existing E&O may not reach it. Most professional policies cover only the professional services they describe.
- Property. Property coverage is tied to the premises described in your declarations. A new shop, kitchen, or storage unit for the DBA usually gets only a limited, temporary extension, if any, until it's added.
Three ways the gap shows up at claim time
The landscaper who starts a tree-removal DBA. A landscaping company starts taking removals under a new name. Many landscaping policies limit or exclude tree work, especially above a certain height. A limb comes down on a client's garage. The claim is against the landscaping company, because the DBA is the landscaping company, and the policy was never written for tree service work.
The restaurant that starts a catering DBA. A restaurant launches an off-site catering brand. Now there's cooking at venues the policy never contemplated, a van driven to events, and possibly alcohol served away from the restaurant. A guest gets food poisoning at a wedding. Whether the off-premises work, the van, and the liquor exposure are covered depends entirely on whether anyone told the insurer.
The property manager who starts a handyman DBA. A property management firm starts doing repairs for its owners under a handyman name. Its professional liability covers managing property, not swinging hammers, and its GL was rated as an office. A water line the handyman crew installed fails and floods two units. The firm is sued as the contractor it never told its insurers it had become.
The gotcha: the name on the certificate isn't the coverage
Here's the trap most owners miss. They ask their agent to "add the DBA" so the new name shows up on certificates, and they assume that settles it. It doesn't.
Adding the DBA to the named insured fixes the *name*: it ties the trade name to your legal entity on the declarations (usually written as "Your Company LLC dba New Name"), so certificates and contracts in that name match the policy. Our guide to what a named insured is walks through why that matters. But a matching name says nothing about whether the *operation* behind it is disclosed, classified, and covered. You need both: the DBA on the dec page, and the new work on the application.
When a separate LLC may make more sense
If the new operation is riskier than your core business, or you want a lawsuit there kept away from the assets of the first business, a DBA may be the wrong tool. A separate LLC can do that, but only if it's properly insured and actually run as a separate business. It also isn't covered by your existing policies automatically. We compare the two in DBA vs. LLC: what changes for your insurance. The legal and tax side is a conversation to have with your attorney and CPA.
Before the first job under the new name
- Call your agent before you book work, not at renewal. Describe the new operation plainly: what you'll do, who does it, what equipment and vehicles it uses, and roughly what it will bring in.
- Get the DBA added as a named insured on every policy: GL, workers' comp, auto, umbrella, property.
- Confirm the classification on GL and comp, and ask directly whether any endorsement limits coverage to listed operations.
- Add vehicles, locations, and equipment the new operation uses.
- Check professional liability if the new work involves advice, design, or management for others.
- Only then request certificates in the DBA name, so the paper matches real coverage.
Our approach
At Cory Washington & Co., we treat a new DBA as a new operation, not a name change. We review what the new work actually involves, add the DBA to the named insured on each policy, confirm the general liability and workers' comp classifications match what your crews will do, and flag any endorsement that would leave the new operation outside the policy. If the exposure is different enough that it belongs on its own policy or its own entity, we tell you that too.
Starting something new under a second name? Request a quote or a policy review and we'll line up your coverage before the first job.
Frequently Asked
Does my business insurance cover a new DBA automatically?
Not reliably. A DBA is the same legal company as your existing business, so the claims belong to you, but your policies were written and classified around the operations you disclosed. If the new work is a different kind of operation, it may be rated wrong, picked up as a charge at audit, or excluded outright, depending on the policy. Tell your agent before the first job so the DBA name and the new operation are both on the policies.
Is a DBA a separate legal entity?
No. A DBA (doing business as, also called an assumed, fictitious, or trade name) is just a name your existing business operates under. It does not create a new company, a new liability shield, or by itself a new tax identity, so the DBA's contracts, debts, and lawsuits belong to the business that registered it. Registration rules vary by state and sometimes by county or city.
How do I get my DBA name on my certificate of insurance?
Ask your agent to add the DBA to the named insured on each policy, usually written as your legal name followed by "dba" and the trade name. Once it's on the declarations, certificates can show it. A certificate is only a summary of the policies, so the name has to be on the policy first, and the new operation has to be disclosed and classified too.
Should I form an LLC instead of using a DBA for a second business?
It depends on how different and how risky the new operation is, and that's a question for your attorney and CPA as much as your agent. From the insurance side, a new LLC is a separate legal person that isn't automatically covered by your existing policies; it has to be added as a named insured or carry its own coverage. A DBA keeps one set of policies but puts everything on one balance sheet.
This article is general information for business owners, not insurance or legal advice, and does not bind or alter coverage. Policy terms, eligibility, and pricing vary by carrier and state — confirm specifics with our licensed team before making decisions.