A controlled mobile workspace—not an unrestricted cloud editor.

Indelo Teacher is planned as a separately governed mobile application for assigned institutional work. Academic locking, permissions, approvals, and final record application will remain under the campus system.

Planned first teacher release

Start with narrow, owned workflows.

The teacher app will follow after the family read model and payment workflows prove the hybrid foundation.

IN DEVELOPMENT

Assigned work only

Campus, academic session, class, subject, role, and assignment determine what each teacher can see and submit.

IN DEVELOPMENT

Attendance

Planned support for daily and per-lesson attendance through durable, idempotent submissions.

IN DEVELOPMENT

Teacher comments

Controlled comments and pastoral inputs with submission, review, and outcome status.

IN DEVELOPMENT

Offline drafts

Encrypted, scoped working sets and pending submissions designed for intermittent connectivity.

IN DEVELOPMENT

Conflict handling

Expected versions and explicit conflict states—never generic last-write-wins for institutional records.

IN DEVELOPMENT

Later academic submissions

Marks, continuous assessment, results, assignments, and behaviour workflows will follow only after narrower workflows are proven.

Device and identity controls

Institution-issued authority follows the role—not the email address.

Teacher access will be provisioned by the institution. Sensitive functions may require a registered device, strong authentication, encrypted local storage, remote session revocation, and local data purge when authorization ends.

Release sequencing

Indelo Teacher is deliberately later in the roadmap because teacher writes create institutional records and require mature conflict, lock, approval, and audit behavior.

Teacher workflow pilot

Tell CABS which teacher workflows matter most.

Pilot applications can identify attendance, comments, offline field conditions, device policy, and academic approval requirements.