The Contractor One Site Turned Away Is Bidding at Another Site Next Month

A site safety lead at one facility declines to bring a contractor back after a near miss involving an unguarded saw and a worker who hadn't been through the site's orientation. The decision is documented in that site's files, communicated to the contractor's account manager, and then it stays exactly where it was made. Six weeks later, a different facility two states away — same parent company, different purchasing team, different safety lead — evaluates the same contractor for a similar scope of work, using its own prequalification checklist, and approves them. Nothing in that second site's process was wrong on its own terms. The contractor had current insurance, a workers' comp experience modification rate under the site's threshold, and no open OSHA citations on record. What the second site didn't have was any way to know what the first site already learned, because prequalification was never built to travel between locations that happen to share a logo.

Prequalification lives at the site because the hazards do

This isn't an oversight so much as a reasonable response to a real constraint: the hazards a contractor will face are specific to a location, so the person best positioned to vet a contractor against those hazards is the person who runs that location. A prequalification process built entirely at headquarters, disconnected from the floor, would miss the things that actually matter on a given job — whether a contractor's crew has confined space experience if this site has permit-required spaces, whether their equipment matches this site's power requirements, whether their safety orientation covers this facility's specific lockout points. Decentralizing the judgment call to the site level gets that part right.

What decentralization doesn't solve, and was never designed to solve, is the question of what happens to what one site learns about a contractor once that contractor moves on to bid somewhere else in the same portfolio. Under OSHA's multi-employer worksite doctrine, a host employer can be cited for hazards created by a contractor operating on its property, and a controlling employer with the authority to direct how work gets done carries even broader exposure. That doctrine attaches to the site where the incident happens — but a corporate safety function overseeing many sites is exposed to the pattern across all of them, and a pattern is exactly what a purely site-local record can't show. A contractor rejected once looks, from any other single site's vantage point, exactly like a contractor with no history at all.

What doesn't travel between sites

Three pieces of a contractor's record tend to live and die at the site that generated them. The first is the outcome of past work itself — a near miss, a citation the contractor received while working at your facility, a pattern of late safety documentation — none of which is typically recorded anywhere a different site's purchasing team would think to look. The second is the threshold each site actually applies. One facility's safety lead may reject any contractor with an experience modification rate above 1.0; another may accept up to 1.2 because the regional labor market makes stricter enforcement impractical. Neither number is wrong in isolation, but a contractor who fails at one site and passes at another isn't being evaluated against a company standard — they're being evaluated against whichever number happened to be in that site's spreadsheet. The third is orientation and training verification. A contractor's crew that completed site-specific safety orientation at one location has completed nothing that a second location can rely on, because the orientation was written for the first site's hazards, not a portable credential the contractor carries with them.

None of this requires bad faith or negligence at either site. It requires only that two sites made independent, locally reasonable decisions using different information, and nobody above either of them was positioned to notice the two decisions were about the same contractor.

The gap becomes a repeat exposure, not two separate ones

The practical risk isn't abstract. A contractor that one site correctly screened out for a documented safety failure showing up, cleared, at a second site creates the same underlying hazard exposure that the first site's decision was meant to prevent — except now it's happening at a location with no institutional memory of why that contractor was a problem in the first place. If an incident follows, the citation and the liability land on the specific site where the work happened, but the pattern that a plaintiff's attorney or an OSHA area office would eventually surface is a corporate one: your company knew, at one location, that this contractor had a safety issue, and continued to use them at another. That's a materially different exposure than an isolated site-level lapse, and it's the kind of fact pattern that shows up in the aftermath of an incident far more often than in the planning that precedes one.

The certificate that lapsed nobody at the next site would catch

A related version of the same gap shows up with insurance documentation rather than safety history. A contractor's certificate of insurance has an expiration date, and the site that originally prequalified them typically checks that date once, at intake, and again only if a renewal happens to cross someone's desk. If that contractor picks up work at a second site eighteen months later, the second site has no way of knowing whether the certificate on file with the first site is even the same policy, let alone whether it lapsed somewhere in between without anyone re-verifying it. A gap in coverage is invisible until a claim exposes it, and a claim exposing it after the fact means the company is now the one holding costs the certificate was supposed to have transferred to the contractor's carrier. This isn't a hypothetical edge case — insurance certificates lapse constantly in the ordinary course of a contractor's business, for reasons that have nothing to do with the quality of their safety program, and a verification step performed once at one site does not stay valid forever just because the paperwork from that first check still sits in a file somewhere.

The fix looks the same as it does for safety history: not a single central approval gate, but a shared expectation that certificate status gets re-verified at defined intervals regardless of which site is currently using a given contractor, and that the verification date itself — not just the certificate's stated expiration — is visible to whichever site engages that contractor next.

What a portfolio-level minimum actually needs to cover

The fix isn't centralizing contractor selection at headquarters — that would recreate the original problem in the opposite direction, stripping site safety leads of judgment they're better positioned to exercise than anyone at corporate. What a portfolio needs instead is a shared floor beneath the site-level process: a minimum EMR threshold every site enforces regardless of local labor market pressure, a requirement that any safety-related rejection or termination of a contractor gets logged somewhere every other site's purchasing team can check before engaging that same contractor, and a baseline safety orientation content standard that sites can add to but not subtract from. None of that requires a single national approval process. It requires a shared record and a shared floor, with the site-specific judgment still happening where the hazard-specific knowledge actually lives.

The alternative — leaving each site's prequalification process fully isolated — isn't neutral. It quietly guarantees that the most useful piece of information about a contractor, the fact that another part of your own company already had a problem with them, is the one piece of information least likely to reach the site that needs it next.

Our contractor safety prequalification checklist gives site teams a consistent baseline to screen against, so "prequalified" means the same thing at every location even when each site's safety lead is still making the final call.