> For the complete documentation index, see [llms.txt](https://guide.mlh.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.mlh.io/general-information/event-logistics/set-up-your-event.md).

# Set Up Your Event

#### Things to Print Before

* Signage -some pointing left, right, or blank so you can fill in the arrow as you place them
  * Checkin (include some pointing up to put on glass doors or in an elevator)
  * Bathrooms
  * Hacker Space
  * Food/Snacks
  * Mentors
  * Organizers Only
  * Do Not Enter
  * Workshops
* Lanyards- having different colors or designs helps differentiate hackers from staff
  * Organizers
  * Volunteers
  * Mentors
  * Judges
  * Sponsors
  * Hackers
  * Blank(if the above run out for some reason have 10-15 blank)
* Parking Passes(if needed)
* Minor Forms(if needed)
* Table Numbers (for Judging) - better to over than under print these

#### Before the Event

Here are common supplies you should have for your hackathon

* First Aid Kit 
* Permanent Markers 
* Paper 
  * Last minute signage 
  * Give out wifi 
  * Parking passes 
  * Link to Discord 
* Box Cutters / Scissors 
  * To open all your/your sponsors swag 
* Painters Tape 
  * Do not use Scotch tape on paint. It will rip away the paint and make your venue mad. It also is not likely to last the full event 
* Gaffer's Tape 
  * Secure electrical cords if they absolutely have to be across walkways 
* Duct Tape 
  * Jack of all trades tape. DO NOT USE ON PAINT

It's important to check that the various tools you're using for your event are ready to go day-of. A dry run of the whole event largely can also help your team be prepared to handle everything and let you know about any bottleneck that might create problems later on.

#### Day-Of

* [ ] Set up tables and chairs
* [ ] Make sure WiFi is working (or set it up)
* [ ] Check power at every table (may need to lay cable)
* [ ] Check-in station
* [ ] Sponsor and swag area
* [ ] Hackathon space
* [ ] Speaking area
* [ ] Judging space
* [ ] Hardware room or table 
* [ ] Food area
* [ ] AV and tech
* [ ] Relaxation area (if providing)
* [ ] Help desk/info center
* [ ] Meditation room

####  

##


---

# 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://guide.mlh.io/general-information/event-logistics/set-up-your-event.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.