Every employee document — tracked, required, audited. Aadhaar, PAN, POCSO — never missing again.

Why Indian schools quietly fail employee document audits

The CBSE affiliation review team arrives in July. The reviewer asks for police verification certificates of all 67 teaching and non-teaching staff under POCSO Act 2012. The HR clerk reaches for the steel almirah. 43 verifications are inside — some original, some xerox, some folded inside a teacher's appointment letter. 14 are missing. 10 nobody can find. The reviewer notes the gap and warns the school: produce the rest in 7 days or the affiliation renewal will stall.

Next month, the auditor for the EPFO inspection turns up. He wants Aadhaar copies, PAN cards and bank passbooks of every employee on the salary roll. The accountant maintains them in a Google Drive folder named 'Salary Docs - 2025'. 8 employees never gave their PAN copy. 3 gave a different bank account on paper than what the school is depositing salary into. Form 16 generation in May had pulled wrong PANs for those 3 — TDS quarterly statement Form 24Q is filed wrong. The auditor flags it.

We asked: what if every employee document — Aadhaar, PAN, B.Ed degree, CTET / TET certificate, police verification, appointment letter, experience letter from previous school, bank cancelled cheque, medical fitness, EPF nomination — lived in one structured store per employee, with a school-wide coverage dashboard that shows exactly which documents are missing, broken down by department and document type, refreshed every time an HR clerk uploads a new file? So we built Employee Documents Management inside the Employee Information module. The same coverage bars and heatmap shown in the dashboard answer every audit — POCSO, EPFO, CBSE, ICSE, state board — in 5 seconds, not 5 days.

How Inkwelly Employee Documents works

Document storage exists at two levels in Inkwelly — one inside every employee's profile for the HR clerk who manages one staff member at a time, one as a coverage dashboard for the principal or admin who needs the whole-school compliance picture. Both views read from the same underlying records.

Per-employee tab — /employees/<id> → Documents. Open any employee profile, click the Documents tab. The view renders as a 2- or 3-column grid of document cards, sortable by upload date (newest first). Each card shows: the document type badge (Aadhaar / PAN / B.Ed / Police Verification / Appointment Letter), the document name, the upload date, an optional description, an internal note (the remarks field, italicised), and a one-click Download button that opens the file in a new tab via signed URL. A Filter dropdown at the top lets you narrow to a single document type — useful when an employee has 6 documents but you only want to see B.Ed-related ones for a CTET application packet. Pagination is set at 20 cards per page; an HR clerk verifying a long-tenured employee with 30+ documents pages through cleanly.

Coverage dashboard — /employees overview cards. Open the Employees module dashboard. The Documents card shows three things: (1) Coverage by type — a horizontal-bar list per document type, sorted worst-coverage-first; each row shows <typeName> [Required badge if mandatory] — <collected>/<total> — <percentage>% with a colour-coded progress bar (red <60%, amber 60–89%, green ≥90%). (2) Coverage heatmap — a department × document-type grid where each cell shows the percentage of employees in that department with that document, colour-coded (green ≥90%, amber ≥50%, red <50%). (3) Recent uploads — the last five employeeName · documentTypeName · employeeIdShort · X minutes ago rows so the principal can see what's flowing in. The same coverage data answers POCSO inspections, EPFO audits, CBSE affiliation reviews and salary-statutory checks.

