---
title: "Plan output documents and the response structure"
description: "List the documents the bid must deliver, give each one a response structure of sections, assign owners and due dates, and link every RFP requirement to the section that answers it."
url: https://helpcenter.complytrain.net/en/articles/183-plan-output-documents-and-the-response-structure
collection: "Writing the response"
updated: 2026-09-22
language: en
---

# Plan output documents and the response structure

List the documents the bid must deliver, give each one a response structure of sections, assign owners and due dates, and link every RFP requirement to the section that answers it.

List the documents the bid must deliver, give each one a response structure of sections, assign owners and due dates, and link every RFP requirement to the section that answers it.

An output document is a deliverable the tender asks you to produce, such as a technical proposal, a pricing schedule or a signed declaration. Each output document has a response document, made of sections, that your team writes. Linking each RFP requirement to the section that answers it is what lets ComplyTrain show which requirements your response covers.

## Who can do what

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open the tender in Tenders and choose the Output documents 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>Who</p></th></tr><tr><td colspan="1" rowspan="1"><p>See output documents, their sections and requirement links</p></td><td colspan="1" rowspan="1"><p>Team members with <strong>View Tenders</strong> (<code>tender:view</code>); they can open response documents read-only</p></td></tr><tr><td colspan="1" rowspan="1"><p>Add, edit and delete output documents; generate structures; add, edit and delete sections; link and unlink requirements; set a document's owner and due date</p></td><td colspan="1" rowspan="1"><p>Team members with <strong>Create &amp; Work on Tenders</strong> (<code>tender:manage-workspaces</code>)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Assign an owner and due date to a single section</p></td><td colspan="1" rowspan="1"><p>Team members with <strong>Manage Tender Team</strong> (<code>tender:manage-team</code>); see <a target="_blank" rel="noopener noreferrer nofollow" class="linktype-link link" data-linktype="link" href="https://help.complytrain.net/en/tender/write-review-sections/">section progress</a></p></td></tr></tbody></table>

Administrators can do all of these on every tender. Everyone else works only on tenders whose team they belong to. Buttons you cannot use are not shown.

## Add output documents

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open the tender in Tenders and choose the Output documents tab.

Open the tender and choose the **Output documents** tab.

1.  Enter the deliverable's name in **Expected document title…**.
    
2.  Choose its category.
    
3.  Choose **Add**.
    

