What it is
A four-column table: the reference for the requirement in the tender documents (art. 2.1, schedule B…), its exact wording, its type (mandatory or desired), and the evidence that your submission meets it (section of your response, attached document, certificate). It doubles as your drafting plan and your final checklist.
How to build it
Comb through the specifications, the instructions and every addendum, tracking obligation markers: "must," "required," "at a minimum," "under penalty of rejection" for the mandatory ones; "asset," "desirable," "preferably" for the desired ones. Every occurrence becomes a row. On a typical services tender, expect 15-30 requirements — if you find only 5, keep looking.
The hidden requirements
The most dangerous ones aren't in the "Requirements" section: a liability insurance amount buried in the contractual framework, a certification slipped into the description of needs, a submission format imposed in the instructions. The matrix only has value if it covers the entire file, not just the neatly labeled chapter.
At the final review
The day before submission, someone who didn't write the response takes the matrix and checks every line against the assembled submission: every mandatory item has its evidence, every required document is in the envelope (or the electronic filing), every addendum has been accounted for. Thirty minutes that are worth weeks.