For the Classroom Teacher
The Teacher Dashboard.
Sundays back. Mondays prepared.
Six surfaces. Six daily decisions. Every signal a class produces — attendance, mastery, behaviour, risk — composed into one screen, plus AI for the chores that used to take Sundays.
Scroll the keynote — one act per surface, one decision per act.
Walk in knowing what every section needs today.
Most teachers walk into the staff room and start the day from memory — who was absent yesterday, whose marks slipped last week, which class needs the gentler tone today. The information is in fifteen places; the morning has none of it.
Edullent collapses the morning into a single screen for the teacher. Each section's attendance, average, top movers and slips, plus the principal's note from yesterday — composed and ready. The teacher walks into the first class with the day's specifics, not yesterday's intentions.
A per-section morning read — attendance, class average and behaviour for every section a teacher handles, composed before first period.
Signals it reads
- Attendance marked in each section
- Marks entered across recent assessments
- Behaviour notes logged through the week
- Week-over-week movement per student
What the engine computes
- One strip per section, rebuilt every morning
- Students who climbed and who slipped this week, surfaced rather than remembered
- The same composite score the principal sees — shown to the teacher first
- Sections compared on identical maths
Decisions it drives
- Which section needs the harder plan today
- Who to check on before the bell
- What to raise in a review before it is raised with you
Section overview
Attendance + class average + behaviour count for every section the teacher handles — all in one strip, refreshed every morning.
Top movers + slips
Who climbed this week, who fell — surfaced by the engine, not by memory. The pre-class glance the staff room never delivered.
Composite score · live
The same composite the principal sees — visible to the teacher first. No surprises in the review meeting.
Morning prep, vs 25 minutes of asking around
Visibility cadence on student trajectory
Find the topic that's sinking the class — by Thursday.
When a class fails a test, the teacher does not know whether it was one topic, one chapter, or the whole unit. Re-teaching everything is a week the syllabus does not have; re-teaching nothing is the next test going the same way.
Edullent scores mastery at the topic level for every student in every subject. Three buckets — strong, developing, focus — with the underlying topics named. The teacher knows exactly which 3 concepts the class needs Friday's period spent on, not the whole chapter.
Chapter marks broken down to named topics and scored per student, so the topic sinking a class is identified while the unit is still open.
Signals it reads
- Question-level assessment results
- Topic tagging on every chapter
- Per-student score history
- Pace against the syllabus plan
What the engine computes
- A 0–100 mastery score per topic per student, rolled up to the class
- Three bands, so the weakest topic is found without reading a table
- A pacing warning when a class moves ahead on weak foundations
- The strongest topic named too, so revision time is not spent there
Decisions it drives
- Which topic to reteach before the next unit
- Which students need a separate reinforcement group
- Whether to slow down or move on
Per-topic mastery score
Every chapter broken into named topics — each scored 0–100 per student, then rolled up to the class. The teacher prepares on the topic, not the chapter.
3 colour-coded bands
Strong · Developing · Focus. The grid finds the weakest topic instantly — and the strongest, which the teacher can stop revising.
Pacing-risk AI
The engine warns when a class is moving too fast on a topic with weak underlying basics — before the next unit makes it worse.
Of re-teaching effort focused on the 3 actual weak topics
Saved by skipping topics the class has mastered
A 45-minute lesson plan, in 30 seconds.
Lesson planning is the chore every teacher loses Sundays to. The format is fixed, the syllabus is fixed, the learning outcomes are fixed — and yet every plan is written by hand, every week.
Edullent's AI Lesson Planner generates a board-ready 45-minute plan in the school's own format — learning objectives, activity flow, time-stamped sequence, recap questions, board work — from one prompt. The teacher edits, approves, and moves on. Sundays return to the teacher.
Lesson plans composed from the school’s own syllabus and format, with minute-level sequencing, board work and recap questions already in place.
Signals it reads
- The syllabus and chapter already on file
- The institution’s own lesson-plan format
- Grade, subject and period length
- Where the class has actually reached
What the engine computes
- A plan written in the school’s template, not a generic one
- Minute-level flow — opener, instruction, practice, recap, exit
- Board work prompts and recap questions generated up front
- Fully editable: the engine drafts, the teacher approves
Decisions it drives
- What to actually run in the next period
- What to cut when the period runs short
- Which activity to swap for a weaker section
School-format aware
Plans land in the institution's own template — same headings, same field order, same length. No copy-paste reformat.
Time-stamped activity flow
Every plan ships with minute-level activity sequencing — opener, instruction, practice, recap, exit — so 45 minutes plan as 45 minutes.
Recap + board work
The plan includes board work prompts and 3 recap questions — the chunks teachers rebuild from scratch every Sunday, generated up-front.
Saved per teacher on lesson planning
From prompt to first draft
A unit test, in the school's pattern, from one prompt.
Question paper setting takes a teacher an evening per unit — pulling from old papers, balancing difficulty, matching the board pattern, building the answer key separately. Half of it is mechanical work.
Edullent's AI Exam Generator builds the paper end-to-end — section-wise distribution, difficulty mix, blueprint compliance, answer key, marking scheme. CBSE / ICSE / state-board patterns are pre-loaded; the teacher picks topics, picks difficulty, ships. The mechanical half disappears.
Question papers built to the board’s section weighting and difficulty distribution, with the answer key and marking scheme attached.
Signals it reads
- Board pattern — CBSE, ICSE or state
- The topics the teacher selects
- The difficulty band chosen
- Time allotment and total marks
What the engine computes
- Section weighting and difficulty distribution applied automatically
- A paper built around the chosen topics, not around a default template
- Answer key and marking scheme produced with the paper
- Output shaped like the school’s own question paper
Decisions it drives
- Which topics this unit test should actually cover
- How hard to pitch the paper for this section
- What to reuse for a retest without rebuilding it
Board-pattern engine
CBSE / ICSE / state-board section weighting, time allotment and difficulty distribution built in. The output looks like the school's own paper.
Topic + difficulty picker
The teacher chooses which 4 topics to test and the difficulty band — the engine builds the paper around those constraints, not around a default template.
Answer key + marking scheme
Every generated paper ships with a teacher-side answer key and marking scheme — the second half of the chore, removed.
Per unit test, returned to the teacher
Coverage matched to the class's actual weak areas
Yesterday's class, distilled into a one-page parent note.
After a 45-minute lesson, the teacher has to compose a short summary for the parents — what was taught, what to revise at home, what's coming next. The lesson is fresh; the writing is not. Most teachers either skip it or send the same generic line every week.
Edullent listens to the lesson (or the teacher's voice note) and ships a parent-ready summary in the school's tone — key concepts, home-work, revision pointer, next-class preview. The teacher reviews, approves, sends. Communication becomes a by-product of teaching, not a second job.
A class recording or voice memo turned into a structured note — concepts covered, homework, next-class preview — written for parents.
Signals it reads
- A voice memo or class recording
- The chapter and topics in play
- Homework set in the period
- The school’s tone and note format
What the engine computes
- Audio in, structured note out
- Concept list, homework and next-class preview kept separate
- Composed in parent-facing language rather than teacher shorthand
- Held for review — nothing sends until the teacher approves it
Decisions it drives
- What to send home today, and to which section
- Which concept needs restating for parents
- Whether the class landed well enough to move on
Audio in, summary out
A voice memo or class recording becomes a structured note — concept list, home-work, next-class preview — in the school's standard format.
Parent-tone composition
Output is written for parents, not for the teacher's own notes — simpler vocabulary, single concept per line, no syllabus jargon.
Review · approve · ship
The teacher edits if needed and approves before sending. The AI drafts; the teacher decides. Always.
Per class returned to the teacher
Parent communication cadence that used to be weekly
See the slipping student before the test confirms it.
When a student starts to slip, the signs are obvious in hindsight — three missed days, a quiet behaviour shift, a low practice score. In real time, the teacher is teaching forty other students and the signal is lost.
Edullent's risk feed surfaces the slipping student to the teacher with the specific reason — attendance, marks, behaviour, assignment lag — and a one-tap action: schedule a check-in, flag to the principal, ping the parent. The teacher catches the slip in week 3, not at term-end.
A class-scoped risk feed naming the students slipping inside this teacher’s own sections, with the signal behind every flag.
Signals it reads
- Attendance within the teacher’s sections
- Recent test and assignment results
- Behaviour incidents logged
- Missed submissions
What the engine computes
- Only the teacher’s own students — never the whole school
- Severity ranking, so the list stays workable rather than exhaustive
- Named signals per student: attendance, last score, incident date
- Routing and follow-up captured automatically
Decisions it drives
- Who to check in with this week
- What to flag to the principal, and what to handle in class
- Which parent to contact, and with what evidence
Class-scoped risk feed
The teacher sees only the students in their own classes — flagged with severity, ranked by urgency, sorted into a workable Friday list.
Reason chips per card
Each at-risk student arrives with named signals — attendance 62%, last test 41%, behaviour incident Tuesday — so the conversation can start informed.
One-tap routing
Schedule a check-in, flag to the principal, ping the parent — the action is one tap, the trail is captured automatically.
Earlier than the term-end report surfaces the same slip
Average recovery rate on flagged students within a term
The best teachers in the next decade
won't write more plans. They'll teach more class.
Edullent ships the lesson plan, the unit test, the parent note and the risk feed — so the teacher's hours go back to the classroom.
Book a Demo