Glossary
Compliance matrix
Loonar · Updated 4 November 2026
A compliance matrix is a table that lists every requirement in a tender package, one per row, with the supplier's response and a reference to where the offer shows it. Buyers use it to check that nothing was skipped. Suppliers use it to check that nothing was missed before pricing. Each line marked compliant is a commitment.
Also called: compliance statement, statement of compliance, clause-by-clause compliance, tender compliance matrix.
What a compliance matrix contains
| Source | Requirement | Status | Offer reference | Comment |
|---|---|---|---|---|
| Specification, p. 12, cl. 4.2 | Shell test to API 598 | Compliant | Test procedure TP-01 | |
| Datasheet, p. 4, item 3 | Cast body ASTM A352 LCC | Not compliant, alternative offered | Deviation list, line 1 | Forged ASTM A350 LF2 Class 1 offered |
| Specification, p. 20, cl. 7.1 | Inspection certificates to EN 10204 type 3.2 | Clarification requested | Clarification 3 | Buyer to name the inspection representative who countersigns, and who pays for the inspection |
| Specification, p. 22, cl. 9.1 | Electric actuator requirements | Not applicable | Datasheet calls for handwheel-operated valves |
Each row carries one requirement. A row that reads "see specification" hides the requirements inside it.
Compliance matrix vs technical deviation list
The compliance matrix covers every requirement. The technical deviation list covers only the exceptions. Many tenders ask for both. The deviation list is then the matrix filtered to the lines that are not compliant. In the buyer's technical bid evaluation, both go straight into the evaluation sheet.
The World Bank's standard bidding documents ask for the same two things: "a detailed item by item description" of the goods against the specification and, if applicable, "a statement of deviations and exceptions" (World Bank, ITB 16.3).
How to build a compliance matrix
- Split the package into single requirements, one per row. Statements with "shall" or "must" are the usual starting point.
- Keep the source of each one: document, page and clause.
- Give each row a status from a fixed list. When the buyer provides a template, use its statuses and do not change its rows.
- Point to the evidence: datasheet, drawing, procedure or certificate.
- Have an engineer sign off every line that is not compliant.
- Check that the matrix, the deviation list and the technical offer say the same thing.
What to avoid
- Vague statuses such as "noted" or "acknowledged". The buyer cannot tell whether you comply, and may read them as compliant.
- "Compliant" without evidence. The matrix is part of the offer and often of the contract. A line marked compliant is a commitment you will be held to.
- Contradictions. A matrix that says compliant next to a deviation list that says otherwise leaves the buyer to decide which one applies.
How Loonar helps
RFQ Analysis extracts the requirements from the package, each with its page. Deviation Analysis drafts the status of each one against your certifications, quality records and past offers, with the citation behind it. Loonar uses its own statuses; when the buyer's template sets others, your team maps them. Your engineers review every line before the matrix goes in the offer.
Frequently asked questions
What is the difference between a compliance matrix and a deviation list?
The compliance matrix lists every requirement with a status. The deviation list lists only the requirements the offer does not meet, with what is offered instead and why. The two must agree line by line.
Is a compliance matrix the same as a requirements traceability matrix?
Not usually. A traceability matrix follows each requirement through design and testing during the project. A compliance matrix is the supplier's statement at bid stage. Some buyers use the names loosely, so read what the tender asks for.
What statuses should a compliance matrix use?
The buyer's, when the tender sets them. Otherwise a short fixed list, for example: compliant, partially compliant, not compliant, clarification requested, not applicable. Every status other than compliant or not applicable needs a comment and, where relevant, a line in the deviation list.
Does the compliance matrix become part of the contract?
Often, either because the contract lists the offer documents or because the purchase order refers to them. Check the contract's list of documents and its order of precedence. Treat every status in the matrix as a statement you will be held to.
Who fills in the compliance matrix?
Usually the sales or bid engineer, with input from the engineers of each discipline. One person checks the whole matrix against the deviation list and the technical offer before submission.