---
title: "Validate, package and submit a tender"
description: "Record the bid decision, check readiness, produce the response documents as Word or PDF, assemble the submission package and mark the tender submitted."
url: https://helpcenter.complytrain.net/en/articles/184-validate-package-and-submit-a-tender
collection: "Submission and learning"
updated: 2026-09-22
language: en
---

# Validate, package and submit a tender

Record the bid decision, check readiness, produce the response documents as Word or PDF, assemble the submission package and mark the tender submitted.

Record the bid decision, check readiness, produce the response documents as Word or PDF, assemble the submission package and mark the tender submitted.

The **Submission** tab brings together everything a tender needs before it goes to the issuer: a readiness check, requirement coverage, the documents that make up the package, the formality checklist and **Submit tender**. Submitting in ComplyTrain records that the bid has gone. It does not send anything to the issuing organisation.

## Who can do what

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open the tender in Tenders, then the Submission tab.

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Task</p></th><th colspan="1" rowspan="1"><p>Permission</p></th></tr><tr><td colspan="1" rowspan="1"><p>Read the readiness panel, requirement coverage, package list and formality checklist</p></td><td colspan="1" rowspan="1"><p><strong>View Tenders</strong> (<code>tender:view</code>)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Move documents between submission and internal, change document and formality statuses, map requirements to sections</p></td><td colspan="1" rowspan="1"><p><strong>Create &amp; Work on Tenders</strong> (<code>tender:manage-workspaces</code>)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Record the bid decision, choose the approval workflow, publish a response document, choose the packaging mode, generate the package and submit</p></td><td colspan="1" rowspan="1"><p><strong>Submit Tenders</strong> (<code>tender:submit</code>)</p></td></tr></tbody></table>

You also need to be on the tender's team. Admins can work on every tender. Buttons you cannot use are not shown to you. See [team and details](https://help.complytrain.net/en/tender/team-and-details/) for team membership and [roles and permissions](https://help.complytrain.net/en/settings/role-permission-review/) for granting these permissions.

## Record the bid decision

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open the tender in Tenders, then the Submission tab.

Record whether you will bid before the team invests in writing.

1.  Open the tender. **Overview** opens first.
    
2.  In **Bid decision**, choose **Edit decision**.
    
3.  Choose **Bid**, **No bid** or **Undecided**.
    
4.  Explain the reasoning: how well you can meet the requirements (the dispositions on the **Requirements** tab), win probability, strategic fit and resourcing.
    
5.  Choose **Save**.
    

<table style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Field</p></th><th colspan="1" rowspan="1"><p>What it does</p></th><th colspan="1" rowspan="1"><p>Limits and defaults</p></th></tr><tr><td colspan="1" rowspan="1"><p>Decision</p></td><td colspan="1" rowspan="1"><p>Records the commitment to pursue or decline the tender.</p></td><td colspan="1" rowspan="1"><p><strong>Undecided</strong> until someone decides. Choosing <strong>Undecided</strong> again clears the reasoning, the date and who decided.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Reasoning</p></td><td colspan="1" rowspan="1"><p>Explains the decision for the team and for later review.</p></td><td colspan="1" rowspan="1"><p>Up to 20,000 characters. When a decision has no reasoning, the card shows <strong>No reasoning recorded.</strong></p></td></tr></tbody></table>

The card then shows the decision, when it was made and who made it. The decision does not change the tender's status. A **No bid** tender stays **Draft** or **Active** until someone withdraws or archives it.

## Choose the approval workflow

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open the tender in Tenders, then the Submission tab.

**Approval workflow** on **Overview** decides how documents in the tender's Document Vault are reviewed before they are published.

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Option</p></th><th colspan="1" rowspan="1"><p>Effect</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>No approval</strong></p></td><td colspan="1" rowspan="1"><p>The default. Documents go straight from draft to published, with no approval step.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Review &amp; approval</strong></p></td><td colspan="1" rowspan="1"><p>Documents move from Draft to In Review to Approved. Approving needs a comment, and returning a document for changes needs a reason. Your administrator decides which groups may approve in the vault's workflow settings.</p></td></tr></tbody></table>

