Subcontractor Quote Collection for General Contracting

Open the latest drawings, specifications, and project factsheet. Confirm you are working from the current issue that includes all known addenda so bid packages reflect the correct scope.

Create a list of trades and systems involved (for example, earthwork, concrete, structural steel, roofing, metal studs and drywall, flooring, mechanical, electrical, plumbing, fire protection). Use prior similar projects as a reference to avoid missing trades.

Decide which scopes will be combined or separated for bidding, following company norms and local market practices (for example, “framing and drywall together,” “roofing and sheet metal together”). Write a draft list of bid packages with a short label for each.

For each bid package, write a short scope paragraph in plain language describing what the subcontractor is expected to furnish and install. Include a phrase like “all labor, materials, equipment, and incidentals necessary to provide a complete system as shown and specified.”

Under each scope description, list specific items that must be included and any known exclusions or “by others” items. Use bullet points for clarity.

Create a simple “Subcontractor Bid Package Matrix” document listing packages, scope summaries, and boundaries between trades. Save it in the bid folder and link it in the bid record so the team can use the same structure.

Access your subcontractor database, past project records, or procurement system. Filter by trade, region, and typical project size to identify subcontractors who have worked on similar projects.

Check notes on quality, schedule performance, safety incidents, and change order behavior. Flag subcontractors with serious or repeated issues so they can be excluded or invited only with caution.

Confirm that each subcontractor works in the project’s geographic area and has the capacity to handle the anticipated contract size. Remove firms that are clearly too small or not active in the region.

If coverage for a trade looks thin, ask project managers, superintendents, or business development contacts for recommendations. Verify basic licensing, insurance, and trade focus before adding new names.

For each bid package, create a list of subcontractors you plan to invite, including company name, contact person, email, and phone. Aim for three to five solid options per trade where possible.

Store the invite list in the bid folder (for example, “Sub_Invite_List.xlsx”) and link it in the bid record so others can see which subcontractors were invited for each package.

Open your company’s standard subcontractor invitation email or letter template. If no template exists, create a simple format that includes project overview, bid package name, bid due date, and submission instructions.

Add the project name, location, owner (if allowed), overall bid due date, and your required subcontractor quote due date and time. Include time zone and clearly state whether this is a budget, hard bid, or negotiated proposal.

Paste the bid package scope description and key inclusions/exclusions for that trade into the invitation. Make sure the language matches the matrix so there is no contradiction between documents.

Tell subcontractors what you need in their proposals: base price, alternates, unit prices, allowances, and a short list of major inclusions/exclusions. Note any specific breakout requirements you will need for estimate assembly.

Clearly state the email address or portal they should use to submit proposals and any subject line or reference format you require (for example, “Project – Trade – Company Name”).

Save a copy of the final invitation text for each trade in the bid folder so you can reuse language for reminders and have a record of what was communicated.

Set up a central folder or project in your file-sharing or plan room system that holds all drawings, specs, addenda, and any bid package matrix you want to share with subcontractors.

Within the share, organize documents into clear folders (for example, “Drawings,” “Specs,” “Addenda,” “Bid Package Matrix”), and ensure file names are readable and not overly technical.

For each trade, copy that trade’s contacts into the “To” or “BCC” line and send the prepared invite, including links to the shared documents or attaching only the critical portions if sharing by email.

In the email, ask subcontractors to reply confirming they received the documents and indicating whether they intend to submit a proposal. This helps you gauge early coverage.

Create or update a “Sub_Bid_Log” with trade, subcontractor, contact, invite date, and a status field (Invited, Confirmed, Declined). Update the log as replies come in.

If you receive bounce-backs, contact the company by phone or check your records to find updated contacts. Resend invitations so coverage for that trade does not suffer.

Use your sub bid log to track each invited subcontractor’s status (Invited, Confirmed, Declined, Quoted). Keep the file open and update it as responses arrive.

When subcontractors reply that they will or will not bid, immediately update their status and, if they decline, note their reason (for example, workload, outside scope, geography).

At least weekly early in the bid period and daily in the final week, review how many confirmed bidders you have for each trade. Flag trades with zero or very few committed bidders.

For trades with weak coverage, identify additional qualified subcontractors from your database or referrals and send them the same bid invitation and documents.

