An early-stage education project

A clearer way to coordinate
digital learning operations.

Setting Class is exploring a shared workspace for tutors and school staff to organize everyday learning work, keep track of evidence, and make human responsibilities clear.

In development. Not yet a production service.

The problem

One school day.
Too many disconnected tools.

Classroom, Calendar, Drive, Gmail, and Meet each hold a different part of the learning process. Staff still need to connect pending work, supporting evidence, and decisions across those tools.

The project aims to bring that operational context together. Students keep using Google Classroom; Setting Class is not a replacement LMS or a student submission portal.

Seven learning operations areas

The work we’re designing around.

The product blueprint includes all seven areas below. These are planned workflows, not a list of live services.

Digital classes

Keep class context, membership references, and pending work together, with Google Classroom as the source of truth.

Schedules

Track proposed changes, reasons, and evidence. Distinguish a scheduling request from a confirmed Google result.

Administration & attendance

Organize participation observations and corrections. Attendance outcomes remain human decisions, not automatic Meet results.

Digital materials

Prepare publication revisions, record external tutor approval, and check readiness before publishing to Classroom.

Preliminary assignment review

Support rubric-based initial notes and manual-assisted external AI review. Assistants review the output; tutors decide feedback and grades.

Technical support

Track learning-related support cases, actions, and resolution evidence without recording passwords or other secrets.

Coordination & data protection

Plan traceable follow-ups through Gmail and Calendar, manual-assisted WhatsApp coordination, and purpose-specific access and retention rules.

Planned scope

People & responsibilities

Clear roles. Human accountability.

The portal is for registered staff. Class assignments and action-specific permissions determine access, not a role name alone.

Academic responsibility

Tutor

Works within assigned classes and retains responsibility for academic decisions.

  • Reviews preliminary assignment notes
  • Determines feedback and grades
  • Approves publication revisions externally

Approval is not delegated to an assistant or an automated tool.

Operational support

Assistant

Coordinates assigned learning work and prepares evidence for human review.

  • Prepares publication requests
  • Reviews AI-assisted initial notes
  • Records support and coordination work

Evidence access needs separate permission. Initial notes are not final grades.

Access management

Security operator

The local access tracer separates security management from academic class access.

  • Manages roles and class assignments
  • Handles verified account recovery
  • Revokes access during offboarding

This role does not grant access to every class or authority to approve academic work.

The broader blueprint also defines coordinator review responsibilities and a separate, restricted application-administrator mode. These are not blanket permissions for the security operator.

Security & human oversight

Controls to prove, not promises to assume.

The local tracer implements staff-access controls. Production security, privacy approvals, and the broader workflows still need their own evidence.

Registered staff only

No open self-registration. The design requires Workspace 2-Step Verification evidence for institutional accounts and a portal passkey for approved personal Gmail accounts.

Scoped, revocable access

Server-side checks enforce class and object permissions. Sessions can be revoked, and sensitive changes require CSRF and origin checks.

Traceable changes

The blueprint requires audit records for sensitive actions. Audit is not claimed to be tamper-proof against the infrastructure owner.

Human review stays essential

Tutor approval, attendance decisions, and academic review stay with people. Account recovery requires human verification through a known channel.

No security certification or legal compliance is claimed. Real student-data use, external AI policy, and production access exceptions require institutional review and authorization.

Current development status

A working local foundation.
A longer road to production.

Implemented locally

Staff-access tracer

Registered staff login, factor checks, assigned class access, recovery, and revocation have been exercised locally with synthetic data.

Class navigation and fixture queues provide context. They do not prove complete learning workflows.

Still ahead

Workflows, gates & pilot

End-to-end delivery of all seven workflows, production integration checks, privacy approvals, and a school pilot remain ahead.

Planned outcomes and acceptance targets are not measured results or permission to process real student data.

Contact & collaboration

Help shape better
learning operations.

Interested in the project’s direction? Educators and potential collaborators can email the Setting Class project owner.

Send Email

Opens your email app. You review and send the message yourself.