No Photographer, No Ordeal: How a Jalpaiguri School Rebuilt ID Card Renewal in Two Days

At a glance: A CBSE school in Jalpaiguri, with over 2,000 students, ran ID card renewal every year as a full-scale event — contracted photographers covering every section on a fixed date, parents filling paper or Google forms for contact details, and a vendor spending weeks consolidating everything into mock prints for approval. Vawsum’s class-teacher photo capture and parent self-service profile updates turned it into a two-day process, with no photographer, and ID cards in parents’ hands within a week of the session starting — the first time that had happened in the school’s decade-long history.

The problem

Every year, once the school reopened for the new session, ID card renewal became something close to a small production. A photographer was contracted, sometimes more than one, to get through every section of a 2,000-plus-student school on a single designated day. Each photographer had to keep accurate records as they went — which student, which class, which section, which roll number — because a mismatch anywhere in that chain meant a wrong photo on a wrong card, discovered only much later.

Running in parallel was a separate exercise to collect updated contact details and addresses from parents. This had moved from a fully paper-based process to Google Forms, which helped, but the underlying problem stayed the same: it still meant a dedicated collection drive, chased down through repeated follow-ups, every single year.

The two exercises rarely finished cleanly. Some students were inevitably absent on photograph day, which meant a second round just to catch stragglers. The photographer and the ID card vendor would then spend a long stretch consolidating everything — matching photos to records, matching records to the latest contact details — before producing mock prints for the school to review. Only after the school checked the data and design and signed off would the batch go to final print.

None of this added real value to the school. It was a mammoth logistics exercise that consumed weeks, generated a service charge for the vendor’s legwork on top of printing costs, and left everyone — office staff, teachers, the vendor — doing a job that was thankless precisely because getting it right was invisible and getting it wrong was obvious.

What changed

The school moved to the workflow behind Vawsum’s Certificate and ID Card system and its Connect app, and restructured both halves of the old exercise around it:

• Parents update their own contact details and address directly from the school app, with no separate link or form to send out and no dedicated collection drive to run. There’s no need to catch this once a year, because the data is never allowed to go stale in the first place.
• The date-window control was left open year-round at this school. It can be configured to a specific window instead if a school prefers, but here the choice was to let it run continuously.
• A handful of reminders through the app’s general communication features nudged any parents who hadn’t yet updated their details, using the same channel the school already used for everything else.
• Class teachers, not a contracted photographer, captured student photos — directly from a standard mobile phone, through the app, one class at a time.
• Parent photo upload was switched off as a privilege at this school. The reasoning was practical: the ID card vendor had previously flagged real problems with photos submitted through Google Forms — poor backgrounds, inconsistent lighting, cropping issues — and training thousands of parents to get this right was a much harder job than guiding a much smaller number of class teachers.
• The school generated a single multi-class list of ID cards from the system once photos and details were in, and sent that one file straight to the printer.

The result

Teachers finished photographing their classes in a single day. Contact details were largely already current, since reminders had gone out ahead of time through the app rather than through a separate form campaign. With both halves of the data already clean, generating the print-ready file and sending it to the vendor took no real consolidation effort on anyone’s part.

The entire exercise wrapped in two days. What used to be an ordeal spanning weeks became routine — simple, and repeatable in the same way every year. No photographer was needed, so the service charge for that legwork went to zero; the school paid for printing and nothing else. Parents had ID cards in hand within a week of the new session starting — the first time that had happened in the school’s ten-year history.

The underlying shift wasn’t really about photography at all. It was replacing a once-a-year scramble to catch a moving target — correct photo, correct details, correct student, all captured on the same narrow day — with a system where that data simply stays current on its own, and a printable file is available whenever the school wants one.

FAQs

Why not just let parents upload the student photo themselves through a form?
This school tried that before switching. The ID card vendor consistently flagged poor backgrounds, inconsistent lighting and cropping problems from parent-submitted photos. Training a much smaller number of class teachers to get this right proved far easier than training thousands of parents.

Does the parent profile-update window have to stay open all year?
No. It’s fully configurable. This school chose to leave it open year-round, but a school can just as easily restrict it to a specific date window if that fits its process better.

What happens to a student who is absent when their photo is normally taken?
Because photo capture isn’t tied to a single fixed day anymore, a class teacher can capture that student’s photo whenever they’re next in class, rather than the school needing a separate follow-up round to catch everyone who was missed.

Does the school still need to review anything before printing?
Yes, the school still generates and checks the print-ready file before sending it on, but there’s no mock-print cycle with a vendor in between — the file is built directly from records already held in the system.

Is this specific to large schools, or does it work for smaller institutions too?
The workflow doesn’t depend on scale. It happened to solve a particularly large logistics problem for a 2,000-plus-student school, but the same self-service updates and class-teacher photo capture apply just as directly to a smaller school running the same renewal every year.

See all case studies

See related case studies: how one 8-branch school group cut its payroll cycle from a week to under a day, how a residential school in Siliguri turned leave policy into a configurable rules engine, how a reputed ICSE school ran 1,000+ annual admissions through one auditable pipeline, how a Kolkata residential school made hostel attendance verifiable with four daily checkpoints, how a multi-branch Kolkata school tracked transport with QR codes alone at zero hardware cost, how a Bengali-medium school with zero computers went digital using nothing but phones — a path many schools across India are still on today — how a CBSE school in Siliguri fixed chronic late fee payment by linking admit card downloads to a fee-clearance cutoff, and how a West Bengal Board school in Burdwan replaced informal cash and screenshot-based fee collection with a fully auditable system, and how a Kolkata-area school with 100+ teachers replaced its daily substitute scramble with rule-based, auditable allocation.