What a requirements matrix actually is
Short answer
One table with a row for every demand the tender makes, each row carrying the document and page it came from, whether it is mandatory or scored, who owns it, and what evidence answers it.
The word "matrix" makes it sound like a technique. It is a transcription. The value is not in the format, it is in the completeness and the citations: a demand nobody wrote down cannot be answered, and a demand written down without its source cannot be checked by anyone except the person who transcribed it.
The minimum columns are the requirement text as the pack words it, the document and page, whether it is a pass-or-fail condition or a scored criterion, the evidence that answers it, and an owner. Weighting and word limits go in where the pack states them. Everything else is preference.
Transcribe the requirement in the buyer’s words, not your summary of them. A paraphrase drifts, and when a reviewer checks the row against the page they will be checking your paraphrase rather than the requirement.
| Column | Why it exists |
|---|---|
| Requirement, as worded | A reviewer compares the row to the page. A paraphrase breaks that check. |
| Document and page | Makes every row verifiable by someone who did not transcribe it. |
| Kind | Mandatory conditions are pass or fail. Scored criteria decide rank among those who pass. |
| Evidence | The document or claim that answers it, and whether you hold it today. |
| Owner and status | Who is answering it, and whether it is open, drafted or approved. |
The five places demands hide
Short answer
Conditions of tendering, the specification or scope, the returnable schedules, the evaluation criteria, and every addendum. A matrix built from the response forms alone misses the conditions that disqualify you.
Bidders read the response schedules first because that is where the questions are, and the schedules are the least dangerous part of a pack. The clauses that end a bid sit in the conditions document, which reads like legal furniture and gets skimmed.
- Conditions of tendering, or instructions to tenderers. Mandatory conditions live here: insurance levels, licences, entity requirements, lodgement rules, the consequences of a late or non-conforming offer. This is the document that disqualifies people.
- The specification, scope or statement of requirements. Technical demands, standards to comply with, service levels, deliverables. Often the longest document and the one where a single referenced standard implies work nobody costed.
- Returnable schedules and forms. The questions you obviously must answer, plus the forms that must be returned unaltered. "Do not modify this form" is a mandatory condition wearing a schedule’s clothing.
- Evaluation criteria and weightings. What is scored and how heavily. These are demands too: an unweighted response to a 40% criterion is a scored loss even when nothing was technically missed.
- Addenda and the question-and-answer log. Issued after release, they change requirements and are binding. A matrix that is not re-checked after an addendum is out of date, and the buyer will assume you read it.
Keep must, should and may apart
Short answer
Transcribe the modal verb exactly as written. "Must" and "shall" are conditions, "should" is a preference that usually scores, "may" is optional. Collapsing them wastes effort on the wrong rows.
This is the cheapest discipline on the page and the one most often skipped. Under time pressure a reader flattens everything into "things the tender wants", and then the team spends three days on a "should" while a "shall" sits unanswered.
Where the pack is genuinely ambiguous, the row is not resolved by guessing. It goes on the question list for the buyer, with the document and clause named. Most procurement processes have a formal question period for exactly this, and the answer becomes an addendum binding on every bidder.
A practical rule: if you cannot tell whether a line is mandatory, treat it as mandatory for planning and ask the buyer. The cost of over-preparing one row is hours. The cost of under-preparing a mandatory one is the bid.
A worked example
Short answer
Five rows from an illustrative pack, showing the shape. The tender below is invented for this guide.
The rows are illustrative and the tender is not real — it exists to show the format, not to describe any buyer’s actual requirements. Notice that three of the five rows come from a document most bidders skim, and that the row which would end the bid is the dullest one on the page.
| Requirement, as worded | Source | Kind | Evidence |
|---|---|---|---|
| "The Respondent must hold public liability insurance of not less than $20,000,000." | Conditions of tendering, p. 11 | Mandatory | Certificate of currency. Held: $10m — short, needs a new certificate. |
| "Tenderers must be registered for GST in Australia." | Conditions of tendering, p. 9 | Mandatory | ABN registration record. |
| "Schedule 3 must be returned without alteration." | Returnable schedules, p. 2 | Mandatory | The original form, filled, not rebuilt. |
| "Demonstrated experience delivering comparable works in the last five years." Weighting 30%. | Evaluation criteria, p. 14 | Scored | Three project references with dates and contact consent. |
| "Respondents should describe their approach to environmental management." | Specification, p. 22 | Scored, not mandatory | Environmental management plan. |
Doing the transcription faster, without trusting it blindly
Short answer
Extraction can pull the tables and text with the page each value came from, which removes the typing. A human still decides what is mandatory, because that judgement is what the matrix is for.
The slow part of a matrix is not judgement, it is transcription: reading forty pages and retyping clauses without losing the page numbers. That part is mechanical, and pulling structured values and whole tables out of a PDF with the page attached to each one removes most of it.
What cannot be handed over is the classification. Whether a clause is a condition or a preference depends on how the buyer will read it, and getting it wrong in the confident direction is how bids are lost. Treat any automated pass as a first draft that a person confirms against the page.
Stipple’s extraction returns the page and position for values it reads from a native-text PDF, which is what makes a row checkable afterwards. It does not decide whether your answer satisfies the requirement, and no tool should claim to — that is the evaluator’s job, against criteria you can read but not score yourself.
Use the matrix to make the bid or no-bid call
Short answer
Once mandatory rows are separated, the no-bid answers itself: a condition you cannot meet before the closing date, and cannot be waived, ends it. Better to find that on day one.
The matrix is usually treated as a response tool. It is more valuable as a decision tool, because the mandatory rows are a checklist of ways to be disqualified and you can read them in an hour.
Sort the mandatory rows into three groups: held today, obtainable before the deadline, and not obtainable. Anything in the third group is either a no-bid, a reason to partner with someone who holds it, or a question to the buyer about whether an equivalent is acceptable.
The timing matters more than most bidders allow for. Renewing an insurance certificate to a higher limit, obtaining an accreditation, or getting written consent from a referee all run on other people’s calendars, and the response window is shorter than most people assume. Read the measured windows before you plan the work.
Frequently asked questions
What is a tender requirements matrix?
A table with one row per demand the tender makes, each row carrying the requirement as the pack words it, the document and page it came from, whether it is mandatory or scored, the evidence that answers it and who owns it. Its purpose is that a second reader can check every row against the source.
What is the difference between a requirements matrix and a compliance matrix?
In practice they are used interchangeably. Where buyers distinguish them, a compliance matrix is the returnable document that states your compliance against each clause, and the requirements matrix is your internal working copy that also tracks owners, evidence and status. Build the internal one first; the returnable version is an export of it.
Where are mandatory requirements usually found in a tender?
The conditions of tendering or instructions to tenderers, which most bidders skim because it reads like boilerplate. Insurance levels, licences, entity and registration requirements and lodgement rules sit there. The returnable schedules carry the visible questions but rarely the disqualifying conditions.
Do addenda change the requirements?
Yes, and they are binding. An addendum can add, remove or reword a requirement after release, and buyers assume every bidder has read it. Re-check the matrix against each addendum and mark which rows changed, rather than trusting that the change was small.
Can a tool tell me whether my response complies?
No, and be wary of one that says it can. Extraction can pull the requirement text and the page it came from, and deterministic checks can report tampering signals on a document, the dates it carries, and whether every required document type is present in a pack. None of that proves a document is genuine, and whether a written response satisfies a criterion is a judgement the buyer’s evaluation panel makes.
Sources and further reading
- 01Stipple tender search — open Australian and New Zealand opportunities
- 02Stipple tender source registry — every source and its latest run
Educational guidance, not a forensic certification. Detection technologies and standards change; review material decisions against current evidence.