TPOC (Topic Point of Contact)

What is a Topic Point of Contact (TPOC)?

The Topic Point of Contact is the government technical lead behind a specific SBIR or STTR topic. They are usually the program engineer, scientist, or technical manager inside the sponsoring agency or program office who proposed the topic, defined the technical objective, and will be the eventual customer for any Phase III follow-on work.

Definition

A TPOC is the named government technical author of an SBIR/STTR topic. The TPOC sits inside the sponsoring program office — for example, an Army program executive office, an Air Force lab, a NASA mission directorate, or an NIH institute. The TPOC drafts the topic's technical objectives, defines the deliverables, and is the human inside the agency who actually wants the technology built. During the pre-release window, the TPOC is reachable for direct technical discussion. Once the topic opens, contact is restricted to formal channels.

Key Points

• Pre-release is the leverage window. Most DOD components release SBIR/STTR topics on a 30-to-60-day pre-release window before formally opening for submissions. During pre-release, offerors can email or call the TPOC directly with technical questions, clarifications, and informal feasibility discussions.
• Open-period blackout. Once the topic opens, all direct contact with the TPOC and other government personnel is prohibited. All questions go through a public Q&A system, and the answers are visible to every other offeror.
• TPOC ≠ contracting officer. The TPOC owns the technical content of the topic but does not award the contract. The contracting officer handles award authority, terms, and compliance.
• Phase III implication. Because the TPOC is the technical sponsor of the topic, they are often the most plausible Phase III customer. A strong Phase I/II that lines up with the TPOC's actual program is the canonical path to a Phase III sole-source contract.

Practical Examples

1. DOD SBIR pre-release call. A small business sees an Air Force SBIR topic on autonomous ISR data fusion enter pre-release. They email the TPOC, ask three specific questions about the operational use case and current capability gap, and learn that the topic is sponsored by a specific Air Force lab with an existing program of record looking for transition partners. That conversation reshapes the Phase I technical approach and the Phase III commercialization narrative.
2. NIH topic clarification. An NIH SBIR topic mentions a specific disease area but is ambiguous about whether translational research or clinical-stage work is in scope. The applicant contacts the listed program officer (the NIH analogue of a TPOC) during the pre-release equivalent to confirm scope, then writes a proposal that hits exactly what the institute is trying to fund.
3. Topic with no TPOC engagement. A small business writes a Phase I without ever contacting the TPOC and submits a technically strong but mis-targeted proposal. It scores well on technical merit but is rejected as "not aligned with current program priorities" — a common signal that the proposal solved a different problem than the one the TPOC was actually trying to fund.