FAR 3.104 draws a boundary around procurement information

Market intelligence needs an information boundary

Federal-market teams can lawfully learn a great deal from public solicitations, forecasts, budgets, award notices, agency records, hearings, official data, company disclosures, and authorized conversations. FAR 3.104 marks a different category: covered contractor bid or proposal information and source-selection information before award. A capture platform should not treat every useful-looking datum as equally collectable.

The boundary belongs at intake, not only in a final legal review. Records should identify the source, access path, date, authorization, public status, handling restrictions, and reviewer. If provenance is missing or the information appears nonpublic, the system should support quarantine and escalation rather than enrichment, scoring, or broad distribution. Training and workflow prompts can reinforce that pause, but the retained review record is what lets the organization explain how the information was handled. That chain should remain reviewable during audits and investigations.

Knowing receipt is not cured by a data field

The official regulation addresses knowingly obtaining or disclosing covered information before award except as permitted by law. Copying information into a CRM, data lake, research note, model input, or collaboration channel does not change its character. Nor does a third-party label establish that the underlying source was authorized.

Product controls should support restricted access, non-editable provenance, retention decisions, deletion or preservation instructions, incident escalation, and documented review. Automated summaries and scoring deserve special scrutiny because they can spread protected substance while obscuring where it came from. The safe design goal is accountable handling, not a larger hidden dataset.

Public inference remains inference

Teams may form hypotheses from lawful public evidence about timing, priorities, incumbency, budgets, acquisition history, or likely competition. Those hypotheses should remain clearly labeled and sourced. A model confidence score does not convert an inference into an agency fact, and similarity to a protected category does not prove that protected information was accessed.

GovCon Market Brief separates observed public facts, company statements, analytical hypotheses, and nonpublic material. That separation lets a reviewer challenge a market conclusion without exposing the organization to unsupported claims about insider knowledge, evaluation preferences, competitor submissions, or pre-award decisions.

The rule does not decide the competition

FAR 3.104 establishes procurement-integrity duties and definitions; it does not determine opportunity fit, acquisition strategy, solicitation meaning, eligibility, responsibility, price, proposal quality, protest merit, or award outcome. Other law, solicitation terms, agency procedures, facts, and authorized officials govern those questions.

This analysis is intentionally limited to information provenance and handling in market-intelligence and capture systems. It does not address FAR Part 15 evaluation-factor design, evaluator workflow, source-selection authority, or tradeoff documentation. Those are separate acquisition-process questions and should not be collapsed into a capture-data rule.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

GovCon Market Brief will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.