# After the Hack

Don't forget to see our [end of event check-list](/general-information/after-the-event.md) before you focus on hardware specific things here.

### Connect Participants to Resources

* Direct hackers to local campus makerspaces or fabrication lab.
* Publicize relevant campus classes (e.g., in engineering, design, or applied arts) that build upon the skills used at the hackathon (e.g. repost course advertisements from volunteer faculty)
* Highlight other local or national hardware-focused events, such as specialized buildathons or technical conferences.
* Remind hackers to document their prototype, the story, and evidence of their build to support their personal portfolio for future jobs

### Future Marketing

Make sure to gather high-quality photos and videos of the working prototypes during judging.

### Lab Maintenance and Restock

As part of the event wrap-up, run your end-of-event checklist for all hardware components and tools. Filter out broken or malfunctioning equipment and components (e.g., melted breadboards, shorted microcontrollers). Inventory all remaining functional equipment. Use the damage report and inventory list to inform the purchasing budget for the next event (i.e., you know exactly how many Arduinos you need to buy and replace).

Finally, conduct a thorough cleanup of all borrowed spaces (makerspaces, classrooms). Follow the post-event checklist to ensure all tools are returned, supplies are put away, and the space is left in better condition than you found it to ensure the chance of relying on the space (or more) for future events.

### Event Evaluation

Evaluation should be based on your event's primary goals defined during initial planning. Develop an evaluation plan early to collect data leading up to and throughout the event weekend.

#### Additional Data Sources to Consider

| Area of Interest | Examples of Metrics                                                             |
| ---------------- | ------------------------------------------------------------------------------- |
| Learning         | Workshop attendance and effectiveness ratings.                                  |
| Theme            | Participant feedback on the theme's relevance and engagement level.             |
| Logistics        | Feedback on component availability, variety, and lab accessibility.             |
| Mentors          | Mentor helpfulness ratings and assessment of sufficient experience at stations. |

Distribute a concise, goal-focused survey immediately after the event. Collect data from all roles (participants, volunteers, judges, mentors, organizers, sponsors), customizing questions where applicable.

Document the number of total participants, diversity breakdown, and percentage of first-time hackers.

Document checkout history, finalized component lists, and damage reports to note trends and inform future lab purchases.


---

# Agent Instructions: 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:

```
GET https://guide.mlh.io/hardware-hackathon-guide/after-the-hack.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.