Run school transport without the daily phone calls. without the daily phone calls

How most Indian schools run transport today

In most schools, transport is the office's loudest pain. The transport in-charge keeps a printed route sheet on his desk that was last updated in April. Parents call the school office at 7:42 a.m. asking why the bus is late, and the receptionist has no answer because she has no link to the bus. The accountant maintains a separate Excel sheet for transport fees, which never matches the tuition fee register. When a parent asks for a transport fee receipt for ITR, two clerks search three folders for ten minutes. By the time the principal hears about the broken stop sign or the driver who missed a turn, half the parents already know.

The cost is rarely measured but always paid. Parents who get five "bus is on the way" calls per week eventually withdraw their child, citing "poor coordination". RTO insurance and fitness renewals are missed because nobody owns the calendar — and an expired fitness certificate during a road check costs the school both a penalty and a press-worthy headline. Transport fee leakage of even ₹500 per child per term across 200 students is ₹2 lakh quietly lost every year. And the transport in-charge, who was meant to focus on driver training and route optimisation, becomes a full-time call-centre.

If you recognised three of those scenes, you already know why transport software is on your shortlist this year. The question is not whether you need it. The question is whether the system you pick handles routes, vehicles, fees, complaints and statutory paperwork in ONE place, or asks you to glue four tools together. Inkwelly Transport is built as the single workspace your office already wished it had.

What Inkwelly Transport actually replaces

Inkwelly Transport is the operations layer for your entire fleet — owned buses, vendor buses, vans, autos and even cabs used for boarding-school airport runs. Routes and stops are drawn once. Vehicles are listed once with full statutory papers. Drivers and conductors are added once with licence and contact details. Students are assigned to a stop once, and from that single click, the parent gets the route confirmation, the transport fee appears in the student's fee ledger, the accountant sees the new invoice, and the driver app shows one more name on his stop list.

From that point on, every change is propagated automatically. A student switches stop mid-year — fee adjusts pro-rata, the old driver loses the name, the new driver gains it, the parent receives a confirmation. A vehicle goes for service — the substitute bus is recorded, the in-charge sees the impact, the route is reassigned in two clicks. A fitness certificate is 30 days from expiry — the system reminds the in-charge in the dashboard and on WhatsApp until renewal. Nothing slips because the system, not memory, owns the calendar.

A complete transport operations toolkit

This is not transport "as a feature inside a generic ERP". It is the operating system for your transport department. Below is the surface area — every tab the transport in-charge will live in, every workflow the office runs once a day or once a term, every report the principal asks for in a board review.

Every tab the transport in-charge will use

Routes and stops — the foundation of everything

Routes and stops are the spine of the transport module. Every other entity — vehicle, driver, student, fee, invoice, complaint — references a route and a stop. Inkwelly insists on doing this once, doing it carefully, and never asking you to do it again.

Vehicles and the statutory paperwork no one wants to track

Indian school transport is regulated. The Motor Vehicles Act, state RTO rules and CBSE School Bus Safety Guidelines all converge on the same checklist — RC valid, fitness valid, insurance valid, permit valid, PUC valid, speed governor working, GPS fitted, driver in uniform with valid licence. Inkwelly turns this checklist into living data, not a folder of scanned PDFs nobody opens until the day of the inspection.

A document register that warns you before the RTO does

Each vehicle has a documents tab that lists RC, fitness certificate, insurance, permit, PUC, road tax and any state-specific paper. Each entry has an issue date, an expiry date, and a scan attached. The system colour-codes anything within 30 days of expiry as amber, anything within 7 days as red, and notifies the transport in-charge by WhatsApp.

When the RTO arrives for a surprise check, you do not search a cupboard. You open the vehicle profile, hit Print, and hand the inspector a single-sheet summary with thumbnails of every active document. The same screen shows pending renewals so you can show the inspector that the next renewal is already booked.

Maintenance and incidents — cost-per-bus that finally makes sense

