Subcontractor Exception Management: Accept, Escalate, or Reject

TL;DR: When a sub shows up with a compliance gap, the GC has three choices: accept with conditions, escalate, or reject. The decision depends on severity (Critical gaps like no COI or no workers' comp equal rejection, High gaps like missing AI endorsements or expired W-9s warrant escalation), urgency relative to project start, and total risk exposure, and every exception needs a named owner with a hard deadline.

In a perfect world, every subcontractor shows up to a project with a complete compliance file: current COI with all the right endorsements, signed W-9, valid license, Workers' Comp verified. In the real world, subs have gaps. Maybe the COI is expired but a renewal is imminent. Maybe the W-9 is missing because the sub is transitioning entity types. Maybe the WC is current but the policy doesn't include your specific state.

When gaps happen, the GC has three choices: accept the sub with conditions, escalate the issue, or reject the sub and find a replacement. This post walks through a practical framework for making that decision.

The Three Outcomes

Accept with Conditions

The sub can start work (or continue working), but with specific conditions attached that must be resolved within a defined timeline. Conditions might include: producing the missing document within 7 days, holding retainage higher than normal until compliance is restored, limiting the sub to specific work types until the gap is closed.

Escalate

The gap can't be resolved at the PM level and needs to go up the chain. Escalation targets might be the GC's risk manager, insurance broker, or construction attorney. Escalation is appropriate when the stakes are high or the gap involves interpretation of contract terms that the PM isn't qualified to make.

Reject

The sub can't start work, or must stop work immediately if already on site. Rejection is the right answer when the gap is serious enough that no reasonable conditions can close it in time.

What Determines the Right Outcome?

Three factors drive the decision.

Factor 1: Severity of the Gap

Not every missing document is equivalent. A severity scale:

• Critical: no COI at all, uninsured sub, expired GL coverage, no Workers' Comp on a project with employees, invalid license on regulated work. These are rejections unless immediately fixed.
• High: missing AI endorsement, missing PNC language, expired W-9, license expiring within 30 days without renewal proof. These warrant conditional acceptance with tight timelines or escalation.
• Moderate: missing non-critical endorsements, incomplete supporting documentation, minor discrepancies in named insured. These usually warrant conditional acceptance.
• Low: formatting inconsistencies, outdated contact info, stale but not expired documents. These warrant routine follow-up, not formal exceptions.

Factor 2: Urgency and Project Impact

A missing document on a sub who starts work tomorrow is different from a missing document on a sub who starts work in three weeks. Urgency weighs heavily:

• Starts work today or tomorrow: the exception must be resolved before work begins. Escalate fast or reject.
• Starts work this week: conditional acceptance with a hard deadline, tracked daily.
• Starts work this month: routine follow-up, standard timelines.
• Not yet assigned to a project: collect the missing documents before project assignment.

Factor 3: Sub's Track Record and Criticality

A long-term sub with a clean history and urgent renewal timing is a different risk profile than a new sub with multiple gaps. A critical-path sub is harder to replace than a finish trade.

• Long-term, trusted subs get more benefit of the doubt, conditional acceptance with trusted follow-through
• New or untested subs get tighter conditions or rejection
• Critical-path subs can tolerate more conditional acceptance because replacement costs are higher
• Easily replaced subs should be rejected quickly when compliance is incomplete

A Decision Framework in Practice

Combine the three factors into a decision matrix:

Severity	Urgency	Track Record	Outcome
Critical	Today	Any	Reject unless immediate fix
Critical	This week	Trusted	Escalate + tight conditions
High	Today	Trusted	Conditional acceptance, 48-hour resolution
High	This month	New	Reject or escalate
Moderate	Today	Trusted	Conditional acceptance, 7-day resolution
Moderate	This week	Any	Conditional acceptance, 14-day resolution
Low	Any	Any	Routine follow-up

This isn't an algorithm, it's a starting point for judgment. Real decisions involve context the matrix can't capture: the owner's risk tolerance, the project's size, the GC's own insurance program, and any specific contract requirements.

Documenting Exceptions

Every exception needs to be documented. At minimum:

• The gap: what's missing or non-compliant
• The decision: accepted with conditions, escalated, or rejected
• The conditions: if accepted, what needs to be resolved and by when
• The authorizer: who approved the exception (PM, ops lead, risk manager)
• The resolution: when and how the gap was closed

This documentation matters for three reasons. First, it creates accountability so exceptions don't drift into permanent gaps. Second, it provides evidence of good-faith compliance management in case of a claim or audit. Third, it gives the organization data on which types of exceptions happen most often so the underlying process can be improved.

Common Exception Patterns

Based on what most GCs encounter, a few patterns come up repeatedly:

"The COI is in process"

The sub's producer has requested the certificate but it hasn't been issued yet. Conditional acceptance is reasonable if the underlying policy is verifiable (call the producer), with a 48-to-72-hour deadline.

"Renewal is pending"

The sub's policy is expiring this week but the renewal isn't finalized. Conditional acceptance with daily monitoring, escalate to reject if the renewal isn't confirmed by expiration date.

"Wrong named insured"

The COI shows "ABC Construction LLC" but the contract is with "ABC Construction Inc." This is almost always a clerical error, but it must be resolved before work starts because the wrong entity means no coverage.

"Exemption claimed without documentation"

The sub says they're WC-exempt as a sole proprietor. Require the state-issued exemption certificate. Don't accept verbal assertions.

"Endorsement pages not available"

The sub refuses or can't produce the actual endorsement documents. This is a red flag. Escalate or reject, especially on moderate and high-risk contracts.

How PaperBoss Supports Exception Management

PaperBoss shows each sub's compliance status as a clear dashboard, making it easy to identify gaps the moment they occur. The dashboard distinguishes between subs who are fully compliant, subs expiring soon, and subs with missing documents, so exception management becomes routine rather than reactive.

For structured exception tracking, you can use PaperBoss's custom fields on Pro and Business plans to record the decision, authorizer, conditions, and resolution timeline per exception. Combined with automated expiration alerts, the system keeps exceptions from getting lost in daily operations.

Start a 14-day free trial, no credit card required.

Frequently Asked Questions

Who should authorize exceptions?

It depends on severity. Low and moderate exceptions can be handled by project managers. High and critical exceptions should require risk manager or operations leader approval. For rejections of critical-path subs, the decision often goes to the GC's executive team because of the schedule impact.

Can conditions include financial holds?

Yes. Holding additional retainage or deferring payment until compliance is restored is a common condition. It provides leverage without stopping the sub's work entirely.

What happens if a sub never closes a conditional acceptance?

Escalate. If conditions aren't met by the deadline, the exception becomes a formal rejection, and the sub must either resolve immediately or be removed from the project.

How do I avoid favoritism in exception decisions?

Apply the framework consistently and document every decision. Over time, the documentation creates accountability and evens out individual PM discretion.

Does PaperBoss auto-reject non-compliant subs?

No. PaperBoss surfaces gaps and provides the dashboard for decision-making, but the decision to accept, escalate, or reject stays with the human operator. Automation shouldn't replace judgment on decisions this consequential.

---

This article is for educational purposes only and does not constitute legal or insurance advice. Consult a construction attorney or risk management professional for specific exception handling questions.