Coworking infrastructure
for academic communities.

The campus-hub reality

Three structural mismatches between universities and commercial coworking software.

Universities aren’t coworking spaces with a different logo. They are tiered communities operating on academic calendars, with sponsor obligations that commercial tools were never designed for. These are the three patterns we see across 12 hub programs.

• Mixed access chaos

  Students, faculty and sponsors share the same door.

  Different tiers, different hours, different agreements — but one floorplan and one card-reader. The current solution is a printed list at reception and a security guard who guesses. The audit trail is whoever’s memory you trust this week.

• Semester scheduling

  Semester schedules break every commercial booking tool.

  Fall semester, winter break, exam week, summer school. Most coworking platforms assume Monday-to-Friday forever. The hub director ends up running a parallel Google Sheet because the booking tool can’t model ‘closed for graduation week, but open for the sponsor demo’.

• No sponsor visibility

  Sponsors want a report you can’t produce.

  Every corporate sponsor wants to know how many of THEIR cohort used the space, in what room, on what day. The data is split across an Eventbrite, a key-fob log and a Google Form — and the year-end report ends up being three nights of manual reconciliation.

What we do for you

Three capabilities built for the campus calendar.

Each capability lands on a specific pain the commercial coworking tools cannot model. No reskinning a workplace platform with a university theme — these were built with hub directors, registrars and advancement teams in the room.

• Solves mixed access

  Tier-based access: student, faculty, sponsor

  Three default roles, configurable to your program. Each tier gets its own hours, room set, booking limits and badge profile. SSO via your university’s identity provider, so a student stops being a student the day they graduate — without anyone having to remember.

  • SAML / OIDC SSO with role mapping from your IdP
  • Per-tier room access, hours and booking windows
  • Auto-expiry on graduation date or sponsor end-of-engagement
• Solves semester scheduling

  Semester scheduling that the registrar will recognise

  Term calendars, exam-week blocks, holiday closures and one-off events all coexist on the same schedule. The hub stays open for the sponsor demo on graduation Friday without breaking the ‘closed for graduation’ rule for everyone else.

  • Term + exam-week templates synced from your academic calendar
  • Override windows for sponsor events without breaking term rules
  • Recurring lab and cohort sessions with one-shot exceptions
• Solves sponsor visibility

  Sponsor reporting on tap

  Every sponsor gets a stable cohort tag, every booking, badge-in and event attendance ties back to it. The year-end report is one filter and an export — not three nights of reconciliation. Hand it to advancement or hand it to the sponsor directly.

  • Stable cohort tags survive role + tier changes
  • Sponsor-scoped dashboards: utilization, events, demos, hires
  • CSV + signed-PDF exports your advancement team can attach to a renewal

Customer story

Otago Innovation Hub customer story

Outcomes

What university hubs run on LiteHQ, in numbers.

Aggregated across 12 university and innovation-hub programs in NZ, Australia and the UK. Each program runs at least one tiered cohort and one sponsor relationship.