> ## 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.

# Prepare buyer questions

> Draft clear clarification questions for the buyer before the questions deadline, with page references to the tender documents.

Most tenders let bidders ask clarification questions up to a set date. Good questions remove risk from your bid and can shape the competition. Reyda proposes questions from the tender documents and Emma helps you sharpen them. You decide what to ask and submit the questions through the buyer's channel.

## Who it's for

Bid managers reviewing a tender with unclear scope, conflicting dates, or requirements that would rule you out if read literally.

## Before you start

* The tender is in **Pipeline**. See [Go/no-go a tender quickly](https://reyda.mintlify.site/use-cases/qualify-a-tender.md).
* The tender documents are available. On the opportunity's **Documents** tab, click **Fetch documents** if needed. Question generation is disabled for notices without documents.
* Check the deadline. The Pipeline item's **Key dates** shows the **Bidder questions end date** when the buyer published one.

## Steps

**1. Open the tender in **Pipeline****

Under **Proposed buyer questions**, click **Generate**. Reyda reads the documents and proposes questions, each with its source and page number.

**2. Check each question against its source**

Remove questions whose answer is already in the documents, and questions that reveal your strategy to competitors. Clarification answers are usually published to all bidders.

**3. Ask Emma to look for issues the first pass may have missed**

Ask Emma

Review the tender documents for contradictions, unclear evaluation criteria, missing
information we need to price, and requirements that could exclude a company our size. Suggest a
clarification question for each, citing the page.

**4. Ask Emma to tighten the final list**

Ask Emma

Rewrite these questions so each asks one thing, quotes the exact clause, and can be answered in
a sentence. Keep a neutral tone and do not mention our company or solution.

**5. Agree the final list with your team**

If the tender is already in a Bid Room, post the list as a comment and mention colleagues with **@** to review.

**6. Submit the questions before the deadline**

Submit the questions yourself through the buyer's portal or the channel the notice specifies, before the deadline.

**7. Ask Emma what the answers change**

When the buyer publishes answers, upload the clarification document to the Bid Room and ask Emma what changed.

Ask Emma

Read the buyer's clarification responses and tell me what changes for our bid: requirements,
deadlines, pricing, or evaluation. Update the response plan if anything affects our
deliverables.

## What Emma does and what you decide

**Emma:** reads the documents, proposes questions with page references, rewrites them for clarity, and later explains how the buyer's answers affect your bid.

**You:** choose which questions to ask, check they do not give away your approach, and submit them to the buyer. Emma only emails a buyer once you approve the message, unless an admin has let her send on her own.

## Tips

> [!TIP]
>
> **Ask early.** Buyers often answer questions in batches, and late questions may go unanswered. Generate questions
> as soon as the tender is in Pipeline, even if you have not decided to bid.

* Add the questions deadline to your calendar with **Add to calendar** in **Key dates**.
* If no questions are found, Reyda says so. That is a useful signal that the documents are clear, but still read the evaluation criteria yourself.
* Question generation is AI work and uses credits.

## Related

* [Proposed buyer questions](https://reyda.mintlify.site/pipeline/buyer-questions.md)
* [Pipeline overview](https://reyda.mintlify.site/pipeline/pipeline-overview.md)
* [Requirements](https://reyda.mintlify.site/bid-room/requirements.md)
* [Glossary](https://reyda.mintlify.site/getting-started/glossary.md)


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