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

# Documents Emma creates

> Working documents, Word, Excel, PDF and PowerPoint outputs, edits to buyer templates, versions, Instruct AI and reviewing Emma's changes.

Emma creates and edits real documents: response plans, method statements, filled buyer forms and pricing schedules. Every change she makes is saved as a new version, so you can review it, compare it and roll it back.

## What Emma can produce

| Output | Typical use |
| - | - |
| **Working document** | Response plans, outlines, notes and drafts your team edits together in the rich editor |
| **Word document** | Quality answers, method statements, letters, annexes |
| **Spreadsheet** | Pricing schedules, compliance matrices, buyer questionnaires |
| **PDF** | Filled PDF forms, reports |
| **Presentation** | Clarification meetings, internal bid reviews |

Emma can also build HTML reports and charts, for example a market overview. When she sends you a file in chat, use **Open file** to view it in Reyda or **Download** to save it.

In the Library, Emma can create Markdown documents, snippets and proposal templates, and update tags.

## Editing buyer documents

When the buyer supplies a template or form, Emma works in it rather than recreating it:

* **Buyer templates stay untouched.** Emma writes into a response copy with the same format and the buyer's original filename. The buyer's original stays as it was.
* **Structure is preserved.** She keeps headings, numbering, tables and layout, and puts each answer in the buyer's actual response field, not on a cover page or contents page.
* **Spreadsheets are handled with care.** Emma keeps formulas, number formats and validation, and never invents a value to fill a cell.
* **PDF forms are filled in place.** Some PDFs, such as encrypted or signed ones, can't be filled. Emma tells you when that happens.
* **Signatures are left for you.** Emma fills the facts she can support and leaves signatures and declarations for an authorised person.

## Versions and review

Every time Emma saves a change, the document gets a new version. Open **Version history** to:

* see each **Version** and which one is **Latest**;
* **Compare** two versions to see what changed;
* **Restore** an earlier version. This creates a new version with the old content, and later versions stay in history.

While Emma is still working on a draft, you may see a **Work in progress** preview. Use **Continue from here** to send her an instruction about that exact draft, such as "Keep this layout, but move the daily rate below the existing rows", then click **Send instruction**.

## Steer Emma's edits in the editor

In a Working document:

**1. Select the text you want changed**

**2. Choose **Instruct AI** and describe the change**

Choose **Instruct AI** and describe the change, for example "Cut to 200 words and keep the figures.".

**3. Click **Send to agent****

Emma proposes the change.

**4. Accept or reject her changes**

Step through her changes with **Previous change** and **Next change**, and **Accept** or **Reject** each one, or use **Accept all** or **Reject all**.

You can also type **/** in the editor and choose **Draft this section with AI** or **Create draft proposal with AI**.

To act on review comments, open a comment thread and choose **Address with AI**. Emma reads the quoted text and the whole discussion, then revises the content.

> [!TIP]
>
> **Instruct AI or comments?** **Instruct AI** sends an instruction to Emma only. It isn't added to the team discussion. Use a
> normal comment when colleagues should see it too.

## Review Emma's documents

* **Start with her report.** After a large drafting pass, Emma reports what she placed, what she left blank on purpose and what needs your decision. Read it before you review the document.
* **Treat every document as a draft.** Emma's documents stay drafts until your team approves them. She doesn't mark her own work final or approved.
* **Every change can be undone.** Accept or reject each proposed edit, and compare or restore any version.
* **Files leave Reyda when you send them.** You download them or approve an email. The two exceptions: in Slack, Emma attaches the documents she creates to her reply, and an admin can let her send emails without asking.

## Example

Bid Room

Update our existing technical response with answers for sections 4 to 6. Don't change sections 1
to 3. Use the Library for evidence and tell me what you left blank.

## Related

> [card] [Documents and editor](https://reyda.mintlify.site/bid-room/documents-and-editor.md)
>
> The Bid Room document workbench in detail.

> [card] [Sources and citations](https://reyda.mintlify.site/emma/sources-and-citations.md)
>
> How Emma backs up what she writes.


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