TenderMatrix / Guides / Compliance matrix mistakes
Compliance matrix mistakes: how a mandatory gets missed
A mandatory requirement usually gets missed because it sits somewhere the team did not look, not because someone ignored it: in the instructions, a form, a table, the contract terms or an addendum. Most misses fall into a handful of patterns, and each has a check.
Where mandatory items hide
Few RFPs keep every obligation in one place. Requirements appear in the specification, but also in the response instructions, the evaluation section, the contract terms, attachments and forms, and the buyer's answers and amendments. A matrix built only from the section titled Requirements will be incomplete however carefully it is filled in.
The consequence of a miss varies by buyer: lost points, a request to correct the response, or exclusion from evaluation. The RFP's own compliance rules decide, and your contracts adviser can say what applies. These checks aim to find the item before the buyer does.
A final sweep in seven steps
- Read the instructions against your outline Check page limits, format, file names, forms, signatures and the submission method. These rules rarely sit in the requirements section.
- Search the text for obligation words Try shall, must, required, mandatory, minimum, at least, no later than, will be rejected and failure to. Each hit should match a row or be set aside on purpose.
- List every attachment, form and appendix Each gets a row and an owner, including price sheets, declarations, certificates and anything to be signed.
- Read tables against their flag columns In a requirements table the obligation may sit in a column headed Mandatory, Priority or Y/N, with no verb in the sentence.
- Read the terms and the evaluation section Look for insurance, security, certification, data location, pass marks and minimum scores.
- Apply every amendment and answer Compare each addendum and Q&A log with the matrix and update the rows that changed.
- Have someone sample the RFP, not the matrix A second reader picks pages from the RFP and finds each obligation in the matrix, then confirms that every Mandatory row has an owner, a response and a place in the draft.
The first pass belongs to the RFP shredding process. This sweep is a second pass over the same document.
How a mandatory gets missed, and what catches it
The examples are invented to show the pattern, not quoted from any RFP.
| Where it hides | What it looks like | The check |
|---|---|---|
| Instructions | Submit pricing as a separate signed file | A row per instruction, with an owner |
| Contract terms | The supplier maintains a stated level of insurance | Read the terms with your contracts adviser |
| Attachments and forms | Complete and return Appendix C | One row and one owner per attachment |
| Tables | A Y/N column marks the item mandatory | Read each row against its flag |
| Compound sentences | Log events and keep the logs for a stated period | One obligation per row |
| No modal verb | Bidders to provide three references | Search for imperatives and read headings |
| Cross-references | As described in Annex 4 | Follow each reference and add its text |
| Definitions | In this RFP, should means must | Read definitions before typing rows |
| Amendments and answers | An addendum adds a security clause | Compare after every issue |
| Scoring section | Responses below a stated score will not be considered | Record pass marks as gates on related rows |
For the wording rows, see shall, will, should and may; the shall statement extraction page lists what TenderMatrix reads. For amendments, see tracking RFP amendments.
What goes wrong with the check itself
- Checking the matrix against itself. A reviewer who reads only rows finds them fine. An omission cannot be seen from inside the list.
- Reviewing the day before. A missing certificate or signature can take days to obtain. Sweep early enough to fix what you find.
- Reading Done as compliant. Done says the answer is placed, not that it satisfies the requirement.
- Comply with no evidence. A mandatory answered by assertion alone is exposed at evaluation.
- Fixing the matrix, not the response. A new row with no draft behind it is still a miss.
- Silent assumptions. Where the RFP is unclear, ask, or state the assumption in the response.
How TenderMatrix helps
TenderMatrix does the first sweep: it turns sentences with shall, must and should, and table flags such as M/D/O and Priority, into rows with the source line beside each. It is rule-based, so it can miss wording with no modal verb, does not follow cross-references and does not read a definitions section. Attachments, forms and addenda need their own conversion or a manual read, and a second person should still check the mandatory rows against the PDF. Try it on the RFP to Excel page. Free: 1 file per day, up to 10 pages, no account. Files over 10 pages are converted up to page 10 on the free allowance; a page code converts the whole file, up to 150 pages. See pricing.
Questions bid teams ask
What is the most common reason a mandatory requirement is missed?
It sits outside the section the team shredded: in the instructions, the contract terms, an attachment or an amendment. Read the whole package, then check it against the matrix.
How do I check that nothing is missing?
Search the RFP text for obligation words and compare the hits with the rows. Then have a second person pick pages from the RFP and find each obligation in the matrix. Sampling the source catches omissions that reviewing the matrix cannot.
Should the number of shall statements match the number of rows?
Use it as a rough check, not a target. One sentence can hold two obligations and need two rows, and a row can come from a table with no verb. A mismatch tells you where to look; a match proves nothing.
What if I find a missed mandatory late?
Tell the proposal manager at once and work out what it needs: a certificate, a signature, a partner or a price change. If it cannot be met in time, ask the buyer in writing whether a clarification or correction is possible. Rules differ by buyer.
Does a Done status mean the requirement is met?
No. Done should mean the answer has been reviewed and placed in the response. Whether the response meets the requirement is a separate judgement, and a Comply entry needs evidence behind it.
Who should review the matrix before submission?
Someone who did not build it, reading the mandatory rows against the RFP itself. A reviewer who only checks the matrix sees what the builder saw. Leave enough time to act on what they find.