Compliance matrix

01Where the requirements come from

In a federal RFP the rows come from three places in the uniform contract format: Section C, the statement of work or performance work statement (what you must do); Section L, the instructions to offerors (how you must present it); and Section M, the evaluation factors (what will be scored). FAR 15.204-2 and 15.204-5 define those sections. A matrix that covers only the statement of work misses the formatting and submission rules, and failing those can make an offer unacceptable before anyone reads it. Outside federal work the same three kinds of requirement exist under other names: scope, submission requirements and scoring criteria, plus any mandatory forms.

02Extracting every requirement

Building the matrix starts with extraction: reading the whole solicitation, including attachments, amendments and answers to bidders' questions, and pulling out each requirement as its own row.

• Look for "shall", "must", "will" and "is required to", and also for requirements stated in tables, forms and pricing sheets.
• Split compound sentences. "The contractor shall provide a transition plan and a staffing plan within 30 days" is two rows.
• Number each row back to its source paragraph so a reviewer can check it.
• Extract again whenever an amendment is issued.

This is the step software now does best. BidAuthor, for example, extracts the requirements from an uploaded solicitation and links each one to the section of the response that answers it.

03Columns that earn their place

An illustration of the format. These three rows are invented to show the columns, not taken from a real solicitation:

The columns worth keeping:

• Requirement ID and exact source reference: section, paragraph, page
• The requirement text, quoted
• Type: statement-of-work task, Section L instruction, Section M factor, form or certification
• Where the response answers it: volume, section, page
• Owner and status: compliant, partially compliant, exception, not yet written
• Notes for reviewers: assumptions, exceptions and risks

04Common mistakes

• Paraphrasing requirements instead of quoting them, which hides what was actually asked.
• Ignoring amendments issued after the matrix was built.
• Mapping a requirement to a section that mentions it rather than one that answers it.
• Treating "compliant" as the goal. Section M scores strengths, so the matrix should also show where you exceed a requirement.

When the RFP asks for a cross-reference matrix as part of the submission, follow its format exactly. When it does not, build one anyway and use it in every color team review.