Vetting Contractors and the Certificates to Demand

Verification is an order of operations rather than a folder. The check that costs nothing goes first, the signed agreement goes before any request for paperwork, and the documents come last — because each one describes a state of affairs the two steps before it created. Reverse the order and the folder fills with paper that settles nothing.

What follows is that order, and what a gap at each stage leaves open.

Step one costs nothing and happens before anyone is asked for paper

Every jurisdiction puts the credential somewhere. In some it is a state license issued by classification. In others it is a state registration that records a firm rather than examining it, or a municipal counter, and in a small number of places there is no statewide record to search at all — which is a fact about the address rather than about the crew, and the state pages carry which of those applies where.

Two agencies publish the step itself, which is useful mainly because it shows what a record is for. The Arizona Registrar of Contractors opens its list for anyone about to hire with reviewing the license record through its own contractor search, and then with making certain “the contractor’s license class allows for the work listed in the contract.” The record and the scope, read against each other, before a signature. More of that position sits on the Arizona page.

Washington’s labor department sets out what its verification tool shows on the page it publishes for people about to hire: whether the license is active, whether the firm is bonded and insured, whether it maintains a safe job site or has corrected any violations, and a license history carrying previous lawsuits or license violations. Four questions answered off a public screen, before anybody has been asked for anything. The rest of that position sits on the Washington page.

Note what none of it measures. A public record answers whether a firm currently stands in good order with an agency. It does not answer whether the work will be square. Those are different questions, and only one of them has a lookup.

Whose payroll the people on site are actually on

The firm you signed with is usually not the only firm on site, and on a job that opens walls it is rarely even close. Generals subcontract. Subcontractors subcontract. A crew that arrives in unmarked vans may be employees of the firm named in your agreement, may belong to a second firm nobody mentioned, or may be individuals working for themselves.

Registers sometimes draw that line out loud. Washington’s labor department, on its own registration page, separates general contractors — who it says can perform most types of construction work and can hire subcontractors in multiple specialties — from specialty contractors, who it says can only perform work in the specialty they registered in and cannot hire subcontractors at all. A registration is a statement about structure as much as about trade.

So the step is one almost nobody takes: ask, before mobilization, for the list of every firm expected to set foot on the site, and put the same requests to each of them that you put to the first. Asked before the crew arrives, that is a term of the deal. Asked afterwards, it is an interruption, and it is answered like one.

Which cover answers for injury to somebody else on ground you own is set out on the general liability page. Read it once before deciding how long you want that list of firms to be.

The agreement has to exist before the paperwork can mean anything

A requirement raised after the crew has mobilized has nothing to attach itself to. Whatever you intend to collect belongs in the document both parties sign, because a request made beforehand is a term and a request made afterwards is a favor.

Arizona’s list is blunt about how much of this is drafting rather than chasing. It asks for a detailed description of every aspect of the project, the price, the responsibility for obtaining building permits and the other relevant terms, all spelled out in the contract document, and for change orders to be properly executed in writing. None of that is exotic. All of it is easier to agree before anybody has spent anything.

What those documents can and cannot establish once they do arrive is a separate subject entirely, and it is the half of this that most people get wrong. The half here is earlier and duller: making sure there is something in the signed agreement for the request to rest on.

Three names, and the trouble when they are three different names

There is the name on the public record. There is the name on the agreement. There is the name on the insurance paperwork. On a tidy file those are one name. On an ordinary one they are three, because the trading name on the door of the truck, the entity that holds the credential and the entity that bought the policy were each created at a different time for a different reason.

Arizona’s list carries a step aimed squarely at this: verify that the person you are negotiating the project with is an authorized representative of the licensed firm, by calling the number listed on the license record rather than the number printed on the card you were handed. The same instinct belongs on the entity. Read the legal name off the record, write that name into the agreement, and check everything that arrives afterwards against it.

A mismatch is rarely evidence of anything dishonest. It is usually housekeeping. It is also the kind of housekeeping that tends to be discovered by somebody reading a claims file rather than by you, and at that point it has stopped being administrative.

Every document arrives with a date, and the schedule outruns it

