Skip to contentSee BidToJob in Action

Subcontractor Bidding: From Scope Selection to Accepted Bid

This guide explains a subcontractor bidding workflow that starts with selected project tasks and ends with an accepted bid, status notifications, invoicing, and payment. It is organized as a practical checklist so you can prepare the scope, recipients, and supporting files before sending anything.

Before you send: a bid-request checklist

Use this sequence to keep a bid request complete and comparable:

  • Select the tasks that form the scope of work from the tasks tab on the project screen.
  • Add those tasks to a bid and complete the relevant information and subcontractor instructions.
  • Attach drawings or other files the subcontractors need to price the work accurately.
  • Add every subcontractor who should receive the request.
  • Before sending, confirm each recipient has an email address in the Workers screen under Admin in the main navigation.
  • Customize the outgoing email, using variables where appropriate to insert bid-request details or subcontractor-specific information.
  • Send the request only after the scope, attachments, recipients, and message have been checked.

What subcontractors see and submit

Subcontractors receive the bid-request email and log in to a subcontractor portal. The portal carries the company's logo and colors, similar in presentation to admin and client portals. Inside, subcontractors can view the bid-request information, including drawings, photos, and other attachments. They enter a price for each line item in the scope of work and may add terms, additional information, or attachments with their submission. That line-item structure matters: it makes it easier to compare what each subcontractor included, rather than relying on a single total with no breakdown.

Comparing bids, accepting a winner, and finishing the loop

Submitted bids can be viewed in the Bids screen from the main navigation, or accessed from the tasks in the project screen. Tasks included in a bid request display an icon next to the task name, which helps you spot bid-linked work without opening every task. When you are ready, accept the winning bid. All subcontractors who submitted bids are automatically notified about the status of their bid once one is accepted. The source describes the winning subcontractor as then able to invoice directly through the app, with payment also made directly through the app; this invoicing and payment step requires owner verification before being presented as a current capability: {{OWNER_CONFIRM_INVOICING_AND_PAYMENT}}.

Worked example: same scope, comparable responses

A worked example using only the captured workflow: suppose a project has several tasks, but only three belong in a subcontractor's scope. Select those three tasks, add them to a bid, attach the relevant drawing, add two subcontractors with email addresses already recorded in Workers, and customize the email with variables for the bid details. Each subcontractor then prices the same three line items in the portal and can attach supporting information. You compare the returned line-item bids in the Bids screen, accept one, and the system notifies both submitters. The source describes the winner invoicing through the app and being paid through the app, subject to owner verification: {{OWNER_CONFIRM_INVOICING_AND_PAYMENT}}. The key distinction is between the request stage, where scope and attachments are prepared, and the response stage, where comparable line-item pricing is collected.

Common distinctions to keep clear

Do not confuse these related steps:

  • Selecting tasks is not the same as sending a request; recipients, instructions, and attachments still need to be added.
  • Customizing the email is not a substitute for recipient setup; subcontractors still need email addresses in Workers under Admin.
  • Viewing a bid in the Bids screen is not acceptance; acceptance triggers automatic status notifications to all submitters.
  • Accepting a bid is not the final financial step; the source describes the winning subcontractor invoicing and payment through the app, subject to owner verification: {{OWNER_CONFIRM_INVOICING_AND_PAYMENT}}.

Frequently asked questions

How do I start a bid request from existing project tasks?

Yes. Choose the relevant tasks from the project's tasks tab, add them to a bid, enter instructions, attach drawings or other files, select recipients, and send. The email can then be customized before sending.

What must be set up before subcontractors can receive the email?

Confirm each subcontractor has an email address in the Workers screen under Admin in the main navigation. Without that address, the customized bid-request email cannot be delivered as described.

What can subcontractors do after receiving a bid request?

Subcontractors log in to a subcontractor portal branded with the company's logo and colors. They can review bid information and attachments, price each scope line item, and add terms, information, or attachments before submitting.

Where do I compare bids and how are submitters notified of the outcome?

Review submissions in the Bids screen from the main navigation, or through the project tasks. Tasks included in a bid request show an icon beside the task name. Accepting one bid automatically notifies all subcontractors who submitted bids about their status.

What happens after a winning bid is accepted?

The source describes the winning subcontractor as able to invoice directly through the app, with payment also made directly through the app. Treat this as a source-described feature requiring owner verification before presenting it as a current capability: {{OWNER_CONFIRM_INVOICING_AND_PAYMENT}}.