Problem briefBid eligibility

Can you support the requirements behind this opportunity?

Review solicitation requirements, package access, qualifications and supporting evidence before committing proposal and engineering resources.

Review bid requirements Explore the procurement guides

Pursuit review

Review eligibility requirements before committing bid resources.

Requirement view
  1. 01 Solicitation Read
  2. 02 Requirement Interpreted
  3. 03 Current status Reviewed
  4. 04 Decision Owned
  5. 05 Pursuit Decided
A go/no-go decision needs the source requirement, current status, accountable owner, and supporting evidence in the same record. Deep Fathom requirement record

01Choose the task

Start with the decision in front of you.

Choose a task for the recommended starting point. Open the complete group only when you need a narrower guide or working resource.

01

Review the package

Find the governing documents, locate the conditions, and separate what is stated from what still needs clarification.

Start withHow to review a government solicitation before you decide to bid

Likely next

View all 8 guides
02

Obtain the package

Identify the access gate, the accountable person, and the receiving environment before the files arrive.

Start withDD Form 2345 and controlled package access

Likely next

View all 6 guides
03

Decide and revisit

Record the decision basis, then reopen it when an amendment or changed condition reaches the pursuit.

Start withBid eligibility checklist for defense solicitations

Likely next

View all 6 guides
04

Understand the market

Use public records to frame the market question without turning a code, count, or prior award into a qualification claim.

Start withSources sought versus a solicitation: decide what response to prepare

Likely next

View all 8 guides

02Source 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.

  1. 01

    Eligibility includes technical and participation conditions. The retained August 2026 F-16 housing notice requires engineering source approval, with a qualification path for eligible sources, separately from its cybersecurity conditions.

    F-16 housing RFP SPRWA1-26-R-0017 official source

  2. 02

    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

  3. 03

    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.

    DFARS 252.204-7021 official source

  4. 04

    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 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.

03Decision 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.

01 Does this solicitation require CMMC?Read the solicitation and attachments for the governing CMMC requirement. The incorporated requirement establishes the level, timing, and scope to review. 02 Is CMMC required at proposal or award?The governing clause and solicitation language control the timing. Verify that timing for the specific requirement. 03 Can I bid without CMMC?Start with the specific opportunity and whether its requirements apply to the planned performance scope.

04Platform 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.

05 / 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

Do not include CUI, credentials, or export-controlled data.

06Related reading

Related resources

Access to the drawings is a readiness milestoneA retained Navy RFQ shows why drawing access needs an owner and a place on the pursuit schedule. CUI boundary scopingReview which systems and information flows belong in the assessed environment.

SourcesReviewed

Read the governing material.