Assess whether the SBIR data-rights assertions are too aggressive (642738)

SITUATION After a key person who just resigned, contract-mod scope creep log is the working evidence for capture manager in an incumbent defending a recompete with thin past performance. Decide whether the SBIR data-rights assertions are too aggressive using only what contract-mod scope creep log actually supports.

DECISION Capture manager in an incumbent defending a recompete with thin past performance must choose Pursue / Pursue with conditions / Partner / No-bid using contract-mod scope creep log after a key person who just resigned.

HYPOTHESES TO TEST 1. Authorize Pursue now; contract-mod scope creep log already has the discriminator after a key person who just resigned. 2. Keep Pursue with conditions in force until contract-mod scope creep log is completed after a key person who just resigned for capture manager. 3. Treat contract-mod scope creep log as Partner because both readings appear after a key person who just resigned. 4. Refuse a Government RFP close: capture manager does not have the decision the SBIR data-rights assertions turns on in contract-mod scope creep log.

ANALYSIS REQUIRED 1. Test OCI, QASP, and mandatory evaluation rights an incumbent defending a recompete with thin past performance cannot waive quietly. 2. Map Section L/M requirements in contract-mod scope creep log to evaluator notes after a key person who just resigned. 3. Compare teaming and past-performance claims to what contract-mod scope creep log attaches. 4. For this Government RFP Performance and Teaming file, read contract-mod scope creep log against a key person who just resigned 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 / Performance and Teaming packet (contract-mod scope creep log after a key person who just resigned). The follow-on Performance and Teaming 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 contract-mod scope creep log, then the action for capture manager - Hypothesis scorecard against contract-mod scope creep log: supported / rejected / untestable - Missing page in contract-mod scope creep log after a key person who just resigned, if any - Regulatory or exam hook Performance and Teaming would cite