Upload flow. From the per-employee Documents tab, click Upload. The dialog asks for the document type (dropdown of your school's configured employee document types, with mandatory ones flagged), document name (required), optional description, optional remarks (the internal note shown in italics on the card), and the file itself. Files go through Inkwelly's MediaPicker — PDFs, JPEG, PNG, HEIC, WEBP are accepted. The file uploads to the school's encrypted media store and links to the employee's document record. Save — the grid refreshes, coverage bars on the dashboard re-compute on the next page load. Edit lets you swap the file or change the type. Delete asks for confirmation, removes the record + underlying media file, and writes the action to the audit log.

Walkthrough — four screens, end to end

“POCSO inspection se 1 hafta pehle dashboard kholi — Police Verification 71% par tha, Transport department 38% par. Maine driver-conductor list pull ki, sabko WhatsApp kiya, 5 din mein 11 verifications upload ho gayi. Inspection ke din coverage 96% par tha. Inspector ne sirf 2 minute mein heatmap dekha aur sign-off de diya.”

When this matters in the school year

April – June: new joiner onboarding. Every new appointment in an Indian school is a small document storm — Aadhaar, PAN, bank cancelled cheque, qualification certificates, B.Ed / CTET / TET if teaching, experience letters from previous school, two passport-size photos, EPF nomination Form 11, ESIC details if applicable, police verification (initiated separately), medical fitness. Inkwelly's per-employee Documents tab is the joining-day checklist — the HR clerk uploads each one as the employee hands it over, the dashboard's coverage bars increment, and on day 7 the employee's profile is fully document-compliant.

July – September: CBSE / ICSE affiliation review. The reviewer asks for teacher-qualification proof, police verification, appointment letters and experience certificates of every staff member. The dashboard's Coverage by Type bars give the headline numbers; the heatmap tells you which department is dragging. You pull the deficient files from each profile, chase them up, and re-upload before the reviewer comes back.

October – November: EPFO compliance audit. EPFO inspector wants Aadhaar, PAN, UAN allotment, EPF Form 11 and bank-passbook copies for every salaried employee. The Required-flagged document types on the dashboard are exactly this set; their coverage percentages are the audit answer.

December – January: Form 16 / Form 24Q TDS prep. TDS Section 192 quarterly statement Form 24Q is filed with employee PANs from the documents on file; if the PAN file is wrong, the TDS goes to the wrong PAN and you spend February correcting it on TRACES. Inkwelly enforces PAN-on-file as a Required type; HR doesn't generate Form 16 against an employee who's missing it.

Continuous: POCSO Act 2012 compliance. Police verification certificates expire (typically 3 years) and need renewal. Filter the dashboard to Police Verification, sort the coverage drop, and chase renewal proactively — never waiting for the next CBSE review to flag it. School transport drivers and hostel wardens are the most-scrutinised cohort — the heatmap's Transport and Hostel cells are the rows you watch every quarter.

Year-end: exit / full-and-final settlement. When an employee leaves, the office issues a relieving letter, experience letter, Form 16 final, EPF transfer documents, and a Bonafide for the next employer. Every reference document — original appointment letter, all uploaded police verification cycles, every B.Ed / qualification proof — is read directly from the documents tab. No more searching through the steel almirah for a 5-year-old appointment letter.

See Employee Documents Management on your school's data, live in 30 minutes

Bring 5 sample employee folders — Aadhaar, PAN, B.Ed, police verification, appointment letter. We'll set up your employee document types during the demo and show how the per-employee tab + dashboard coverage + department heatmap work on your real staff list.

Limits, safety, and the small print

File size. Individual file uploads are capped at the standard MediaPicker limit (typically 10 MB per file — covers a high-resolution scanned PDF, a degree certificate or a passport-size photo). Larger scans should be downsampled or split. The MediaPicker shows a clear error message when the limit is hit; it never silently truncates.

Supported formats. PDF, JPEG, PNG, HEIC, WEBP. Scanned PDFs from office scanners and HEIC photos from an HR clerk's iPhone coexist without conversion friction. Inkwelly does not OCR uploaded files — the document record stores the file, not its text content. (OCR is on the roadmap for v2.)

Per-employee record limits. No hard cap on documents per employee — a 20-year-tenure principal with 35–40 documents (multiple police verification renewals, salary-revision letters, training certificates, multiple ID proofs) is fully supported. The grid paginates 20 cards per page; the document-type filter cuts through long lists fast.

Required vs optional changes. When a document type is changed from optional to required, employees who already uploaded it stay collected; the dashboard's coverage bar for that type updates on next page load. Employees who haven't uploaded shift into the Required gap. The reverse change (required → optional) keeps the data; only the dashboard's Required badge disappears.

Multi-tenant isolation. Document records and underlying media files are scoped strictly per-school within multi-school organisations. Employees moving between schools of the same trust have their documents copied or referenced explicitly — never silently shared. Audit log shows every cross-school document access.

Audit log. Uploads, edits, deletes, and document-type changes all write to the school audit log — user, timestamp, IP address, document type, file name, action verb. Audit log is exportable from the school admin panel and retained for the full lifecycle of the employee plus the school's defined retention period after exit.

Role-based access. Document upload, edit and delete are gated to school admin and HR roles by default. Department heads can view documents of employees in their reporting line but cannot delete. Self-service uploads from the employee portal go through an HR-approval workflow before going live. All of this is configurable from the Identity & Access Management module — your school decides the policy.

Soft-delete is not the default. Deleting a document permanently removes the record and underlying media file. This is intentional — employee documents are personal data under the DPDP Act, and individuals have the right to deletion. If you need a 'safety net' before permanent deletion, configure the role policy so that only one or two designated admins can delete and require a confirmation step. The audit log captures every delete with sufficient detail for retrospective review. (Soft-delete with restore window is on the roadmap as an opt-in setting for v2.)