Fig. 01 — 06:40, first departure
The day's logistics begin before anyone logs in.
Theinstitutionthat finally runslike one.
One bus leaves the depot at 06:40 and the parents see it on their phones. Attendance registers itself. Payroll reconciles without being opened. Every department reads from the same record — because there is only one.
modules across four parts
integrations & open API
institution types, one product
§ 01
Thesis
Every institution already has an operating system. It's mostly paper, chat groups, and hope.
Enrolment lives in one spreadsheet. Fees in another. Attendance in a printed register that ends the term in a cardboard box. Hostel counts on a WhatsApp message. Hospital rotations on a whiteboard that gets wiped.
It works, mostly. Until the accreditation visit — or a parent who wants to know where the bus is, or a doctor who needs a patient's history right now. Then every one of those tools reveals it was always alone.
Infocing is what an institution runs on when it decides it doesn't want to reconcile spreadsheets on a Sunday any more.
§ 02
Contents
Four parts. Thirty-seven modules. One database.
Academics
- Curriculum & timetablep. 12
- Live classes, recordings, LMSp. 18
- Assignments, rubrics, proctoringp. 26
- Grade books & transcriptsp. 34
Operations
- Admissions & CRMp. 42
- Fees, scholarships, refundsp. 48
- Payroll, HR, purchasep. 56
- Audit, budget, reportingp. 64
Campus life
- Hostel, mess, laundryp. 72
- Transport & GPSp. 78
- Library, events, alumnip. 84
Medical Institutions
- OPD, IPD, wardsp. 92
- Pharmacy, lab, radiologyp. 98
- Clinical postings & rotationsp. 104
§ 03
Day book
A single Tuesday, multiple systems, one infrastructure.
One working day on the full product — every module in service. Times are IST.
Morning
06:00 — 12:00Bus 12 leaves the depot while parents follow it on the live map. At the gate, students tap in and the day's attendance opens itself.
Staff mark their own attendance — a tap in the app, or the device at reception. The payroll ledger takes note without being told.
First period starts on schedule. An absence pulls up a substitute from the timetable; the lecture is recorded and filed to the course before the bell.
Afternoon
12:00 — 17:00The office counter clears a morning of fee payments. Receipts go out instantly and the general ledger reconciles itself.
Intern rotation swaps on the ward. Pharmacy dispenses against the electronic order. The audit log is already written.
Results are entered collaboratively — every subject teacher at once, moderated live. Grade books update the moment the last mark lands.
Evening & night
17:00 — 00:00The evening digest goes home: attendance, homework, fee dues, the bus that arrived safely. Nobody sat down to compose it.
Dinner counts draw straight from hostel attendance, and tomorrow's kitchen indent is drafted against what's actually on the shelf.
The warden closes the roll and files the night's entries — visitors, leave, headcount — through the system. The day's audit trail seals itself.
§ 04
Operating principles
No invented figures. Four things we hold to instead.
Principle 01
One database
Academics, fees, hostel and hospital all read from the same record. Nothing is entered twice, so nothing disagrees.
Principle 02
Configured, not customised
Every institution runs the same product, set to its own rules. Your workflows bend.
Principle 03
Your data stays yours
Full export, any day, in open formats. Leaving should be as uneventful as arriving.
Principle 04
A human answers
Support is staffed by people who have run institutions — not a ticket queue that closes at five.
§ 05
Register of institutions
Different institutions. The same product. Configured, not customised.
From brick-and-mortar classrooms to 100% online schools with no campus at all — and the Olympiad that examine a million students — Infocing ships the same product, set to your rules.
§ 06
Built to be trusted with a child's records, and a patient's.
Student data, medical institution charts and financial ledgers ask for a higher bar than a CRM. Ours is defence-in-depth by default — encryption everywhere, granular RBAC, immutable audit logs, and a team that answers the phone.
Read the security note →
§ 07
Correspondents
Talks to everything you already trust.
120+ integrations across payments, communication, exam boards, government portals, identity providers and enterprise systems — plus a full REST & webhook API when you need to write your own chapter.
End of page · Fin.
Move the institution
into one place.
We migrate you off spreadsheets, Tally, Moodle or a decade-old ERP without interrupting a term. Most institutions are live in about one month.