Been placing this coverage since 2006. Most requests feel familiar now. But a contract that feels ordinary on my desk can be someone's first overseas deployment. I keep wondering whether all those years help me hear what they're actually worried about, or just the question I've answered before. I might have had it backwards. Still thinking.

The part of a DBA placement I care about most is quiet. It happens before any underwriter hears your name, while I'm reading how your operation actually works. I call it Risk Reconnaissance. Look first. Then recommend.

A grievance today can be a claim tomorrow. Attorneys who report early position themselves for defense-cost coverage, stay compliant with policy terms, gain expert guidance, and protect themselves if things escalate. Waiting rarely helps. Reporting does. bit.ly/4ieUGGk

Commercial property premiums fell 6.3% in Q2, the steepest quarterly drop since 2010. Every account size posted a decrease this time. Capacity is abundant. Buyers have leverage right now, especially on larger accounts. bit.ly/3TVFjdM

Two companies deploy the same AI tools. One ends up with a coverage gap. One doesn't. The technology isn't the variable. Whether someone asked the right question at renewal is.

When a contractor tells me they're taking work into a new country, my first question is about their company, not the country. Here it is: who owns risk in your company? I've been placing Defense Base Act insurance since 2006, for contractors working everywhere from Afghanistan to Zimbabwe. And this question comes up every time someone expands into unfamiliar territory. The honest answer is all three. The CFO, the contracts team, and operations. Each one sees risk through a different lens. Finance watches cash flow, profitability, and financial stability. Contracts watches compliance, proposal strategy, and contract requirements. Operations watches staffing, performance, and getting the work done. Here's where it breaks down. These groups often work independently. So each one assumes someone else has the rest of the picture. A new territory is where that assumption gets tested first. Risk mitigation starts before the bid, when those three lenses are in the same conversation. Deployment is too late to find the gap. So before your next bid in a new location, use this line: "Before we commit, can finance, contracts and ops walk through the risk on this one together?" Ask it early. It surfaces the gaps while you can still do something about them. #DefenseBaseAct #GovCon #RiskManagement #OCONUS

Your commercial insurance broker doesn't speak government contractor. That gap costs time, money, and resources. Most commercial brokers work with commercial businesses all day. Those clients do not face the same hurdles or the same varied operations as a GovCon company. So the questions never get asked. Where It Shows Up • A contract award deadline arrives, and the broker is still learning what the Defense Base Act requires. • FAR 52.228-3 or FAR 52.228-4 sits in the contract, and nobody on the insurance side reads it. • Contract flow-downs to subcontractors get missed, so the prime carries exposure it never planned for. • An employee deploys OCONUS, and everyone assumes the domestic workers comp policy follows. It does not. DBA is federally required statutory workers comp for U.S. government contractors and subcontractors working outside the United States. A general commercial program does not satisfy that requirement. Questions Worth Asking Your Broker "Which of our contracts include FAR 52.228-3 or FAR 52.228-4?" "How are our DBA requirements flowing down to our subcontractors?" "If an employee is injured overseas tomorrow, which policy responds, and how is the claim reported to the Department of Labor?" "What changes in our program before our next pre-deployment?" If the answers come slowly, that tells you something. We work on Defense Base Act and government contractor insurance. Our team is small, and the focus is narrow by design. That focus is how we catch the clause, the flow-down, and the gap before a claim finds them. Happy to compare notes on your current program.

Business interruption adds 650% to the cost of a cyber claim, per NetDiligence. Most SMEs set their cyber limits before they ever run that math. Worth a second look at your coverage gaps in our 2026 midyear outlook. bit.ly/4i2IdFu

Commercial property premiums fell 6.3% in Q2, the steepest quarterly drop since 2010. Every account size posted a decrease this time. Capacity is abundant. Buyers have leverage right now, especially on larger accounts. bit.ly/4z4Pwny

