Skip to content
OverviewGetting startedCreating challengesChallenge analyticsEvaluating submissions
Partners

Creating challenges

Draft challenges and submit them for BoardingPass review.

Create a challenge

  1. Go to New challenge from the partner nav.
  2. Fill in title, kind (software, UI/UX, slide deck, marketing), summary, team size, submission questions, judging mode, and deadlines.
  3. Optionally add a listing header image (1600×900, 16:9 recommended; hero on the catalog), event registration URL, and event start time.
  4. Save as draft.
  5. Open Page builder to add the brief, deliverables, schedule and prizes. Then click Submit for BoardingPass review when ready.

On your partner home page, set your public slug and about text so students can find your organization at /experience/partners/{slug}.

BoardingPass admins must approve before the challenge appears on Experience. See Admin help → Challenge reviews.

Page builder

After creating a draft, open Page builder to compose the public challenge landing page with blocks:

  • Markdown content
  • Image gallery
  • Prizes, schedule, sponsors
  • Deliverables checklist

Blocks are stored in page_config and rendered on the student challenge detail page.

Teams

Challenges created here support teams. Students create/join teams with invite codes. Set max team size (2–20). One submission per team; any member can submit for the group.

Draft vs published

StatusWhat it means
DraftOnly your org can edit
Pending reviewSubmitted to BoardingPass admins
PublishedLive on Experience
RejectedRevise using admin notes and resubmit

Tips

Tip

Write deliverables as a checklist students can follow — links, file types, and length limits reduce incomplete submissions.

Note

Deadlines on challenges are shown on the public catalog; keep them realistic for student schedules.

Run hackathon judging

Organisation owners and admins manage challenge settings and judges. Reviewers use the judging portal for assigned submissions.

  1. Open the challenge’s Judges tab and Enable event judging.
  2. Save a rubric with weights totalling 100%, reviews per team and visit length; invite judges by email.
  3. Ask teams to submit, save their organiser-issued location and mark themselves ready. Judges accept their invitation using their verified invited email and check in.
  4. Open judging, monitor coverage and resolve stalled visits. The rubric locks when judging first opens.
  5. Close judging and export private results. Give a reason when closing with incomplete coverage or reopening.

Judges use their invitation link, choose I’m ready to judge / next team, visit the assigned location, score the demo and select Submit and next. Notes are optional. My reviews allows corrections while judging is open.

PreviousGetting startedNextChallenge analytics