A compliance matrix is a table that answers one question for every obligation in a solicitation: where did we answer this, and what proves it? It is not a summary of the bid. It is the audit trail that lets a reviewer check the bid without reading it end to end.

Most matrices fail for a boring reason. Not the formatting, not the colour coding. Rows are missing, because the requirement was never captured as a row in the first place.

What belongs in a row

One row per obligation. Each row needs, at minimum:

the requirement as the solicitation states it, quoted or closely paraphrased;
where it came from: section, clause and page;
the response status, and the vocabulary has to be honest — comply, exception, or no response yet;
the answer that goes in the bid;
the evidence the answer rests on.

The last two are where teams improvise, and where an otherwise tidy matrix stops being useful. An answer without evidence is an assertion. An evidence column filled with “see proposal” is not a trace.

Where matrices actually lose rows

The rows that go missing are rarely in the body of the solicitation. They hide in the places a skimming reader does not open:

Attachments and exhibits. The pricing form, the certification schedule, the insurance table. These carry obligations that are easy to miss because they do not look like instructions.
Amendments. An amendment can add, delete or renumber requirements. A matrix built before the amendment is now wrong in a way that looks complete.
Instructions to offerors. Formatting, page limits and submission rules are requirements too. They get read once and then forgotten.
Requirements spread across a section. One paragraph can contain three separate obligations. One row for the paragraph quietly drops two of them.

Build the matrix before the draft

The order matters more than the tool. If the matrix is produced after the draft, it is a description of what someone wrote, and the gaps are whatever the writer happened not to mention. If the matrix is built first, it is a work plan: every row is an obligation that needs an owner and an answer, and an empty row is a visible problem rather than an omission nobody notices.

This is why “one row per requirement, in document order” is a better rule than “one row per section”. Document order is also the only order a reviewer can follow while holding the solicitation in their other hand.

What a gap row is for

A gap row is not a failure of the bid. It is a finding. Some requirements genuinely have no supporting document in the company’s files: a certification not held, a past performance the team cannot evidence, a capability nobody has written down.

The useful matrix says so. It marks the requirement missing, records that it is missing, and moves on. The dangerous matrix fills the cell with plausible prose, because the prose will survive until someone at the buyer asks for the certificate.

How Typezo produces one

Typezo reads the solicitation once, at upload, and extracts every requirement with its section and page. Rows are emitted in document order. Each answer is drafted only where a stored span in the company’s own documents supports it; where nothing supports it, the requirement stays missing and the matrix gets a gap row.

Before export, a deterministic verifier re-checks every quote against the stored page text, every page against the parser, and every number, date and dollar figure against a cited quote. The model does not grade its own work. The output is a compliance matrix in XLSX and a requirement-by-requirement draft in DOCX, which your team then edits.

You can open the sample workspace and click a citation to see the page it came from. It is fictional, plainly labelled, and it needs no sign-in.