---
title: 'SCA Wicks subcontractors: qualification does not settle scope coverage'
url: 'https://piper-ai.com/resources/nyc-sca-wicks-subcontractor-scope-review'
description: 'For an SCA school bid, verify named Wicks subcontractor qualification and test the quote against the package. A scope-review method for GC estimating teams.'
contentTypes: [guide]
publishedAt: '2026-11-15T12:00:00.000Z'
updatedAt: '2026-11-18T15:33:17.998Z'
author: 'Ido Gedanken, CEO'
readingTime: 4
---

# SCA Wicks subcontractors: qualification does not settle scope coverage

1. Check named subcontractor qualification against the current SCA requirements.
2. Review quote coverage independently from qualification status.
3. Escalate unclear package boundaries before selecting the carry.

An SCA subcontractor's qualification status establishes something different from the completeness of its bid. The GC needs both checks before relying on a named Wicks proposal: confirm the current qualification requirements and verify that the quote carries the intended package.

On a hard-bid school pursuit, a missing trade interface cannot be closed by pointing to a firm's place on an approved list. Conversely, a well-scoped quote does not establish that the firm meets the agency's eligibility requirements at bid opening.

This is a GC preconstruction review guide for packages identified as Wicks trades in the issued SCA bid documents. It does not interpret Wicks applicability for every New York public owner or replace the project's bidder instructions.

## Verify qualification through the current SCA process

[SCA's prequalification guidance](https://www.nycsca.org/Doing-Business/Prequalification-Process) states that named Wicks subcontractors must be prequalified at bid opening. It also describes an additional qualification level for work at or above $1 million. The [subcontractor page](https://www.nycsca.org/Doing-Business/Subcontractor) describes project-specific requirements and uses different wording at the threshold. Confirm borderline cases with SCA using the issued bid documents; do not resolve them by rounding an estimate.

Keep evidence of the checked firm, relevant trade and check date in the bid file. A status captured for another job or a different scope is not a complete review of this one.

The Subcontractor Approval Form process is a separate project-specific process with stated exceptions. Do not assume a post-award form will cure a bid-opening qualification issue.

## Build the scope reference before comparing proposals

Ask what the package must deliver across the drawings, specifications, construction exhibit and addenda. The trade's primary specification section is only one input.

For occupied work, begin with the [school phasing guide](https://piper-ai.com/resources/nyc-sca-school-construction-phasing-estimate). Protection, access and turnover assumptions may change how multiple trades price the same location. A common location does not mean every quote includes the same work cycle.

Then mark scope at the boundaries: openings, sleeves, supports, controls connections, testing and reinstatement where the project requires them. The documents and contract allocation determine responsibility. The reviewer's task is to find where a quote disagrees with that allocation or says nothing about it.

## Keep coverage findings separate from bidder status

An illustrative review record can have two independent decisions: eligible for the proposed role, and acceptable basis for carry after scope review. Do not collapse them into one approved column.

For each qualification in the quote, identify the corresponding requirement and treatment. Does the proposed exclusion remove work the GC must carry elsewhere? Is that work actually included in another package, or only assumed to be there?

The method in [reviewing subcontractor exclusions](https://piper-ai.com/resources/review-subcontractor-exclusions-and-qualifications) helps classify the difference. Keep raw quoted price distinct from the estimator's review adjustments and unresolved issues.

## Do not convert a clarification into an informal substitution

A late coverage problem can tempt a team to treat the issue as an ordinary commercial swap. On public work, the applicable bid instructions and rules determine what the team may name, qualify, correct or change. Escalate that question to the submission owner and appropriate legal or agency reviewer before acting.

The estimating team can still document the facts: which quote was received, its scope basis, the unresolved interface and the proposed cost treatment. That evidence supports the decision without pretending the spreadsheet determines responsiveness.

## Preserve the file behind the selected number

Use the [public-bid documentation guide](https://piper-ai.com/resources/public-bid-leveling-documentation) to retain the package baseline, received proposals, written clarifications and review basis. Feed unresolved issues into the [NYC final-review map](https://piper-ai.com/resources/nyc-public-construction-bid-review-checklist).

The chief estimator should be able to distinguish a qualification question from an uncovered scope item without rereading the entire correspondence chain. Both may stop the bid, but they need different owners and different evidence to close.

## Check the Wicks proposal against the package you need covered

After qualification is verified through the SCA process, the estimator still needs to understand what the proposal actually covers. Piper’s [bid leveling](https://piper-ai.com/use-cases/bid-leveling) compares subcontractor proposals against the intended project scope, extracting inclusions, exclusions, qualifications and addenda acknowledgments. It surfaces gaps and uncertain coverage with their sources so the reviewer can see what needs clarification before selecting a carry.

Those findings remain connected to the project context used in scope preparation and final review. The GC retains responsibility for qualification evidence, any required subcontractor naming and the number it submits. A scope comparison supports that decision; it does not establish eligibility or responsiveness.
