Onboard a new teacher in six minutes. Profile, IDs and joining — one form, one save.

How most Indian schools onboard a new teacher today

It is the first week of April. The principal has interviewed and finalised three new joiners — a TGT Mathematics, a PRT Hindi and a lab assistant for the senior science block. The HR clerk pulls out the joining register, opens the staff Excel sheet, opens the previous year's EPFO Form 11 PDF for reference, and starts. Name. Father's name. Aadhaar — twelve digits, copied from a photograph of the card, hopefully without dropping a zero. PAN — ten characters, five letters, four digits, one letter, no spaces. UAN — twelve digits if the teacher has one, else blank. Joining date. Department. The same three teachers, fifteen fields each, three forms — appointment letter, EPFO Form 11, salary register opening row.

By lunch, the lab assistant's record is in the Excel sheet but not in the appointment letter template, the TGT's appointment letter is signed but her PAN was mistyped, and the PRT Hindi teacher's name was entered in English in the salary register but the principal needs it in Devanagari for the formal appointment letter the management trust signs. Three new joiners. Two and a half hours of office time. At least one error that will surface six weeks later when the EPFO ECR upload bounces back with a UAN-PAN mismatch.

Now imagine you do this for fifteen teachers in a single April joining cycle, plus three lateral hires through the year. The cost is not the typing — it is the appointment letter that goes out with a wrong PAN, the EPFO penalty notice, the salary register that says one name and the bank statement another, and the new teacher who walks in on day one to discover her record is incomplete in five different places. We built Employee Enrollment so that day-one for a new staff member happens once, in six minutes, and every downstream module — payroll, attendance, employee documents, the school website CMS roster, the parent app teacher card — picks up the same record without anyone re-typing.

How New Enrollment works — one form, six minutes

Open Employees → New Enrollment. The page shows two structured sections in a single scrolling form: Employee Profile (the person) and Academic Enrollment (the joining for the current academic session). One Enrol Employee button at the bottom commits both — there are no half-saved records, no orphan profiles, no academic record without a person attached.

Section 1 — Employee Profile. Start with the identifiers row. Employee ID can be typed manually or auto-generated by Inkwelly if your school has enabled autoGenerateEmployeeId in Enrollment Settings — same for Joining Number. PF Number, ESI Number, UAN Number — all optional, all 50-character free-text fields. PAN is validated inline against the official format ^[A-Z]{5}[0-9]{4}[A-Z]{1}$ — type one wrong character and the form tells you before save, not the EPFO portal six weeks later. Aadhaar must be exactly twelve digits — ^\d{12}$ — no spaces, dashes or dots accepted; the validator strips them silently and asks for the canonical form.

Title is a 12-option dropdown — Shri, Smt, Kumari, Kumar, Master, Miss, Mr, Mrs, Ms, Dr, Prof, Other — built for the salutation conventions Indian government schools, residential schools and trust-run schools all use side by side. First Name is required, Middle and Last names are optional but every name field is multi-language. Type the English value, click the language icon beside the input, fill the Hindi or regional value once, save — the appointment letter draft picks up the Devanagari name automatically.

Date of birth, gender (Male / Female / Other), blood group (8 options), religion (Hinduism / Islam / Christianity / Sikhism / Buddhism / Jainism / Other), nationality, mother tongue, caste category (General / OBC / SC / ST / Other), marital status (Single / Married / Divorced / Widowed) — every demographic field a CBSE board affiliation paperwork, an EPFO Form 11, an ESIC Form 1, a state board roster or a school management trust review will ask for, captured once. Spouse name and spouse occupation appear when marital status is Married, Divorced or Widowed. Profile photo via the Inkwelly MediaPicker — pick from the school's existing media library or upload a new image, with proportional cropping, captured at the same time as everything else.

Contact row. Email is validated; mobile and alternate mobile are 15-character strings with country-code support. The mobile number flows directly into the WhatsApp announcement workflow your school sends every payday and the OTP-based employee portal login that lets the teacher check her own profile from day one.

Section 2 — Academic Enrollment. Pick the academic session (defaults to the active session — 2025-26 for most April joiners). Employee Number for the session is optional and separate from the global Employee ID — useful for schools that re-number staff at the start of every academic year. Pick the Department from the school's department list (Mathematics / Science / Computer Science / Hindi / English / Administration / Transport / Support — whatever your school has configured, with multi-language department names if your school has enabled them). Joining Date is required and audited — once saved, it forms the official service-period anchor on the Service Period Certificate and on the EPFO Form 11 row. Remarks is an optional free-text note — useful for noting the contract type, the probation period, or the trust resolution number that authorised the appointment.

Click Enrol Employee. In two seconds, the new staff member exists in five places at once: the Employee Information directory with the full 11-tab profile, the academic session roster for the current session, the Identity & Access Management system with a teacher role and an OTP-able login, the employee portal at /e/<profileId> ready for her first sign-in, and the audit log with the timestamp, user, IP and the full payload that created her record. No double entry. No orphan rows. Every downstream module is now aware of her, automatically.

Walkthrough — the four screens of a six-minute joining

