Frequently Asked Questions

Two Q&A Sessions have occurred:
Session #1: April 28, 2023 | Video | SlidesTranscript

Session #2November 8, 2023 | Video | Slides | Summary Document (Updated 11/16/23)

Questions received via email will be added to the FAQ below:

Most undergraduate and graduate Students attending an accredited, U.S.-based university are eligible to participate. Please visit the Eligibility section on the Challenge Guidelines Document for full eligibility requirements.

Please visit the Eligibility section on the Challenge Guidelines Document for eligibility requirements, including full information on participation for international universities and foreign students attending U.S.-based universities.

Please visit the Eligibility section on the Challenge Guidelines Document for full eligibility requirements.

Federal Co-Op/Pathways Interns may participate in HuLC anytime when they are on Leave Without Pay (LWOP).
Federal Co-Op Interns can also participate in HuLC if the following criteria are met:

  1. HuLC funds cannot be used to support travel for Civil Service Interns who are operating in an active federal work status (i.e., during a timeframe when they are working and receiving pay).
  2. During times of active work at a government agency, federal co-op/Pathways interns may participate in HuLC only if their paid work/research/project is not directly related to their HuLC project. (e.g.: An intern who is conducting research on dust mitigation COULD NOT contribute to a HuLC team).

The forum competition is judged by a NASA and industry subject matter experts. Please see the About Us page on the website for more information on the judging panel.

Yes, multiple teams from the same university can submit separate proposals for the HuLC competition, and multiple teams from the same university may move on to the next round of the competition if their proposals merit selection into the program.

If all of the universities are U.S.-based, then no, you do not need an advisor from each university. However, one of the universities must be designated as the “lead” university. The primary point-of-contact advisor must come from the lead university, and all correspondence would occur through that advisor and the team lead. The joint team will receive one stipend (the same as if the team were from a single university), and it will be sent to the lead institution. It is up to the lead institution to determine how the stipend will be distributed.

He/she can mentor the team as much or as little as desired. Some faculty take a very hands-off approach, while others are actively involved in all aspects of the team’s research and submissions. The HuLC program allows faculty to be involved in the students’ work and product as much as they would like to, but the expectation is that the students are doing the bulk of the work.

Faculty advisors of finalist teams will be responsible for accepting the stipend, submitting any university paperwork we require for the competition, and working with the university to make any necessary arrangements for the team to attend the HuLC Forum. The advisor also ensures that teams submit their deliverables by the established deadlines and that Forum registration is conducted on time.

Faculty advisors must also sign the first page of their team’s proposal to acknowledge they’ve reviewed and approve of the submission. Advisors of finalist teams must also fill-out and submit the Advisors Approval Attestation form for their team’s Technical Paper.

Yes, however, each team will require a “primary” faculty advisor who will serve as the team’s main point-of-contact alongside the student team lead.

Yes, absolutely. We understand that sometimes things change between the time proposals are submitted and the time the technical paper is due. We just ask that you list every person who contributed to your project in the final technical paper.

Working with industry in a small capacity is acceptable, as long as this remains a student project with the students doing the bulk of the work.  Teams can work with industry to receive mentorship, sponsorships, donations (cash or materials/supplies), or in-kind use of testing facilities. 

A photo of the team members incorporated into the video is fine. Individual photos are also acceptable.

The HuLC Competition will be held at or near NASA’s Marshall Space Flight Center in Huntsville, Alabama in June 2024. Visit the Challenge Details page for specific dates.

More information on Forum logistics, registration, and hotel reservations will be made available to finalist teams.

It is possible that individuals may need to cover some of the Forum costs.  Each team will receive a $7,000 award to facilitate full participation in the HuLC Competition. Although it is ultimately up to each university / advisor on how to best distribute the stipend, part of the stipend is intended to help offset some of the costs associated with participating in the Forum.

No. The HuLC Forum is closed to the public. Only finalist team members and advisors may attend the Forum.

No.  Teams are not permitted to use technical advisors who work for NASA, either as civil servants or contractors. 

A post-doc can serve as your official advisor, as long as he/she is employed by the university to teach or conduct research, and can manage a stipend in an official capacity behalf of your team.

There is no limit to the number of students who can participate throughout the year on a team.

However, if any individual finalist team desires to bring more than 10 students to the HuLC Forum, permission must be requested from the HuLC Program Staff prior to registering. Requests will be reviewed, and approvals will be granted on a case-by-case basis, space permitting. 

Yes, there can be a mix of levels within a team. We categorize an “undergraduate team” as one having a majority of team members who are undergraduates. (Similarly, a “graduate team” has a majority of students who are graduate students.)

Yes, as long as they were students during the Fall semester when you begin working on the project. If they are an undergraduate moving on to graduate level work, they may still compete as part of an undergraduate team without changing the team’s status.

Yes, visit the Challenge Details page to view the most up-to-date Challenge Guidelines document for full details on each deliverable.

No. The university must fill out the W9, as we are only able to issue stipend checks directly to universities (not to individual student organizations).

However, if you are selected as a finalist, we can mail the check to any specific mailing address at the university, including a student club address (eg. SEDS).

There is a section on the bottom of the online proposal submission form that allows you to enter in a specific mailing address of your choosing, to ensure the stipend check reaches the correct point of contact that can deposit the stipend into the correct university account.

It is the responsibility of each team to appropriately handle copyright issues related to anything you choose to use in your presentation (including, but not limited to: music, images, graphics, and photos). Neither NASA nor NIA can grant permission for you to use copyrighted material.

Any graphics software will suffice. Please do not include hand-drawn graphics in the proposal.

While we expect that your concept will evolve as you continue working, you should be prepared to explain and justify that evolution in your final technical paper and presentation.

You can absolutely submit your design as an abstract to other conferences, as long as it is presented to the public at the HuLC Forum first.

It’s also okay to present the work at your university (to other students/faculty/internal school events) before HuLC.

Your quad chart’s cost and schedule should refer to the entire concept’s cost and schedule (i.e., for NASA’s path-to-adoption).

Teams can generate graphics for their HuLC projects in any way they want, as long as copyright and trademark laws are followed. When using AI generated files, teams must also abide by the software’s polices on use and ownership of images.