Jackson SenczyszynDuring the pre-release period of a DoW SBIR/STTR release, topic authors’ names and contact details are published and companies may contact them directly with technical questions about a specific topic. The BAA limits those questions to understanding the topic’s requirements. You may not ask for advice on your solution approach or send the topic author additional material. Once the release opens, direct contact ends, and questions move to the public, anonymous DSIP Topic Q&A until two weeks before close. The window is for learning the problem, not for pitching the answer.
Most companies treat pre-release as a head start on writing. The better ones treat it as the only time in the entire cycle they can learn, directly from the government engineer or scientist who wrote the topic, what problem the topic is actually trying to solve.
Those are different uses of the same three weeks, and they produce very different proposals.
What does the BAA actually allow?
The fiscal year 2026 DoW SBIR/STTR BAA sets out the rules in its communications section. In plain terms:
- During pre-release, topic authors’ contact information is published with each topic, and you may call or email them to ask technical questions about that topic.
- Those questions must be limited to specific information related to understanding the topic’s requirements.
- You may not ask for advice or guidance on your solution approach, and you may not submit additional material to the topic author.
- If something shared in a direct conversation is needed to prepare a proposal, it is posted publicly in the DSIP Topic Q&A so every proposer has it.
- Once the release opens, no further direct contact is allowed, except a topic author answering a question you asked during pre-release.
- After the close date, no communication of any kind.
The Topic Q&A runs alongside all of this. It opens on the pre-release date, stays open until two weeks before the topic closes, is anonymous, and publishes every answer for everyone. It is for technical questions only; questions about eligibility, page counts, budgets, or deadlines are not answered there.
What are you trying to learn?
The line in the BAA is between understanding the requirement and getting help with your answer. Stay on the first side and there is a great deal to learn.
The problem behind the topic. Topics are written in compressed, formal language. The author usually has a specific operational problem in mind. Understanding it in their words is the single most valuable thing you can take away.
The environment. Where would this be used, by whom, under what conditions? A topic that says “operationally relevant environment” means something specific to the person who wrote it.
What has already been tried. If current approaches fall short, knowing where they fall short tells you what the topic is really asking for.
The constraints that matter most. Size, weight, power, interfaces, data, and integration. Topics often list several; the author can tell you which ones are firm.
What success would look like. In the topic’s own terms, what would a strong Phase I result demonstrate?
Before you ask a question, imagine the answer posted publicly for every other proposer, because it may be. If the question only makes sense with your solution attached, it is about your approach, not the topic’s requirement, and it is on the wrong side of the line.
What crosses the line?
- Pitching. Describing your approach and asking whether it is what they want is asking for guidance on your solution.
- Sending material. Slides, white papers, and capability briefs are additional material, and the BAA says you may not send them.
- Asking about competitors or who else has called. The author cannot share that and should not be asked.
- Treating the call as a relationship meeting. Pre-release contact is tied to a specific topic. It is not a general business development channel, and using it as one damages the goodwill you will need later.
- Calling after the release opens. Direct contact ends on the open date. From then on, it is the Topic Q&A.
How should you use the window?
Read the topic closely before you contact anyone. Know exactly what the text says, so your questions are about what it does not say.
Ask few questions, and make them good. Topic authors hear from many companies. Short, specific technical questions get better answers than a long list.
Listen for the decision you need to make. Sometimes the most useful outcome is learning that the problem is not one you solve. That is a no-bid decision made in week one instead of week five, and it is worth the call on its own.
Write down what you learn. Keep a record of what you asked and what you were told. It helps your team, and it keeps your communications on the record.
Watch the Topic Q&A. Other companies’ questions, and the answers, are public. They often tell you as much as your own call.
Three questions before the next pre-release
Do you have a short list of topics from offices you already want to work with, so you can spend the window on the right ones? Can every question you plan to ask be answered without describing your solution? Do you know the date the window closes for each topic you care about?
If the answers are yes, the window will change your proposal. If not, it will mostly change your calendar.
For how the monthly release calendar fits together, see what the same-day close and open means.
Sources: DoW 2026 SBIR/STTR BAA, Release 6 Preface (Amendment 3, September 2, 2026), Section 6.2. Future BAAs may change these rules; read the communications section of the current BAA before contacting a topic author.