Skip to content

School Operations & Inventory Operating System

Campus360

Schools run on requests and assets, and both usually live in paper trails. Campus360 gives operations teams a structured spine: a location hierarchy, an asset register, and approval workflows that actually match how the institution decides.

All products

Know what you own, where it is, and who approved it.

What it covers

The operating surface.

Assets, requests and approvals across every branch, building and room.

Places

Branches

Assets, requests and approvals across every branch, building and room.

Branches / Buildings / Floors / Rooms

Places

Branches

Buildings

Floors

Rooms

People

Teachers

Staff

Role-based access

Things

Assets

Maintenance

Vendors

Procurement

Flow

Requests

Approval workflows

Reports

WhatsApp

SaaS management

How it runs

From setup to daily operation.

  1. 01

    Map the campus

    Branches, buildings, floors and rooms form the hierarchy every asset and request hangs from.

  2. 02

    Register assets

    Tag, categorise and locate assets with custody, condition and maintenance history attached.

  3. 03

    Route requests

    Staff raise requests; configurable approval chains route them to the right authority.

  4. 04

    Procure and report

    Approved needs turn into vendor procurement, and operations reporting closes the loop.

Workflow case study

Managing a school's asset request

Based on the documented product workflow. No customer deployment or measured results are recorded in this project.

The problem
Paper requests and asset records make location and approval responsibility hard to follow.
Supported outcome
Assets resolve to campus locations; staff requests follow approval chains into procurement and reporting.

Design decisions

Why it holds up in the field.

Location as first-class data

Every asset, request and maintenance job resolves to a real room in a real building.

Approvals that mirror hierarchy

Multi-step chains reflect how schools actually authorise spend, not a generic ticket queue.

Multi-branch by design

Group institutions manage many campuses under one tenant with role-scoped visibility.

See it against your own operation.

Bring your messiest workflow. We will walk through how the system models it.

Explore products