Every driver. Every paper. Every duty. Tracked, trained, trusted.

How most Indian schools manage their drivers and conductors today

The transport in-charge has a register at the back of the office. On the first page is a list — driver names, mobile numbers, and licence numbers, last updated when the school year began. Behind the list is a folder of photocopied driving licences, some current and some not. The conductors, where the school employs them, are listed on a sticky note. The female attendant assigned to the route carrying minor girls is mentioned only in conversation. When asked, the in-charge can usually name his ten drivers and the two conductors. He cannot, on any given day, tell you which licence expires next month, which conductor missed yesterday's bus, or which driver had a parent complaint last term.

Every school we have worked with starts in roughly this place. Then the year hits its first incident — a parent complains that her daughter's driver was speaking on the phone while driving; a State RTO check finds an expired licence on Bus 6; a vendor's substitute driver shows up on a Tuesday morning without anyone in the office knowing his name. Each incident exposes the same root cause: drivers are not first-class entities. They are sticky notes, photocopies and conversations. The decisions taken about them — hire, fire, promote, retrain, swap — are taken from memory and gut, never from data.

Inkwelly's Transport module gives you the people-management workspace your office never built itself. Every driver, every conductor, every attendant, every helper is a real profile with documents, training records, route history, complaint history, attendance, and salary if applicable. The transport in-charge stops being a switchboard — he becomes an actual operations manager. The principal, when she asks, gets a clean answer about who is on which bus today and why.

How the operators workspace actually works

Open Transport → Operators. Every person who works on or for the school's buses is listed — drivers, conductors, female attendants, helpers, even the workshop mechanic if you want him on the books. Each row carries the name, the role, the operator (the school itself, or a named vendor), the photograph, the route currently assigned, the licence validity, and a colour-coded summary of paperwork and complaints — green if clean, amber if anything is within 30 days of expiry or there is an open complaint, red if a paper has lapsed or a complaint is unresolved.

Click into any person. Their profile reads like a single source of truth. Identity — full name, photograph, date of birth, blood group, emergency contact, home address. Documents — driving licence with class and expiry (for drivers), conductor licence where applicable, Aadhaar reference, police verification, medical fitness certificate. Operations — currently assigned route and bus, shift timings, days available, leave history. Training — every training session attended, with date, topic and certificate. Performance — punctuality, attendance, parent complaints history, accident history, incident history, the speed and route-deviation alerts attributed to them. Salary — if your school pays drivers in-house, the salary is on the profile, with the employee payroll integration for owned drivers. Vendor drivers carry the vendor's billing rate.

This is not a spreadsheet of names. It is the workspace that lets the in-charge run drivers like an operations manager, the principal review the team like a leader, and the school answer parent questions in seconds, not minutes.

Walkthrough — four screens the in-charge runs every week

“Pehle drivers ke documents folder mein the. Kis driver ki license kab expire hogi pata hi nahi tha. Ab WhatsApp pe 30 din pehle alert aata hai — ‘Ramesh ji ki license 18 ko expire ho rahi hai’. Hum advance mein renew kara lete hain. RTO check pe ek baar bhi tension nahi hota.”

Five real moments this is built for

1. The 7:42 a.m. parent question. "Who is driving my daughter today?" Old way: receptionist says she will check and call back; sometimes she does. Inkwelly way: she opens the parent's child's bus profile, sees the driver's name, photograph and contact, says "Ramesh ji is driving today, his licence and police verification are both current, this is his fourth year on this route". The parent thanks her and goes back to work.

2. The licence expiring on the 18th. A WhatsApp lands on the in-charge's phone on the 18th of the previous month — "Ramesh's driving licence expires in 30 days". He sends Ramesh to the State RTO portal for renewal, attaches the new licence to the profile, and Inkwelly's amber turns back to green. The school never runs a bus on an expired licence.

3. The substitute driver on a Tuesday. Bus 4's regular driver applies for leave for two days. The in-charge approves Suresh as the substitute — his licence is valid, his training is current, and he was already off rota that day. The trip log records the substitution. The parent app updates with Suresh's name and photograph. Parents see no surprise. The morning runs.

4. The October parent complaint about phone-on-the-wheel. A parent says her daughter saw the driver on the phone last Tuesday. The in-charge opens the driver's profile, sees one open complaint with the same category from August, sees two speed alerts during morning trips that week, and sees that the safe-driving training certificate is overdue. He counsels the driver, books him for a fresh training session, and writes a note on the complaint with a closure date. The parent gets a substantive update. The driver knows the conversation was fair.

5. The vendor's surprise substitute. A vendor sends a substitute driver on a Wednesday morning. Inkwelly's pre-trip check refuses to start the trip because the substitute is not on the operators register. The in-charge gets a flagged alert, asks the vendor to register the driver with all the papers, and only then approves the start. No vendor driver runs a school bus without verified papers. Period.

See your transport team rebuilt during a 25-minute demo

Bring photographs of three of your drivers' driving licences. On the demo we will set up their profiles inside Inkwelly while you watch — you will see exactly what the people-management workspace feels like before you sign anything.

Limits, safety and the small print

Roles supported. The same workspace handles drivers, conductors, female attendants and helpers. You can add custom roles per State if a regulator requires it (some States require a separate certification for school van drivers, for example). Each role gets its own fields and route-eligibility rules.

In-house and vendor. In-house drivers integrate with Inkwelly's employee information and payroll modules — the operators register and the HR file are the same person. Vendor drivers stay on the operators register only; the vendor's billing rate is what flows into the cost-of-ownership reporting.

Document scans. Each scan is stored at full resolution on Inkwelly's CDN, served to your screen in seconds. PDF, PNG and JPEG are accepted, up to 10 MB per scan. Older documents stay attached after a renewal so the timeline is never lost.

Renewal reminders. Per document type, per person. Defaults match what schools want — 30 days amber, 7 days red, day-of ping. The principal's dashboard rolls up amber and red counts across the team.

Privacy and access. Driver names and photographs are visible on the parent app for transparency — only the parent of a child currently on that driver's bus can see them. Licence numbers, salary, complaint history and police verification are visible only to the transport in-charge, the principal and (for the inspector during a verified visit) on-screen briefly. Class teachers see only the driver of the bus assigned to their class.

Migrating the register. During onboarding, our team takes photographs of your existing register, folder and sticky notes, keys the data into Inkwelly with you, attaches the scans, and hands you back a fully-loaded operators workspace. A school with 12 drivers is typically live in two weekends.

Audit readiness. Every change to a profile, document or assignment is recorded — who, when, what changed. The full history is exportable per person or per term. Auditors at board affiliation reviews see live records, not screenshots.