The choice applies to documents added after the change. Documents already in progress keep their current state. See [document workflows](https://help.complytrain.net/en/document-vault/workflows-actions/) for how workflows and approvers are configured.

## Check readiness

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open the tender in Tenders, then the Submission tab.

Open **Submission**. When nothing blocks submission, the panel at the top reads **Ready to submit — all required outputs are final and formality requirements are satisfied.** Otherwise it reads **Not ready to submit yet:** and lists each blocker, naming the document, formality or requirement and its current status, for example **Drafting** or **In progress**.

<table style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Blocker</p></th><th colspan="1" rowspan="1"><p>When it appears</p></th><th colspan="1" rowspan="1"><p>How to clear it</p></th></tr><tr><td colspan="1" rowspan="1"><p>Required output not final</p></td><td colspan="1" rowspan="1"><p>An output document that is marked required and included in the submission has a status other than <strong>Final</strong> or <strong>Submitted</strong>.</p></td><td colspan="1" rowspan="1"><p>Publish the document, which sets it to <strong>Final</strong>. You can also clear its required flag or move it to <strong>Internal</strong> if it is not part of the bid.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Formality not satisfied</p></td><td colspan="1" rowspan="1"><p>A formality has a status other than <strong>Satisfied</strong> or <strong>Not applicable</strong>.</p></td><td colspan="1" rowspan="1"><p>Complete it and update its status on the <strong>Formality</strong> tab.</p></td></tr><tr><td colspan="1" rowspan="1"><p>Requirement not addressed</p></td><td colspan="1" rowspan="1"><p>A requirement with the disposition <strong>Can meet</strong> or <strong>Partial</strong> is not covered. A requirement is covered when it is mapped to a response section that has content, or when an existing document is attached to it on the <strong>Compliance matrix</strong> tab.</p></td><td colspan="1" rowspan="1"><p>Write the mapped section, map another section, attach a document, or correct the disposition.</p></td></tr></tbody></table>

Requirements with the status **Not applicable**, and requirements with the disposition **Cannot meet** or **Undecided**, never block submission. A ready panel therefore does not mean every requirement has a positive answer. Review those requirements on the [compliance matrix](https://help.complytrain.net/en/tender/compliance-matrix/) before you submit.

Below the panel you find:

-   **Requirement coverage**: how many requirements are covered, and the uncovered ones by name, whatever their disposition.
    
-   **Submission package**: each document included in the submission, with a **Required** badge where it applies, its status, and **Produced** once a published file is linked to it, or **Not produced**.
    
-   **Formality checklist**: each formality with its type and status. **Satisfied** and **Not applicable** show green.
    

## Decide what goes in the package

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open the tender in Tenders, then the Submission tab.

On **Output documents**, every document carries a pill that reads **Submission** or **Internal**. Click the pill to move a document between the submission package and internal-only work. Internal documents, such as a pricing calculation or a win strategy, never appear in the package or in the readiness check.

New output documents are marked required. When you edit a document on **Output documents**, clear the required flag for anything the issuer treats as optional. Only required documents block submission while they are not final. Documents appear in the package in the order they are listed on **Output documents**.

## Produce each document

Product location: `/tender/workspaces/{workspaceId}/documents/{documentId}/sections` (fallback: `/tender/workspaces`). Open the tender, go to Output documents and open the document.

A document counts as **Produced** once you publish its response.

1.  On **Output documents**, open the document. The **Document Sections** page opens.
    
2.  Choose **Publish**.
    
3.  Choose Word or PDF, and confirm.
    

ComplyTrain renders the current text of every section, files the result in the tender's Document Vault under the document's name, sets the output document to **Final**, and links the file to it. The published file is shown when publishing finishes. Publishing again files a new document and links the newest one. **Publish** in the document editor's header does the same.

Publishing uses the text as it stands, whether or not each section has been approved. Editing an approved section sends it back to **In review**, so finish the edits and the reviews before you publish. See [write, review and approve sections](https://help.complytrain.net/en/tender/write-review-sections/).

## Generate the submission package

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open the tender in Tenders, then the Submission tab.

1.  Open **Submission** and go to **Generate submission package**.
    
2.  In **Packaging mode**, choose **Single merged PDF** or **ZIP of individual files**. The choice is saved on the tender and used for every package you generate, unless you choose a different mode for one package when you generate it.
    
3.  Choose **Generate submission package**. The button reads **Assembling…** while ComplyTrain works.
    
4.  Read the result: **Submission package ready**, the page-limit line, any warnings under **Review before submitting**, and the list of documents with their page counts.
    
5.  Choose **Download package** and check the file before you send it.
    

<table style="min-width: 50px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Mode</p></th><th colspan="1" rowspan="1"><p>What you get</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Single merged PDF</strong></p></td><td colspan="1" rowspan="1"><p>One PDF. It starts with a cover page headed "Submission package" that shows the tender name, issuing organisation, reference number, submission deadline, the date it was generated, a numbered contents list with each document's category and page count, and a "Not included" list naming any skipped document and why. Every included document follows the cover page.</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>ZIP of individual files</strong></p></td><td colspan="1" rowspan="1"><p>A ZIP with each included document as its own PDF, numbered in package order, plus a <code>manifest.txt</code> listing the contents and anything not included.</p></td></tr></tbody></table>

Each document is built from the current text of its response sections. A document is skipped, with its reason shown in the list and under **Review before submitting**, when no response has been started for it or its response has no sections. If no document is included in the submission, or none of the included documents has a response to package, no package is built and ComplyTrain tells you why.

Every package is filed in the tender's Document Vault as a new document named "Submission Package — " followed by the tender name. Earlier packages stay in the vault. The result panel shows the package from your current visit only; to find earlier ones, open the vault from the **Documents** tab.

### Page limit

When the tender has a formality of the type **Page limit**, ComplyTrain takes the first number in its name or description as the limit, for example "Maximum 40 pages". It adds up the written pages of the included documents, without the cover page. **Page limit exceeded** warns you when the total is over the limit. Otherwise a line confirms that the package is within the limit. The page limit never blocks generation or submission.

## Submit the tender

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open the tender in Tenders, then the Submission tab.

Only an **Active** tender can be submitted. For any other status the card reads **Only an active tender can be submitted.**

1.  Open **Submission**.
    
2.  Clear the blockers you can. If blockers remain and you still need to submit, enter the reason in **Override reason (required to submit with unmet blockers)**.
    
3.  Choose **Submit tender**. While blockers remain, the button reads **Submit anyway (override)** and cannot be used without a reason.
    

The tender's status becomes **Submitted**. ComplyTrain records who submitted it and, for an override, that the readiness check was overridden and the reason given. **Submit tender** is the only way to reach **Submitted**; **Change status…** does not offer it.

From now on the response, requirements and documents are read-only, so what you submitted stays on record. You can still record the outcome, write the debrief and track clarifications on the **Q&A** tab.

Submitting sends nothing to the issuer. Deliver the package through the issuer's required channel, such as its procurement portal, and file the receipt in the tender's Document Vault. If someone changes the tender while you submit, reload the page and submit again.

After submission the tender counts under **Submitted** on the Tenders dashboard. When the issuer announces the result, someone with **Submit Tenders** records **Won**, **Lost** or **Withdrawn** with the tender's outcome action; see [record the outcome](https://help.complytrain.net/en/tender/record-outcome/).

## Example: submit with an override

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open the tender in Tenders, then the Submission tab.

A managed-services framework tender limits the response to 40 pages and requires a signed declaration of honour.

1.  The bid manager publishes the technical proposal and the pricing schedule as PDF. Both show **Produced** and **Final**.
    
2.  The first ZIP package reports **Page limit exceeded**: 43 written pages against 40. The team trims the case studies, publishes again and regenerates. The new package is within the limit.
    
3.  One blocker remains: the formality "Signed declaration of honour" is **In progress**, because the chief executive signs it and uploads it directly to the issuer's portal.
    
4.  The bid manager enters the override reason "Declaration signed by the CEO on 12 March and uploaded directly to the portal; scan filed in the tender vault" and chooses **Submit anyway (override)**.
    
5.  The team uploads the package to the portal and files the portal's receipt in the tender's vault.
