Problem briefBid eligibility
Can you support the requirements behind this opportunity?
Review compliance requirements and evidence before committing proposal and engineering resources to a pursuit.
Pursuit review
Review eligibility requirements before committing bid resources.
- 01 Solicitation Read
- 02 Requirement Interpreted
- 03 Current status Reviewed
- 04 Decision Owned
- 05 Pursuit Decided
01Source requirement
Review the governing requirement.
These pages explain the source requirement and its practical implications. A contracting officer defines solicitation requirements. Assessors, customers, and counsel make their own determinations.
- 01
The opportunity record is the starting point. Requirements can appear in clauses, attachments, statements of work, amendments, and prime flowdowns.
DFARS 252.204-7012 official sourceDFARS 252.204-7020 official sourceDFARS 252.204-7021 official source
- 02
Where DFARS 252.204-7021 applies, it requires the contractor to have and maintain a current CMMC status at the level stated in the contract for systems used in performance, and it includes subcontract flowdown conditions.
- 03
DFARS 204.7302 says contractors subject to NIST SP 800-171 under DFARS 252.204-7012 need a current Basic Assessment at time of award unless a lesser timeframe is specified in the solicitation.
DFARS 204.7302 official sourceNIST SP 800-171 Rev. 3 official source
BoundaryResponsibility
Prepare the record for review.
Deep Fathom organizes the requirements review and supporting evidence. The company decides whether to bid. The contracting officer and customer determine their own requirements and approvals.
02Decision guides
Answer the buyer question before the decision.
Short, source-backed answers for teams reviewing a requirement, making a representation, or committing time to a pursuit.
03Platform workflow
Assign the work. Keep evidence with the requirement.
Deep Fathom records requirements, accountable owners, work, evidence, and decisions so the team can prepare for the next review.
- Record clauses and obligations as assigned work with evidence requirements.
- Connect evidence to the exact claims the pursuit team must support.
- Update the record when the opportunity, scope, or owners change.
Review bid requirements
Review the requirements before you commit bid resources.
Tell our team about the opportunity, deadline, and qualification question. We will show how Deep Fathom can organize the requirements, work, and evidence for the pursuit decision.
- The solicitation, customer request, or pursuit deadline
- The requirement that may block eligibility or award
- The bid decision the team needs to make
Request a platform evaluation
Reviewed by our teamProvide the details listed at left. Our team will review them, clarify what the platform can support, and recommend an evaluation step.
Do not include CUI, credentials, or export-controlled data.
05Related reading
Related resources
SourcesReviewed
Read the governing material.
- DFARS 252.204-7012Safeguarding covered defense information and cyber-incident reporting clause.Official source ↗
- DFARS 252.204-7020NIST SP 800-171 DoD assessment requirements, including Basic Assessment and subcontract provisions.Official source ↗
- DFARS 252.204-7021Current CMMC status, annual affirmation, and CMMC flowdown requirements where the clause applies.Official source ↗
- NIST SP 800-171 Rev. 2The 110 security requirements incorporated by reference into 32 CFR part 170 and assessed at CMMC Level 2.Official source ↗
- NIST SP 800-171 Rev. 3The current NIST publication. DFARS 252.204-7012 points at the revision in effect at time of solicitation, while CMMC assessments are conducted against Revision 2.Official source ↗
- DFARS 204.7302Policy requiring a current Basic NIST SP 800-171 DoD Assessment at award when DFARS 252.204-7012 applies.Official source ↗