KIDUART school ERP

KIDUORBIT · AI signal layer · Not launched

The AI brainorbiting your ERP

Pattern intelligence on attendance, fees, and academics your teams already enter ranked review queues for staff, not chatbot theatre. Next phase of KIDUART. Building now.

▸ tenant.streams → orbit.models → staff.review_queue

signal_status // no production switch yet

BuildingTenant-localStaff reviewHonest roadmap

Orbit console

Workflows we are wiring into the ring

Same console dialect as the homepage signal layer scoped to what KIDUORBIT will add. Building lanes pulse yellow; roadmap stays muted.

Student review lists

Who needs a look this week

Actively building

▸ attendance ∩ marks.trend → ranked review queue → counsellor desk

  1. 1Signal in

    Attendance drift and academic movement already sitting in your tenant.

  2. 2What runs

    Pattern rules and models you configure no public ranking, no auto labels.

  3. 3What staff sees

    Authorised staff open a short queue with context, then decide follow-up.

Why orbit

Shorter scan lists. People keep the judgement.

Signal overload is the problem not lack of care. KIDUORBIT is designed to surface patterns in data you already record, hand staff a ranked review list, and leave decisions with people who know the child.

Full preview on the Signal Desk

Will be

  • Intelligence inside ERP modules
  • Attendance · fees · academics patterns
  • Flags for authorised roles only
  • Human follow-up queues not labels

Will not be

  • A product without the operational ERP underneath
  • Public at-risk boards or WhatsApp ranking lists
  • Training on your students for resale elsewhere
  • A switch you can flip in production today

Already on the platform

The signal layer you can explore today

Live models and building lanes from the homepage intelligence console the foundation KIDUORBIT extends. Ask on demo which rows are clickable in your tenant.

9 live3 in development

Attendance risk forecast

Catch the slide early

Live in the product

attendance.monthly → regression(trend, r²) → at-risk list

  1. Signal in

    Each student's monthly attendance percentage, rebuilt from the daily marks your teachers already take.

  2. What runs

    A regression runs over each student's trend line, projects the next 30 days, scores confidence from the fit, and tags the direction as improving, stable or declining against the threshold your school sets.

  3. What your team sees

    Class teachers and counsellors open a ranked at-risk list with critical cases on top, plus a parent notification list weeks before a term is lost.

Data ring

Nothing extra to type if the ERP is clean

Streams in

Attendance marks, fee ledger events, exam scores produced by daily work inside KIDUART.

Stays in tenant

Models run on your instance. We do not sell student data or train outside models on it.

Noise in → noise out

Paper attendance or wrong fee heads will amplify. Solid ERP first; orbit second.

Human loop

An alert is a start never a verdict

  1. 01

    Orbit adds a student or account to a review list

  2. 02

    Assigned staff open profile context

  3. 03

    Qualitative facts first talk, check, call if policy allows

  4. 04

    School decides support; flag cleared or monitored

Never publish “at-risk” lists on staff WhatsApp or notify parents of algorithmic scores without human review. KIDUORBIT is for clarity not labelling children.
Live demo

See today’s KIDUART then an honest orbit preview

Walk fees, attendance, and role panels first. Ask what is clickable now versus what ships in the KIDUORBIT phase.

  • 30-minute walkthrough

    Booked around your school hours

  • Run on your own data

    Your fee heads, classes and staff roles

  • No card, no lock-in

    Nothing is charged to see the product