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

# Respond to a tender end to end

> Take a tender from notice to a downloadable submission package, with Emma organizing the work and drafting the documents.

This recipe follows one tender from the notice to the files you upload to the buyer's portal. Emma plans the work, extracts requirements, and drafts documents. You make the commercial decisions, review the drafts, and submit.

## Who it's for

Small bid teams, often one or two people, who run the whole response themselves. You have decided to bid and want Emma to carry as much of the groundwork as possible.

## Before you start

* You have qualified the tender. See [Go/no-go a tender quickly](https://reyda.mintlify.site/use-cases/qualify-a-tender.md).
* Your [Library](https://reyda.mintlify.site/knowledge/library.md) holds your policies, CVs, case studies, and certificates. Emma drafts from evidence, not from memory.
* You are an Owner, Admin, or Editor.

## Steps

**1. Create the response**

In **Pipeline**, open the tender and click **Create response**. Confirm in the **Create a bid-room response?** dialog. Reyda opens a Bid Room and moves the item to **Pursue**. If the tender is not on Reyda, go to **Bid Room** and create one from the buyer's files instead. See [Create a Bid Room](https://reyda.mintlify.site/bid-room/create-a-bid-room.md).

**2. Check the **Requirements** tab**

Reyda extracts requirements from the buyer documents automatically, grouped into areas such as critical requirements, evidence and declarations, and contract terms. Each one shows its source page or sheet.

**3. Set the end date and assignees**

On the **Overview** tab, set the **End date** to the submission deadline and add **Assignees**.

**4. Ask Emma to plan the response**

**Plan** mode makes her propose the plan first and wait for your approval.

Ask Emma

Plan our response to this tender. Map every deliverable the buyer requires, who should own each
one, what evidence we have in the library, and where the gaps are. Then start the work that
does not need a decision from us.

**5. Answer Emma's questions**

When she needs a decision, such as pricing approach or which case study to use, a **Needs input** card appears in chat and in the Bid Room activity. Pick an option or type your own answer, then click **Continue**.

**6. Review drafts in the **Documents** tab**

Open each file in the document workbench. In working documents, Emma's edits appear as changes you **Accept** or **Reject**. Use **Version history** and **Compare** to see exactly what changed.

**7. Ask for specific improvements rather than a full rewrite**

Ask Emma

Strengthen the social value answer using our community projects from the library. Keep the
structure, stay under the word limit, and show me which claims still need evidence.

**8. Ask Emma for a compliance check**

Ask Emma

Run a compliance check against the extracted requirements. List anything missing, partially
met, or needing a signature from us.

**9. Assemble and download the package**

Assemble the final package in the **Documents** tab using the **Final package** panel, then click **Download package**. Upload the files to the buyer's portal yourself and record the result by setting the Bid Room status to **Submitted**.

## What Emma does and what you decide

**Emma:** creates the work plan, reads the tender and your library, drafts documents, fills supported forms, cites her sources, keeps working on independent tasks while a question waits for you, and reports what is done and what is not.

**You:** approve the plan, set the price, choose between commercial options, review every buyer-facing document, sign declarations, and submit. Emma does not submit bids, sign on your behalf, or decide pricing.

## Tips

> [!TIP]
>
> **Keep gaps out of the buyer's documents.** Emma puts caveats and missing evidence in her report to you, not in the response itself. Read her
> final message carefully. A saved document is not the same as a finished one.

* Start early. Requirements extraction and document drafting take time, and you will want a review cycle.
* Ask Emma what she still needs from you at any point: "What is blocking submission?"
* Check citations marked **Needs review**. They mean the cited text changed after Emma used it.

## Related

* [Work overview](https://reyda.mintlify.site/bid-room/work-overview.md)
* [Requirements](https://reyda.mintlify.site/bid-room/requirements.md)
* [Documents and editor](https://reyda.mintlify.site/bid-room/documents-and-editor.md)
* [Questions and approvals](https://reyda.mintlify.site/emma/questions-and-approvals.md)
* [Answer quality questions](https://reyda.mintlify.site/use-cases/answer-quality-questions.md)
* [Fill buyer forms](https://reyda.mintlify.site/use-cases/fill-buyer-forms.md)


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