Each thing you collect describes a moment. The public record was accurate the afternoon it was pulled. The insurance paperwork was accurate the morning it was typed. A renovation calendar, meanwhile, only ever moves one way, and the weeks it adds are weeks none of that paper knows anything about.

The step at collection is therefore to write two things beside each document: the date it stops describing anything, and where that date falls in the build calendar. If it falls before the last day of work, you have a diary entry rather than a problem — but only if the entry is made on the day the document arrives, because nobody goes back and makes it later.

The same arithmetic runs on your own side of the site, where a construction placement ends on a date rather than on the day the work happens to finish, which is why cover can stop earlier than people expect. Both halves of the job are running calendars. Only one of them is yours to extend, and a builders risk placement is written to the finished building rather than to the day it was bound.

When the answer is that it will be sent over later

It usually will be sent. That is not the point. The point is that the exposure is not the missing document — it is the days worked while nobody was holding it, and those days do not turn insured retroactively because the paper lands on the Friday.

There are three ways to handle it and they cost different things. Move the start date, which costs schedule. Narrow what the firm is allowed to do until it arrives — demolition and haul-off rather than anything behind a wall — which costs sequence. Or start anyway and write down that you started anyway, with the date, what was asked for and when it was promised. The third is not a control. It is a record of a decision, and a record of a decision is the only thing that separates a decision from an oversight when somebody reads the file long afterwards.

Real-World Scenario: Four firms are lined up for a rehab that opens walls, and by the Friday before demolition three of them have produced everything asked for. The fourth is the electrician, who is between agents, and the answer, day after day, is that it is coming. Nobody wants to lose the panel slot, so the crew starts. Well into the delay, a delivery backing into the drive flattens the meter riser, the line is shut at the street, and the file that gets opened wants to know who was on site and under what arrangement. The paperwork turns up that afternoon, current and correct, and it describes a firm that had been covered the whole time — which is the good version of this story. The bad version is identical in every particular except one: the firm let its policy go at the end of the previous season, and the owner learns that from somebody reading a claims file rather than from a request made before the first day. Nothing about that stretch was a decision. It was a start date nobody moved.

What a gap reaches that is not the firm that left it

Paperwork gaps do not stay with the party that created them, and the clearest published illustration of that shape is not an insurance document at all. OSHA’s multi-employer citation policy defines a controlling employer as one “who has general supervisory authority over the worksite, including the power to correct safety and health violations itself or require others to correct them,” and states that such control “can be established by contract or, in the absence of explicit contractual provisions, by the exercise of control in practice.”

Read the factors that directive lists next to that definition. How closely such an employer has to look turns partly on “how much the controlling employer knows both about the safety history and safety practices of the employer it controls,” and the directive adds that greater inspection frequency may be needed, especially at the beginning of a project, where the controlling employer has never before worked with the other firm and does not know its compliance history.

That is a federal enforcement directive about safety citations and it decides nothing about any policy of insurance. It is quoted here for its shape: what you knew about a firm before you put it on your site is already a question somebody asks in writing, in a document that predates every certificate in your folder.

The other place a gap lands is the submission. An underwriter reading a renovation file wants to know who is doing the work, and the distance between a file that answers with firm names, credential status and a written scope and one that answers with “subs” is measured in how long the answer takes to come back. That holds on a structural job and on a finish-level one alike.

Running the same check again when the scope moves

The record you pulled described the job as it was written that day. Change orders rewrite the job. Arizona ties the class question to “the work listed in the contract,” which makes a change order a re-verification trigger rather than only a price event — the sentence that made the original check meaningful is the sentence a change order edits.

Three triggers are worth putting in the diary at the start. A change order that pushes the scope behind a wall or into a system. A firm appearing on site that never signed anything. And the expiry date you wrote down the day the document arrived.

None of this changes what a placement costs, and none of it decides whether the job is finish work that can sit on an endorsed dwelling form or something that opens the structure. It changes something narrower and more useful: whether, on the day somebody asks, the answer to who was working on the house and what they were carrying is a folder rather than a shrug. When the crew list is settled and you want the insurance side lined up against it, tell us who is on the job and what the scope is.