Compliance matrix for tenders: format, example and how to build one

What is a compliance matrix?

A compliance matrix is a requirement-by-requirement table of a tender and your response to it. Each row holds one requirement, where it appears in the tender, your position on it and where your offer proves it.

Tenders in India and elsewhere use several names for the same thing: technical compliance statement, clause-by-clause compliance, compliance sheet, technical compliance checklist or point-wise compliance. In US federal bidding the common term is proposal compliance matrix, which maps the RFP's instructions (Section L) and evaluation factors (Section M) to the sections of the proposal.

This guide covers the technical and commercial tender version used by EPC contractors, equipment manufacturers and government suppliers, where the key column is the position: complied, complied with clarification, deviation or not applicable.

Why a compliance matrix for a tender matters

In a two-cover tender, the technical bid decides whether your price is ever opened. Paragraph 4.15.2 of the Department of Expenditure's Manual for Procurement of Goods (opens in a new tab) (Second Edition, 2024), referring to Rule 163 of GFR 2017, says the financial bids of technically non-compliant offers remain encrypted and unopened in e-procurement.

The same manual defines the terms evaluators use (paragraph 7.3.4). A deviation is a departure from the requirements in the tender document. A reservation sets limiting conditions or withholds complete acceptance. An omission is a failure to submit some or all of the required information. A substantive deviation, one that affects scope, quality or performance, limits the buyer's rights or the bidder's obligations, or would unfairly affect other bidders if corrected, leads to rejection as non-responsive.

For capital goods, paragraph 8.3 of the manual advises buyers to ask for a statement of deviation with a detailed justification for deviations from each clause of the specification, and a schedule of guaranteed particulars where the bidder quotes the offered value of each parameter. That is a compliance matrix and a filled datasheet by another name.

Individual tenders are often stricter. A BHEL tender (opens in a new tab) states that an offer without its deviation list will not be evaluated and shall be rejected. Some PSU tenders say that a blank Accepted or Deviation column will be treated as accepted, and an Oil India technical compliance checklist says deviations stated anywhere other than that checklist are ignored. Read the tender's own rule before you fill anything in.

Compliance matrix format: the columns to use

If the tender supplies a compliance format, use it exactly and add nothing that changes its meaning. If it does not, these columns cover what evaluators and your own reviewers need. This is also a workable compliance matrix template for Excel.

Keep the last column in your working copy and remove it from the submitted version unless the buyer asks for it. Number rows so the deviation sheet, pre-bid queries and the offer can refer to them.

Compliance matrix example: a valve tender (illustrative)

The rows below are illustrative. They show how a ball valve manufacturer might answer clauses from a specification, a datasheet and the special conditions of one tender. Clause numbers and values are invented for the example.

Notice row T-04. The requirement came from the datasheet, not the specification, and the tender left the class open. The team raised a pre-bid query rather than guessing, and recorded the answer it relied on. Datasheet requirements like this are covered in technical datasheets in tenders.

Deviation sheet format and technical deviations

A technical deviation is any point where your offer departs from what the tender specifies. The deviation sheet lists them in one place so evaluators can judge each one. The goods manual says submission formats typically include exception and deviation forms, and many PSU tenders attach their own.

• Quote the tender clause and requirement exactly, then state what you offer instead, in the same units.
• Give a short technical reason. A deviation without a reason invites a technical query or rejection.
• Keep deviations out of the covering letter, technical literature and price bid unless the tender says otherwise.
• If you have no deviations, submit the 'nil deviation' statement or declaration the tender asks for.
• If you offer an equivalent standard, attach proof. A BHEL tender document (opens in a new tab) says alternative standards need sufficient documentary evidence of equivalence, failing which the offer is considered not technically acceptable.

How to build a compliance matrix, step by step

1. Collect the whole pack: NIT, instructions, special and general conditions, specifications, datasheets, drawings, BOQ, forms, every corrigendum and the pre-bid replies. Our explainer on tender documents lists what each section holds.
2. Break the text into single requirements, one per row. Sentences with 'shall', 'must', 'required' or 'bidder to confirm' are the usual markers, and one sentence can hold several requirements.
3. Classify each row: mandatory, desirable, eligibility, commercial or submission. Eligibility rows feed the eligibility check.
4. Assign an owner to each group: engineering for specifications and datasheets, quality for inspection and tests, commercial for SCC terms, and the bid coordinator for forms.
5. Record each position against the original wording, with the offered value and the evidence reference.
6. Find conflicts. Where the datasheet and specification disagree, or a value is missing, raise a pre-bid query before the clarification deadline instead of choosing silently.
7. Move every deviation to the deviation sheet in the buyer's format, with a reason and its effect.
8. Before submission, check each evidence reference against the compiled offer and re-check every row a corrigendum touched.

For a large EPC pack, split the matrix by discipline and merge it at the end, keeping one numbering system. The tendering process guide shows where this work sits between the pre-bid meeting and submission.

Common mistakes in a technical compliance statement

• Writing 'complied' against every row without evidence. Evaluators check the datasheet and drawings, and a mismatch reads as a hidden deviation.
• Using vague words such as 'noted' or 'will be considered', which an evaluator may read either as acceptance or as no answer.
• Leaving cells blank, which some tenders treat as acceptance.
• Paraphrasing the requirement, so the row no longer matches the clause it answers.
• Missing requirements that sit in datasheets, drawings or the special conditions rather than the specification.
• Answering with conditions such as 'subject to' or 'if possible'. Paragraph 7.3.1 of the goods manual lists conditional bids, unless the tender permits them, among the grounds for treating a bid as unresponsive.
• Forgetting to update rows after a corrigendum.

How AI tools help with a compliance matrix, and what people still decide

The slowest part of the work is finding every requirement and tracing it to its source. TenderGenie's Document Intelligence extracts specifications, scope, clauses, obligations and datasheet requirements from PDF, DWG, XLS and DOC files, including complex datasheets, and links each one to the document and page it came from. Risk & Compliance maps requirements to the response so gaps show early, and Collaboration keeps owners, queries and approvals in one tender workspace.

For manufacturers, TenderGenie's enquiry checklist shows what to supply, what you already meet and what is missing, and Filled-in Datasheet completes the buyer's own datasheet format for engineers to review. See how this works for valve manufacturers.

People still decide:

• Whether a requirement is met, which is an engineering judgment against the original wording.
• Whether to state a deviation, and how to word it.
• Which questions to raise with the buyer before the clarification deadline.
• Sign-off of the matrix and the final offer.

The next step is the tender compliance matrix workflow, which shows how a team builds a source-linked matrix from the tender pack with owners and a position on each requirement.

Questions and answers