Fleet ready. Papers ready. Even when the inspector arrives unannounced.
Every school bus, every paper, every fuel bill in one place. The fitness certificate that is 30 days from expiry shows red on the principal's dashboard. The insurance that lapsed yesterday triggers a WhatsApp to the in-charge. The maintenance bill that was approved last month is one click from the audit. Built for the way Indian schools actually run their fleet — owned buses, vendor buses, vans for hostel runs — under a Motor Vehicles Act regime that does not give second chances.
How most Indian schools manage their bus fleet today
The transport in-charge has a green diary. Inside it are pages for each bus: registration number on top, fitness expiry written in pencil, insurance renewal date scribbled in the margin, the driver's licence number on a sticky note that has lost its stick. The bus's RC and permit are in a manila folder in the principal's filing cabinet. The PUC certificates were issued by a roadside testing centre; only the most recent one is in the folder. Last month's tyre bill is in the accountant's drawer. The fuel log lives on the workshop wall in chalk.
When the bus needs servicing, the in-charge remembers — sometimes. When a fitness certificate is 30 days from expiry, no one sees it; no one sets a reminder. When the RTO inspector turns up unannounced, two staff spend the next hour digging through the folder, the diary, the sticky notes and the cabinet, trying to assemble a complete picture of one bus that should have taken five minutes. Sometimes the picture is incomplete. The school pays a penalty, and the principal makes a quiet promise to digitise everything next term.
Next term arrives. The diary gets a fresh cover. Nothing else changes. Except now it is also the year someone tells you the Motor Vehicles Act, the State RTO rules and the CBSE School Bus Safety Guidelines all expect a documented, queryable maintenance and compliance trail — not a diary. Inkwelly's Transport module gives you that trail without asking the in-charge to learn anything new beyond the bus and the paper he already touches every day.
How the fleet workspace actually works for an Indian school
Open Transport → Buses. Every bus the school runs is listed — the school's own buses and the vendor's, side by side, in one register. Each row carries the registration number, the bus name ("Bus 4", "Vidya Express"), capacity, fuel type, the route it is currently running, the driver on duty today, and a colour-coded compliance summary — green if every paper is current, amber if any is within 30 days of expiry, red if anything has lapsed. Filter by status, by fuel type, by GPS-fitted, by ownership.
Click into any bus. You land on a profile that reads like a single source of truth for that vehicle. Identity — registration number, chassis, model, year, capacity, ownership type, the operator who runs it. Documents — RC, fitness certificate, insurance, permit, PUC, road tax, with issue and expiry dates and scanned attachments. Operations — the route currently assigned, the driver, the conductor, the GPS device fitted, the speed governor flag. Money — the year's fuel cost, the maintenance ledger, vendor billing if applicable. History — every incident logged, every service done, every previous driver, every previous route assignment.
This is not five different modules glued together. It is one workspace that the in-charge can run on a single screen — and that the principal can review, the accountant can audit, and the inspector can be shown without drama.
Every paper an Indian school actually has to keep ready for inspection
- Registration Certificate (RC) — issue date, validity, scanned copy on the bus profile
- Fitness Certificate — the State RTO's annual mandatory check, with renewal reminders 30 days out
- Insurance — typically annual, with the policy number, insurer, sum insured and renewal date
- Permit — the contract carriage or stage carriage permit your bus runs under, with validity dates
- Pollution Under Control (PUC) certificate — typically valid for 6 to 12 months, renewed at the testing centre
- Road tax — quarterly or annual depending on the State, with payment receipts attached
- Speed governor compliance — ticked per bus, in line with the CBSE School Bus Safety Guidelines
- GPS device fitted — a Yes/No flag matched against the live tracking system
- Driver's photograph and a copy of the driving licence, on the bus profile for inspector review
- Conductor or female attendant on routes carrying minor girls — POCSO Act 2012 alignment
- Annual maintenance contract details, if any, with the workshop or service partner
- Per-bus accident and incident history, with severity, root cause and corrective action
Walkthrough — four screens the in-charge actually lives in
A document register that warns you before the RTO does
Each bus has a documents tab that reads exactly like the inspector's checklist. RC, fitness certificate, insurance, permit, PUC, road tax — each entry has an issue date, an expiry date, and a scanned copy attached. Inkwelly colour-codes everything. Anything within 30 days of expiry turns amber on the principal's dashboard, on the in-charge's worklist, and (if enabled) on a WhatsApp to the in-charge. Within 7 days, red. On the day, it pings once more.
When the RTO arrives unannounced, you do not search a cupboard. You open the bus profile, hit Print, and hand the inspector a single-sheet summary — every paper currently active, with thumbnails of the scans and the next renewal date. The same screen also shows the fitness centre receipt for the most recent renewal so the inspector can verify continuity. A 60-minute paper hunt becomes a 5-minute show-and-tell.
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 — a small breakdown, a late arrival, a side-mirror accident — with date, severity, root cause and corrective action. Over a term, each bus's profile shows total cost-of-ownership, mean time between breakdowns, and incident count.
This is the data the principal actually needs at term-end. Which buses are profitable? Which vendor's vehicles break down twice as often as the rest? Should we keep the 14-year-old bus for another year, or replace it? Without this log, the conversation is opinion. With it, the conversation is numbers — and the school's annual board review acquires a section it never had before. Insurance claim disputes, where they happen, are settled with the maintenance ledger as evidence. Vendor renewal negotiations get sharper because the data is on the table.
Fuel logs that cut leakage without changing routine
The driver fills fuel at the school workshop or at a designated petrol pump. Inkwelly's fuel log captures the date, odometer, fuel type, quantity, rate, total cost, the petrol pump's bill number and a scanned copy of the receipt. The bus's mileage is computed automatically (kilometres covered between fills, divided by litres). Anomalies surface — a bus suddenly clocking 4 km/litre when it normally clocks 6 says something is wrong, and the in-charge investigates.
Most Indian schools lose between 8 and 15 percent of their fuel budget every year to petty leakage that no one sees in time. Inkwelly does not enforce policing — it simply makes the leakage visible. Schools that move from chalk-on-the-workshop-wall to a digital fuel log typically see their fuel cost drop by 6 to 10 percent in the first quarter. The accountant nods. The principal smiles. The transport in-charge gets credit for a number that was always there.
Owned, vendor, hired — one register, one principal
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, its own driver pool, its own accountability. Inkwelly treats operators as first-class entities so the principal sees the whole picture, not a fragmented one.
Create operators with type marked as in-house or vendor. Attach a contract document, a billing rate, a contact person and the operator's GST details. Each bus lists the operator it belongs to. The bus 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 the vendor's bus actually ran, how many incidents were logged, what the contract rate is. The accountant cross-checks the vendor's bill against this report. Disputes drop. Payment cycles tighten. The school stops paying for trips that never happened.
“Saal mein do baar RTO inspection ke time poora office tense ho jaata tha. Ab ek button dabaake har bus ke saare papers nikal aate hain — fitness, insurance, permit, PUC, sab dates ke saath. Inspector 5 minute mein satisfied ho jaata hai aur main apni baaki ki list mein wapas chala jaata hoon.”
Five real moments this is built for
1. The unannounced RTO inspection on a Wednesday. Old way: two staff scramble for an hour. Inkwelly way: the in-charge clicks Print on each bus's profile and hands the inspector a single-sheet summary per bus — RC, fitness, insurance, permit, PUC, road tax, all current, all dated. Inspection wraps in 30 minutes for an entire fleet of eight buses.
2. The fitness certificate due in 28 days. A WhatsApp lands on the in-charge's phone with the bus number and the date. He books the renewal at the State RTO portal, attaches the receipt to the bus profile, and Inkwelly's amber turns back to green. No frantic calls on the morning of the inspection.
3. The mid-term workshop visit. Bus 4 needs servicing. The in-charge marks the bus under maintenance with the workshop name and expected return date. Inkwelly automatically suggests substituting Bus 12 onto Route 4 — same capacity, same fuel type, papers all current, currently on a less-used route. He approves the swap, the parents on Route 4 see no change, the system records the substitution for vendor reconciliation if it applies.
4. The 14-year-old bus decision. At the year-end board review, the principal pulls the cost-of-ownership report. Bus 7 is at ₹4.2 lakh in maintenance over 18 months. Bus 11, same age, is at ₹1.6 lakh. Bus 7's incident count is 9 versus Bus 11's 2. The board votes to retire Bus 7 and contract a fresh vendor bus on Route 7 instead. Decision time: 12 minutes. Numbers, not arguments.
5. The insurance claim dispute. A bus has a minor accident. The insurer asks for the maintenance and inspection history. Inkwelly exports the bus's full ledger — every service, every fitness renewal, every PUC, every prior incident. The claim is settled in three weeks instead of three months. The school's no-claim bonus survives intact.
Common operations the in-charge runs each week
- Scan the dashboard for amber rows and book renewals before they go red
- Renew the State RTO fitness certificate and attach the receipt to the bus profile
- Log every fuel bill on the day the bus is filled, not at month-end from memory
- Log a service visit with cost as soon as the bus comes back from the workshop
- Mark a bus under maintenance and approve the substitute the system suggests
- Review the morning's incident log and follow up on any open corrective action
- Pull the bus profile when the principal asks any question about any bus
- Run vendor reconciliation at month-end against actual trips and incidents recorded
- Export the bus's history to defend an insurance claim or board affiliation review
- Retire a bus cleanly with a date, a reason and a final-papers archive
See your school's bus fleet rebuilt live during a demo
Bring photographs of the fitness certificate, insurance and permit of two of your buses. On the demo we will set them up inside Inkwelly while you watch — you will see exactly what an inspection-ready bus profile looks like before you sign anything.
Limits, safety and the small print
Buses per school. Unlimited — schools running 60 plus buses use the same plan as schools running two. Sorting, filtering by ownership and fuel type, and search by registration number keep the list usable as the fleet grows.
Document scans. Each scan is stored at full resolution on Inkwelly's CDN, served to your screen in seconds. We accept PDF, PNG and JPEG; a single document scan is capped at 10 MB which covers every State RTO form we have seen. Older documents stay attached even after a renewal so the timeline is never lost.
Renewal reminders. Set per document type, per bus. The defaults match what most schools want — amber at 30 days, red at 7 days, ping on day. The principal's dashboard rolls up amber and red counts across the fleet so a single glance tells you whether anything needs attention this month.
Vendor billing. Operators marked as vendor get a monthly invoice generated against actual trips run, incidents logged, and the contract rate. The accountant cross-checks the vendor's own invoice against this report. Disputes about phantom trips simply stop happening.
Audit readiness. Every change to a document, fuel log entry, maintenance entry or incident is recorded — who, when, what changed. The full history is exportable per bus or per term. Auditors at board affiliation reviews see live records, not screenshots.
Privacy and access. Driver and conductor names and licence numbers are visible to the transport in-charge, the principal, and the inspector during a verified visit. Class teachers see only the bus assigned to their class. Bus and document data lives on servers in Mumbai, encrypted, handled the way the DPDP Act 2023 expects.
Migrating the diary. During onboarding, our team takes photographs of your existing diary, folder and cabinet, keys the data into Inkwelly with you, attaches the scans, and hands you back a fully-loaded fleet workspace. A school with 12 buses is typically live in two weekends.
Belongs to
1 moduleFrequently asked
7 questionsCan Inkwelly handle both school-owned buses and vendor-contracted buses in one place?
Yes. Each bus is tagged with its operator, and operators are marked as in-house or vendor. The same fleet workspace shows both side by side. Vendor invoices generate from actual trips run — the school stops paying for phantom trips that never happened. Disputes about vendor billing drop sharply once the data sits in one place.
What happens when a fitness certificate or insurance is about to expire?
The bus's row turns amber on the principal's dashboard and on the in-charge's worklist 30 days before expiry. A WhatsApp goes to the transport in-charge if the school has WhatsApp alerts enabled. At 7 days the row turns red and pings again. On the day, one final ping. The renewal happens on the calendar, not in the cabinet.
Do we need to scan and upload all our existing documents to start?
Not all at once. During onboarding, our team helps you photograph and upload the active documents (the most recent fitness, insurance, permit, PUC, road tax) for each bus. Older paperwork can be added gradually — the system is fully usable from day one. Within a month most schools have a complete documented history for every bus.
Will Inkwelly work for schools that run only two buses?
Yes. The same plan supports schools running two buses and schools running 60 plus. The dashboard scales down cleanly — you do not see fields you do not need. Smaller schools usually find the renewal reminders and the fuel log saves more time than they expected.
Can we track maintenance for vans and other smaller vehicles, not just buses?
Yes. The fleet workspace handles every kind of vehicle the school runs — buses, vans, autos, even cars used for hostel airport runs. Each gets the same kind of profile: identity, documents, operations, money and history. Vehicles are tagged by category so reports can break out by category.
What if our State requires extra paperwork beyond RC, fitness, insurance and permit?
You can add custom document types per state — some States require a school transport authorisation letter, some require a contract carriage permit endorsement, some require a quarterly road tax receipt. Each custom type gets its own renewal reminders, scans and audit trail. The set we ship covers the documents every State RTO has asked for in our existing client base.
Can the principal see the cost of every bus at year-end without asking the in-charge?
Yes. The bus profile rolls up cost-of-ownership for the year — fuel, maintenance, vendor billing, incident-related costs. The fleet view rolls these up across all buses. The principal opens the report on a tablet during a board meeting and answers questions live, no spreadsheet preparation needed.
You might also like
2 readsSee Inkwelly on your school
30-minute demo. We open your current ERP with you and load your data into Inkwelly on the call. Dated go-live plan by the end of it.