---
title: "Check compliance and requirement coverage"
description: "Read the compliance matrix, attach documents that already answer a requirement, export the matrix or turn it into a submittable document, validate a response document and check coverage before you submit."
url: https://helpcenter.complytrain.net/en/articles/237-check-compliance-and-requirement-coverage
collection: "Writing the response"
updated: 2026-09-22
language: en
---

# Check compliance and requirement coverage

Read the compliance matrix, attach documents that already answer a requirement, export the matrix or turn it into a submittable document, validate a response document and check coverage before you submit.

Read the compliance matrix, attach documents that already answer a requirement, export the matrix or turn it into a submittable document, validate a response document and check coverage before you submit.

The compliance matrix shows every requirement of the tender against your answer to it: whether the response covers it, whether you can meet it, how far the work has got and where it is answered. Evaluators often ask for exactly this table, and it is the quickest way for your team to find what is still missing.

## Who can do what

Product location: `/tender/workspaces/{workspaceId}` (fallback: `/tender/workspaces`). Open the tender in Tenders and choose the Compliance matrix 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>Read the matrix, export it and see requirement coverage</p></td><td colspan="1" rowspan="1"><p>Team members with <strong>View Tenders</strong> (<code>tender:view</code>)</p></td></tr><tr><td colspan="1" rowspan="1"><p>Attach documents, generate the matrix document and validate a response document</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></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.

## Read the matrix

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

Open the tender and choose the **Compliance matrix** tab. A summary above the table gives the number of requirements and how many of them are covered. The table has one row per requirement:

<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>Column</p></th><th colspan="1" rowspan="1"><p>What it shows</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Requirement</strong></p></td><td colspan="1" rowspan="1"><p>The requirement's text and its type</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Covered</strong></p></td><td colspan="1" rowspan="1"><p><strong>Covered</strong> or <strong>Uncovered</strong>, calculated by ComplyTrain</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Disposition</strong></p></td><td colspan="1" rowspan="1"><p>Whether you can meet it: <strong>Undecided</strong>, <strong>Can meet</strong>, <strong>Partial</strong> or <strong>Cannot meet</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Status</strong></p></td><td colspan="1" rowspan="1"><p>The requirement's progress: <strong>Not started</strong>, <strong>In progress</strong>, <strong>Addressed</strong> or <strong>Not applicable</strong></p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Addressed by</strong></p></td><td colspan="1" rowspan="1"><p>Each section linked to the requirement, with its output document's title after a dot; any attached document with its number; and any accepted product answer; <strong>Not yet addressed</strong> when there is none of these</p></td></tr></tbody></table>