Every contractor has met this figure. He reads the quote you forwarded, skips the number at the bottom, and asks who is actually going where. Accessories include a subcontractor roster with one certificate still missing, a map pinned from Afghanistan to Zimbabwe, and an Army canteen cup that outlasted three offices. Calculator included, pressed only after he knows who is deploying. The cheapest quote is rarely the cheapest contract.

Commercial property premiums fell 6.3% in Q2, the steepest quarterly drop since 2010. Every account size posted a decrease this time. Capacity is abundant. Buyers have leverage right now, especially on larger accounts. bit.ly/4yqnxNF

There is no dramatic origin story here. When a contractor asks us for a Defense Base Act quote, it lands with people who have been doing exactly this since 2006. Behind our quote and enrollment process is Brian Smith, our founder. He has been placing DBA insurance since 2006 for government and defense contractors across the United States and around the world, from Afghanistan to Zimbabwe. So a new country on a quote request does not read to us as a guess. It reads as a familiar set of questions. A simple quote process usually comes from repetition, not reinvention. The same careful questions about who is going, where, and under which contract, asked the same way every time. Brian is a U.S. Army veteran, and that habit of discipline tends to show up in unglamorous places. Reading a solicitation fully before a quote goes out, for one. The useful thing to know before you request a quote is not how big a team is. It is how long the people reading it have been doing this one thing.

The news from the region your contract points to just got worse. Two sensible contractors can make opposite calls on their coverage right now, and both can be right. The real question is when, not just what. Revisit everything now, or keep what you have and change only what the contract changes. Here is what each path buys and what it costs. Path A: Review now. Buys you time and fewer surprises later. Costs you attention in an already busy moment, and some of the changes you make may turn out to be unnecessary. Best for: teams with people in or near the affected area, or deployments that have not started yet. Path B: Hold steady. Buys you stability and a clean, consistent paper trail. Costs you reaction time if events move faster than the contract does. Best for: contractors whose location, headcount and scope are genuinely not changing. The question that settles the fork is narrow. Has anything about who is going, where they are going, or for how long actually changed? If the answer is yes, the hold steady case weakens quickly. Brian Smith has been placing Defense Base Act coverage since 2006, for contractors working everywhere from Afghanistan to Zimbabwe. From that seat, either path can be the careful one. The careless choice is not deciding at all.

A government contract can look profitable on paper and disappear the moment insurance is left out of the bid. The work has not even started. The loss already has. Factoring the cost of insurance into your government contracting bid is one of the most important parts of contract profitability. Without adequate rates, and without the cost of insurance considered, a contract can become a loss before anyone deploys. Where the gap shows up If the work is OCONUS, expect FAR 52.228-3, Workers' Compensation Insurance (Defense Base Act), in the contract. That makes DBA a requirement. It is statutory workers' comp for your people overseas. Coverage must be active before deployment. Your domestic workers' comp does not replace it. DBA premium is typically calculated against payroll. The cost moves with headcount, wages, and location. The insurance costs that get left out of bids: • DBA premium tied to OCONUS payroll • Subcontractor coverage required through contract flow-downs • Other insurance the contract language calls for • Coverage that has to be bound before the first person travels Each one is a real cost. Each one comes out of your margin if it is not in your rates. Price it right from the start Get the insurance number before you submit. Here is what to ask your broker: "We are bidding on an OCONUS contract with FAR 52.228-3. Here is our estimated payroll by country. What will DBA cost for the full period of performance?" "Our subs will deploy too. How do we confirm their DBA is in place before they go?" "What else in this contract language needs to be priced before we submit?" Then build that number into your rates. A cost you find after award is a cost you absorb. This is a conversation worth having before the proposal goes out.

