# Conciseness Source: https://docs.hackersquad.io/Conciseness This page is under construction. ## Under construction This page is under construction. See [Host an Event](/event-managers/host-an-event) or [View Projects](/event-managers/view-projects) in the meantime. # Resources Source: https://docs.hackersquad.io/Resources This page is under construction. ## Under construction This page is under construction. See [Host an Event](/event-managers/host-an-event) or [View Projects](/event-managers/view-projects) in the meantime. # Support the Community Source: https://docs.hackersquad.io/Support the Community This page is under construction. ## Under construction This page is under construction. See [Host an Event](/event-managers/host-an-event) or [View Projects](/event-managers/view-projects) in the meantime. # Create a team Source: https://docs.hackersquad.io/builders/create-a-team Find teammates, use the HackerSquad Discord effectively, and build a balanced team for your hackathon project. Hackathons move quickly, so finding the right teammates early can make a big difference. A strong team usually combines a clear project idea with a mix of skills that helps the group actually ship something by the end of the event. ## Use Discord to find teammates HackerSquad has a Discord where builders can connect with other participants before and during the hackathon. Use Discord to post: * Your project idea * Your technical skills * What kind of project you want to work on * What kind of teammates you are looking for This makes it easier for other builders to understand whether they are a good fit for your team. ## What to include in your post When you introduce yourself in Discord, be specific enough that people know how to respond. A strong post usually includes: * Your name or handle * Your core skills, such as frontend, backend, AI, design, or product * Whether you already have an idea or want to join someone else's * The kinds of tools or technologies you want to use * The type of teammate you are hoping to find The more clearly you explain your skills and interests, the easier it is for compatible teammates to reach out. ## Good team formation advice Try to build a team with complementary strengths. A good hackathon team does not need to be large, but it should cover the work needed to design, build, and explain the project clearly. Helpful team qualities often include: * At least one person who can build quickly * Someone who can explain the product clearly * Teammates who communicate well under time pressure * A realistic project scope for the event timeline It is often better to have a small, aligned team than a larger team with unclear roles. ## How to choose teammates well When you talk to potential teammates, ask simple questions like: * What do you want to build? * What are you strongest at? * How hands-on do you want to be? * Are you trying to win a specific prize or explore a specific technology? These conversations help you figure out whether you are aligned on goals, pace, and project direction. ## Be clear about roles early Once you find teammates, agree on a rough plan early. You do not need a perfect structure, but it helps to know who is leading which part of the project. For example, you might decide who will focus on: * Product direction * Frontend implementation * Backend or infrastructure * Demo preparation and submission Clear ownership reduces confusion later in the event. If you do not have a project idea yet, that is okay. Posting your skills and the kinds of problems you want to work on is often enough to find a strong team. ## Next steps Learn what your team will need when it is time to submit. Return to the Builder Portal and keep exploring the event. # Submit a project Source: https://docs.hackersquad.io/builders/submit-a-project Submit your project details from the Builder Portal, then complete the required video submission in HackerSquad. When your team is ready to submit, go to the Builder Portal and open the `project.sh` tab. This is where you enter the core details of your project for the hackathon. Project submission is the first part of the review process. After you submit these details, you also need to submit your project video through HackerSquad. ## Open the project details form From the Builder Portal, navigate to the `project.sh` tab and complete the project details form. Project details form ## Complete the project details Fill out each part of the form carefully so event managers, judges, and partners can understand what you built. | Field | What to enter | | ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Project name** | Enter the name of your project. Choose a clear name that helps reviewers understand what your team built. | | **Project description** | Describe your project, what problem it solves, and how it works. Use this space to explain the technical story of your submission. | | **Technologies used** | Select the technologies your team used during the hackathon. This helps organizers and partners understand how their tools were used. | | **Other technologies** | If you used tools that are not listed, add them here so your project stack is represented more completely. | | **Team members** | HackerSquad pulls this from your team automatically. If you do not see the right people here, update your team in the Team tab first. | | **GitHub repository URL** | Add the repository link for your project so reviewers can inspect the code and understand the implementation. | | **Contact permission checkbox** | Check this if you agree that judging partners for the hackathon may contact you by email about your submission or prize-related follow-up beyond the judging process. | After you complete the form, click `./save_project.sh` to save your project submission. Write your description for someone who did not watch you build the project. Clear descriptions make it much easier for organizers and judges to review your work. ## Submit your project video next Submitting the project details form is not the final step. After this, you must also submit your project video through HackerSquad. The video submission is required because it helps the teams managing the hackathon review your project successfully. A video gives organizers and judges a reliable way to understand your demo, even if they cannot see the project live in person. When you begin the video submission flow, go through these three steps to start the recording: 1. Select the screen to share. We recommend sharing your entire screen. 2. Enable camera and mic. 3. Click **Start Recording**. ## Why the video matters Your project video helps reviewers: * Understand what your project does * See the product in action * Review your submission consistently * Compare projects more fairly across the event ## Next steps Return to the Builder Portal and continue the rest of your submission flow. Review other builder workflows available from the Builder Portal. # Capture live demos Source: https://docs.hackersquad.io/event-managers/capture-live-demos Use a display-connected base station to accept live demo requests, present wirelessly, and capture demos for the post-event summary. HackerSquad helps you capture live demos during the event so those presentations can become part of the broader event record. This is especially useful when you want to stream demos to the room, support wireless presenting, and preserve the content for the post-event summary. ## Set up a base station To capture live demos, you need a computer connected to the main display in the room. This computer acts as the base station for live presentations. The base station is responsible for receiving requests to go live, showing presenter content on the room display, and helping route the demo experience through HackerSquad. On the base station computer, open the event manager dashboard in HackerSquad. This dashboard contains the navigation items that allow the base station to receive requests from speakers and demo presenters. Live demos and speakers navigation Set up the base station before the event begins and test it with the main display so you are ready when presenters request to go live. ## Start the live viewer session On the base station, open the live viewer tool and click **Start Session**. Live viewer tool Once the session has started, the base station is ready to receive live requests from presenters. Live viewer session on When a builder or speaker requests to go live, the base station will receive a prompt like this. Accept live request Once the base station accepts the request, it presents both the individual's webcam feed and the screen they shared. This allows the room to see the presenter and the live demo at the same time. When the presentation timer ends, HackerSquad automatically cuts off the session and begins processing the video production. ## How presenters request to go live When a speaker or builder is ready to present, they request to go live directly in HackerSquad. 1. The builder opens the event experience and starts the presentation flow in HackerSquad. Builder present step 1 2. The builder continues through the present flow and confirms they want to present. Builder present step 2 3. The request is sent through HackerSquad so the base station can receive it and prepare the room display. Builder present step 3 Once accepted, the base station handles streaming the presenter's content to the room while the presenter remains remotely connected and shares their own laptop screen. ## How the demo display works The display-connected base station is the machine responsible for showing the presenter's shared screen to the room. This setup allows the speaker or presenter to stream wirelessly from their laptop while the base station delivers that content to the larger display. It creates a smoother live-demo experience without requiring every presenter to plug directly into the room hardware. ## What HackerSquad captures As live demos run through HackerSquad, the platform automatically captures: * Video footage * Presentation materials * Demo content This gives you a record of the live showcase and makes it easier to preserve what happened during the event. ## Why live demo capture matters Captured demos help extend the value of the event after it ends. Instead of losing presentations once the room clears out, you can keep a record of what builders and speakers shared live. That captured content also supports the post-event summary. When your live demos are recorded through HackerSquad, they can contribute to the final event recap alongside projects, speakers, and other event activity. ## Next steps Set up a similar workflow for live presentations during the event. See how captured demos contribute to the final event recap. # Capture live presentations Source: https://docs.hackersquad.io/event-managers/capture-live-presentations Invite and approve speakers, then use a display-connected base station to receive live presentation requests and capture them through HackerSquad. Capturing live presentations in HackerSquad works very similarly to capturing live demos. You still need a base station connected to the main display, and the speaker still presents wirelessly from their own laptop through HackerSquad. The difference is that live presentations require speaker setup before anyone can go live. Event managers must add and approve speakers in the event management dashboard first. ## Add speakers before the event Start in the event management dashboard and open the speakers navigation. Manage speakers navigation This takes you to the speakers management page. Speakers management page On this page, you can review existing speakers or invite new ones. ## Invite and approve speakers When you invite a speaker, HackerSquad sends them an automatic email with a form to complete. Speaker form After the speaker fills out the form, they still need to be accepted in the speaker management portal before they can present live. Invite and approve speakers before the event starts so they are ready to present without delays. ## What speakers see Once a speaker has been accepted, they will see a **Present** button on the builder dashboard. Present button From there, the speaker follows the same general presentation request flow used for live demos. ## Set up a base station To capture live presentations, you need a computer connected to the main display in the room. This computer acts as the base station for live presentations. The base station is responsible for receiving requests to go live, showing presenter content on the room display, and helping route the presentation experience through HackerSquad. On the base station computer, open the event manager dashboard in HackerSquad and select **Live Speakers**. This is the navigation flow the base station uses to receive requests from approved speakers. Live demos and speakers navigation The base station remains the computer that is actively presenting to the main display or projector in the room. This is the screen the audience watches during the live presentation. ## Start the live viewer session On the base station, open the live viewer tool and click **Start Session**. Live viewer tool Once the session has started, the base station is ready to receive live presentation requests from speakers. Live viewer session on When a speaker requests to go live, the base station will receive a prompt like this. Accept live request Once the base station accepts the request, it presents both the speaker's webcam feed and the screen they shared. This allows the room to see the speaker and the presentation at the same time. The operator on the base station can also zoom in on the video to expand the desktop view and the presenter view for the audience. When the presentation timer ends, HackerSquad automatically cuts off the session and begins processing the video production. ## How speakers request to go live Once a speaker is approved, they go through the presentation request flow inside HackerSquad. 1. The speaker opens the presentation flow from the event experience. Speaker presentation step 0 2. The speaker begins the request to present. Speaker presentation step 1 3. The speaker continues through the presentation flow in HackerSquad. Speaker presentation step 2 4. The speaker reviews the presentation flow and confirms they want to go live. Speaker presentation step 3 5. The request is sent through HackerSquad so the base station can receive it and prepare the room display. Speaker presentation step 4 Once accepted, the base station continues presenting that content to the main display or projector while the speaker remains remotely connected and shares their laptop screen. ## Why live presentation capture matters Captured presentations help preserve key moments from the event, including talks, speaker sessions, and live walkthroughs. That recorded content can then support the post-event summary, alongside projects, demos, and other event activity captured in HackerSquad. ## Next steps See how captured presentations contribute to the final event recap. Continue into hosting tips that help you communicate clearly during your event. # Create an Event Source: https://docs.hackersquad.io/event-managers/create-an-event Learn what you need before you can create an event on HackerSquad. Before you can create an event on HackerSquad, you must have an approved company connected to your account. Company Portal ## Before you create an event Event creation is only available for approved companies on HackerSquad. If you do not have a company yet, create one first at [Create a company](https://hackersquad.io/companies/access-denied). Make a company After you submit your company, the HackerSquad team reviews and verifies it. You must wait until that review is complete before you can create events. If your company is still pending review, you will not be able to create an event yet. ## How event creation works To create a company navigate to the events page on the left navbar. Go to event navbar 1. Create your company on HackerSquad. 2. Wait for the HackerSquad team to review and verify your company. 3. Once your company is verified, return to HackerSquad and create your event. ## If you are blocked If you already created a company but still cannot create an event, your company may still be waiting for verification. Check your company status and wait for the HackerSquad team to complete the review. ## Next steps Learn how to access the event manager portal and start managing your event. Add partner companies so builders can use the right tools during your event. # Manage an Event Source: https://docs.hackersquad.io/event-managers/host-an-event These docs guide an event manager to use HackerSquad to track engagement, understand their audience, and engage with builders in meaningful and impactful ways. Builder terminal in HackerSquad To host an event, you'll need to have Manager access to an event. These docs guide you to view project details as an event manager, add partnering companies to the event, add other event managers, update a photo gallery, and more. Manager button in HackerSquad If you are event manager for an event, you will see this `Manage` button on a given event. If you should be an event manager but you aren't, reach out to the event host to add your email . Once you're an event manager, you'll have access to all the features that help you manage a hackathon successfully. Interested in some tips on how to host your event successfully? ## Next steps Add partner companies before builders start exploring your event. Add teammates who should help run the event with you. # Manage event managers Source: https://docs.hackersquad.io/event-managers/manage-event-managers Add the right event managers so your event team can coordinate smoothly across the full event management portal. Event managers help keep your event running smoothly. Anyone you add here gets access to the full event management portal covered in these docs, which means they can help coordinate operations, review projects, and support builders throughout the event. Add event managers ## Why event managers matter You should add the people who need direct access to help run the event. This often includes team members from partner companies, selected judges, and anyone else who should actively manage event operations. When the right people have access, your team can respond faster, support builders more effectively, and keep the event moving without bottlenecks. Only add people who should have manager-level access to the event. Event managers can access the same management portal described across these guides. ## Who to add Add people who play an active role in running the event, such as: * Team members from partner companies * Judges who need to review projects closely * Internal teammates helping with event operations * Community leads or moderators supporting builders during the event Choose people who need visibility into the event and who can take action when something needs attention. ## Add an event manager Open your event management portal and click **Settings**. In the **Team Access** section, enter the email address of the person you want to add and click **Add**. Use this list intentionally. Event managers should be trusted collaborators who are directly involved in hosting, reviewing, or supporting the event experience. ## Team access The **Team Access** section is where you manage manager permissions for the event. Here, you can: * View who already has access to the event * See who created the event * Add new managers by email Make sure the email you enter matches the email that person uses for HackerSquad. ## When to add them Add event managers before the event starts whenever possible. Early access gives your team time to get familiar with the portal, understand the event setup, and prepare to support builders once submissions and judging begin. This is especially helpful for partner company representatives who may need to answer questions about their tools or evaluate projects that use their products. ## Next steps Define the prizes that will guide builder submissions. Create volunteer roles so your event team has enough support. # Manage feedback Source: https://docs.hackersquad.io/event-managers/manage-feedback Review builder feedback, understand the AI analysis workflow, export results, and run raffles from HackerSquad. Feedback helps you capture product experiences that builders might otherwise keep to themselves. It gives event hosts a structured way to learn how builders actually felt about the tools, APIs, and workflows they used during the hackathon. Feedback also encourages builders to think more deeply about what they are building and the tools they are integrating with. Instead of treating tooling as a black box, builders are pushed to reflect on what worked, what did not, and how each part of the stack shaped the final project. You can also incentivize feedback collection with raffles. This makes it easier to gather more responses while still surfacing the highest-quality developer experience feedback inside HackerSquad. ## Find the feedback section Use the event management portal to open the feedback section for your event. Manage feedback navigation This is where you review submitted feedback, filter results, export data, and run a raffle. ## Why feedback analysis matters Builders do not always submit thoughtful feedback on their own. It is common for people to write low-effort responses, very short responses, or AI-generated responses that do not reflect a real developer experience. To improve quality, every feedback submission goes through a multi-step LLM analysis workflow. This helps HackerSquad identify feedback that is more likely to be human-written and technically useful. The **LLM Score** reflects the technical depth of the submission. Higher scores generally indicate that the builder explained their experience in more detail and gave more meaningful product feedback. The points generated from the LLM Score also feed into the leaderboard in the builder portal. This gives builders an additional reason to submit thoughtful, experience-based feedback instead of low-effort responses. ## AI detection overview HackerSquad includes an AI Detection Overview so you can understand the quality of the feedback collected for your event. AI detection overview This view helps you quickly understand: * The total number of feedback submissions * How many responses were classified as human-written * How many responses were flagged as AI-generated * Whether any responses could not be classified Rejected feedback usually means the submission was flagged as AI-generated, too short, low-quality, or low-effort. The default filters show only accepted feedback, which helps you focus on the responses most likely to be useful. ## Filter and review feedback Use the feedback filters to narrow the list to the responses you want to review. By default, HackerSquad shows accepted feedback first. This helps you spend time on the submissions most likely to contain real developer insights. As you review feedback, use the LLM analysis and score as signals for depth and quality, especially when you want to understand how builders experienced partner tools or developer workflows. ## Export feedback Feedback can also be exported from HackerSquad. Use the export tool to download feedback entries as a CSV file for deeper review, sharing, or post-event analysis. Export feedback Exporting is useful when you want to: * Share results with internal teams * Review feedback outside the platform * Analyze product experience trends after the event ## Run a raffle HackerSquad includes a built-in raffle tool for feedback submissions. When you click the raffle button, the platform randomly selects one feedback entry. This is a simple way to reward participation and encourage more builders to leave thoughtful feedback during the event. Export feedback Mention the raffle during your event and remind builders that thoughtful feedback helps improve the developer experience for future events and product teams. ## Next steps Capture live builder demos so key event moments are preserved. Invite speakers and capture presentations through the base station workflow. # Manage partner companies Source: https://docs.hackersquad.io/event-managers/manage-partner-companies Add partner companies before your event so builders can use complementary tools and build more complete projects. Partner companies give builders more depth at your event. When you add the right mix of companies before the event starts, builders can combine complementary tools, tell a stronger technical story, and ship more complete projects. Manage partner companies ## Why partner companies matter Partner companies shape the technical narrative of your event. A strong partner mix helps builders move beyond a single feature or workflow. For example, one company might provide infrastructure, another might provide AI tooling, and another might provide communications or payments. Together, those tools help builders create projects that feel more realistic and more complete. Add partner companies before your event begins so builders can see the available tools from the start. ## Add a partner company To add a partner company, open your event management view and go to the partner companies section. Add partner company button Click **Add Partner Company** to open the form. Add partner company form ## Complete the form Use the form to connect a company to your event and give builders the right context for how to use that partner. | Field | What to enter | | -------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | | **Company** | Search for and select the partner company you want to attach to the event. | | **Sponsorship Tier** | Choose the sponsorship level for that company, such as Bronze. | | **Technical Challenge URL (Optional)** | Add a link to the partner's challenge, prompt, or technical brief if they are sponsoring a specific builder challenge. | | **Discord Link (Optional)** | Add the partner's Discord channel or support link so builders can ask questions during the event. | After you complete the form, click **Add Partner Company** to save the company to your event. ## How to choose the right partners Choose companies whose tools work well together. The best partner sets usually help builders cover multiple parts of a project, such as: * Building the core product * Adding AI or automation * Handling data, infrastructure, or deployment * Supporting communication, authentication, or payments When your partners are complementary, builders can create projects with a clearer end-to-end story. ## Next steps Give the right teammates access to help run the event. Set up prizes that align with your partner companies and event goals. # Manage prizes Source: https://docs.hackersquad.io/event-managers/manage-prizes Add prizes that increase registrations, guide builder behavior, and support platform-based prize distribution. Prizes help shape what builders create at your event. They can encourage builders to explore specific technologies, tell a stronger technical story, and stay motivated to build more complete projects. Prizes can also increase interest before the event starts. A clear prize lineup gives people a stronger reason to register and helps communicate what kinds of projects and technologies you want to highlight. Manage prizes ## Why prizes matter Use prizes to guide builders toward the technologies, themes, and outcomes you want to feature at your event. For example, you can create prizes around: * Specific partner tools * Best use of a technology * Strongest end-to-end product experience * Most creative project or technical implementation Well-defined prizes give builders direction while helping your event tell a more coherent story. ## Add a prize Open the prize management section for your event and create a new prize. Manage prize form Use the form to define the prize details builders will see during the event. ## Complete the prize form The prize form includes the following fields: | Field | What to enter | | ---------------- | ------------------------------------------------------------------------------------------------------- | | **Prize Title** | Enter the name of the prize, such as `Best Use of AI` or `Best Developer Tool Workflow`. | | **Description** | Describe what the prize is for and what builders should optimize for when submitting. | | **Value** | Enter the displayed reward description, such as `$100 Gift Card`, swag package, or another prize label. | | **Dollar Value** | Enter the numeric dollar amount for platform-based prize distributions through the Tremendous API. | Click **Add Prize** to save the prize to your event. The **Dollar Value** field is required if you want HackerSquad to support platform-based prize distribution through the Tremendous API. ## Prize distribution status Right now, prize distributions through the platform are only possible with help from the HackerSquad Support Team. Funding prizes directly in the HackerSquad event management portal is planned, but that workflow is still under construction. If you want to use platform-supported prize distribution, reach out to `support@hackersquad.io` and let the team know. ## Tips for creating strong prizes Create prizes that are specific enough to guide builders, but broad enough to allow creativity. Good prizes often: * Align with partner companies and their tools * Reward complete projects, not just isolated demos * Reflect the technical narrative of the event * Make the event more appealing to potential registrants ## Next steps Organize volunteers who can help support the event experience. Share the builder event link so attendees can access the event dashboard. # Manage volunteers Source: https://docs.hackersquad.io/event-managers/manage-volunteers Create volunteer opportunities, invite the community to help, and use HackerSquad to coordinate volunteer roles for your event. You can use HackerSquad to organize volunteers for your event. Create volunteer opportunities in the event management portal, then invite your community to register for those roles. Those opportunities appear on the Builder Dashboard as a **Volunteer** button for each event. This makes it easier for community members to see where they can help and sign up for the work that fits them best. Volunteer Button ## Why volunteer opportunities matter Volunteer opportunities help you turn general interest into clear responsibilities. The more specific you are about what needs to happen, the easier it is for people to step in and help. For example, you can create volunteer opportunities for: * Support check-in and registration * Support lunch catering * Help direct attendees at the venue * Assist with setup or teardown HackerSquad helps you see who is signing up for what, but it does not remove the need to coordinate people directly. You should still confirm assignments, timing, and expectations with your volunteers. ## Create volunteer opportunities From the Event Managers portal, select **Tools** and then **Manage Volunteers**. Manage volunteers Start in the event management portal and open the volunteer management view for your event. Manage volunteer opportunities From there, create a new opportunity for each role you want volunteers to fill. Create volunteer opportunity form ## Complete the volunteer opportunity form Use the form to describe the role clearly so people know exactly how they can help. | Field | What to enter | | ------------------ | ------------------------------------------------------------------------------------------------ | | **Title** | Enter a clear role name, such as `Check-in Support` or `Lunch Catering Support`. | | **Category** | Choose the volunteer category that best matches the work. | | **Time Slot** | Enter the time range when you need help, such as `9:00 AM - 12:00 PM`. | | **Location** | Add the place where the volunteer should report, such as `Main Entrance` or `Registration Desk`. | | **Max Volunteers** | Set the number of people you need for that role. | | **Description** | Explain what the volunteer will do and what success looks like during the shift. | | **Requirements** | List any skills, preparation, or expectations the volunteer should know before signing up. | Click **Create Opportunity** to publish the role. Be specific in the title, description, and requirements. Clear opportunities attract better signups and reduce confusion on event day. ## How volunteers discover opportunities Once you publish volunteer opportunities, they appear on the Builder Dashboard for the event. Volunteers signing up Community members can use the **Volunteer** button to review available roles and register for the ones they want to help with. ## Track who is assigned After people sign up, you can review who has taken each role and see how your volunteer coverage is shaping up. Volunteer opportunities assigned Use this view to confirm that each opportunity has enough coverage. If an important role is still unfilled, update the opportunity details or continue promoting it to your community. ## Next steps Share the event dashboard so attendees can get into the event experience. Start reviewing builder submissions once projects begin coming in. # Post event summary Source: https://docs.hackersquad.io/event-managers/post-event-summary Understand how HackerSquad automatically generates a post-event summary from projects, demos, speakers, presentations, and prizes. HackerSquad automatically generates a post-event summary for completed events. This gives you a single page that captures what happened at the event and makes it easier to share outcomes with builders, partners, and your broader community. The post-event summary is built from the activity that happens throughout the event. As builders submit projects and live content is added to the event, HackerSquad turns that information into a structured event recap. ## See an example Here is an example of a post-event summary in action.