MAKTABZ Product Update: The ORBIT Intelligence Architecture

School software has traditionally been organized around modules. ORBIT is being designed around a different question: how can school leadership move from operational data to attention, evidence and accountable action without losing governance?

The problem we are addressing

School leaders often have more data than time. Information may exist across attendance, academics, homework, finance, HR, admissions, communications and student support, but identifying the issue that matters can still depend on manual dashboard review and cross-module investigation.

The architecture

ORBIT Command Center

↓

Suggestive AI tells you what needs attention

↓

ASK ORBIT lets you investigate it conversationally

↓

Evidence tells you why

↓

Action Center lets you do something about it

↓

Workflow follows responsibility/SLA/escalation

↓

ORBIT CHAT keeps the conversation/action connected

↓

MG VISTA adds the next visual intelligence layer

What is different about this approach

The design target is not simply AI-assisted search. ORBIT's intelligence layer is intended to operate under the same underlying authority model as the rest of the platform. The relevant chain is: package entitlement → school configuration → role permission → responsibility → individual or delegated permission.

That means a conversational request should not become a shortcut around institutional access controls. The same principle applies to Action Center and workflow.

Evidence before confidence

ORBIT's product direction treats evidence as part of the user experience. Where the platform surfaces a material signal or answers an operational question, authorised users should be able to inspect the basis of the answer. The objective is explainable institutional intelligence, not opaque certainty.

Who this is for

School owners and group leadership seeking cross-campus visibility.

Principals who need to prioritize attention rather than monitor every dashboard continuously.

Academic and pastoral leaders coordinating interventions.

Operations, finance and HR leaders who require accountable workflows.

Technology leaders responsible for governance, security and integration.

Availability language for publication

Publication teams should distinguish clearly between generally available capabilities, controlled pilots, preview features and roadmap items. A product update should never imply that a capability is production-available unless that status has been verified at publication time.

“Product credibility is strengthened when availability language is as disciplined as the technology itself.”