How to build a tender compliance matrix

Give every requirement a place in the response

A tender compliance matrix is a working record that connects each requirement to its source, the response location, the person responsible and the evidence needed. It helps a bid team organise preparation and review. It is not a certificate of compliance, a replacement for the tender pack or a guarantee that an answer will score well.

Use it after the team has authorised bid preparation. If the pursuit decision is still open, start with the bid/no-bid decision guide. The matrix answers a different question: what must we produce, and how will we know it has been checked?

Keep it proportionate. A short response may need only a few rows; a multi-document tender may need separate records for questions, attachments, pricing and submission instructions. A useful row should lead to a specific task, rather than repeat a large paragraph that nobody owns.

1. Establish the current document set

Collect the notice, instructions to tenderers, specification, response templates, pricing schedules, contract terms and published clarifications that apply to your bid and lot. Check the buyer’s portal for amendments. Record filenames, version dates and where the files came from before extracting requirements.

• Identify which documents describe the work and which tell you how to respond.
• Keep superseded versions separate so reviewers do not quote old instructions.
• Record the submission and clarification deadlines exactly as published, including time zone where stated.
• Note documents you cannot access and assign someone to resolve that gap.

This is an internal working method, not a mandatory statutory template. Apply the instructions and regime for the specific procurement. Cabinet Office transitional guidance explains why procurements begun under previous legislation can continue under it; guidance on devolved contracting authorities explains why jurisdiction and purchasing arrangements also matter.

2. Separate different kinds of requirement

Do not put everything under a single “compliance” label. A participation condition, a scored question and a delivery obligation require different checks. Under the Procurement Act framework, conditions of participation assess supplier suitability, while award criteria assess the tender. The Cabinet Office guidance on assessing competitive tenders sets out that distinction.

Scroll across to see requirement types →

Record any published weighting or threshold exactly; do not infer one. Also record timing. A requirement due at contract commencement needs a different action plan from evidence due with the response. Ask through the permitted clarification route when the wording does not settle that point.

3. Build one actionable record at a time

Use a stable requirement ID and retain the original question or clause reference. Split a compound question into manageable subparts, such as Q3a, Q3b and Q3c, while keeping the relationship to Q3 visible. This makes it harder to answer the first part well and overlook the remaining instructions.

Quote a short requirement or paraphrase it accurately. Always include the source document, version and page, clause or question number. A colleague should be able to locate the wording without repeating your research. Record any word limit, attachment format or required response location alongside it.

A matrix that merely says “see specification” moves the reading burden to the next person. A record that identifies the clause, the action and the response location makes the handover usable.

4. Connect ownership, evidence and response location

Give each record a named owner and reviewer. The owner prepares the material; the reviewer checks that it addresses the requirement and that the business can support the commitment. Agree an internal due date early enough to allow corrections before submission.

• Response location: identify the answer number, portal field, file or pricing cell where the requirement will be addressed.
• Evidence: identify the relevant case study, certificate, method, calculation or reference, including its actual location.
• Evidence gap: state what is missing and who will obtain or confirm it.
• Dependencies: note partner input, permissions or approvals needed to complete the answer.

Evidence should support the claim being made. A reference for a smaller or differently scoped service may still be useful, but its limitations should be understood rather than hidden. Check permission to name clients and use their information. Keep sensitive supporting material in your team’s approved working environment.

5. Keep unresolved points visible

Use plain statuses such as unreviewed, action needed, in progress, ready for review and checked. Define “checked” as a completed review of both the response and its supporting material. It should not mean that a writer has added text somewhere.

For an ambiguity, record the exact question, its source, the responsible person and the clarification deadline. Submit through the buyer’s permitted channel. Do not treat a preferred interpretation as confirmed simply because drafting would be easier that way.

For an internal gap, record the next action and its due date. “Evidence needed” is too vague; “commercial lead to reconcile the pricing assumptions with the proposed staffing by Tuesday” gives the team a task it can complete. Keep unresolved issues visible to the bid lead at review checkpoints.

6. Recheck the matrix when documents change

A clarification can change more than the sentence that prompted it. Revised volumes may affect price, staffing, mobilisation and supporting evidence. Compare new files with the versions recorded in the matrix, then identify every affected record and notify its owner.

The Cabinet Office guidance on modifying a competitive procurement discusses amendments to notices and associated tender documents. For your working record, retain the amendment reference, date checked and resulting action. Do not overwrite the history so thoroughly that nobody can explain why an answer changed.

Ask whether completed reviews need reopening. If an amended requirement changes a delivery commitment, the earlier “checked” status should not carry forward automatically. Record who rechecked the response against the current wording.

7. Review the response, not just the matrix

At review, open the actual answer, attachment or workbook referenced by each record. Check question coverage, evidence relevance, stated limits and consistency with other parts of the bid. A complete-looking matrix can still point to an incomplete answer.

• Confirm that every requested subpart has an identifiable response.
• Check that names, dates, resources and commitments agree across the method and price.
• Confirm required declarations, signatures and attachments using the current instructions.
• Separate unanswered questions from delivery risks already reviewed and accepted by the appropriate owner.
• Record the reviewer and date, and reopen records when material changes occur.

Use the final check to confirm the submission route, correct file versions and any required receipt or acknowledgement. Allow time for the process the buyer actually specifies; do not assume a generic deadline extension or alternative delivery method.

Start with a working template

Use the editable tender compliance matrix to record requirements, sources, owners and review status. It can be completed on screen and printed or saved as a PDF using your browser. Add records for the requirements that matter to the specific bid rather than treating the starting fields as an exhaustive checklist.

TenderSNAP Tender Intelligence organises tender requirements, risks, dates and source evidence into a reviewable briefing. That can support the initial review of the pack. Your team still checks the underlying documents, prepares the response and owns its commitments; this standalone template does not imply that TenderSNAP assigns response owners or certifies compliance.