Assess whether the SBIR data-rights assertions are too aggressive (c84376)
August 31, 2026
SITUATION Past-performance volume owner is responsible for the SBIR data-rights assertions in a mid-tier integrator bidding a DoD IDIQ task order, using contract-mod scope creep log as the only working extract. A subcontracting goal the supply base cannot hit is what reset the timeline for this Government RFP Capture and Pricing file.
DECISION Past-performance volume owner in a mid-tier integrator bidding a DoD IDIQ task order must choose Pursue / Pursue with conditions / Partner / No-bid using contract-mod scope creep log after a subcontracting goal the supply base cannot hit.
HYPOTHESES TO TEST 1. Contract-mod scope creep log reads as Pursue once a subcontracting goal the supply base cannot hit is lined up to the same Government RFP population. 2. Contract-mod scope creep log is closer to Pursue with conditions after a subcontracting goal the supply base cannot hit; Pursue would over-claim this Capture and Pricing extract. 3. Partner is still live in contract-mod scope creep log for past-performance volume owner in a mid-tier integrator bidding a DoD IDIQ task order. 4. Contract-mod scope creep log is missing the fact past-performance volume owner needs after a subcontracting goal the supply base cannot hit; stop this Government RFP close.
ANALYSIS REQUIRED 1. Map Section L/M requirements in contract-mod scope creep log to evaluator notes after a subcontracting goal the supply base cannot hit. 2. Compare teaming and past-performance claims to what contract-mod scope creep log attaches. 3. Normalize pricing and exceptions against the solicitation that governs the SBIR data-rights assertions. 4. For this Government RFP Capture and Pricing file, read contract-mod scope creep log against a subcontracting goal the supply base cannot hit and write the one fact that would move the SBIR data-rights assertions for past-performance volume owner.
RECOMMENDATION Choose Pursue / Pursue with conditions / Partner / No-bid on this Government RFP / Capture and Pricing packet (contract-mod scope creep log after a subcontracting goal the supply base cannot hit). The follow-on Capture and Pricing action is what past-performance volume owner does next: implement the option, assign an owner, and log the missing fact.
COMMAND RETURNS - Bottom-line Government RFP option on the SBIR data-rights assertions, then the evidence in contract-mod scope creep log, then the action for past-performance volume owner - Hypothesis scorecard against contract-mod scope creep log: supported / rejected / untestable - Missing page in contract-mod scope creep log after a subcontracting goal the supply base cannot hit, if any - Regulatory or exam hook Capture and Pricing would cite
Explore more
More Government RFP prompts
- Assess whether the teaming structure creates OCI or workshare risk (3356b6)
- Assess whether a protest is rational after debrief after a data-rights
- Assess whether claimed differentiators would survive a fact check (2b8514)
- Assess whether Section M scoring math was applied consistently (ebb2c8)
- Assess whether to price to win or walk from a buy-in (b45bfa)
Explore related decision areas
See governed multi-model AI on your own prompt
Compare GPT-5, Claude, and Gemini side by side, with human review and a decision record built in.