A new output document starts as **Not started**, required, and included in the submission. Output documents also arrive from [RFP analysis](https://help.complytrain.net/en/tender/rfp-analysis-assessments/) and from the Tender Assistant, usually with a description taken from the RFP.

<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>Category</p></th><th colspan="1" rowspan="1"><p>Use it for</p></th><th colspan="1" rowspan="1"><p>Default structure</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Proposal</strong></p></td><td colspan="1" rowspan="1"><p>The main written response</p></td><td colspan="1" rowspan="1"><p>Full proposal outline</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Technical</strong></p></td><td colspan="1" rowspan="1"><p>Technical approach, method statements</p></td><td colspan="1" rowspan="1"><p>Full proposal outline</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Compliance matrix</strong></p></td><td colspan="1" rowspan="1"><p>A requirement-by-requirement compliance table</p></td><td colspan="1" rowspan="1"><p>Compliance sections only</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Pricing</strong></p></td><td colspan="1" rowspan="1"><p>Price schedules and commercial offers</p></td><td colspan="1" rowspan="1"><p>Pricing-first outline</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>CV</strong></p></td><td colspan="1" rowspan="1"><p>Key personnel CVs</p></td><td colspan="1" rowspan="1"><p>Full proposal outline</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Certification</strong></p></td><td colspan="1" rowspan="1"><p>Certificates and accreditations you must supply</p></td><td colspan="1" rowspan="1"><p>Full proposal outline</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Letter</strong></p></td><td colspan="1" rowspan="1"><p>Cover letters, declarations, letters of intent</p></td><td colspan="1" rowspan="1"><p>Full proposal outline</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Other</strong></p></td><td colspan="1" rowspan="1"><p>Anything else (the default)</p></td><td colspan="1" rowspan="1"><p>Full proposal outline</p></td></tr></tbody></table>

The default structure is what **Generate structure** creates; see below.

## Output document details

Product location: `/tender/workspaces/{workspaceId}/documents/{documentId}/sections` (fallback: `/tender/workspaces`). Open the tender's Output documents tab and select the output document.

Open the output document from the **Output documents** tab to see and edit its details.

<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>Detail</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>Title</p></td><td colspan="1" rowspan="1"><p>The deliverable's name, shown everywhere the document appears</p></td><td colspan="1" rowspan="1"><p>Required, up to 500 characters</p></td></tr><tr><td colspan="1" rowspan="1"><p>Category</p></td><td colspan="1" rowspan="1"><p>The kind of deliverable; decides the default structure</p></td><td colspan="1" rowspan="1"><p>Default <strong>Other</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>Status</p></td><td colspan="1" rowspan="1"><p><strong>Not started</strong>, <strong>Drafting</strong>, <strong>In review</strong>, <strong>Final</strong> or <strong>Submitted</strong></p></td><td colspan="1" rowspan="1"><p>Any status can be chosen; <strong>Publish</strong> sets <strong>Final</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p>Required</p></td><td colspan="1" rowspan="1"><p>Whether the tender demands this deliverable</p></td><td colspan="1" rowspan="1"><p>On by default. A required document included in the submission must be <strong>Final</strong> or <strong>Submitted</strong> before the readiness check passes</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Submission</strong> or <strong>Internal</strong></p></td><td colspan="1" rowspan="1"><p>Whether the document goes into the submission package or is an internal working document</p></td><td colspan="1" rowspan="1"><p><strong>Submission</strong> by default. Select the pill on the row to switch</p></td></tr><tr><td colspan="1" rowspan="1"><p>Code</p></td><td colspan="1" rowspan="1"><p>The issuer's reference for the deliverable, such as "Annex C"</p></td><td colspan="1" rowspan="1"><p>Optional, up to 100 characters</p></td></tr><tr><td colspan="1" rowspan="1"><p>Description</p></td><td colspan="1" rowspan="1"><p>What the document is for, what it must contain and the RFP's constraints, such as page limits</p></td><td colspan="1" rowspan="1"><p>Optional, up to 20,000 characters. Shown to authors as <strong>About this document</strong> and given to the AI when it drafts</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Owner</strong></p></td><td colspan="1" rowspan="1"><p>The person responsible for producing it</p></td><td colspan="1" rowspan="1"><p>Optional; choose from the people who use Tenders, typing to search</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Due date</strong></p></td><td colspan="1" rowspan="1"><p>Your internal target date</p></td><td colspan="1" rowspan="1"><p>Optional. Independent of the tender's submission deadline</p></td></tr><tr><td colspan="1" rowspan="1"><p>Produced document</p></td><td colspan="1" rowspan="1"><p>The finished file in the tender's vault</p></td><td colspan="1" rowspan="1"><p>Set automatically when you publish the response; you can also link an existing vault document</p></td></tr></tbody></table>

Set the owner and due date in the **Owner & deadline** panel, then choose **Save owner & deadline**. The owner and due date appear on the board card.

## Track output documents

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open the tender in Tenders and choose the Output documents tab.

The **Output documents** tab has two views; switch with **Table** and **Board**.

-   **Table** lists each document with its category and a status list that saves as soon as you change it. Filter the table with **All**, **Submission** and **Internal**.
    
-   **Board** shows a column for each status. Drag a card to another column to change its status. Each card shows the category, the **Submission** or **Internal** pill, the due date as **Due** and a date, and the owner or **Unassigned**. Choose **View** to open the document.
    

## Open the response document

Product location: `/tender/workspaces/{workspaceId}/documents/{documentId}/sections` (fallback: `/tender/workspaces`). Open the tender's Output documents tab and select the output document.

Select a row in the table, or **View** on a card, to open the **Document Sections** page. The response document is created the first time a team member who works on the tender opens it.

The page shows:

-   The document's name, status, code, category, language and dates, and **Completeness**, the share of sections with content.
    
-   **Back to workspace**, **Open editor** and **Add section**.
    
-   An actions panel with **Write with AI**, **Generate structure**, **Validate**, **Publish**, **Promote to library** and **Delete**.
    
-   The **Owner & deadline** panel.
    
-   **About this document**, when the output document has a description.
    
-   Two tabs: **Sections**, with the section progress, coverage and section tree, and **AI history**.
    

Writing, review, publishing and the AI history are covered in [writing and reviewing sections](https://help.complytrain.net/en/tender/write-review-sections/). **Validate** is covered in [compliance and coverage](https://help.complytrain.net/en/tender/compliance-matrix/).

## Generate a structure

Product location: `/tender/workspaces/{workspaceId}/documents/{documentId}/sections` (fallback: `/tender/workspaces`). Open the output document from the Output documents tab and choose Generate structure.

**Generate structure** gives the response document a ready-made outline in one step.

<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>Category</p></th><th colspan="1" rowspan="1"><p>Sections created</p></th></tr><tr><td colspan="1" rowspan="1"><p>All except Pricing and Compliance matrix</p></td><td colspan="1" rowspan="1"><p>Executive Summary; Company &amp; Experience; Technical Approach; Compliance &amp; Requirements; Pricing; Assumptions &amp; Dependencies (optional)</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Pricing</strong></p></td><td colspan="1" rowspan="1"><p>Pricing; Assumptions &amp; Dependencies (optional); Compliance &amp; Requirements</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Compliance matrix</strong></p></td><td colspan="1" rowspan="1"><p>Compliance &amp; Requirements; Assumptions &amp; Dependencies (optional)</p></td></tr></tbody></table>

Each section comes with a purpose that tells the author what it should cover. **Compliance & Requirements** gets one child section for every requirement recorded on the tender, named after the requirement and already linked to it.

A generated section is empty. It does not count towards coverage until it has content, so generating a structure never makes a requirement look answered.

If the document already has sections, **Replace existing structure?** asks you to confirm. Choose **Regenerate** to replace them; their content is lost. Choose **Cancel** to keep them. Add requirements before generating so each one gets its child section; requirements added later need linking by hand.

## Add and edit sections

Product location: `/tender/workspaces/{workspaceId}/documents/{documentId}/sections` (fallback: `/tender/workspaces`). Open the output document from the Output documents tab and choose Add section.

Choose **Add section** in the page header, or **Add the first section** on an empty document. To add a section inside another, use the add-child action on the parent in the section tree.

<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><strong>Name</strong></p></td><td colspan="1" rowspan="1"><p>The section heading</p></td><td colspan="1" rowspan="1"><p>Required, for example "Executive Summary"</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Code</strong></p></td><td colspan="1" rowspan="1"><p>A short reference shown in the outline</p></td><td colspan="1" rowspan="1"><p><strong>Auto-generated if blank</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Type</strong></p></td><td colspan="1" rowspan="1"><p><strong>Text</strong>, <strong>List</strong>, <strong>Numbered list</strong>, <strong>Table</strong> or <strong>Diagram</strong></p></td><td colspan="1" rowspan="1"><p>Default <strong>Text</strong>. A diagram section opens in the diagram editor</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Purpose</strong></p></td><td colspan="1" rowspan="1"><p>What this section should cover; shown to the author and given to the AI</p></td><td colspan="1" rowspan="1"><p>Optional</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Optional section</strong></p></td><td colspan="1" rowspan="1"><p>Marks a section the response can leave out</p></td><td colspan="1" rowspan="1"><p>Off by default</p></td></tr></tbody></table>

Choose **Save**. To change a section, use its edit action in the tree; the dialog opens with every field filled in. To remove one, use its delete action and confirm **Delete section**. Deleting a section deletes its content and its requirement links.

To write the content, use the edit-content action on the section, or **Open editor**.

## Link requirements to sections

Product location: `/tender/workspaces/{workspaceId}/documents/{documentId}/sections` (fallback: `/tender/workspaces`). Open the output document from the Output documents tab and use Link requirement under Section progress.

A link records that a section answers a requirement. You can link one requirement to several sections, and one section to several requirements.

1.  On the **Sections** tab, find the section under **Section progress** and choose **Link requirement**.
    
2.  **Link a requirement to** the section opens. Type in **Search requirements…** to narrow the list.
    
3.  Each candidate shows a short code taken from the start of the requirement's text, its type, and either **Not yet addressed** or **Already in N section(s)**.
    
4.  Choose **Link**.
    

Linked requirements appear as chips under the section's name. Select the cross on a chip to unlink it. In the section tree, select a requirement chip to open **RFP requirement**, which shows the full text and **Mapped to section**; choose **Unmap from section** to remove the link.

**No requirements to link** means every requirement is already linked to this section, or the tender has no requirements yet.

## How coverage is counted

Product location: `/tender/workspaces/{workspaceId}/documents/{documentId}/sections` (fallback: `/tender/workspaces`). Open the output document from the Output documents tab and read RFP requirement coverage on the Sections tab.

ComplyTrain uses one rule everywhere: a requirement is addressed when at least one section with content is linked to it, or when an existing document is attached to it. An empty section linked to a requirement does not count.

The same rule drives:

-   **RFP requirement coverage** on this page: the number addressed out of the total, how many of them this document addresses, and a list under **Not yet addressed by any section:**, or **Every RFP requirement is addressed by at least one section.**
    
-   The **Covered** column and summary on the **Compliance matrix** tab.
    
-   **Requirement coverage** on the **Submission** tab and the readiness check before you submit.
    

Attaching an existing document, such as a certificate, is done on the **Compliance matrix** tab; see [compliance and coverage](https://help.complytrain.net/en/tender/compliance-matrix/). A link records where the response addresses a requirement. It does not prove you can meet it; record that with the requirement's disposition on the [Requirements tab](https://help.complytrain.net/en/tender/requirements/).

## Delete an output document

Product location: `/tender/workspaces/{workspaceId}/documents/{documentId}/sections` (fallback: `/tender/workspaces`). Open the output document from the Output documents tab and choose Delete.

Choose **Delete** in the actions panel. **Delete this document?** warns that this permanently removes the output document and its response. Choose **Delete** to confirm.

The response document, its sections and their requirement links are removed, and coverage is recalculated. Any requirement that was addressed only by those sections shows as not addressed again. A file already published to the tender's vault stays in the vault.

## Example: plan a technical proposal

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open the tender in Tenders and choose the Output documents tab.

The RFP for a regional hospital's patient-transport contract asks for a technical proposal, a price schedule and a signed form of tender. RFP analysis has added 18 requirements.

1.  On **Output documents**, the bid manager adds "Form of Tender" as a **Letter** and keeps "Technical Proposal" (**Technical**) and "Price Schedule" (**Pricing**) from the analysis. They add "Bid strategy notes" as **Other** and switch its pill to **Internal**, so it never goes into the package.
    
2.  They open "Technical Proposal", set the code "Schedule 2" and the description "Maximum 30 pages; must follow the evaluation criteria order", choose the operations lead as **Owner** with a due date a week before submission, and choose **Save owner & deadline**.
    
3.  **Generate structure** creates the six-section outline, with 18 requirement sections under **Compliance & Requirements**.
    
4.  Two requirements about vehicle cleaning also belong in **Technical Approach**, so the bid manager uses **Link requirement** on that section to link them there too.
    
5.  **RFP requirement coverage** shows 0 of 18 addressed, because nothing is written yet. As authors fill the sections, the count rises.