Log every service visit with date, odometer reading, work done and cost. Log every incident — minor breakdown, late arrival, accident — with a date, severity and resolution note. Over a term, the vehicle profile shows total cost-of-ownership, mean time between breakdowns and incident count.

This is the data the principal needs at term-end review. Which buses are profitable? Which vendor's vehicles break down twice as often as the rest? Should we replace the 14-year-old bus or extend by one more year? Without this log, the conversation is opinion. With it, the conversation is numbers.

Operators — your fleet is half-owned, half-vendor, fully tracked

Most Indian schools run a hybrid fleet. Two or three buses are school-owned. Three more come from a vendor on a per-trip or per-month contract. One additional van is hired during exam season. Each operator has its own billing terms, driver pool and accountability standards. Inkwelly treats operators as first-class entities so the principal sees the whole picture, not a fragmented one.

In-house and vendor in one workspace

Create operators with type marked as in-house or vendor. Attach a contract document, a billing rate (per route, per trip or per month), a contact person and GST details. Vehicles list the operator they belong to. The vehicle profile rolls up vendor cost into the maintenance ledger.

At month-end, generate a vendor invoice from the system itself — Inkwelly knows how many trips each vendor's bus ran, how many incidents were logged, and what the contract rate is. The accountant cross-checks the vendor's bill against this report. Disputes drop, payment cycles tighten, and the school stops paying for trips that never happened.

Student-to-stop assignment — the single source of truth

The student assignment screen is where transport meets student records. One click here means: the student is on this stop, on this route, on this vehicle, with this driver. The transport fee for that route is added to the student's fee ledger. The parent receives a route confirmation. The driver app updates.

Assign one student, one sibling group, or a whole class

For a single child — open the student profile, pick the route and stop, set a start date, save. For sibling groups — assign the elder sibling and the system suggests applying the same route to the younger one. For brand new admissions across a class — bulk-assign by selecting the class, picking the route, and resolving any stop preferences in a single sheet.

Mid-year transfers are handled cleanly. Pick a transfer date, the new route and stop, and the system pro-rates the fee, refunds any unused portion, and notifies the parent. The transfer is logged with a reason — "shifted residence", "vendor route changed", "requested change of stop" — for future audits.

Transport fees — separate from tuition, never out of sync

Transport fees are a different beast from tuition. They depend on which route the child takes, change mid-year if the child shifts stop, attract sibling concessions, are paused during long vacations, and need to be refunded when a child leaves transport. Inkwelly models all of this without asking the accountant to keep a parallel register.

Fee structures the way Indian schools actually price transport

Set up fee structures per route, per stop, per distance tier, or a flat rate for the whole school. Add a sibling concession (e.g. 25% off second child). Add a staff-child concession. Mark certain months as no-charge (May vacation in CBSE schools, October Durga Puja in West Bengal schools). The structure is reusable across routes — change it once, every assigned student updates next billing cycle.

Part-month joiners are pro-rated automatically. Mid-month leavers get a refund line item without a manual journal entry. The accountant's quarterly reconciliation shrinks from two days to two hours.

Invoices, payments, receipts, concessions, refunds — under one roof

Every student on transport has a transport invoice generated alongside their tuition invoice. The parent sees one combined fee bill in the parent app, with tuition and transport listed as separate line items so the receipt is clear. Online payment via UPI or Razorpay reconciles to both ledgers in one transaction.

Receipts carry the school letterhead, the GST number if applicable, the route and stop, the billing period, and a QR code for verification. Concessions, refunds and adjustments are first-class entries with a reason and an approver, not Excel notes that vanish at audit. ITR season requests for past receipts are answered in 30 seconds, not 30 minutes.

Before and after Inkwelly Transport

“Earlier my receptionist used to take 18-20 calls every morning from parents asking where the bus is. Now those calls have nearly stopped — parents see it in their app. The biggest change is that my transport in-charge actually has time for safety drills now.”

Built for every person who touches transport

A transport workspace is not used by one person. The principal needs the term review. The transport in-charge runs the day. The accountant reconciles the fee. The parent wants a receipt and a complaint channel. Each role gets a screen tuned to their need — but all of them work on the same data.