“Pehle ek nayi teacher ko enrol karne mein ek-do ghante lagte the — alag form, alag register, photo alag, appointment letter alag. Ab Inkwelly mein ek hi page hai. April mein 12 teachers enrol kiye, sab six-six minute mein. Form 11 ka data CSV se direct upload ho gaya. EPFO se ek bhi rejection nahi aaya.”

Real-world enrollments your office runs every term

1. April joining cycle (every year). A school adds 8 to 18 new teachers in the first two weeks of April — TGT and PRT replacements, lateral subject hires, the new lab assistant for the senior block. Without Inkwelly: two days of office work, three half-built Excel sheets, a stack of physical files. With Inkwelly: each enrollment is six minutes, a single CSV of new joiners is exported the same evening for the EPFO Form 11 batch upload, and every new teacher walks in on her first day to a profile that already exists with her photo on the parent app.

2. Mid-year lateral hire. A senior English teacher resigns in October. The principal interviews and finalises a replacement within the week. The HR clerk opens New Enrollment, picks the active session (2025-26), enters the joining date as 2025-10-21, picks the English department, and saves. The new teacher's first salary slip is generated correctly on the next payroll run on the 1st — no scrambled overrides, no manual adjustments.

3. Non-teaching staff onboarding. A new bus driver, two security guards and a librarian join in July — all non-teaching, all needing the same statutory paperwork as teaching staff. The same enrollment form handles them — pick the relevant department (Transport, Support, Library), capture PAN and Aadhaar, the salary register and EPFO Form 11 batch include them on the next monthly run alongside the teaching staff.

4. Multi-school trust onboarding. A trust runs three schools in one city. The HR head enrolls a teacher to one school today, and three months later the same teacher transfers to a sibling school in the same trust. Inkwelly supports trust-level employees with the Identity & Access Management module; New Enrollment at each school surfaces the trust roster so the second enrollment is a one-click promotion of an existing trust profile, not a fresh entry. Service period continuity is preserved automatically.

5. Re-joining after a sabbatical. A senior teacher who left in 2022 returns in 2025-26 after a two-year break. The HR clerk types her PAN at the start of the form; Inkwelly's Trash & Restore flow surfaces her old record. Her qualifications, certifications, previous employment history and old photographs are preserved — she only needs a fresh academic enrollment for the new session, with the new joining date, new department and new role. The full service history is restored without re-typing a single past field.

6. Probation conversions. A teacher hired in April on six-month probation is confirmed in October. New Enrollment is not used here — instead, the existing employee record's academic remarks field is updated, and the employee documents module generates the confirmation letter. New Enrollment is a one-time create event; the lifecycle that follows is handled by the rest of the Employee Information module.

See New Enrollment on your school's data, live in 30 minutes

Bring three new teachers' joining files to the demo — PAN, Aadhaar, UAN, joining date, department. We will enrol all three live, generate the EPFO Form 11 CSV, and hand you back the appointment letter PDF before the call ends.

Limits, safety and the small print

One person, one record. New Enrollment is a single-person create flow. For onboarding 50 to 200 staff at once during a fresh school migration, use the bulk import flow on the Employee Information module instead — same field set, CSV-driven, the migration team validates your sheet before import.

Required fields are minimal, optional fields are many. The validator hard-requires only First Name, Date of Birth, Gender, Academic Session and Joining Date. Employee ID and Joining Number become optional when auto-generation is enabled in Enrollment Settings. Every statutory identifier (PAN, Aadhaar, UAN, PF, ESI) is optional at enrollment so a teacher with paperwork mid-flight can still be onboarded today — fill the missing identifier later via the same profile.

Inline validation is strict where it matters. PAN must match the official format ^[A-Z]{5}[0-9]{4}[A-Z]{1}$ — five letters, four digits, one letter. Aadhaar must be exactly twelve digits. Email must satisfy RFC validation. Mobile is capped at 15 characters to support international country codes. Title is constrained to one of 12 enum values. Gender is constrained to Male / Female / Other. Religion, Blood Group, Caste Category, Marital Status — all enum-validated. Free-text drift is not possible.

Multi-language is opt-in per school. If your school's supportedLanguages array is ['ENGLISH'] only, the language-icon UI does not appear on the name fields and the form behaves as a single-language form. Add Hindi or your regional language to the school setting once, and every name field across the form, the directory, the appointment letter template and the salary register picks up the multi-language input — without re-deploying or re-training your office staff.

Audit log on every save. Every enrollment writes an audit row — user, timestamp, IP, the full payload (with masked Aadhaar) — so any later edit, correction, or dispute can be traced to the moment of joining. Combined with role-based access, you know exactly which office user enrolled which teacher.

Cross-tenant isolation. Like every Inkwelly module, New Enrollment writes only to your school's tenant. Trust-level promotion across sibling schools is an explicit, audit-logged transfer — never an accidental cross-school write. Multi-school trusts running their own staff lists per school enjoy strict isolation; trust-wide rosters are read-only views built on top of the per-school tenant data.

Hosted in India. All enrollment data — including Aadhaar (masked at rest), PAN (encrypted at rest), photos and the full audit log — is stored on Inkwelly's Mumbai-region PostgreSQL. No cross-border PII transfer occurs as part of normal operation. DPDP Act 2023 obligations — consent capture, purpose limitation, deletion-on-request, breach notification — are built in from day one of every school's lifecycle on Inkwelly.