> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/front-office/rendering-types/uncommoditized-rendering-types/request-for-proposal-rfp/bid-proposals-rfp.md).

# Bid proposals (RFP)

Understanding the bid proposals page seen when the RFP bundle is activated

{% hint style="info" %} <mark style="color:blue;">Path: Homepage > All Request for proposal > Request for proposal > Bid</mark>
{% endhint %}

## Definition <a href="#id-1.14.x-bidproposals-rfpbundle-definition" id="id-1.14.x-bidproposals-rfpbundle-definition"></a>

The bid confirmation process is made out of the checkout + the payment process + the confirmation

<mark style="color:red;background-color:yellow;">WHO CAN USE THIS FEATURE?</mark>

Logged in users

## Create a bid confirmation <a href="#id-1.14.x-bidproposals-rfpbundle-createabidconfirmation" id="id-1.14.x-bidproposals-rfpbundle-createabidconfirmation"></a>

Select a request for proposal, choose the date and starting time, and click “Bid” (figure 1). The bid confirmation process starts.

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/RzlvpKDkN1cPNAhVHa8p/image.png" alt=""><figcaption><p>Figure 1</p></figcaption></figure>

## Read the bid confirmation pages <a href="#id-1.14.x-bidproposals-rfpbundle-readthebidconfirmationpages" id="id-1.14.x-bidproposals-rfpbundle-readthebidconfirmationpages"></a>

### The checkout overview page <a href="#id-1.14.x-bidproposals-rfpbundle-thecheckoutoverviewpage" id="id-1.14.x-bidproposals-rfpbundle-thecheckoutoverviewpage"></a>

The checkout overview page is the first page displayed to users after clicking the “bid” button. The checkout overview is visually split into two sections:

* The right section
* The left section

#### The left section <a href="#id-1.14.x-bidproposals-rfpbundle-theleftsection" id="id-1.14.x-bidproposals-rfpbundle-theleftsection"></a>

**The request**

The request displays:

* The title of the request for proposal (figure 2.1)

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/YNwVJw7PkmsvikTqpMlI/image.png" alt=""><figcaption><p>Figure 2.1</p></figcaption></figure>

* The date block (figure 2.2) displays the start and end dates during which the asker would like the services to take place.

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/oYeOGulMF97I2JFVAOBd/image.png" alt=""><figcaption><p>Figure 2.2</p></figcaption></figure>

* The location block (figure 2.3) reminds the user where the service will take place.

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/EcBJeSKjTNfDqIv8BTqL/image.png" alt=""><figcaption><p>Figure 2.3</p></figcaption></figure>

**The offer**

The offeror enters information about his offer:

* Description (figure 3.1)

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/0T53DKfb9yxhNGa9ocQ8/image.png" alt=""><figcaption><p>Figure 3.1</p></figcaption></figure>

* Price for the service (figure 3.2) (potential income and platform fees are automatically calculated)

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/w9Lisqpbq6RDfpZqRL1L/image.png" alt=""><figcaption><p>Figure 3.2</p></figcaption></figure>

* Dates & location (figure 3.3)

{% hint style="info" %} <mark style="color:blue;">The location can not be updated since it is set by the asker.</mark>
{% endhint %}

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/R8gPTA3LCX6KxR93uGbm/image.png" alt=""><figcaption><p>Figure 3.3</p></figcaption></figure>

* Message (figure 4) (optional).

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/fhnV0y67cVUBQ30nuIpj/image.png" alt=""><figcaption><p>Figure 4</p></figcaption></figure>

Accept the terms & conditions of the platform by clicking the checkbox (figure 5).

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/eaubabRg7BGyTWT6QdAn/image.png" alt=""><figcaption><p>Figure 4</p></figcaption></figure>

Click on “Continue >” (figure 6) to confirm the proposal.

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/dwmTVop2E6ooBsSnzFwo/image.png" alt=""><figcaption><p>Figure 6</p></figcaption></figure>

#### The right section <a href="#id-1.14.x-bidproposals-rfpbundle-therightsection" id="id-1.14.x-bidproposals-rfpbundle-therightsection"></a>

On the right-hand side of the page, the RFP-related asker’s information (figure 7) is displayed in a dedicated information block.

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/ENaSHQf948KSHYz4H796/image.png" alt=""><figcaption><p>Figure 7</p></figcaption></figure>

## Update the bid confirmation pages <a href="#id-1.14.x-bidproposals-rfpbundle-updatethebidconfirmationpages" id="id-1.14.x-bidproposals-rfpbundle-updatethebidconfirmationpages"></a>

The user can click “Edit” (figure 8) available on the left-hand side at the end of the checkout overview page to modify the date and time for his proposal.

<figure><img src="https://content.gitbook.com/content/n4EIoqjZx1xWQIo6LnjB/blobs/Zs9fzZiWHtpatY5UH4jW/image.png" alt=""><figcaption><p>Figure 8</p></figcaption></figure>

## Delete the bid confirmation pages <a href="#id-1.14.x-bidproposals-rfpbundle-deletethebidconfirmationpages" id="id-1.14.x-bidproposals-rfpbundle-deletethebidconfirmationpages"></a>

Users cannot delete a proposal.

Users can either stop the proposal process, in which case no proposal is made; or users can cancel proposals from their dashboard.

The process is described in the article: [Bids dashboard (RFP rendering type) - Delete a Bid](https://features.scnd.com/pages/8FdMu5oRAoxmaBkUDNQp#id-1.14.x-bidsdashboard-rfpbundle-deleteabid)

## Related resources <a href="#id-1.14.x-bidproposals-rfpbundle-relatedresources" id="id-1.14.x-bidproposals-rfpbundle-relatedresources"></a>

**Dashboard:**

* [Bids dashboard (RFP rendering type) - Delete a Bid](https://features.scnd.com/pages/8FdMu5oRAoxmaBkUDNQp#id-1.14.x-bidsdashboard-rfpbundle-deleteabid)

**Business rules:**

* [Request for proposal rendering type (RFP) - Business rules](https://features.scnd.com/v2.0/core-concepts/request-for-proposal-bundle-rfp.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://features.scnd.com/v2.0/front-office/rendering-types/uncommoditized-rendering-types/request-for-proposal-rfp/bid-proposals-rfp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