For the Principal

A single dashboard with the numbers a board meeting cares about — route occupancy, revenue per route, vendor cost per term, document-expiry queue, complaints open vs closed, average complaint resolution time. No chasing the in-charge for spreadsheets. No surprises during board reviews. Drill into any number to see the underlying records. Approve refunds, concessions and vendor invoices that cross the in-charge's authority limit, all with a one-tap audit trail.

For the Transport In-charge

The daily worklist — buses on duty today, drivers absent, documents expiring this week, complaints open, students requesting transfer. One screen tells the in-charge what to do today, in the right order. Documents, incidents, vendor invoices and parent complaints are all routed here. The in-charge stops being the office's call-centre and starts being a real operations manager.

For the Accountant

Transport fees are presented exactly the way the accountant thinks — separated from tuition, with concessions and refunds as line items, with month-end reconciliation built in. Razorpay and UPI settlements are auto-matched to invoices. The day-end report shows what came in, what is pending, and which routes contributed how much. GST handling is explicit where applicable. Year-end audit is a single export — every transport invoice, payment, refund and concession with full traceability.

For the Parent

Inside the parent app the parent sees their child's route, stop, pickup time, drop time, current fee status and any due payment, plus a one-tap complaint button. Receipts arrive on WhatsApp. Route changes show up immediately. There is nothing to install separately — it is the same app the parent already uses for fee, attendance and result. This single change — a parent can self-serve the question "where is the bus?" and "is my fee paid?" — eliminates more than half of the daily phone traffic to the school office.

vs Excel and paper registers

One module, integrated with everything else

A transport system that does not talk to your fee, student and communication modules adds work — it doesn't reduce it. Inkwelly Transport is built to read from the same student database your admission and attendance modules use, write into the same fee ledger your accountant already trusts, and push messages through the same WhatsApp channel parents already receive their report cards on.

Safety, compliance and the data residency question

Indian school transport carries minor children. The bar for safety, compliance and data handling is therefore higher than for any other module. Inkwelly is engineered to make the school's job easier on every one of these axes — not just to claim compliance, but to provide the evidence trail that compliance authorities and worried parents both ask for.

Migration — moving from Excel, paper or another ERP

The biggest blocker every school flags is migration. "It will take three months", "my staff cannot learn new software in admission season", "data entry from scratch will break". Inkwelly's onboarding for transport is built around the opposite assumption — most schools should be live in two weekends, with the data they already have.

From Excel

If you already maintain routes, stops, students and fees in Excel — even three different Excel files — the Inkwelly team will give you a single template. You fill in the data you already have. We import routes, stops, vehicles, drivers, students and fee structures in one pass. You verify on a test instance. Two weekends, fully live. No data is keyed in twice. Sibling concessions, mid-year transfers and historical receipts are migrated with metadata, so a parent asking for last year's transport receipt sees it as if Inkwelly was always there.

From another ERP

If you are switching from Fedena, Entab, Campus, MyClassboard or any other ERP, we have done this migration enough times to make it boring. We export from your current system, map the fields, validate the data, import into Inkwelly. Vendor contracts, document scans, complaint history — all preserved. The school keeps the old ERP read-only for one term so historical lookups are still possible. By the second term, the old system is decommissioned.

From paper

Many schools run transport entirely on paper today — a register on the in-charge's desk, printed route sheets, manual receipts. Inkwelly's onboarding includes a one-day data entry assist by our team. We come on site (in-person for Tier-1/2 cities, remote-with-video for Tier-3), key in the routes, stops, vehicles and student assignments together with your in-charge. By the end of the day, the paper register is digitised, the staff has been trained on the workflow they will repeat, and the school is ready to issue its first digital transport receipt the next morning.

See Transport Management on a real school dataset

20-minute walkthrough on a working school. Bring your own pain points — we will show how each one is handled. No sales pitch.

vs imported global tools (HR/SIS suites)

Stop the 7:42 a.m. phone calls

Twenty minutes. A real school dataset. Decide afterwards. We will not chase you with sales emails.