There can be a LOT of reviews when you’re executing a USG contract. As a result, I HIGHLY recommend you read your full Contract Data Requirements List (CDRL) list and look at the associated DD Form 1423 or Data Item Description (DID) BEFORE you sign a contract. Reviews for the USG, whether design reviews or programmatic reviews, can be time consuming for a small business and time is money.

Here is a top-level list of the type of reviews you may see in your SBIRs or Phase III contracts:

• System Requirements Review (SRR)

A formal review designed to ensure that all stakeholders understand and agree on the system requirements and gain concurrence the developer is ready to proceed with the initial system design. They typically come with specific CDRL deliverables.

• Preliminary Design Review (PDR)

A formal review to ensure the preliminary design and system architecture are complete or being completed on track with the projected schedule. There is focus on technical confidence the work can be accomplished within the cost and schedule goals set forth at the beginning of the contract as well as focus on any risk and associated mitigation strategies. They typically come with specific CDRL deliverables.

• Critical Design Review (CDR)

A formal review to confirm the system design is stable and expected to meet the system requirements and performance goals set forth in the SRR and PDR. There is focus on status of goals within cost and schedule constraints as well as an outstanding risk that could prevent initial product baseline accomplishment. They typically come with specific CDRL deliverables.

• Test Readiness Review (TRR)

A formal review to verify that a system is ready to proceed to the test and evaluation stage of development. The review verifies that the test execution plan will test and gather the appropriate and required system information with focus on risk mitigation and quality of performance/test metrics. They typically come with specific CDRL deliverables.

• System Verification Review (SVR)

A formal review to verify the system performs in accordance with the system requirements agreed upon during the SRR and PDR. There is focus on system performance specifications and integration of those performance specifications into the functional baseline product.

• Program Management Review (PMR)

A structured program review conducted by the Program Manager (PM) with all the key stakeholders. These reviews are typically focused on a deep dive of program status and future efforts of the project. They typically come with specific CDRL deliverables.

• Technical Interchange Meeting (TIM)

More informal meetings that are typically reoccurring or conducted on an as needed basis where issues, problems, and concerns are discussed and addressed. Focused on problem solving or information exchange and typically involves those working directly with the project and problem specific stakeholders.

That’s a lot, right? And this list is not all inclusive. I left quite a few less common reviews off the list. But at least you have a starting point for what you can expect to see in a request for proposal (RFP), and you’ll be familiar with the term and its general purpose.

-----

IMPORTANT NOTE: Not all these reviews are appropriate for every contract but that won’t stop the USG from putting it in the RFP. That is why it is SO IMPORTANT that you read the RFP and the CDRLs for the reviews being requested of you. If you don’t think you need a review or there are too many of one kind, then you can submit a request for information (RFI) back to the contracting officer to have that request updated or changed. I’ve seen those conversations go well for businesses if you have reasonable rationale.

Keep Moving Forward,