> For the complete documentation index, see [llms.txt](https://docs.iowacityrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iowacityrobotics.org/awards/submitted-awards/impact-award/judging-interview.md).

# Judging Interview

## **Judging Interview Overview**

The judging interview is the final stage of the Impact Award process and the only portion evaluated at the competition.

### **Interview Structure**

* Duration: 10-15 minutes
  * 7-minute presentation
  * 5-8 minutes for Q\&A
* Presenters: Only three students may participate, so it is crucial to select individuals who can confidently and clearly convey the team’s story.

### **Presentation Tips**

* Create an engaging and well-structured presentation that highlights:
  * Key outreach initiatives
  * Long-term impact on the community
  * Alignment with FIRST Core Values
* Use supplemental materials to reinforce key points, such as:
  * Poster boards
  * Slideshows
  * Handouts

### **Q\&A Preparation**

* Judges will ask follow-up questions about your team's work and impact.
* Practicing responses to common Q\&A questions (found on the next page) will help your team be prepared and confident.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.iowacityrobotics.org/awards/submitted-awards/impact-award/judging-interview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.