Enlisted soldier. ROTC. Commissioned officer. Three stages in one Army career gave our founder, Brian Smith, two views of the same mission: the person doing the work, and the person planning it. That matters more than it sounds, because a contractor's workforce plan exists twice. Once on paper. Once as the actual people who deploy. Coverage has to fit the second version, because that is where a claim happens. An injury overseas does not read the org chart. It happens to a specific person doing a specific job in a specific place. So we read a roster from the ground up. Brian's method is risk reconnaissance. Look first. Gather intelligence. Identify what might create a problem. Then recommend action. Applied to staffing, that means we learn who is going and what they will be doing before we approach an underwriter. Not the title on the plan. The work in the field. Brian has been placing Defense Base Act insurance since 2006, for government and defense contractors in the United States and around the world. Here is the part that shapes how we look at a roster. Brian instinctively roots for the person who may not have the advantage. On most staffing plans, that is the person with the least say in how the plan was built and the most exposure once they land. So we start there. The plan tells you what the contract needs. The roster tells you who carries the risk.

Every contractor who has worked with Brian knows the accessories come standard. Binoculars for looking first. A phrasebook for translating your operations into something a carrier can underwrite. A Retroactive Date stamp, because switching claims made coverage without a plan is where risk hides. A field notebook from his Army years. And the gap list, found before it became a claim. Underwriter sold separately.

Sure, a checklist is great for contract analysis, but with today's tools and AI, there are a lot of better, more efficient ways of ensuring the contract reads correctly. You just have to use them

The best claims work we do happens long before an incident. Nobody sees it, and that is the point. When a claim goes smoothly, people credit the adjuster or the paperwork. We credit the quiet work Brian Smith, our founder, does months earlier. He calls it Risk Reconnaissance. Look first. Gather intelligence. Identify what might create a problem. Decide what matters. Then recommend action. Before he ever approaches an underwriter, he researches how the contractor actually operates. So the policy gets built on the real work and not a guess. Part of that is translation. Turning complex contractor activities into language a carrier can underwrite. That is where a lot of coverage mismatches quietly start, or quietly stop. Here is the line that matters. A compliance gap found before deployment is a conversation. A gap found after an incident is a claim problem. The habit has roots. An Army path from enlisted soldier to commissioned officer. A Detroit public school upbringing. An instinct for rooting for the person who may not have the advantage. We have been placing Defense Base Act insurance since 2006, for contractors working everywhere from Afghanistan to Zimbabwe. The smoothest claims are usually the ones somebody saw coming.

Underwriters will guess what you do if you don't tell them. Their guesses cost you. Your contract includes FAR 52.228-3. The underwriter sees that clause and knows Defense Base Act coverage applies. The clause says nothing about what your people actually do OCONUS. So the underwriter starts filling gaps. If the application says "logistics support" in a high-risk country, what does that mean? Warehouse inventory on a secured base? Driving supply routes? Security escort? Without an answer, they assume the higher hazard. That is their job. They have to price a risk they cannot see, and they have to defend that price to their own management. Give them the facts. Tell them what you do. Then tell them what you don't do. That second part is equally important. It is also the part most applications leave out. What that sounds like "Our employees provide IT help desk and network administration from an office inside a U.S. installation." "Our employees do not carry weapons. They do not travel outside the installation. They do not perform security or convoy work." "All in-country driving is handled by a subcontractor that carries its own DBA policy." Three sentences. Now the underwriter has something to document. Why the "don't" matters An exclusion statement tells the underwriter where the exposure stops. It narrows the questions. It shortens the back-and-forth. It gives them a written basis to quote your actual operation. Vague applications create friction for everyone. More follow-up emails. Slower quotes. Pricing built on assumptions. We spend a large share of our time on this step before a submission ever reaches a carrier. Write your scope down before the underwriter has to write it for you.

Chewed on this one all week. When a contract flows down two or three layers, I can usually tell you who signed what. Finance, contracts, operations, each sees its own piece. The worker hired by a sub of a sub can sit outside all three. I keep wondering whether all those pieces add up to anyone holding the whole. Not sure yet.