01
Curriculum
Source
An approved chapter and learning objectives are selected.
Industry · Education
Education software shaped around teaching—not just content delivery.
Thalenor designs learning platforms, assessment systems, student and parent portals, admissions workflows and careful AI-assisted tools for schools, coaching institutes, training providers and education products.
CURRICULUM · TEACHER · LEARNER01
A clear answer
What does Thalenor build for education organisations?
Thalenor builds education software around the complete learning operation: how a learner discovers and joins a programme, how content is organised, how work is assessed, how teachers intervene and how families or administrators understand progress. AI can help draft questions, classify responses or retrieve grounded material, but curriculum control, assessment validity and consequential decisions remain with educators.
Operating landscape
One connected operation. Six places where context can break.
The system should carry meaning across these hand-offs, not leave users to rebuild it in messages and spreadsheets.
01
Admissions and enrolment
Programme discovery, enquiry qualification, applications, document collection, review, fee milestones and joining communication.
02
Student and parent portals
Timetables, resources, attendance, assignments, results, notices and a dependable record of what requires attention.
03
Assessment workflows
Question banks, test assembly, delivery, marking, moderation, feedback and analysis tied to learning objectives.
04
Teacher workspaces
Planning, review queues, intervention notes, resource sharing and class-level visibility without another administrative burden.
05
School and institute operations
Batches, rooms, faculty allocation, attendance, fees, certificates and communication across academic and administrative roles.
06
Learning products
Curriculum-aware practice, spaced revision, mastery views and mobile experiences for independent or institution-led learning.
Workflow in view
A credible product should make the work visible before it tries to make it fast.
Follow the record, the responsible role and the decision that must remain human.
ILLUSTRATIVE MODEL · FICTIONAL RECORDS
A curriculum-grounded practice set reaches students only after teacher approval.
A realistic AI-assisted feature is a controlled drafting workflow, not an unsupervised question generator.
CURRICULUM → PRACTICE → EVIDENCE
ILLUSTRATIVE OPERATING MODEL · 05 STATES02
Assistance
Draft
The system proposes questions, answers and explanations tied to that source.
03
Teacher
Review
A teacher edits wording, checks difficulty and rejects weak items.
04
Learning platform
Release
The approved set is assigned to a class with clear practice rules.
05
Teacher
Learn
Results surface misconceptions; the teacher decides the response.
Illustrative process using synthetic content. The education provider defines curriculum authority, assessment policy and review responsibility.
Where design judgement matters
The hard part is rarely the screen someone asks for first.
01
A score is the end of a workflow, not the whole learning signal.
A credible assessment system begins with curriculum objectives and question quality. It should distinguish practice from evaluation, preserve question provenance, support moderation and show teachers patterns they can act on—not merely rank students.
- ATag questions by objective, skill, difficulty and source
- BSeparate automated marking from responses that need educator judgement
- CKeep version history when questions or rubrics change
- DShow misconception patterns alongside aggregate scores
02
Generated material needs a source, a purpose and an educator gate.
Language models can accelerate first drafts of questions, explanations and feedback. They cannot be assumed to understand a board, grade, pedagogy or local policy from a short prompt. Grounding and review are product requirements, not optional safeguards.
- ARetrieve from approved curriculum material
- BDisplay the source context used for a draft
- CRequire teacher approval before student release
- DRecord edits so quality can improve over time
03
Different users need different truths from the same record.
Students need clarity about what to do next. Parents need proportionate visibility. Teachers need exceptions and patterns. Administrators need complete records and controls. One overloaded dashboard rarely serves all four.
- ARole-specific home screens and permissions
- BActionable notifications instead of indiscriminate alerts
- CAccessible mobile behaviour for families
- DClear correction and escalation routes
04
The timetable is connected to almost everything.
Batch changes affect rooms, teachers, attendance, reminders and sometimes fees. Education operations benefit from shared source data and explicit dependencies instead of repeated spreadsheet updates.
- AModel academic structures before screens
- BKeep scheduling conflicts visible
- CDefine ownership for attendance and record corrections
- DIntegrate payments and messaging at controlled boundaries
Decision guide
Before buying or building an education platform, map the academic operating model.
Feature lists often start with video, quizzes and dashboards. The more important questions concern academic structure, responsibility and how information becomes action.
The strongest first release usually completes one academic loop—such as admissions, assessment or student communication—rather than imitating an entire institutional ERP.
01
Define the unit of learning
Is the system organised around classes, courses, competencies, modules or examination objectives? This choice shapes content, progress and reporting.
02
Name the authoritative records
Decide where enrolment, attendance, grades, fees and identity are mastered. Duplicate authority produces disputes and manual reconciliation.
03
Separate practice from evidence
Hints, retries and AI help may be appropriate during practice but invalid during an examination. The product must represent that distinction.
04
Design the teacher workload
Every alert, approval or insight becomes someone’s queue. Show only what is actionable and make bulk work genuinely efficient.
05
Plan change by academic cycle
Curricula, batches and permissions change on term boundaries. Versioning and rollover deserve explicit workflows.
Relevant capabilities
The engineering disciplines this work usually touches.
Boundaries built into the product
Responsible software states what it will not decide.
A disclaimer cannot compensate for a workflow that hides uncertainty or lets sensitive actions happen without ownership.
01
Teacher authority
AI may draft and recommend. Educators approve released content, assessment rules and interventions.
02
Student data
Collect only what the product needs; define who can see performance, behavioural and contact information.
03
Assessment integrity
Separate low-stakes practice assistance from controlled evaluation and make permitted tools explicit.
04
Accessibility
Keyboard navigation, readable contrast, captions, clear language and assistive-technology support belong in the initial design.
05
Explainability
A teacher should be able to trace why a question, score, recommendation or alert exists.
Practical questions about education software.
Technically yes, but unsupervised release is rarely the responsible design. A stronger workflow grounds drafts in approved material, checks the intended objective and difficulty, and requires educator review.
Build around the learning loop that matters most.
Tell us whether the current constraint is admissions, teaching, assessment, communication or administration. We will map the people and records before proposing the product.