Set the fields, rows and branding once; ePravesh generates each admit-card PDF with photo and signature pulled from their uploads.
Fully configurable per institute — pick the content, order it, brand it; the layout renders consistently for every candidate.
Select any application-form fields for the ticket and set their order — nothing prints that you didn't pick.
Add fixed rows that aren't on the form — "Exam Centre: Mumbai Central", "Reporting Time: 09:30" — ordered alongside the field rows.
Set title, header, footer and instructions, and upload a signature image so every card carries your identity.
Photo and signature are pulled from the candidate's form uploads and placed on the ticket — no manual attaching.
Prefer a pasted passport photo? Blank-frame mode leaves an empty box for a physical photograph.
The PDF is cached and shared across admin and candidate views, and auto-invalidated when you change the template.
Download eligibility depends on the course and its fee — no admit card goes out before the required step is done.
Add the WhatsApp, chat, voice and email agents: "when is my hall ticket out?" and "why can't I download it?" get instant, accurate answers — the agent explains the rule and sends paid-pending applicants back to checkout. See the Suite →
Hall tickets are configurable (hall_ticket_enabled), switched on per institute — not every admission runs an entrance exam. Photo and signature auto-detection need the form to collect those uploads. AI counseling agents are an optional add-on.
Four steps. Your office never emails a hall ticket again.
Pick the fields to print, add centre rows and upload your authorising signature.
Your teamFree courses unlock on submission; paid courses unlock on confirmed payment.
ePravesh engineThe applicant pulls an A4 PDF with their auto-detected photo and signature.
ApplicantThe cached PDF invalidates on any config change, so nobody carries a stale hall ticket.
ePravesh engineIt depends on whether the course charges a fee. On a free course the admit card unlocks the moment the application is submitted; on a paid course it needs a paid payment row on the application, so a submitted-but-unpaid candidate cannot download one. That rule is what stops admit cards leaking before fees are collected.
No — both are auto-detected from the candidate's own form uploads and placed on the ticket. This only works if your application form actually collects those uploads, so include the photo and signature fields when you build it. If you'd rather paste a physical passport photo at the centre, blank-frame mode leaves an empty box instead.
Yes, as custom static rows — fixed key-value rows that aren't on the application form, like "Exam Centre: Mumbai Central" or "Reporting Time: 09:30". They order alongside the rows you pick from the form fields. You also set the title, header, footer and instructions, and upload a signature image so every A4 PDF carries your identity.
The cached PDF is invalidated automatically, so nobody carries a stale hall ticket. The ticket renders once and that same cached file is shared across the admin and candidate views for speed; the moment you change the configuration, the cache drops and the next download reflects your edit.
No — hall tickets are configurable and switched on per institute, because not every admission runs an entrance exam. When enabled, the module is native to the Admission Engine rather than a paid extra. The AI Counseling Suite that fields "when is my hall ticket out?" is the separate, optional add-on.
Book a demo — we'll build a hall-ticket template live (your fields, branding, eligibility rules) and generate a sample PDF.