Managed Markbook
Whole-school assessment workflows built for consistency, governance, and reliable academic data.
What is the Markbook?
An assessment platform that replaces the term-marks spreadsheet, run by us.
Spreadsheet-like, without the downsides
The familiar grid you already know, without the scattered files, mismatched formats, and version confusion
Live as marks are entered
Cohort statistics and grade distributions update in real time
Automatic calculations
Weighted components calculate automatically and stay consistent
Consistent by design
Everything is organised the same way across the school, so there's no inconsistent naming, structure drift, or fiddly setup to manage
Every school knows the file.
Term 2 Marks FINAL v7.xlsx. Emailed between three teachers. Two are editing it at the same time. One is on the wrong version. A formula broke last week and nobody noticed. Reporting week is coming.
We built the Markbook because that file should not be running a school's assessment cycle.
Teachers enter marks. Heads of department design assessments. Leaders see live cohort statistics as marks are entered. Admins decide who can see what. That's the shape of it.
Weighted components calculate automatically. Grade cutoffs can be adjusted between reporting periods. Every change is tracked.
When reporting week comes, the numbers are already there.
Built around how schools actually work
Reporting periods, weighted components, learner profiles, IMA codes. The shape of a real school, modelled properly.
Real school structures
Academic years, reporting periods, weighted components, learner profiles, and IMA codes
Permissions you can trust
Department read/write, year-level read-only, and per-markbook access
Versioning by default
Every save is a version, so you can branch, test, and roll back
Single source of truth
One consistent record of assessment data across the school
Spreadsheets pretend a school's assessment cycle is just rows of numbers. It isn't. It's academic years and reporting periods. Weighted components. Learner profiles. IMA codes for when an assessment goes wrong. Lock statuses for when marks need to be frozen. Customised grade cutoffs that your Head of Department might want to adjust between Term 2 and Term 3.
The Markbook models all of that directly, so the system matches how your school already works. It becomes a single, consistent source of truth for your school's assessment data.
Permissions you can actually trust. Department-based read/write. Year-level read-only. Per-markbook teacher access. Admin overrides where they make sense. No more "anyone with the link can edit" tabs and the awkward conversations afterwards.
Versioning by default. Every save creates a new version. You can branch off to test what happens if the cutoff for an A moves up by 3%, keep that branch, or roll back. Nothing is ever lost. Your source of truth is always one click away.
Designed for every role
Different people in a school need different things from the markbook. We built for all of them.
Teachers
A keyboard-first grid that gets out of your way. Tab between cells. Enter to commit. Arrow keys to move. Mark entry takes seconds, not minutes. Learner profile ratings live alongside the marks, so non-academic attributes like effort and cooperation don't end up in a second spreadsheet you forget to update.
Heads of Department
Design assessments end-to-end. Set component weights and let the system enforce that they actually total 100%. Adjust the grade cutoffs your faculty uses for each reporting period. Decide which teachers in your department can edit, which can view, and which see only the learner profiles. Your faculty stops being a permission free-for-all.
Administrators and IT
Configure academic years and reporting periods once. Sync students, staff, and classes from TASS or Schoolbox. Manage SSO. Then mostly leave it alone, because we run the rest.
Principals and coordinators
Live, read-only visibility of performance as marks are entered. Summary statistics and cohort metrics update as marks are entered. Grade distributions. Estimation status flags so you can see at a glance what's confirmed and what's still provisional.
Connected, not siloed
Connected to the systems your school already runs.
TASS and Schoolbox
Students, staff, classes, and enrolments sync automatically
CSV import
Get started without committing to a full integration project upfront
Single sign-on
SAML or OIDC, so staff and students use the credentials they already have
A markbook only matters if the data in it can be used elsewhere without extra work.
The Markbook integrates with the systems your school already runs.
TASS and Schoolbox handle students, staff, classes, and enrolments automatically.
CSV import is there for schools that want to get going without committing to a full integration project upfront.
SAML or OIDC single sign-on means your staff and students log in with the credentials they already have, not a new password to remember.
Security
The Managed Markbook is built with Australian hosting, isolated school environments, role-based access, Single Sign-On, and full audit and version history. Operations, patching, and backups are handled by us.
For full detail on infrastructure, encryption, and Australian data residency, see our page on platform security and Australian data residency.