> For the complete documentation index, see [llms.txt](https://docs.buildertek.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildertek.com/request-for-quotes-rfqs/award-vendor.md).
# Award Vendor
Once all bids have been received, reviewed, and compared, the next step is to select the vendor you want to move forward with.
At this stage, the RFQ process transitions from vendor bidding to procurement and customer proposal preparation. However, BuilderTek supports multiple business workflows, and not every company follows the same process.
By default, BuilderTek is configured to perform the following actions when a vendor is awarded:
* The selected vendor receives an Award Notification email.
* The vendor is notified that they have been selected for the project.
* The vendor may be required to accept the award before work proceeds.
* Vendors who were not selected automatically receive a thank-you notification.
* The RFQ bidding process is closed.
But We can configure to support different procurement workflows, including:
* **Create Purchase Order on Vendor Award: A Purchase Order is automatically created when the vendor is awarded.**
* **Create Purchase Order on Vendor Acceptance: A Purchase Order is created only after the vendor formally accepts the award.**
* **Do Not Send Award Notification Email: The vendor is marked as awarded within BuilderTek, but no award email is sent.**
* **Do Not Require Vendor Acceptance: The vendor is awarded without requiring an acceptance response.**
#### Step 1: Select the Vendor
From the RFQ Dashboard, review all submitted bids and identify the vendor you wish to move forward with.
This decision may be based on:
* Lowest bid amount
* Best overall value
* Scope completeness
* Vendor experience
* Availability
* Project-specific requirements
Select the vendor by checking the box next to the vendor's name.
***
#### Step 2: Award the Vendor
Once the vendor is selected, click the "Award Vendor" button.
BuilderTek will process the award according to your configured workflow settings.
Depending on your organization's setup, this may:
* Notify the vendor
* Request vendor acceptance
* Create a Purchase Order
* Mark the RFQ as awarded
* Close the bidding process
### Outcome
The RFQ process is now complete.
A vendor has been selected based on submitted bids, pricing comparisons, project requirements, and your organization's procurement workflow. The awarded vendor and final pricing are now available within BuilderTek and can be used throughout the remainder of the preconstruction process.
At this stage, all vendor pricing, bid revisions, communications, and award decisions remain connected to the original Walkthrough and RFQ records, providing a complete audit trail and ensuring full project visibility.
The selected vendor gets an email receipt of “Bid Awarded”. They can either accept it or decline it.
The other vendors also get notified that the bidding process is over and the RFQ is closed. Thank you for your participation.
Now The Next Step:
1\. You create a Quote to share with your customer and get approval to create a new project based on the approved quote.
2\. If you have already created a project, you can move on to the next step of making a purchase order for the vendor.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.buildertek.com/request-for-quotes-rfqs/award-vendor.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.