Prompt to ProductionNBKRIST × ISTE × Paytm

Event rules

How registration, entry, the Build Challenge and certificates work for Prompt to Production – Paytm AI Workshop. These rules are enforced by the event platform itself.

30 September 2026 · Seminar Hall-1, New CSE Block, NBKRIST

1.Registration

  1. 1.1Each student may register once. An email address and a roll number can each be used for only one registration.
  2. 1.2Registration is open while seats remain and the organisers keep it open. Seats are limited to 100, and a registration awaiting payment verification holds a seat.
  3. 1.3Enter your name exactly as it should appear on your certificate. Roll number, email, branch, year and section can be changed only through the Support Desk.
  4. 1.4Your account password is set during registration. Password resets are sent only to the registered email address.

2.Fees and payment verification

  1. 2.1The fee is ₹50 for ISTE student members with a valid membership number, and ₹100 for everyone else.
  2. 2.2Pay by UPI to the official UPI ID shown on the registration page, then submit the 12-digit UTR (transaction reference) and a screenshot of the payment (PNG, JPG, WEBP or PDF, up to 5 MB).
  3. 2.3Each UTR can be used for one registration only. Reused or shared UTRs are rejected automatically.
  4. 2.4Your registration stays pending until an organiser checks the UTR and screenshot. No ticket is issued until the payment is verified.
  5. 2.5If a payment is rejected, the reason is shown on your dashboard and you may resubmit a new UTR and screenshot while seats remain. A rejected registration does not hold a seat.

3.Ticket and entry

  1. 3.1After verification your QR ticket appears on your dashboard. Bring it on your phone or printed, along with your college ID card.
  2. 3.2Each ticket admits its holder once. A second scan shows the time of the first check-in and is not admitted again.
  3. 3.3Tickets are personal and carry a security token. Screenshots of someone else's ticket, edited codes or unverified registrations are refused at the gate.
  4. 3.4Your attendance is recorded only when a coordinator scans your ticket at the Seminar Hall-1 entrance. Attendance is required for a certificate.

4.Build Challenge teams

  1. 4.1Only participants whose payment is verified can create or join a team.
  2. 4.2A team has 1 to 4 members. Each participant can be in only one team.
  3. 4.3The creator becomes team leader and receives an invite code to share. Members join with that code.
  4. 4.4A member may leave before the team submits. The leader can leave only after every other member has left, which dissolves the team.
  5. 4.5Once the team submits its project, the roster is locked: nobody can join or leave.

5.Project submission

  1. 5.1Each team makes one submission. Any member can save drafts; drafts are not judged.
  2. 5.2A final submission needs a project name, the problem statement, a description and at least a GitHub repository or live demo link.
  3. 5.3The submission deadline is to be announced. After it, submissions cannot be created or edited.
  4. 5.4Once a submission is evaluated it is locked, and the scores and feedback appear on the team's dashboard.

6.Judging

  1. 6.1Submitted projects are scored out of 100: Innovation (25), AI & prompt engineering (25), Technical execution (25) and Presentation (25).
  2. 6.2Teams are ranked by total score. A tie is broken in favour of the team that submitted first.
  3. 6.3The live leaderboard shows project names and scores only; repository and demo links are not published.

7.Certificates

  1. 7.1A Certificate of Participation is issued only when all three conditions are met: your payment was verified, you were checked in at the venue, and the event has ended (to be announced).
  2. 7.2Registered participants who did not attend, or whose payment was not verified, do not receive a certificate.
  3. 7.3A Certificate of Merit goes to every member of the 1st-place (Winner) and 2nd-place (Runner-up) teams, in addition to their participation certificate.
  4. 7.4Each certificate has a unique ID and can be verified by anyone on the public verification page. Certificates found to be issued in error may be revoked, and verification will then show them as revoked.

8.Support and decisions

  1. 8.1Raise questions and corrections through the Support Desk on your dashboard; replies appear there.
  2. 8.2Decisions of the organising committee (Department of IT & AI&DS, NBKRIST, with ISTE) on verification, entry, judging and certificates are final.

By registering you agree to these rules.

RegisterRead the FAQ