Skip to main content
The Final package collects the exact accepted files for a bid, checks them and packages them for download. You then upload the package to the buyer’s portal yourself. Reyda and Emma never submit a bid for you.

How it fits together

Emma turns the buyer’s requirements into a response plan listing every deliverable. You and Emma produce each one in the Bid Room. Reyda then assembles the accepted versions into the buyer’s documents, verifies them and packages them for you to Download package. Each build uses exact file versions. If anything changes later, such as a buyer addendum or a new draft, prepare a new assembly and build.

Before you start

  • You need edit or export access to the Bid Room. The Final package bar appears at the top of the Documents tab only for people who can edit or export.
  • Generating a response plan and building a package use AI and require an active plan. See Plans and credits.
  • The response plan must be accepted before you can compile the package.

Compile and download the package

1

Open the Bid Room and go to the Documents tab

The Final package bar shows its status: Not ready to compile, Ready to compile, or Verified with the number of files.
2

Click Review package

3

Check readiness

The panel shows Ready to build or Blocked before build, how many deliverables are ready (for example “6/8 deliverables ready”), and a list of blockers. Resolve the blockers first. Ask Emma for help with any of them.
4

Under Prepare submission assembly, click Prepare assembly

Reyda fills and places each accepted deliverable, then verifies every change. Wait for Assembly ready.
5

Under Compile pinned submission, click Start build

Wait until the build shows Verified.
6

Review and download the package

Review the Verified package files, then click Download package.
7

Upload the files to the buyer's portal before the deadline

Waived deliverables and handoffs

Not every line in a response plan becomes a file.
  • Waived or not applicable. You can record a deliverable as waived or not applicable, always with a reason.
  • Handoffs. Steps that need a person, such as a wet signature or a portal action, are recorded as handoffs. A person marks each one complete, and Reyda records who did it and when.

When something goes wrong

  • Assembly blocked or Assembly failed: a deliverable could not be placed or verified. Read the message, fix the deliverable, and click Try again.
  • A build that ends Blocked or Failed: read the cause shown, then use Retry same snapshot to repeat the build with the same accepted files.
  • The panel says “Accept the response plan before compiling the final package.”: the plan has not been accepted yet. If you can’t accept it, email support@reyda.ai.
Check the files, not just the status. A verified build means Reyda checked structure, placement and content against the plan. It does not replace a final read by your team. Open each file before you upload it.

Ask Emma

Ask Emma

Ask Emma

Requirements

Documents and editor

Respond to a tender end to end

Trust and limits

Last modified on October 28, 2026