When a product answer has been accepted for a requirement on the **Products** tab, **Addressed by** lists it as a product answer, and the PDF and Word exports include it. See [bidding products](https://help.complytrain.net/en/tender/bid-products/#use-accepted-answers-in-the-response).

**No requirements yet** means the tender has no requirements. Add them on the **Requirements** tab or extract them with [RFP analysis](https://help.complytrain.net/en/tender/rfp-analysis-assessments/).

## Covered, disposition and status

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

The three columns answer different questions, and they can disagree.

-   **Covered** is calculated. A requirement is covered when at least one section with content is linked to it, or when an existing document is attached to it. An empty linked section does not count. This is the same rule used on the **Document Sections** page and the **Submission** tab.
    
-   **Disposition** is your judgement of whether you can meet the requirement. Set it, with your reasoning, on the [Requirements tab](https://help.complytrain.net/en/tender/requirements/).
    
-   **Status** is set by people on the **Requirements** tab to track the work. Marking a requirement **Addressed** does not make it covered, and a covered requirement stays **Not started** until someone changes it.
    

A row that is **Covered** with **Cannot meet** needs attention: the response says something about a requirement you have said you cannot meet. A row that is **Uncovered** with **Can meet** is a gap in the response.

To cover a requirement, link it to a section and write that section; see [linking requirements](https://help.complytrain.net/en/tender/draft-map-response/#link-requirements-to-sections). Or attach a document that already answers it, as described next.

## Attach an existing document

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

Some requirements are answered by handing over a document you already hold, such as an ISO certificate or an insurance schedule, rather than by writing text. When your organisation uses QMS, each row offers **Attach a document**.

1.  On the requirement's row, choose **Attach a document**.
    
2.  **Attach an existing document** opens and shows the requirement. Enter at least two characters of the document's name or number in **Search your documents by name or number**.
    
3.  Choose **Search**, or press Enter.
    
4.  Each result shows the document's name, number and vault. Choose the right one.
    

The document then appears under **Addressed by** with its number, and the requirement counts as covered. The search covers QMS documents and Document Vault documents that you are allowed to read. **No documents match that search.** means nothing matched; try the document number or a shorter part of the name.

A requirement holds one attached document. To replace it, choose **Change document** and pick another. **Find evidence** on the **Requirements** tab can also attach a document automatically when it finds a strong match by name; check such attachments here.

Attaching records which document answers the requirement. It does not add the document to the submission package. If the issuer must receive the certificate, add it as an output document of category **Certification** too.

## Export the matrix

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

Three exports are available once the tender has requirements. Each downloads a file to your computer; nothing is stored in ComplyTrain.

<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>Button</p></th><th colspan="1" rowspan="1"><p>File</p></th><th colspan="1" rowspan="1"><p>Contents</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Export CSV</strong></p></td><td colspan="1" rowspan="1"><p>A comma-separated file for a spreadsheet</p></td><td colspan="1" rowspan="1"><p>Columns Requirement, Type, Priority, Covered (Yes or No), Disposition, Reasoning, Status and Addressed by</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Export PDF</strong></p></td><td colspan="1" rowspan="1"><p>A PDF document</p></td><td colspan="1" rowspan="1"><p>Title "Compliance Matrix" with the tender's name, the reference number and issuing organisation, a summary line, and a numbered table with requirement, type, priority, disposition, status and what addresses it</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Export Word</strong></p></td><td colspan="1" rowspan="1"><p>A Word document you can edit</p></td><td colspan="1" rowspan="1"><p>The same as the PDF</p></td></tr></tbody></table>

The PDF and Word buttons read **Exporting…** while the file is prepared. Use the CSV to sort and filter in a spreadsheet, and the PDF or Word file for internal review meetings.

## Generate the matrix document

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

Many RFPs require a compliance matrix as part of the submission. **Generate matrix document** turns the matrix into a response document that you review, approve and publish like any other.

1.  Choose **Generate matrix document**. The button reads **Generating…**.
    
2.  ComplyTrain creates an output document called "Compliance Matrix", of category **Compliance matrix**, required and included in the submission, with a description of what the matrix is for. If the tender already has a compliance-matrix output document, that one is used.
    
3.  Its response document gets one section, "Compliance Matrix", holding a table with the columns Requirement, Comply, Addressed by and Notes.
    

The Comply column is taken from the disposition: **Can meet** becomes Yes, **Partial** becomes Partial, **Cannot meet** becomes No, and **Undecided** becomes TBD. The Notes column holds the disposition reasoning.

The section shows **AI draft** under **Section progress**. Open it from the **Output documents** tab, check it, then take it through review and **Publish**; see [writing and reviewing sections](https://help.complytrain.net/en/tender/write-review-sections/).

Choosing **Generate matrix document** again refreshes the table from the current requirements. It replaces the section's content, including any edits you made to it, and returns the section to **AI draft**, so it needs approving again. Set dispositions and reasoning on the **Requirements** tab rather than editing the table, and regenerate the document as the last step before publishing it.

## Validate a response document

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

**Validate** checks one response document's sections against the requirements linked to them. On the output document's **Document Sections** page, choose **Validate**. The button reads **Validating…**, then **Validation** appears above the sections with a summary of failing, warning and passing sections.

<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>Result</p></th><th colspan="1" rowspan="1"><p>Message</p></th><th colspan="1" rowspan="1"><p>What to do</p></th></tr><tr><td colspan="1" rowspan="1"><p><strong>Fail</strong></p></td><td colspan="1" rowspan="1"><p>The section is empty, but requirements are linked to it</p></td><td colspan="1" rowspan="1"><p>Write the section; the requirements are not covered until you do</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Warning</strong></p></td><td colspan="1" rowspan="1"><p><strong>Section has no content yet.</strong></p></td><td colspan="1" rowspan="1"><p>Write it, or delete it if it is not needed</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Warning</strong></p></td><td colspan="1" rowspan="1"><p><strong>No RFP requirement is mapped to this section.</strong></p></td><td colspan="1" rowspan="1"><p>Expected for an introduction or cover letter; otherwise link the requirement it answers</p></td></tr><tr><td colspan="1" rowspan="1"><p><strong>Pass</strong></p></td><td colspan="1" rowspan="1"><p>The section addresses its linked requirements</p></td><td colspan="1" rowspan="1"><p>Nothing</p></td></tr></tbody></table>

A final line looks at the whole tender: whether all requirements are addressed across all output documents, either by a section or by an attached document, and which are not. **Nothing to report — every section this document owns passed.** means there was nothing to flag. Choose **Dismiss** to hide the results.

Validation checks that sections have content and are linked. It does not judge whether the text actually meets the requirement; that is the reviewer's job.

## Check requirement coverage

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

Coverage appears in two more places, using the same rule as the matrix.

-   **RFP requirement coverage** on each **Document Sections** page shows how many requirements are addressed across the tender, how many this document addresses, and lists those not yet addressed by any section. See [planning the response](https://help.complytrain.net/en/tender/draft-map-response/#how-coverage-is-counted).
    
-   **Requirement coverage** on the **Submission** tab shows how many requirements are addressed and lists the rest, leaving out requirements marked **Not applicable**, or says **Every requirement is addressed by at least one response section.**
    

Before you submit, the readiness check lists every requirement with the disposition **Can meet** or **Partial** that is still not covered, unless its status is **Not applicable**. Requirements marked **Cannot meet** or **Undecided** do not block submission. See [preparing the submission](https://help.complytrain.net/en/tender/prepare-submission/).

## Example: close framework bid gaps

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

A software company is bidding for a public-sector framework with 64 requirements. The **Compliance matrix** summary shows 51 covered.

1.  The bid manager sorts an **Export CSV** by Covered and finds 13 rows with No.
    
2.  Four of them ask for certificates. On each row they choose **Attach a document**, search for "ISO 27001" or "Cyber Essentials", and pick the current certificate from QMS. Those rows now show the certificate under **Addressed by**.
    
3.  Seven are linked to sections under **Compliance & Requirements** that nobody has written yet. **Validate** on the Technical Proposal lists them as failing, and the bid manager assigns them to authors.
    
4.  Two are **Cannot meet** requirements about on-site support in regions the company does not cover. They stay uncovered, and the reasoning explains the partner arrangement.
    
5.  When the authors finish, the bid manager chooses **Generate matrix document**, reviews the Compliance Matrix section, approves it and publishes it with the rest of the response.
