Imperial
Requirements are not evaluation criteria
Instructions tell you what to submit and how. Evaluation criteria tell you what will be scored and with what weight. They are usually in different sections and they rarely match line for line.
A matrix that tracks only one of them produces a response that is either compliant and unpersuasive, or persuasive and non-compliant.
Capture the source reference
Record the section and page each requirement came from. When an amendment lands, or an evaluator questions a response, the reference is what lets you check the answer against the source rather than against memory.
Assign owners
Every row needs one name. Shared ownership of a requirement reliably produces either two answers or none.
Map response sections
Record where in your response each requirement is answered. This is what makes the final compliance check possible, and it is what allows an evaluator to find the answer where they expect it.
Manage amendments
An amendment can change instructions, criteria, due dates or the requirement itself. Each one needs a pass through the matrix, with changed rows marked so the affected response sections are revisited rather than assumed still valid.
Track missing evidence
Where a requirement needs a certificate, a letter, a resume or a past-performance reference, track it as its own row with its own owner and date. These are the items that arrive last and they should not be discovered last.
Run the final compliance check
Before submission, walk the matrix a final time against the response as assembled. Confirm every requirement has a location, every location contains an answer, and the format instructions have been followed.
Suggested columns
Source reference, requirement, response location, owner, due date, evidence, status. Seven columns is enough to run a response and few enough that people keep it updated.