> ## Documentation Index
> Fetch the complete documentation index at: https://reyda.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Go/no-go a tender quickly

> Decide quickly whether a tender is worth bidding, using the notice, Reyda's fit assessment, and a bid/no-bid report.

Use this recipe when a promising notice lands and you need a fast, defensible bid or no-bid decision. Reyda and Emma gather the facts. You make the call.

## Who it's for

Bid managers, founders, and sales leads who see more tenders than they can bid for. You have a notice open and want to know, before you spend a day on it, whether you can win it.

## Before you start

* Your [company profile](https://reyda.mintlify.site/getting-started/company-profile.md) is filled in, including financials, certifications, and past projects. Thin profiles produce vague assessments.
* An owner or admin has set your bid criteria in **Settings → Bid criteria**. The report is scored against them. See [Bid/no-bid report](https://reyda.mintlify.site/pipeline/bid-no-bid-report.md).
* You are an Owner, Admin, or Editor. Viewers can read Pipeline but cannot change it.

## Steps

**1. Open the notice from **Opportunities****

On the **Overview** tab, read the **AI Summary**, the key deadlines and the **Relevance** box, which explains why the tender matched your profile. If the notice asks for something your profile doesn't show, such as a certificate, **Qualification notes** list it.

**2. Open the **Documents** tab**

If no files are listed, click **Fetch documents**. Emma needs the tender documents for a useful assessment.

**3. Ask Emma for a first read while the documents load**

Use **Ask** mode if you only want answers and no changes.

Ask Emma

Is this tender worth pursuing for us? Summarise what the buyer wants, the deadlines, the
minimum requirements we must meet, and anything in our profile or past projects that supports
or weakens our case.

**4. Click **Add to pipeline****

The tender appears in **Pipeline** under **Triage**, assigned to you by default.

**5. Create the bid/no-bid report**

Open the item in **Pipeline**. On the **Bid/no-bid report** card, click **Create report** and confirm. When it is ready, click **Open full report**. Check the blockers and evidence gaps against the cited pages.

**6. Generate the buyer activity report (optional)**

Generate the **Buyer activity report** to see what this buyer has bought before and from whom. It helps you judge an incumbent advantage.

**7. Ask Emma to pressure-test the recommendation**

Ask Emma

Read the bid/no-bid report for this tender. Which blockers are real, and which could we close
before the deadline? What would we need to show for each one?

**8. Decide**

To go ahead, click **Create response**. This opens a Bid Room and moves the item to **Pursue**. To walk away, set **Status** to **No bid**, add the reason and click **Mark no bid**. You can restore it later.

## What Emma does and what you decide

| Emma | You |
| - | - |
| Reads the notice, documents, profile, and past projects | Confirm the facts that matter, such as turnover thresholds |
| Generates the bid/no-bid and buyer activity reports when asked | Set the bid criteria the report is scored against |
| Flags blockers, gaps, and unknowns with citations | Decide bid or no bid. Emma always leaves this decision to you |
| Explains her reasoning | Record the reason so the team understands it |

## Tips

> [!TIP]
>
> **Mark what does not fit.** If a recommended tender is clearly wrong for you, click the thumbs-down icon (**Not relevant**) on the opportunity and
> pick a reason. It is quicker than a no-bid and helps keep your recommendations focused.

* Generate reports only for tenders you are seriously considering. Reports are AI work and use credits.
* If the report says evidence is missing, check your profile and library first. The evidence may exist but not be uploaded.
* Note the **Bidder questions end date** in **Key dates**. If something is unclear, see [Prepare buyer questions](https://reyda.mintlify.site/use-cases/prepare-buyer-questions.md).

## Related

* [Opportunity details](https://reyda.mintlify.site/opportunities/opportunity-details.md)
* [How matching works](https://reyda.mintlify.site/opportunities/how-matching-works.md)
* [Pipeline overview](https://reyda.mintlify.site/pipeline/pipeline-overview.md)
* [Bid/no-bid report](https://reyda.mintlify.site/pipeline/bid-no-bid-report.md)
* [Respond to a tender end to end](https://reyda.mintlify.site/use-cases/respond-to-a-tender-end-to-end.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.