How to use the Q&A forum on a partnering request
Last updated: November 2, 2026
What the Q&A is for
Every partnering request has a Q&A where you can ask the industry partner about their need before you submit a proposal. Use it to clarify the problem, the requirements or the scope, or to check whether your approach is relevant.
A few things to know before you post:
Questions and answers are public. Other innovators viewing the request can see them, and the industry partner's lead answers on the request page.
Halo reviews every question before it's posted. Questions that don't meet the guidelines below aren't published.
Don't include confidential information. Everything you write is visible to others.
Questions that get posted
The questions that get approved are specific, about this request, and answerable by the industry partner in a reply. They usually fall into one of these types.
Type | Example |
|---|---|
Clarifying a technical requirement | "For the 0.4 to 0.6 friction target, what test conditions should we assume: counterface, load, speed, wet or dry?" |
Understanding the system or process | "Is color added to the wet mix before the extruder, or applied after extrusion?" |
Checking whether an approach is in scope | "Would a surface treatment that provides a liquid barrier count as a treated nonwoven, or as an out-of-scope film?" |
Checking how TRL applies | "Would you consider a lab-validated platform if this project validated it in your manufacturing environment, or must line validation already exist?" |
Confirming relevance of your technology | "Would a fungus gnat lure and trapping device be relevant to this request?" |
Project terms | "Do you allow indirect costs in the budget?" "What provisions apply to IP?" "How many months should we propose?" |
Eligibility | "Can researchers at universities outside the U.S. apply?" |
It's fine to briefly mention what you work on, as long as it ends in a question the partner can answer. "We have a technology that does X. Is this within the scope of what you're looking for?" gets posted.
Questions that don't get posted
Asking to meet or be contacted
Requests for a call, a meeting, an email or a direct contact at the company aren't posted. This includes "Can we have a call if this fits?", "Please email me for more information" and "Is there a way to talk with someone before I submit?"
The fix is usually small. Two posts with the same technology description were treated differently: one ending in "Can we have a call if this fits?" was declined, and one ending in "Does this align with your needs?" was posted. Ask the question you'd ask on the call. If the partner wants to talk, they'll reach out after reviewing proposals.
Pitches and self-promotion
Posts that promote a product or offer a deal without asking anything about the request aren't posted. Neither are pitches for products unrelated to the request, or general outreach that isn't tied to a specific request. If you have something ready to offer outside a request, create a partnering listing instead.
Questions about Halo, not the request
Questions about how Halo works go to Halo's support team, not the industry partner, so they aren't posted. For example:
How do I submit a proposal? (Click Easy Apply on the request page.)
Should I include confidential information? (No. Only submit non-confidential information.)
Can I apply as a team or with another company?
Check the submission process article first, or email support@halo.science.
Asking who the partner is
Some partners post requests anonymously as a Private Company. Questions asking for the company's name aren't posted. The partner decides whether and when to identify themselves, typically if they choose to engage with you.
Repeat posts
If you post the same question twice, only one will appear. Post it once and allow time for review.
How to write a question that gets answered
Read the request first. Check the background, must-haves and out-of-scope list so you don't ask something already answered.
Ask one clear question. If you have two, keep them closely related. Long multi-part posts are harder to answer.
Be specific. Quote the requirement or number you're asking about, such as a target value, a TRL threshold or a material.
Keep any context short. One sentence about your approach is enough to make the question make sense.
End with a question the partner can answer in writing. Not a request to meet, and not an offer.
Leave out confidential details and contact information.
What happens after you post
Halo reviews your question before it's published. If it's posted, the industry partner's lead answers it on the request page, where everyone can see the answer. Questions about Halo's process may get a reply from Halo's support team instead.
Whether or not you ask a question, the way to be considered is the same: submit a proposal through Easy Apply before the deadline.
Questions about the Q&A? Email support@halo.science.