A productive teaming discussion connects an opportunity to specific work, responsible parties, and evidence. General statements of interest can start a relationship, but they do not establish who will prepare a technical response, supply an item, or own a deliverable. This checklist is editorial guidance for structuring the first substantive discussion.

Identify the arrangement being discussed

FAR 9.601 describes contractor team arrangements that include a partnership or joint venture acting as a potential prime, and a potential prime agreeing with other companies to act as subcontractors for a specified government contract or acquisition program. [^1] A preliminary introduction is not proof that either arrangement exists. Use precise language about what has been agreed and what remains exploratory.

Build a scope map

Start with the opportunity reference and a short list of work packages. For each package, record the proposed lead, supporting participants, deliverables, and interfaces. In a hypothetical facility requirement, technical review, field verification, and product supply could be separate packages even when they support the same project. The map should identify handoffs instead of treating related capabilities as identical responsibilities.

Request evidence that matches the role

Ask for the information needed to assess the proposed contribution: relevant qualifications, availability, scope experience, or product documentation as appropriate. Distinguish an individual's prior experience from a company's past performance. Obtain permission before naming people or including their materials in a proposal. Keep unsupported statements out of shared drafts so they do not become harder to correct later.

Set proposal ownership and timing

Assign an owner to each response section and identify who checks technical consistency, pricing assumptions, and submission readiness. Record the latest solicitation amendment and the deadlines for inputs. Keep a decision log for changes to the proposed scope. If an input depends on information that has not arrived, identify the dependency rather than disguising it as a completed commitment.

Record what the meeting actually decided

Close with a short action list covering the next document, owner, due date, and unresolved question. Separate a decision to continue discussions from an executed agreement or authorization to represent another company. Commercial terms, confidentiality, exclusivity, and contract responsibilities belong in the appropriate agreements and review process, not assumptions in a meeting summary.

A clear scope map gives each participant a practical basis for deciding whether the opportunity fits. It also makes the next discussion more focused: the team can review a specific work package and its evidence instead of repeating a general capabilities presentation.

Related capability: prime contractor teaming.