Software for university incubation centres

A university incubation centre is not a small version of a private accelerator. The pressures are genuinely different.

The team is small and often part-time, with faculty splitting time between the centre and teaching. Decisions have to be justified to a governing body or an academic committee. Funding usually comes from a government scheme or a university corpus with real reporting obligations. And the student cohort turns over annually, which means institutional memory lives in documents or nowhere at all.

That last point is the one most tooling ignores. When the program manager changes and the previous one's spreadsheets are on a laptop that has left, the centre loses its history.

Academic selection processes attract scrutiny precisely because the people involved are known to each other. A defensible process protects the centre and the people running it.

Define a weighted rubric with scored options before applications open. Assign panel members to specific programs - including external experts who get evaluation access without access to the rest of the portal. Each evaluator scores independently, and the system keeps the per-evaluator breakdown rather than presenting a single average that hides disagreement.

Combined with an audit trail on every application status change, the record of how a cohort was selected is intact regardless of who is asked about it later.

Most campus centres run more than one thing at once: a pre-incubation or ideation track for students, a full incubation program for registered startups, sometimes a faculty venture track or a scheme-specific cohort with its own criteria.

Each of those is a program with its own application form, its own rubric and its own batches. A student ideation track does not have to be squeezed into the same questionnaire as a deep-tech incubation program. Batches inside a program let this year's cohort and last year's run alongside each other without duplicating the program definition.

Campus centres are frequently funded through a government scheme, a university corpus, or a mix - each with its own expectation about how money is accounted for.

Funding is recorded as a source, allocated to a program, and disbursed to startups in tranches. Allocating more than a source holds is blocked at entry. Every disbursement traces back through its allocation to its source, so a question about a specific payment has a specific answer, and reporting per funder does not require rebuilding the picture from receipts.

Campus centres usually control physical resources that are genuinely scarce - a fabrication lab, prototyping equipment, meeting rooms, incubatee desks.

Facilities are bookable against day-of-week time slots with an approval step where supervision is needed, and slots can be blocked out for teaching or maintenance. Utilisation reporting tells you whether the equipment the centre argued for is actually being used, which is a materially better position to be in at the next budget meeting. Desks and cabins can be allocated with terms and, where the university permits it, charged for.

A campus centre's biggest structural disadvantage is reach. Its startups are visible to the university and not much further.

Your workspace sits alongside a public network, so a startup in your program is findable by founders, mentors and investors rather than listed only in your own records. Applicants who have never walked past your building can find your programs. And you can draw mentors from that network instead of only the alumni you can reach personally - with the centre paying, the startup paying, the cost split, or the mentor on a retainer.