412 admit cards. One Friday afternoon. Generate, print, distribute, verify — every status tracked.

How most Indian schools issue exam admit cards today

It is the Wednesday before the Class 10 pre-board in a CBSE school in Bangalore. The exam coordinator opens last year's admit-card Word file, copy-pastes 412 student names from the school's roll register, types the photo placeholder onto each card by hand, prints the entire stack on letterhead paper, and walks them up to the principal for signature. The signature pen runs out on card 134. The print machine jams on card 287. The Class 10 D batch has a child whose admission was finalised the morning of, and the office assistant pencils her name onto card 413 because reprinting the entire booklet for one card seems wasteful. By Thursday evening, the cards are in 11 different class-teacher folders. By Friday morning, two parents call to ask why their child's admit card lists Room 204 when the seating plan posted on the noticeboard says Room 207.

The cost is not just the Wednesday afternoon and the Thursday morning. The hand-typed admit card carries a photo placeholder that does not match the child in the room — the invigilator allows the child in based on a parent's reassurance, not on documentary evidence. The pencilled-in name on card 413 is undocumented; the audit log when the trustees ask is a printed sheet with handwritten annotations. The QR code that the school used for last year's pre-board is broken; the parent who tries to verify the card on their phone sees a 404 page. The reputation cost of a single 'admit card mistake' is the kind of thing the school carries silently for years; the next March's admission inquiries quietly weigh it.

Inkwelly's Examinations module replaces this entire workflow with a single Generate button. Every admit card is generated server-side from the Class assignment, Subject configuration and Room allocation data. Each card carries the school logo, the student photo, the verified roll number, the exam-center address, the per-paper room and time, and a QR code that resolves to the live admit-card record. The class-wise booklet exports as a single PDF; the office prints it once; the office assistant hands one folder per class to the class teacher. The Friday morning that follows is uneventful, which is the entire point.

How admit cards work in Inkwelly

When the coordinator opens the Exam → Admit Cards screen, she sees four summary cards across the top — total cards (one per linked student), generated count, distributed count and blocked count. Below the cards, a sortable table of every student in the exam with the admit-card number, the exam roll number, the linked class, the current status (DRAFT, GENERATED, DISTRIBUTED, BLOCKED) and action buttons — Generate PDF, Print, Distribute, Block / Unblock, View. The status flow is forward by default — DRAFT becomes GENERATED on PDF generation, GENERATED becomes DISTRIBUTED when the card is sent or printed, BLOCKED is a separate state for children whose card has been pulled (fee due, attendance shortage, board-disqualification rule).

Generation is the workhorse action. The coordinator can generate per-student, per-class or for the entire exam. The default workflow is per-class — select a class from the filter, click Generate, and within seconds Inkwelly produces a single class-wise PDF booklet with one card per child. Each card pulls data from four sources — the Student Information Module for the name, the verified profilePhotoMediaId, the parent contact and the academic ID; the exam itself for the exam name, the school logo, the exam center address and the principal signature; the Subject configuration for the per-paper schedule; the Room allocation for the room and seat. The card carries an auto-generated admitCardNumber (sequence per exam), a unique verificationToken, and a QR code whose data is the verification URL plus the token.

Distribution is the second decision. The school configures a distributionMode per exam — PRINT (offline only), DIGITAL (parent app + WhatsApp Business), or BOTH (the office prints and also pushes to the parent app). The default is BOTH because every Indian school has parents on both ends of the digital divide. The DIGITAL channel pushes a notification to the parent app with a tappable card view; the parent can save it as PDF or screenshot it. The PRINT channel produces the class booklet PDF for the office printer.

The BLOCKED state is the safeguard. If a child has unpaid fees beyond the school's grace period, the Fee Module (when integrated) can auto-flag the admit card as BLOCKED. If a child has below-threshold attendance, the Attendance Module can flag. If the principal manually blocks a card for disciplinary reasons, the office records the reason. A BLOCKED card is not generated, not distributed, and shows on the parent app as 'Please contact the school office' with a link to chat. The block can be lifted with a logged action — the audit log captures who blocked, who unblocked, when and why.

See admit cards in action

“Pichli baar admit cards print karne mein 2 din lag gaye the. Is baar Inkwelly mein 'Generate' button click kiya, 5 minute mein 412 admit cards ka booklet ready ho gaya. Class teachers ko Friday subah folder mein de diya. Zero phone calls.”

Real-world scenarios for admit cards

1. A late-admission child two days before the paper. A new admission joins on Wednesday for the Class 10 pre-board starting Friday. The moment the Student Information Module confirms the admission and the Class assignment auto-links her, an admit card row in DRAFT appears on this screen. The coordinator generates a single-student admit card from the action menu, prints it, and hands it to her by Wednesday evening. Friday morning is uneventful.

2. A schedule change after admit cards were printed. The Class 9 Hindi paper is shifted by 24 hours due to a regional bandh. The coordinator updates the Room allocation; the system flags the affected admit cards as 'snapshot stale'. She clicks 'Regenerate for affected'. New cards are issued; old cards are invalidated; parents receive a notification on the app and a WhatsApp message. The office reprints only the affected class.

3. A child whose fees are outstanding. Class 11 commerce has one child whose fees are 90 days outstanding. The Fee Module auto-flags the admit card as BLOCKED with reason 'fees outstanding 90 days'. The card does not appear in the class booklet. The parent app shows 'Contact school office'. The principal calls the parent; the parent pays; the principal unblocks with reason 'paid 24 Feb'. The card generates immediately.

4. A QR scan at the exam center entrance. Friday morning. The Class 10 Hindi paper begins at 9 AM. The invigilator at the door scans the QR on every child's printed admit card with the school's mobile app. Each scan returns a verified copy with the live photo. One child's QR returns 'invalid — see updated card'; the invigilator pulls her aside, checks her phone, finds the updated card, and admits her. Every scan is captured in the audit log.

5. A parent who claims they never received the admit card. A parent calls the office on Thursday evening claiming no admit card was distributed. The coordinator opens the admit card row, sees status DISTRIBUTED with the WhatsApp delivery timestamp, the parent app push receipt and the read-receipt from the Wednesday distribution. She sends the PDF again to the parent's primary contact and updates the distribution log.

See admit cards generated for your school in real time

Bring your school logo and a sample student list. We will generate the class booklet PDF live in front of you, with QR verification working end to end.

Limits, safety and the small print

Admit cards are governed by the exam lifecycle. They can be generated at SCHEDULED stage and onwards; not at DRAFT. Once an exam reaches IN_PROGRESS, generation is allowed only via the per-student override (for late admissions or replacement cards). Once the paper has been sat (the audit log records examConducted), the admit card row is archived and not re-generatable. The student's profile retains a copy for the affiliation cell visit.

The verificationToken is a 32-character random string, unique per card per exam, and rotates on regeneration. The QR resolves to a public verification URL but the verification result requires a logged-in user (parent, invigilator, principal). An anonymous scan returns a generic 'this card is valid; for details, log in' message; this prevents scrape-and-fake attacks while keeping the parent-side verification trivially easy.

DPDP-Act compliance requires that student personal data on the admit card (photo, name, parent contact) is stored with parental consent recorded at admission. Inkwelly's admit-card module respects the consent state — a child whose parental consent has been withdrawn for marketing data still gets an admit card (because the school's exam process is a legitimate interest, not marketing), but the WhatsApp distribution channel is paused for that child; the printed card remains the canonical delivery. The audit log captures the consent-aware delivery decision.