What is a compliance matrix?
A compliance matrix is the table a bid team builds from the tender pack, with a row for each requirement and evaluation criterion, recording whether the response complies and where it addresses it.
On this page
Each row takes one item from the tender pack and records its reference, the document and section it comes from, its text, the place in the response that answers it, its owner, and its compliance status. The team keeps the matrix from its first read of the pack until the response is submitted. In bid and proposal management, it is the supplier-side team’s own working document for tracking the response. It is not part of what the buyer receives, unless the tender asks for a compliance matrix to be submitted with the response.
What goes in a compliance matrix?
A row for each requirement, instruction, and criterion
A compliance matrix commonly includes a row for each requirement in the tender, each submission instruction, and each question or criterion the buyer scores, wherever it sits in the pack. Pass/fail questions get rows as well, so the matrix covers everything the response is assessed against.
Take a supplier’s bid team answering an ITT for a multi-site facilities management contract. Its tender pack runs across several files: the ITT instructions, the specification, the quality questionnaire, the pricing schedule, and the form of tender. The rows come from across those files: the instruction on how to name files for upload to the buyer’s portal, the specification’s requirement for a mobilisation plan, each scored and pass/fail question in the quality questionnaire, and the mandatory declarations in the form of tender.
The columns
The columns commonly hold a reference for the row, its source in the tender pack by document and section, the requirement’s text, the place in the response that answers it, the row’s owner, its compliance status, and notes. The owner is whoever answers the row, and the status records whether the planned response meets it.
The response location shows where the response answers each row. A row with that cell still empty is an item the response has not answered yet.
What one looks like
In the facilities management bid, the matrix opens with rows from the ITT instructions, the specification, the quality questionnaire, and the form of tender.
| R01 | ITT instructions, section 3 | Name each file as the instructions set out for upload to the buyer’s portal | Submission pack | Bid manager | Compliant | Checked again before upload |
|---|---|---|---|---|---|---|
| R02 | Specification, section 5 | Provide a mobilisation plan | Quality response, mobilisation answer | Subject matter expert, mobilisation | Partially compliant | Plan to be confirmed against the requirement in full |
| R03 | Quality questionnaire, question 4 | Scored question on service delivery across sites | Quality response, question 4 | Writer | Compliant | Ready for review |
| R04 | Form of tender, declarations | Sign the mandatory declaration | Form of tender | Bid manager | Compliant | Signature before upload |
The mobilisation row reads partially compliant until its owner confirms that the plan meets the requirement in full.
When is it built and updated?
Before drafting starts
Teams commonly build the matrix at the start of the bid, once the tender pack is in and before anyone drafts. It follows the team’s first read of the full pack, and each writer then starts from the rows they own.
That places it early in the tender process on the supplier’s side, ahead of drafting, reviews, and the final check, all of which run against its rows.
When a clarification answer changes the tender
When the buyer issues a clarification answer or an amendment to the tender documents, teams commonly update the rows it touches. The matrix then matches the tender documents as they now stand.
Midway through the facilities management bid, the buyer’s answer to a clarification question changes the specification’s mobilisation requirement. The team rewrites the requirement text in the mobilisation row. The subject matter expert who owns that row reworks the answer, because a plan drafted against the old wording no longer answers the requirement as it is now written.
How is it used in reviews and at submission?
In reviews
Reviewers commonly check the draft against the matrix, confirming that each requirement is answered where its row says it is. In colour-team reviews, that check runs alongside the reviewers’ judgement of each answer’s quality.
A gap found in review is a row whose answer is missing or sits somewhere other than the matrix records. It goes back to the row’s owner while there is still time to rework the answer to that question.
The final check before submission
Before submission, teams commonly run a final check against the matrix: every row has its answer, and every required document is in the pack.
In the facilities management bid, that check takes the form of the form of tender’s mandatory declaration. The team signs and attaches it, closes the row, and uploads the response to the buyer’s portal. The bid manager gives final approval, and this check shows them that no row is still open.
What do procurement rules require?
Compliance as a condition of award
What a missed requirement costs, and whether a submitted bid can still be corrected, turns on the rules the buyer’s procurement runs under. In the EU, for example, Directive 2014/24/EU lets the contracting authority award a contract only after verifying that the bid meets the requirements, conditions, and criteria set in the contract notice and procurement documents. A bid that does not comply with the procurement documents counts as irregular under the directive. The bid team must meet each compliance requirement row by row.
In a 2014 ruling, the Court of Justice of the EU held that an authority must apply the criteria it set strictly and must exclude a bidder that failed to provide a required document, on pain of exclusion. Unless the omission is purely formal, the bidder cannot put it right after the deadline. For such a document, the team catches the gap in its row in the matrix while it can still be fixed.
Correcting a bid after the deadline
Once submitted, a bid cannot, in principle, be amended, the Court of Justice of the EU held in a 2012 ruling, and the authority need not ask a bidder to clarify a bid that is imprecise or fails the technical specifications. Exceptionally, the authority may allow details to be corrected or filled in where they need mere clarification or contain obvious material errors. The correction must not amount to a new bid, and any request goes equally to every bidder in the same position.
The authority may also, unless national law provides otherwise, ask a bidder to submit, supplement, clarify, or complete information or documents that are or appear incomplete, erroneous, or missing, under the directive. It sets an appropriate time for this. Both are powers of the authority, not rights of the bidder.
What the bidder can rely on
Under the same 2014 ruling, every condition and rule of the procedure must be clear, precise, and unequivocal, so that every reasonably informed bidder exercising ordinary care reads it the same way. A requirement the team can read two ways calls for a clarification question.
Additional information on the specifications, requested in good time, has to reach all bidders no later than six days before the deadline under the directive. The authority must also extend the deadline when it makes significant changes to the procurement documents. The matrix’s rows capture these answers and changes as the bid progresses.
How does it differ from a statement of compliance?
When the tender asks for the matrix
The compliance matrix is the bid team’s working document for tracking its response. Some tenders ask for a compliance matrix to be submitted with the response, and it then becomes part of what the buyer receives.
When the instructions ask for one, the submitted matrix is required, so it has its own row in the team’s matrix.
A statement of compliance
A tender may instead ask for a statement of compliance on the buyer’s own template. An EU agency’s tender, for example, asks each bidder for a signed statement on the agency’s template, indicating its degree of compliance with the contract, its service level agreement, and the security annex. For the technical requirements, the bidder either confirms full compliance or defines partial or non-compliance, justifies each statement, and points to the sections of its response where the justification is developed.
That tender also sets what the statement binds the bidder to. Where full compliance is stated, comments, assumptions, and limitations are not taken into account and do not apply on award. Where partial or non-compliance is stated, the bidder has to propose alternative wording, contract wording included where relevant. A justification left out of the statement is disregarded and cannot be relied on against the agency during the contract. The response is then scored on its level of compliance and on the credibility of its justifications and alternative wording.
In a tender like this, the team declares the compliance status it settles in its matrix and is held to it.
How SEQUESTO tracks each requirement to sign-off
Tracking leaves the team to keep every requirement, instruction, and criterion across the pack, and every change to them, tied to an answer, an owner, and a review until sign-off, and SEQUESTO aOS brings governance to that work. Each response runs on workflows the team configures to match the organisation’s process and governance.
Specialist agents in Agent Force extract the requirements, evaluation criteria, questions, mandatory attachments, and the word and character limits from the tender documents into the project. Each item is tracked there, so compliance can be confirmed before the response goes out. Before drafting starts, the bid manager reviews the structure the agents extracted and confirms it; each item then stays tracked until the bid manager signs it off.
In the Bid Capabilities layer, each question carries its owner, status, and deadline, and can have its own reviewer and approver. Reviewers, approvers, and subject matter experts work inside the workflow, on the review chains and approval logic the team configures.
James orchestrates the work, and the team stays in charge of the result: it accepts, adjusts, or rejects what the agents did, and the bid manager keeps the final wording and the sign-off.