School Techy
School Techy
Modules
AdmissionsStudent InformationFees & FinanceAttendanceExaminationsTimetableTransportHostelLibraryHR & Payroll
Solutions
Colleges Universities Coaching institutes Mobile app Integrations
Company
Pricing All features About Case studies Security Resources Blog Partners Contact Sign in
Start free trial
For universities & education groups

University management software as the group layer over many institutions

Each constituent school, college or department as its own campus with its own staff, fee heads and books — and one consolidated view of enrolment, collection and results across all of them.

Start a 14-day free trial
No card required · We will tell you if it is a poor fit
Campus comparison across constituent institutions with enrolment, collection and results
Suited to Education trusts Multi-school groups Deemed universities Constituent colleges Group management offices
The difference

Read this section before anything else on the page

A university has two distinct software needs, and we are honest about serving only one of them well. The first is running each constituent institution — admissions, fees, attendance, results, payroll — and consolidating it for the trust. That is what this product does, and does properly, with genuine per-campus isolation and a real consolidated ledger. The second is the academic administration of a degree-awarding body: credit frameworks, CBCS transcripts, board-of-studies curriculum governance, thesis and research administration, and affiliation of external colleges. Those are not modelled, and a university buying on the assumption that they are will be disappointed.

  • 01 Genuine per-campus isolation A campus administrator sees only their institution — enforced in the query, not by hiding a menu. Two constituent colleges cannot see each other’s students, staff, fees or results.
  • 02 Consolidated without merging The group office sees enrolment, collection, outstanding, attendance and results across every institution side by side, while each institution keeps its own books that close independently.
  • 03 Shared services where you want them One HR and payroll establishment across institutions if that is how the trust operates, or separate per institution. One vendor and procurement ledger, or several.
  • 04 Not a degree-awarding academic system Credits, CBCS transcripts, curriculum governance, research administration and affiliation of external colleges are absent. Say so on the call and we will tell you what the practical arrangement looks like.
The student record adapted for universities
Vocabulary

How the model maps to universities

The software was built around a school’s structure. Where your vocabulary differs, this is what it corresponds to — and where there is no correspondence, that is said too.

In your institution In School Techy Notes
Constituent institution / faculty Campus Direct equivalent, with its own books and staff
Group / trust management office Group workspace Direct equivalent, read across all campuses
Department Programme or stream within a campus Direct equivalent
Programme & batch Course & class Direct equivalent
Semester with internal + external Weighted exam terms Direct equivalent
Credits, credit hours, CBCS Not modelled
Degree transcript & convocation Certificates, serialised and verifiable Partial — not a credit transcript
Board of studies / curriculum approval Not modelled
Research, PhD, thesis, viva Not modelled
Affiliation of external colleges Not modelled
Consolidated trust accounts Per-campus books with group consolidation Direct equivalent
Fit

Where this is a good fit, and where it is not

The clearest way to judge this page: if the value you want is operational consolidation across institutions, it fits. If the value you want is degree-awarding academic administration, it does not.

Good fit: a trust running several schools and colleges
This is the strongest case. Each institution operates independently, the trust gets one comparison and one consolidated ledger, and no institution can see another’s data.
Good fit: consolidated finance
Per-campus double-entry books that close independently, consolidated income and expenditure and balance sheet for the trust, and one vendor and payroll ledger where you want it shared.
Good fit: group-level operational reporting
Enrolment, collection, outstanding, attendance, results and staff cost across every institution, on one screen and refreshed live rather than assembled monthly.
Poor fit: credit-based academic records
No credits, no credit hours, no CBCS transcript, no CGPA on credits. If a degree transcript is the deliverable, this is not the system that produces it.
Poor fit: research and curriculum governance
Board of studies workflow, syllabus versioning and approval, thesis supervision and viva records are all absent.
Poor fit: affiliating external colleges
Affiliation applications, inspections and results processing for colleges you do not own is a different product entirely.
Architecture

How the isolation actually works

