Raptor Hackathon Platform: Submission Checks & Judging

The Raptor hackathon platform evaluates submissions through a two-stage process: automated checks that verify technical requirements and a human judging phase that scores projects against set criteria. You submit your project, the system validates it, then a panel reviews and scores it. This article explains exactly how that pipeline works, what the automated checks look for, and how judges make their final decisions.

What is Raptor and Why Does It Matter?

Raptor is a hackathon management platform used by event organizers to handle submissions, judging, and scoring. It is one of several tools (like Devpost, HackerEarth, or Miro) that streamline the chaos of a hackathon weekend. For participants, Raptor is the portal where you upload your project, provide a demo video, and answer questions. For organizers, it is the backend that ensures every submission is complete, on time, and fairly judged.

The platform matters because it standardizes the process. Instead of collecting links in a shared spreadsheet, Raptor gives every project the same submission form, the same deadline, and the same judging rubric. That consistency is what makes a hackathon fair, and it is the core reason organizers choose it.

How Submission Checks Work

When you hit “Submit” on Raptor, the platform runs a series of automated checks before your entry is officially accepted. These checks are designed to catch common mistakes and ensure your submission meets the minimum requirements set by the organizers.

• Required fields: Every form field marked as mandatory must be filled. This typically includes a project name, a description, a demo video link, and a repository link.
• File uploads: If the hackathon asks for a pitch deck or a code archive, Raptor verifies the file type and size. For example, a PDF must be under 10 MB, or a ZIP under 50 MB.
• URL validity: The platform checks that URLs are in the correct format (http/https) and sometimes pings the link to see if it is live. A broken link will trigger a warning.
• Deadline enforcement: Submissions are timestamped. If you submit after the cutoff, Raptor marks it as late, and the organizer decides whether to accept it.
• Duplicate detection: Raptor flags submissions that share the same project title or description, which helps prevent copied entries.

These checks are not a deep code review. They are a quality gate. If your submission fails a check, you get an error message telling you what to fix, and you can edit and resubmit until the deadline passes.

The Judging Process: From Rubric to Winner

Once the submission window closes, the human judging phase begins. Organizers set up a rubric in Raptor before the event, defining the criteria and their weights. A typical rubric might look like this:

• Technical complexity (30%) – How challenging was the project to build? Did the team use advanced algorithms, APIs, or hardware?
• Innovation (25%) – Is the idea novel? Does it solve a problem in a creative way?
• Impact (20%) – Does the project address a real-world issue? How many people could benefit?
• Presentation (15%) – Is the demo video clear? Is the pitch compelling?
• Code quality (10%) – Is the code organized, commented, and well-structured?

Judges log into Raptor and see a list of assigned projects. They watch the demo video, read the description, and optionally clone the repository to run the code. For each criterion, they give a score (e.g., 1 to 10) and often leave a comment. Raptor automatically calculates the weighted total for each judge’s score.

After all judges submit their scores, Raptor aggregates them. The platform can show the average score per project, or the median to avoid outlier bias. The organizer then reviews the top-ranked projects and selects the winners. Some hackathons also have a “people’s choice” award, where Raptor collects public votes via a shareable link.

How to Choose a Hackathon Platform

If you are an organizer deciding between Raptor and alternatives, consider these factors:

• Ease of use for participants: Is the submission form simple? Can teams collaborate on one submission?
• Judging tools: Does the platform support multiple judges, weighted rubrics, and anonymous scoring?
• Integration: Can it pull data from GitHub, Devpost, or Discord? Does it support Slack notifications?
• Pricing: Raptor has a free tier for small events, but larger hackathons may need a paid plan. Compare the cost per participant.
• Support: Is there live chat or email support during the event? A platform that crashes on demo day is a nightmare.

Raptor is a solid choice for mid-sized hackathons (50–500 participants) that need a structured judging workflow. For smaller events, a simple Google Form might suffice. For massive global hackathons, Devpost has a larger community and built-in sponsor tools.

Common Problems and How to Avoid Them

Participants often run into the same issues on Raptor. Knowing them in advance saves you a headache.

• Missing the deadline because of timezone confusion: Raptor uses the organizer’s timezone, which is usually displayed on the event page. Double-check the countdown timer on the submission page.
• Demo video not playing: Raptor accepts YouTube and Vimeo links, but some organizers require an unlisted link. Make sure your video is not private.
• Repository access: If your code is in a private repo, the judges cannot see it. Either make it public or add the judge’s email as a collaborator.
• Submitting a zip with compiled binaries: Judges want source code. Include a README with build instructions.
• Ignoring the rubric: If the rubric says “impact” is 20%, spend time in your description explaining who benefits from your project.

If you encounter a technical bug on Raptor (like a file not uploading), contact the organizer immediately. They can often extend the deadline or accept a manual submission via email.

Raptor vs. Other Platforms

Raptor is not the only player. Here is a quick comparison to help you understand where it fits.

• Devpost: The largest hackathon community. It has a built-in audience for publicizing your event, but the judging tools are less detailed than Raptor’s.
• HackerEarth: Focuses on coding challenges and recruitment. Good for hiring-focused hackathons, but less flexible for hardware or design projects.
• Miro: Not a dedicated hackathon tool, but some organizers use it for brainstorming and presentations. It lacks submission and scoring features.
• Raptor: Balances simplicity with powerful judging. It is especially strong for events that require multiple judges and weighted scoring.

In practice, many hackathons use a combination: a platform like Raptor for submissions and judging, plus Discord for communication and GitHub for code.

Cost and Safety Considerations

Raptor’s pricing is not publicly listed, which means you need to contact their sales team for a quote. For small events, the free tier may be enough, but for larger hackathons, expect to pay a few hundred dollars. Always read the terms of service to understand data ownership. Your project code and personal information are stored on Raptor’s servers, so check their privacy policy. For participants, there is minimal risk: you are uploading your own content, and you retain all intellectual property rights. However, be cautious about uploading proprietary code to any third-party platform. If your hackathon project contains confidential information, consider using a private repository and sharing access only with judges.

Frequently Asked Questions

Can I edit my submission after I click “Submit”?

Yes, as long as the deadline has not passed. Raptor allows you to go back and edit any field or re-upload files. Once the deadline hits, the submission is locked, and you can no longer make changes.

How are judges assigned to projects?

Organizers can assign judges manually or let Raptor distribute them randomly. In some events, judges are assigned to projects they have no conflict with (e.g., not from the same team). The organizer controls this in the judging settings.

What if my demo video is longer than the limit?

Most hackathons set a video limit (e.g., 3 minutes). If your video exceeds it, Raptor will not block the submission, but judges may only watch the first few minutes. Keep your demo concise and put your best work in the first 60 seconds.

Do judges see my team’s names?

It depends on the organizer. Raptor supports “blind judging,” where judges only see the project name and description, not the team members. This reduces bias. Check the event rules to see if your hackathon uses blind judging.

What happens if my code doesn’t run on the judge’s machine?

This is a common issue. Judges typically try to run the code, but if it fails due to environment differences, they will rely on your demo video and description. To avoid this, include a README with exact setup steps and dependencies, and test on a fresh machine before submitting.

Related

• How to Tell If a Pokémon Card Is Fake Before You Buy
• Should Your MVP Include AI? A Workflow-First Guide
• Open Source vs Closed AI Models: How to Choose