Share a short summary with the estimating lead showing trades with low coverage or major declines so they can assist with targeting or strategy adjustments.

Keep the log current through bid day so at any point you can see which trades are still missing quotes and who has indicated they will submit.

Regularly check the plan room, email, and bid portal for new addenda or clarifications issued by the client. Note which trades and scopes are affected.

Save addenda drawings, specs, and clarification letters into an “Addenda” subfolder within the bid folder. Label files with addendum numbers and dates (for example, “Addendum_2_2026-02-10.pdf”).

Scan each addendum to identify which bid packages and trades are affected. Note changes such as added alternates, revised details, or scope deletions.

Send a concise email to subcontractors in affected trades with a summary of the addendum, its number and date, and links to the updated documents. Instruct them to base their bids on the latest set.

If an addendum significantly changes scope or quantities, ask subcontractors to revise their proposals or confirm in writing that their current pricing includes the addendum.

Record addenda details and subcontractor notifications in your sub bid log or a separate addenda log. Note which addenda are included in bids and which may still be pending.

In the bid folder, create a “Sub_Bids” folder with subfolders for each trade (for example, “Sub_Bids_Concrete,” “Sub_Bids_Roofing,” “Sub_Bids_Mechanical”).

When a proposal email arrives, save the attached proposal and any supporting spreadsheets into the correct trade folder. Convert emails to PDF if needed and include them with the proposal.

Use a consistent naming pattern such as “CompanyName_Trade_2026-02-10.pdf” so it is obvious who submitted what and when, without opening each file.

Mark each subcontractor as “Quoted” in the sub bid log when their proposal is received. Record the date and time and, if readily visible, the base bid amount.

Scan each proposal to confirm it references the correct project, trade, and document set, and that it addresses base scope and clearly requested alternates. Flag bids that appear incomplete for follow-up.

Send a brief email thanking the subcontractor for their proposal and confirming it has been received and logged. Ask obvious clarifying questions immediately rather than waiting until bid day.

For each trade, open the bid package scope description and the subcontractor’s proposal at the same time so you can compare them directly.

Use a standard scope checklist or create a quick list of key items that must be included for a complete bid in that trade. This may include demolition, temporary work, and coordination requirements.

Review the subcontractor’s listed inclusions and exclusions, highlighting any items that differ from your scope checklist or appear incomplete or unusual.

For each item on your checklist, mark whether the proposal clearly includes it, excludes it, or is ambiguous. Focus on items that could cause significant cost differences.

For unclear or excluded items, note questions you need to ask and whether you expect a cost impact if they must be added. Use a simple comments column or note field.

Store your marked-up checklist or notes in the same trade subfolder as the bids so anyone reviewing can understand your initial assessment of each proposal.

Create a sheet or tab per trade that lists subcontractors across the top and key cost and scope items down the side (base price, main alternates, key inclusions/exclusions).

For each subcontractor, enter their base bid amount and prices for requested alternates as listed in their proposals. Note whether alternates are add or deduct prices.

From your scope review, enter short notes for each subcontractor highlighting major differences in inclusions and exclusions that affect comparability.

Indicate which addenda and clarifications each subcontractor has acknowledged in their proposal so you can see who is aligned with the current document set.

Mark which bids require follow-up questions before they can be fairly compared, based on missing information or unclear scope language.

Store the comparison sheets in the “Sub_Bids” or a “Sub_Comparison” subfolder. These will be used directly in the Estimate Assembly process.

Open the latest sub bid log and comparison sheets for all trades. Confirm which trades have multiple bids, single bids, or no bids.

Create a short summary document listing trades at three levels: “complete coverage,” “limited coverage,” and “no bids,” with a few words explaining the situation for each.

Note trades where all bids have major exclusions, unusually high or low pricing, or significant uncertainty. Flag where you expect to carry contingencies or allowances.

List specific subcontractor proposals that need clarification calls or emails before numbers can be used in the estimate. Note who will contact them and by when.

For trades with no bids or insufficient coverage, describe any provisional costs you intend to use (for example, benchmarking, vendor pricing, or historical unit costs).

Save the summary in the bid folder and send it to the estimating lead and anyone responsible for Estimate Assembly. Confirm that they know where to find all detailed logs and comparison sheets.