The IT setup at an Indian school or college doesn't look like an SME's IT setup. The hardware is older, the procurement cycle is longer, the failure pattern is batchy and seasonal, and the buyer (the principal or the institution's IT head) is working against an academic-year budget that doesn't always flex. The standard SME repair playbook — quarterly refresh, distributed marketplace dispatch, near-real-time spare swaps — doesn't fit. This post is the realistic IT-repair budget model for an Indian education institution: how to think about fleet age, where the failure peaks fall in the academic year, why AMCs are mis-sold to this segment, and what actually works.
The education IT-repair pattern is different
Three things make education-sector IT distinctive:
Aging fleets. Schools and colleges keep hardware for longer than commercial operations — 5–7 years for student-facing lab desktops, sometimes 8+ for administrative machines. The failure curve at year 6 is steep; you're operating in the high-tail of the bathtub curve continuously.
Seasonal use. A computer lab gets hammered during teaching weeks and goes idle during breaks. Failures that would surface gradually under continuous use cluster at the start of a semester or just before a key exam window. The IT person's calendar has predictable spikes.
Procurement cycles. Annual budgets are set on the academic-year cycle, often with capital allocations frozen until the next year's budget is approved. A surge of failures in October can't always trigger replacement until the following April.
These are not bugs; they're the structure of the sector. A repair model that respects them works; one that assumes commercial rhythm doesn't.
A per-device, per-year repair budget model
For an Indian school or college, a realistic annual repair budget by device age:
| Device age | Annual repair budget (per device) | Notes |
|---|---|---|
| Year 1–2 | ₹0–₹200 | Warranty + early-failure exclusions |
| Year 3 | ₹300–₹600 | Beyond warranty; minor issues |
| Year 4 | ₹600–₹1,200 | Battery replacements, peripheral wear |
| Year 5 | ₹1,200–₹2,500 | Mid-tier component failures |
| Year 6+ | ₹2,500–₹5,000 | Major repairs likely; replace decision approaching |
For a lab of 40 desktops averaging 4 years old, annual repair budget is roughly 40 × ₹900 = ₹36,000. For a fleet of 200 mixed-age computers across labs, classrooms, and admin, budget ₹2–4 lakh annually for repair, not counting replacement.
The numbers grow when consumables are included (paper, toner for office printers, network gear), but those are typically tracked separately in education budgets.
The summer-break repair wave
The right time to repair an education fleet is when students aren't using it. That's a narrow window — typically the summer break (April-end through early June for most North Indian institutions, slightly different for South Indian and CBSE-aligned calendars). A working pattern:
- Last 2 weeks of the academic year: survey labs, log known issues, photograph problems.
- Week 1 of the break: consolidate the list, get vendor quotes, decide repair vs replace.
- Weeks 2–4 of the break: vendor performs repairs in batches. Onsite or batch-pickup, depending on volume.
- Last week of the break: spot-check, refresh OS images, prepare for the new year.
This concentrates dispatch and saves cost. A vendor doing 30 lab desktops in one visit can offer a per-device price that no individual ticket can match. It also avoids classroom disruption.
The wave is also when major refreshes can happen — OS upgrades, disk imaging, network gear updates. Roll these in.
Why most AMCs mis-fit schools
Annual maintenance contracts are aggressively sold to education institutions. For most, they're not the right model. Here's why:
The fixed-fee structure doesn't match bursty usage. An AMC quotes for "available capacity"; the school uses that capacity in two narrow windows a year and idle the rest of the time.
SLAs don't match school calendars. A 4-hour SLA is overkill when students are on break. A 4-hour SLA during a teaching week is sometimes too slow for an exam-day lab failure.
AMC vendors don't always know education IT. A school's lab desktop is typically managed differently from a corporate desktop — multi-user logins, restored daily, locked-down software. AMC vendors used to corporate fleets aren't always set up for this.
The replace-cycle lock-in. AMCs sometimes try to bundle replacement procurement; the lock-in disadvantages the institution over time.
When AMC does fit: very large institutions (1000+ devices), institutions with onsite IT staff who can manage the contract well, and institutions that have specific compliance reasons to maintain a single-vendor relationship.
When marketplaces are the right fit for schools
A marketplace works well for education when:
- The fleet is in the 50–500 device range.
- Usage is seasonal and repair demand is bursty.
- The IT manager wants per-ticket visibility without managing a vendor relationship full-time.
- The procurement department wants a single point of GST invoicing without paying for AMC capacity.
For schools running mixed equipment across labs, classrooms, library, and admin, the marketplace model often replaces the patchwork of "the person we always call for desktops" + "the printer guy" + "the network guy" with a single dispatch surface. Each vendor still does what they're good at; the institution just doesn't have to maintain three separate relationships.
Government and grant procurement: GST invoicing
For schools and colleges that procure through grants, government tenders, or specific accounting structures, GST-compliant invoicing per repair event is non-negotiable. The vendor must issue a GST invoice in the school's name, with the school's GSTIN if applicable. Cash-economy local repair shops, however good they are technically, fail this test for grant-funded institutions.
A marketplace with verified vendors who all issue GST invoices solves this without the school having to police invoice quality per ticket. See our GST-ready asset register post for the broader procurement-invoice discipline that schools should adopt.
How a marketplace handles a 40-machine lab failure
Imagine a CBSE secondary school with a 40-desktop computer lab. The labs went unused for three weeks of winter break. On day one of the new term, eight machines won't boot, six have network issues, and the rest are slow. The class is in 90 minutes.
A WhatsApp call to the institution's regular technician gets a "I'll come tomorrow". A marketplace dispatch:
- Submit a batch ticket for 14 machines, listing the symptoms.
- Validation call within 15 minutes; validator pre-classifies: 8 boot issues (likely PSU or RAM), 6 network issues (likely switch or cable side).
- Two vendors assigned — one with hardware skill flag, one with network skill flag. Both arrive within 4 hours.
- By end of day: boot issues triaged (3 PSU swaps, 2 RAM reseats, 3 likely motherboard for next-day return), network issues resolved (switch reset + cable replacements on 6).
- Single GST invoice for the institution covering the day's work.
The classroom returns in a day with degraded capacity instead of waiting a week.
Fixr supports batch tickets for education and other multi-device contexts, with the platform's three-role validation step handling the upfront classification that turns a 14-machine "the lab is down" message into a triaged dispatch. The platform is free; vendor invoices the school directly.
What about Chromebooks and education-specific devices?
Increasingly, Indian schools deploy Chromebooks rather than full Windows PCs in student-facing roles. The repair pattern shifts:
- Lower per-device repair cost (Chromebooks are simpler hardware).
- More replacement than repair at year 5–6, because Chromebook costs are low enough that repair often doesn't justify itself.
- Different vendor skills required — many Windows-laptop technicians can work on Chromebooks competently, but skill flags matter.
The same marketplace model fits; the device-class flag is the operational difference.
A short pre-break repair SOP for an Indian school
Three weeks before the summer break:
- Survey every device. Tag known issues. Even minor issues — slow boot, occasional crash, fan noise.
- Consolidate into a list. Group by symptom and by physical location.
- Get a quote. Either from a regular vendor or by posting the batch ticket to a marketplace.
- Schedule the work for the break window, with a defined start date and end date.
- Plan the OS / image refresh simultaneously if the cycle calls for it.
- Reserve 10–15% of the budget for unexpected discovery during the break.
This is the operational discipline that turns the summer break from "we'll fix things if we get time" into a planned maintenance window.
FAQs
Should I capitalise repair costs or expense them? Routine repairs are expensed; substantial component replacements that extend useful life can sometimes be capitalised. Coordinate with your institution's accounts team for the specific treatment.
How long should a school keep a desktop in service? For administrative use, 6–8 years is reasonable. For student labs, 5–7. Beyond that, the repair cost trajectory and the educational software requirements both push toward replacement.
Is open-source software a substitute for repair / refresh budget? Partly. Running Linux on otherwise-failing machines can extend useful life by 1–2 years for basic use cases, and the licence savings can fund repair. Not a universal answer; teaching requirements determine feasibility.
What about libraries and other shared computers? Same model as lab desktops, with usage patterns that are steadier (not seasonal). Treat as ongoing-repair rather than burst-repair.
Can marketplaces handle the procurement compliance schools need? For repair, yes — GST invoicing per ticket from verified vendors covers most school accounting needs. For larger device procurement, traditional channels (tenders, OEM authorised resellers) still dominate.