Define the operating boundary
A useful definition names the triggering event, required inputs, governing source, accountable owner, decision or action, exception path, evidence retained, and downstream handoff. Buyers should adapt those elements to their own population, jurisdictions, policies, systems, and control model before writing requirements.
The most important distinction is between a label and an operational capability. A provider may document partner discovery teaming and subcontracting outreach while depending on customer-supplied policy, licensed content, third-party data, integration partners, manual review, or services. The demonstration should expose those dependencies rather than hiding them behind a completed interface.
What a demonstration should prove
- Begin with representative source records and a named policy, standard, or controlled rule.
- Show the normal path, an ambiguous case, missing data, an exception, an override, and a material source change.
- Identify who can change rules, who can approve or reject, and how accountability is preserved.
- Trace every output back to inputs, versions, timestamps, user actions, and governing evidence.
- Export the resulting record and reconcile it with downstream systems and retained obligations.
Authority and operating context
FAR Part 9 — Contractor Qualifications
FAR Part 9 — Contractor Qualifications defines an authoritative part of the federal acquisition, award-data, small-business, vehicle, or contract-administration environment. The record must be read with its current text, scope, status, and procurement-specific facts. Part 9 addresses responsibility and other qualification matters. Public data and vendor profiles cannot make the contracting officer's procurement-specific determination.
FAR Part 19 — Small Business Programs
FAR Part 19 — Small Business Programs defines an authoritative part of the federal acquisition, award-data, small-business, vehicle, or contract-administration environment. The record must be read with its current text, scope, status, and procurement-specific facts. Part 19 governs federal small-business acquisition procedures. A database label does not establish size, affiliation, certification, or set-aside eligibility for a procurement.
FAR 3.104 — Procurement Integrity
FAR 3.104 — Procurement Integrity defines an authoritative part of the federal acquisition, award-data, small-business, vehicle, or contract-administration environment. The record must be read with its current text, scope, status, and procurement-specific facts. Market research and relationship work must remain separate from protected source-selection and contractor-bid information. Public records do not authorize access to nonpublic information.
FAR Subpart 9.5 — Organizational and Consultant Conflicts of Interest
FAR Subpart 9.5 — Organizational and Consultant Conflicts of Interest defines an authoritative part of the federal acquisition, award-data, small-business, vehicle, or contract-administration environment. The record must be read with its current text, scope, status, and procurement-specific facts. Potential organizational conflicts require procurement-specific analysis and mitigation decisions. A company relationship graph or public award history is only a research input.
SBA Size Standards and 13 CFR Part 121
SBA Size Standards and 13 CFR Part 121 defines an authoritative part of the federal acquisition, award-data, small-business, vehicle, or contract-administration environment. The record must be read with its current text, scope, status, and procurement-specific facts. Size depends on the procurement's NAICS code, applicable threshold, receipts or employees, affiliates, and timing. A profile label or historical award does not decide size.
SBA Prime and Subcontracting Guidance
SBA Prime and Subcontracting Guidance defines an authoritative part of the federal acquisition, award-data, small-business, vehicle, or contract-administration environment. The record must be read with its current text, scope, status, and procurement-specific facts. Prime and subcontract opportunities have different counterparties, notices, obligations, and selection processes. A teaming lead is not a government opportunity or award.
GSA Multiple Award Schedule
GSA Multiple Award Schedule defines an authoritative part of the federal acquisition, award-data, small-business, vehicle, or contract-administration environment. The record must be read with its current text, scope, status, and procurement-specific facts. A schedule contract, SIN, modification, team arrangement, reseller relationship, and individual order each have distinct scope and evidence. One cannot be inferred from another.
Operating domains
Qualification and go/no-go governance
The accountable decision to pursue, hold, partner, or decline based on scope, customer, vehicle, eligibility, capabilities, capacity, competition, economics, risk, and evidence.
Capture planning and stakeholder strategy
The governed pursuit process connecting win themes, customer needs, competitive position, actions, reviews, relationships, teaming, solution, price, and solicitation readiness.
Contract vehicle and task-order access
The evidence needed to distinguish a vehicle, contract, SIN or scope, holder status, team arrangement, ordering rules, task-order opportunity, and entity authority to compete.
Teaming and subcontracting
The partner-discovery, due-diligence, role, workshare, agreement, flowdown, proposal, and post-award process connecting primes, subcontractors, mentors, protégés, and channel partners.
Registration, representations, and small-business status
The controlled maintenance of entity registration, identifiers, representations, certifications, size facts, NAICS context, exclusions, credentials, and renewal dates without treating self-reported data as a procurement determination.
Evidence and comparison limits
Official provider documentation can establish product positioning. Provider confirmation can clarify package or availability. Independent observation requires a disclosed scenario, environment, date, inputs, and reproducible result. None of those sources alone establishes buyer-specific legal, clinical, regulatory, quality, or operational fitness.
Buyer questions
- What exact outcome and evidence should partner discovery teaming and subcontracting outreach produce?
- Which source, version, and customer facts govern the workflow?
- Which decisions remain human and who is accountable for them?
- What is native, configured, integrated, service-delivered, or planned?
- How does a changed source affect open and historical records?
Recent changes
SBA size research begins with the solicitation's NAICS code and current entity facts — SBA size research begins with the solicitation's NAICS code and current entity facts matters because federal market decisions depend on source identity, lifecycle stage, exact dates, and authority—not just a surfaced record or vendor label.
SBA SubNet separates prime-led subcontracting leads from government solicitations — SBA SubNet separates prime-led subcontracting leads from government solicitations matters because federal market decisions depend on source identity, lifecycle stage, exact dates, and authority—not just a surfaced record or vendor label.
GovDash spans opportunity discovery, capture, and proposal response — GovDash spans opportunity discovery, capture, and proposal response matters because federal market decisions depend on source identity, lifecycle stage, exact dates, and authority—not just a surfaced record or vendor label.
FAC 2026-01 resets the current FAR baseline for acquisition research — FAC 2026-01 resets the current FAR baseline for acquisition research matters because federal market decisions depend on source identity, lifecycle stage, exact dates, and authority—not just a surfaced record or vendor label.