This matters more for a group than for a single school, so it is worth being specific rather than saying “multi-tenant”. Every record in the system carries the institution it belongs to, and that filter is applied at the data-access layer rather than by each screen remembering to add a condition. A query written without a campus filter returns nothing rather than everything, which is the behaviour you want when the alternative is one forgotten clause exposing another college’s fee ledger.

On top of that, staff hold roles that are scoped to a campus. A branch administrator at one constituent college holds the administrator role for that campus only; the same person can hold a different role at a second campus if the trust genuinely wants that, and it is an explicit grant rather than a side effect. The group office holds a role that reads across campuses and, deliberately, cannot write into an institution’s books.

The same rules apply to the mobile API. There is no version of a request — browser or phone — that returns another institution’s data to a user who lacks the grant, because the narrowing happens in the query rather than in the interface. That is the difference between isolation and a hidden menu item.

Finance

Consolidation without losing the individual books

A trust needs both: each institution’s accounts must stand on their own for its own audit, and the trust needs a consolidated position. Doing this with a single set of books and a cost-centre column is where school-group accounting usually goes wrong, because a period cannot then be closed for one institution without closing it for all.

Here each campus has its own chart of accounts, journals and accounting periods. One college can close March while another is still posting. Consolidation reads the underlying journals rather than a summary, so the trust’s income and expenditure and balance sheet are derived from the same entries the institutions’ own statements are derived from — and cannot drift from them.

Inter-institution transactions — a shared bus, a teacher on secondment, a central purchase allocated across three campuses — are recorded as entries on both sides rather than as a note, which is what makes the consolidated position reconcile.

Questions

Questions from universities

Something not answered here?

Is this a full university ERP?
No, and we will keep saying so. It runs the operations of each constituent institution — admissions, fees, attendance, marks-and-grades assessment, payroll — and consolidates them for the trust, with genuine per-institution isolation. It does not do credits, CBCS transcripts, curriculum governance, research administration or affiliation of external colleges. If those are the requirement, this is the wrong product and you should not spend a demo finding out.
Can each constituent college keep separate accounts?
Yes, properly separate: its own chart of accounts, its own journals and its own accounting periods, so one institution can close a month while another is still posting. The trust’s consolidated statements are derived from the same journals rather than from summaries, so they cannot drift from the institutions’ own audited statements.
How is one college stopped from seeing another’s data?
Every record carries its institution and the filter is applied at the data-access layer, not by each screen. A query written without the filter returns nothing rather than everything. Staff roles are scoped to a campus, and the same rule applies to the mobile API — there is no version of a request that returns another institution’s data to a user without the grant.
Can a student move between our institutions?
Yes, with their full history — previous results, attendance and documents — rather than being re-created at the receiving institution. The transfer is recorded on both sides, and the outstanding balance goes with them, which is the part a manual process always loses.
Can we run one payroll across all institutions?
Either way. A single establishment with staff attributed to their institution, or a separate establishment per institution, depending on how the trust actually employs people. The salary expense posts to the institution the staff member belongs to, so each set of books carries its own staff cost.
What does the group office actually see?
Enrolment, fee collection, outstanding, attendance percentage, average results and staff cost for every institution side by side, refreshed live. It is deliberately a read-across rather than a write-across: the group role cannot post into an institution’s books, because a consolidated view that can also edit is how accountability disappears.
How many institutions can it handle?
The group console was rebuilt to run in a constant number of queries regardless of how many institutions there are — measured flat from five campuses to three hundred — so scale is not what limits it. What limits it is whether the academic model fits, which is the first section of this page.
Can we white-label it for each institution?
Yes on Enterprise: your own domain, each institution’s own logo and colours, and branded parent and staff apps. Parents at one constituent school see that school’s identity rather than the trust’s or ours.
Next step

A twenty-minute fit assessment, with the gaps named

Tell us how many institutions, what each awards, and whether a credit transcript is mandated. You will get a straight answer, including the parts we do not do.

  • No card required
  • Your data stays yours — export any time
  • Setup help included

No card required. We reply within one working day and never share your details.