Starting a Subcontractor Discovery Conversation

A general contractor telling you a new subcontractor handles their own insurance sounds like a settled matter. It is not. Your job as the commercial producer is to find out what work the crew will actually perform, who has access to the site, what the prime contract says about coverage, and who on the contractor's side reviews documents before anyone sets foot on the job. Skip that discovery and you are building the file on a hallway assurance instead of a real record that your service team can act on.

Why This Conversation Goes Wrong

Project managers move fast and answer in shorthand. "They handle their own insurance" or "our super checks that" sounds complete, but it tells you nothing about the actual risk. A glass installer working from a lift creates a different exposure than a subcontractor pulling wire inside a finished space, and "handles their own insurance" covers both answers equally badly.

The conversation goes wrong when you accept the shorthand as fact instead of treating it as a starting point. You ask one question, get a vague answer, and move on because the client sounds confident. Confidence is not documentation. If nobody names the actual scope of work, the certificate holder, the contract clause, and the person who signs off before site access, you end up with a verbal impression, not a record your service team can review. When a claim comes in months later, that gap is exactly where coverage disputes start.

How to Prepare Before You Ask

Before you call the project manager, pull the prime contract and read the subcontractor insurance clause yourself. Do not assume it matches what you handled on the last job for this client. Contract language changes between projects, and a clause that required additional insured status on one job might require primary and noncontributory language on the next.

Check the file for the last time this client added a subcontractor. If there was a delay or a coverage gap before, that history tells you where to press harder this time. Note the site schedule too. If the crew starts work in five days, your certificate request has a real deadline attached to it, not an open ended one.

Know your own agency's review path before you ask anyone else a question. If you cannot tell the project manager exactly where the certificate goes and who reviews it, you cannot run this conversation with any authority. Producers who work several accounts in the same trade build a mental map of these patterns after a few reviews, similar to the discipline described in Finding Supplier Concentration Before a Commercial Renewalwhere a handful of specific questions reveal a concentration risk that a general answer would have hidden.

What to Say When You Start the Conversation

Open with two questions, not one. You want the scope of work and the name of the person who reviews documents before site entry. Do not let the project manager answer with just a company name.

You ask, "What exact work will this crew perform, and who on your side reviews insurance documents before they get site access?" The project manager answers, "They're doing electrical work on the second floor, and our field superintendent collects a certificate before he lets anyone badge in." That answer is better, but it still leaves out the contract requirement and the actual deadline.

You follow with, "Can you send me the contract clause that covers subcontractor insurance and the certificate instructions your superintendent uses? I will route that through our review process and confirm what is needed before your start date." The project manager, wanting a fast answer, pushes back. "Can you just tell me if they're covered so I can tell my super to let them in?" This is where you hold the line. You answer, "I cannot confirm coverage from a phone call. Once I have the contract language and the certificate, our reviewer will tell us exactly what is missing, if anything, and I will get back to you before the crew shows up."

Notice what that last line does. It gives the project manager a real next step and a real timeline. It does not promise an outcome you cannot verify.

Mistakes That Undermine the Review

The biggest mistake is telling the client a subcontractor "meets requirements" before a reviewer has actually looked at the certificate. That sentence feels helpful in the moment and creates a real problem later if the certificate turns out to be missing an endorsement. You are not the reviewer. Your job is to gather the right documents and route them, not to interpret the policy on the phone.

The second mistake is accepting a vague scope description. "They handle the glass work" is not scope. Ask what tasks, what floors, what access, and whether the sub works alongside other trades on the same site. A vague scope produces a vague file, and a vague file produces a service team that has to call the client back and ask the same questions you should have asked the first time.

The third mistake is skipping the deadline. If you do not ask when the crew starts, your request sits in a queue while the crew is already on site without documentation. The fourth mistake is closing the file on memory instead of the actual document. Keep the contract language and the certificate attached to the file, not just your summary of the call, so the next reviewer can check your notes against the source.

How to Practice and Score This Conversation

This conversation is easy to get wrong live and easy to fix in rehearsal. Ask a colleague to play a project manager who is in a hurry, gives partial answers, and pushes you to confirm coverage on the spot. Run the call and check three things afterward. Did you get the actual scope of work, not a summary. Did you name a document owner and a deadline instead of accepting a name and moving on. Did you avoid stating a conclusion about coverage that only a reviewer can make.

DealSpeak builds this exact scenario into its practice conversations, scoring whether you asked for the right facts and whether you stayed inside your role instead of guessing at policy interpretation. The same discipline carries into other discovery conversations you run as a producer, including the very different tone needed for Handling a Teen Driver Quote Conversationwhere the goal is again to gather facts before you commit to a number or an outcome. You can find more scenarios built for your role on the Insurance practice conversations page.

A subcontractor discovery call is not about producing a yes or no answer on the phone. It is about building a file with the right names, dates, and language attached to it, so the people qualified to make a coverage decision can actually make one. Get the scope, the deadline, and the document owner right, and the rest of the review takes care of itself.