Assess whether the SBIR data-rights assertions are too aggressive (f29793)
August 31, 2026
SITUATION After a data-rights assertion the customer already rejected last year, teaming agreement with IP and workshare holes is what capture manager can touch in a lab competing a Phase II SBIR. Government RFP will live with Pursue versus Pursue with conditions on this Protest and Modifications file.
DECISION Capture manager in a lab competing a Phase II SBIR must choose Pursue / Pursue with conditions / Partner / No-bid using teaming agreement with IP and workshare holes after a data-rights assertion the customer already rejected last year.
HYPOTHESES TO TEST 1. Capture manager can defend Pursue from teaming agreement with IP and workshare holes after a data-rights assertion the customer already rejected last year in a Government RFP challenge. 2. Capture manager cannot defend Pursue from teaming agreement with IP and workshare holes; Pursue with conditions is what the extract actually supports after a data-rights assertion the customer already rejected last year. 3. A data-rights assertion the customer already rejected last year never reached the population in teaming agreement with IP and workshare holes — reopen intake, do not close the SBIR data-rights assertions. 4. Two facts in teaming agreement with IP and workshare holes after a data-rights assertion the customer already rejected last year conflict for capture manager; hold this Protest and Modifications file.
ANALYSIS REQUIRED 1. Normalize pricing and exceptions against the solicitation that governs the SBIR data-rights assertions. 2. Score competitive posture if capture manager pursues, partners, or no-bids. 3. Test OCI, QASP, and mandatory evaluation rights a lab competing a Phase II SBIR cannot waive quietly. 4. For this Government RFP Protest and Modifications file, read teaming agreement with IP and workshare holes against a data-rights assertion the customer already rejected last year and write the one fact that would move the SBIR data-rights assertions for capture manager.
RECOMMENDATION Choose Pursue / Pursue with conditions / Partner / No-bid on this Government RFP / Protest and Modifications packet (teaming agreement with IP and workshare holes after a data-rights assertion the customer already rejected last year). The follow-on Protest and Modifications action is what capture manager 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 teaming agreement with IP and workshare holes, then the action for capture manager - Hypothesis scorecard against teaming agreement with IP and workshare holes: supported / rejected / untestable - Owner and next date for capture manager in a lab competing a Phase II SBIR - What changes the SBIR data-rights assertions if a data-rights assertion the customer already rejected last year is later withdrawn
Explore more
More Government RFP prompts
- Assess whether to price to win or walk from a buy-in (117fb0)
- Assess whether past performance will score or be deemed not relevant (ac5a85)
- Assess whether to bid as prime, sub, or no-bid (f332ef)
- Assess whether the bid is compliant enough to survive a responsiveness check
- Assess whether to bid as prime, sub, or no-bid (605fa3)
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.

