EDU Curriculum Planning & Sharing is lesson planning software for colleges and universities: a faculty lesson planner where every course gets a course plan with unit-wise hours, a lecture-wise lesson plan, HOD approval before the semester, and syllabus completion tracking that compares planned with delivered lectures — because faculty record the topic covered with attendance, not in a separate register.
The course file is paper, and the lesson plan lag shows in week 14
Course plans sit in ring binders, the lecture log is a work diary no one reconciles, and syllabus coverage is a figure the HOD asks for a week before end-semester exams. When a faculty member changes mid-semester, the plan, and the knowledge of what the class actually covered, goes with them.
Lesson plans kept in paper course filesReviewed once for audit, never consulted during the term.
Syllabus lag found only before end-semester examsUnits 4 and 5 compressed into three weeks of extra lectures.
HOD cannot see coverage across divisionsDivision A is on Unit 4, Division C still on Unit 2; nobody knows until someone asks.
Plans not linked to lectures actually takenThe plan says 45 lectures; the attendance register shows only 38.
Faculty change mid-semester and the plan vanishesThe substitute starts from the syllabus PDF and asks students where they got to.
IQAC compiles teaching-plan evidence by handCourse files photocopied and scanned per criterion, per cycle.
A course plan is a live document. When faculty build the plan per course with unit-wise hours against the L-T-P from Academics, the HOD approves it, and every lecture reconciles it with the topic recorded at attendance, coverage is a number anyone authorised can see in week 9 — and the course file for academic audit is an export, not a binder.
Scanned by IQACLesson sequenceTopics vs planDivision CSaturday classes46 bindersNot updated sinceNot reconciledUnit 2 · estimated4 booked, 2 held
Evidence of coverageResources listedLectures actually heldFigure requested by HODStudents informedSelf-declaredFile names, no files38 of 45 plannedWeek 14WhatsApp
Compiled by handFiled · unreadDoes not match planAsked in week 14Compressed
Course plan software
Lesson Planning Software for Colleges: Features
Course plan per course with unit-wise hours; HOD approval of course and lesson plans; topic covered recorded with attendance; planned vs delivered lectures; department-wise syllabus completion with coverage lag alerts; copy plans to the next semester and attach e-content to lessons. Each course plan breaks into a lecture plan for every session, and lesson plan approval by the HOD happens before the semester begins, so EDU tracks coverage against an agreed plan.
Six cards · scroll lifts the next
Card 01 of 06Card 02 of 06Card 03 of 06Card 04 of 06Card 05 of 06Card 06 of 06
Course plan with unit-wise hoursHOD approval before the semesterTopic covered recorded with attendancePlanned vs delivered, coverage lag alertsDepartment-wise syllabus completionCopy to next semester, attach e-content
Build the course plan from the course's L-T-P: units and modules, hours per unit, lecture, tutorial and lab sessions, and a lecture-wise lesson plan with the topic, method and resource for each session.Faculty submit course and lesson plans; the HOD reviews unit hours, sequence and resources, returns with comments or approves, so every course starts the semester with a reviewed plan on record.When faculty take lecture attendance, they pick the planned topic (or record what was actually taught); EDU then marks the lesson delivered and the work diary writes itself — no separate lecture log.Every course shows planned against delivered lectures by week; a configurable lag (say two lectures) raises an alert to the faculty member and the HOD while there is still time to add an extra or remedial lecture.HODs see every course and division in the department on one coverage view; the Dean and Principal see departments side by side; the course coverage report is one click for academic audit.Roll an approved plan forward to the next semester or a new faculty member with its lessons and resources, adjust the calendar, and attach e-content from the Academic Resource Library to each lesson so the plan and the material travel together.
Units · modules · hoursSubmit · review · approvePick the topic at attendancePlanned vs delivered by weekCourse × division gridCopy plan to next semesterL-T-P from AcademicsComments on the planLesson marked deliveredLag threshold per departmentDepartment and college viewsHand over to new facultyLecture-wise lesson planApproved plan on recordWork diary auto-filledAlert to faculty and HODCoverage report exportLesson-level resources
PHY-301 · course plan · 45 L · 15 TApprovals · Physics · Odd 2027Lecture 23 · 14 Nov · Div ALag alerts · Physics · week 9Coverage · Physics · Sem III · week 9Copy plan · PHY-301 · 2027 → 2028Draft v246 coursesAttendance taken3 open60% expectedPreview
Unit 1 · FoundationsPHY-301 · Dr. P. MenonPlannedPHY-311 · Div B45 lessons · 5 units8 lectures · 3 tutorialsSubmitted 22 JulL23 · Perturbation · non-degeneratePlanned 27 · delivered 23Dates shifted to 2028 calendarWk 1–3ApprovedTaught−4Copied
Unit 2 · 1-D systemsPHY-302 · Dr. S. RaoAttendancePHY-302 · Div CHolidays · 202810 lectures · 3 tutorialsSubmitted 23 Jul52 of 56 presentPlanned 27 · delivered 25Div A3 lessons movedWk 3–6ApprovedSaved−2Div BAdjustedDiv CDiv DPHY-30160%58%55%62%PHY-30260%57%52%60%PHY-303 Lab62%62%50%62%PHY-31158%45%57%60%PHY-30460%60%60%60%
Unit 3 · PerturbationPHY-303 Lab · Dr. L. IyerResourcePHY-301 · Div AResources10 lectures · 3 tutorialsLab plan · 8 experimentsUnit 3 slides · v3Planned 27 · delivered 2638 files · 6 videos re-linkedWk 7–10ApprovedAttached−1
Unit 4 · Angular momentumPHY-311 · Dr. A. KhanDiary entryPHY-304 · Div AOwnerDepartments on target9 lectures · 3 tutorialsUnit 4 hours queriedWritten from this lecturePlanned 18 · delivered 18Dr. R. Nair (new)9 / 11Wk 10–13ReturnedAuto0Assigned
Unit 5 · Identical particlesPHY-304 · Guest facultyNextExtra lectures bookedHOD approval8 lectures · 3 tutorialsNot yet submittedL24 · degenerate casePHY-311 · Sat 16, 23 NovRequired before Sem startWk 13–15PendingWk 92
Hours planned vs L-T-PApproved before day oneDiary entries this semesterRemedial lectures this termLessons with a resource attached60 / 6043 / 461,2841141 / 45
Card 01
Course plan with unit-wise hours
Build the course plan from the course's L-T-P: units and modules, hours per unit, lecture, tutorial and lab sessions, and a lecture-wise lesson plan with the topic, method and resource for each session.
Card 02
HOD approval before the semester
Faculty submit course and lesson plans; the HOD reviews unit hours, sequence and resources, returns with comments or approves, so every course starts the semester with a reviewed plan on record.
Card 03
Topic covered recorded with attendance
When faculty take lecture attendance, they pick the planned topic (or record what was actually taught); EDU then marks the lesson delivered and the work diary writes itself — no separate lecture log.
Card 04
Planned vs delivered, coverage lag alerts
Every course shows planned against delivered lectures by week; a configurable lag (say two lectures) raises an alert to the faculty member and the HOD while there is still time to add an extra or remedial lecture.
Card 05
Department-wise syllabus completion
HODs see every course and division in the department on one coverage view; the Dean and Principal see departments side by side; the course coverage report is one click for academic audit.
Card 06
Copy to next semester, attach e-content
Roll an approved plan forward to the next semester or a new faculty member with its lessons and resources, adjust the calendar, and attach e-content from the Academic Resource Library to each lesson so the plan and the material travel together.
This is the teaching plan, not CO-PO mapping. Course plans, lesson plans, the work diary and syllabus completion live here. Course outcomes, programme outcomes, CO-PO mapping and attainment belong to OBE & Compliance Management, which reads the course and lesson list from this plan. Academic audit and NAAC criteria are context only; we confirm the evidence formats your IQAC needs during the demonstration.
This is the teaching plan, not CO-PO mapping.
Course plans, lesson plans, the work diary and syllabus completion live here. Course outcomes, programme outcomes, CO-PO mapping and attainment belong to OBE & Compliance Management, which reads the course and lesson list from this plan. Academic audit and NAAC criteria are context only; we confirm the evidence formats your IQAC needs during the demonstration.
Semester teaching plan
Lesson planning before the semester, every week, and at audit
Stop 01 of 05Stop 02 of 05Stop 03 of 05Stop 04 of 05Stop 05 of 05JulWk 1–15Wk 9Dec
Course plan draft · PHY-301Approval · HOD PhysicsLecture 23 · recorded with attendanceLag alert · PHY-311 Div BCoverage report · Physics · DecDraft v2ApprovedDelivered−4 lecturesExported
ResourcesCommentResourceCauseRemedial lectures38 attached from Resource LibraryAdd tutorial on problem set 6Unit 3 slides v3Guest faculty gap · wk 5–6Logged with datesLinkedDoneAttachedNoted11
Syllabus sourceApprovedWork diaryExtra lecturesAudit packUniversity R-2024 · Sem III28 Jul · plan of recordEntry written automaticallySat 16 Nov · Sat 23 NovAcademic audit 2027–28Loadedv3AutoBookedReady
Submitted to HODShared withDelivered so farRe-sequencedIQAC22 JulDiv A, B students · on app26 of 27 planned by week 9L24–L45 shiftedCriterion evidence · datesSentPublished−1Done
FacultyHODFaculty · every lectureFaculty · HODHOD · IQAC
Plan drafted from the syllabusReviewed and approvedDelivered and recordedLag caught and correctedCoverage reported
The faculty member builds the course plan against the university or autonomous syllabus and the course's L-T-P, with unit hours and a lecture-wise lesson plan.The HOD reviews sequence, hours and resources, returns with comments or approves; the approved version is the plan of record.At each lecture, faculty record the topic with attendance; EDU then marks the lesson delivered and fills the work diary.Planned vs delivered raises a lag alert; the HOD books an extra or remedial lecture and re-sequences the plan.Finally, the HOD exports the syllabus completion report and course file (plan, diary, coverage) for audit.
Faculty change mid-semester: the plan, the delivered lessons and the attached resources pass to the new faculty member, who continues from lesson 24, not from the syllabus PDF.
JulPlan drafted from the syllabusThe faculty member builds the course plan against the university or autonomous syllabus and the course's L-T-P, with unit hours and a lecture-wise lesson plan.
JulReviewed and approvedThe HOD reviews sequence, hours and resources, returns with comments or approves; the approved version is the plan of record.
Wk 1–15Delivered and recordedAt each lecture, faculty record the topic with attendance; EDU then marks the lesson delivered and fills the work diary.
Wk 9Lag caught and correctedPlanned vs delivered raises a lag alert; the HOD books an extra or remedial lecture and re-sequences the plan.
DecCoverage reportedFinally, the HOD exports the syllabus completion report and course file (plan, diary, coverage) for audit.
Faculty change mid-semester: the plan, the delivered lessons and the attached resources pass to the new faculty member, who continues from lesson 24, not from the syllabus PDF.
Syllabus coverage · Physics · Sem III · week 12Syllabus coverage · Physics · Sem III · week 9Back on plan1 lag alert
Course · divisionPlanned vs deliveredLagAction
PHY-301Div A · Dr. Menon-1Watch
PHY-302Div C · Dr. Rao-2Watch
PHY-303 LabBatch B1 · Dr. Iyer-1Watch
PHY-311Div B · guest gap0-4FixedAlert
PHY-304Div A · Dr. Das0On plan
PHY-311Div A · Dr. Khan-1Watch
Courses · divisions46 · 4
Open alerts01
Extra lectures2 held2 booked
Coverage lag
A lesson plan lag caught in week 9, not week 14
PHY-311 Division B is four lectures behind plan in week 9 — a guest faculty gap in weeks 5 and 6. The lag alert reaches the faculty member and the HOD the same week; the HOD books two Saturday lectures and re-sequences the remaining lessons, so by week 12 the division is back on plan. The end-semester exam is not the moment anyone finds out.
FoundWeek 9 · alert
Fixed2 extra lectures
Back on planWeek 12
Faculty, HOD, Dean, Principal, IQAC
Benefits for Faculty, HODs and the Principal's Office
Teaching plan software serves the faculty member first: a course plan and lesson plan built once and reused, a work diary that fills itself, and a view of their own coverage. The HOD reviews plans and watches coverage per faculty and division; the Dean wants consistent plans across departments and campuses; the Principal wants college-wide syllabus completion; IQAC wants plans and coverage reports for academic audit without compiling binders.
FacultyPlan once, teach, and let the diary write itself
Course plans, lesson plans and the work diary in one place; faculty record the topic covered with attendance, so coverage is always current, and they can copy the plan to next semester or hand it to a colleague.
My work diary · this week
Wk 9L23 · Perturbation · non-degenerateTaught
Wk 9T8 · Tutorial · problem set 6Taught
Wk 9L24 · Degenerate caseThu
HODCourse plan review and coverage per faculty and division; approves before the semester, acts on lag alerts during it.43 / 46Plans approved
DeanConsistent teaching plans across departments and campuses; department coverage side by side.9 / 11Depts on target
PrincipalCollege-wide syllabus completion as one figure, by department, by week.61%Covered · week 9
IQACPlans and coverage reports as academic audit evidence, exported with dates.46Course files ready
Affiliated, autonomous, university
University syllabus or your own, the same course plan
An affiliated college plans against the affiliating university's syllabus; an autonomous college or university plans against its own. Engineering colleges plan L-T-P hours and lab sessions; management institutes plan sessions per trimester. The course plan template is the same; the syllabus source and the period unit come from Academics.
Session plans for management institutes, lab plans for engineering. A trimester session plan with case assignments and a 15-week L-T-P plan with eight laboratory experiments are both course plans: units or sessions, hours, resources, approval and coverage. The planner adapts to the structure Academics defines for the programme.
Affiliated collegePlan against the university syllabus
Units and hours follow the affiliating university's syllabus as loaded in Academics; previous-year question papers from the Resource Library sit beside the plan.
Units · sessions · hoursLecture-wise lesson planHOD approvalTopic recorded with attendanceCoverage and lag alerts
Autonomous college · universityPlan against your own syllabus
Units and hours follow the regulation your academic council set; electives and evaluation are your own; IQAC reports per criterion.
SyllabusOwn regulation per batchUnitsSet by the departmentEvaluationOwn scheme
Engineering collegesL-T-P course plans and lab plans
Lecture, tutorial and practical hours per week; lab plans with eight to ten experiments per semester and batch rotation from the timetable.
L-T-P3-1-2
Lab experiments8
Lab batches4
Management institutesSession plans per trimester
Case-based sessions with pre-reads attached, guest sessions flagged, coverage tracked per trimester rather than per semester.
Sessions20 / trimester
Cases12 attached
Guest sessions3
Connected modules
The lesson plan is where four modules meet
A lesson in the plan takes its course and L-T-P from Academics, its slot from Timetable, its delivered status and topic from Attendance, and its material from the Academic Resource Library. So nobody re-enters any of that here.
Lesson 23 · PHY-301 · Unit 3Time-independent perturbation theoryPlanned week 9 · delivered week 9 · 52 of 56 present
From AcademicsPHY-301 · 3-1-0 · Unit 3 of 5
From TimetableThu 10:00 · Room 204 · Div A
From AttendanceDelivered · 52 / 56 · topic L23
From Resource LibraryUnit 3 slides v3 · Lecture 14 recording
Is this the same as CO-PO mapping? No. OBE & Compliance Management maps course outcomes to programme outcomes and computes attainment; it reads the course and lesson list from this plan.
In depth
More on lesson planning in higher education
Work diary and lecture log without a second register
A faculty daily work register is a statutory habit in many institutions, and a separate lecture log is where plans and reality drift apart. When faculty pick the topic covered at attendance, the diary entry is the attendance record: date, slot, division, topic, present count. Faculty can amend the topic if the lecture went differently, and the HOD sees the diary and the plan as one sequence.
Work diary · Dr. P. Menon · week 9Written from attendance
Academic audit asks for the course file: the approved course plan, the lesson plan, the work diary, coverage and remedial lectures, and the question papers and materials used. The planner exports the file per course with dates and the approval record, and the syllabus completion report per department, so IQAC assembles audit evidence from exports rather than photocopies.
Handing a lesson plan to a substitute or new faculty member
A faculty member on leave, exam duty or leaving mid-semester hands over a plan with its delivered lessons marked, the next lesson identified and the resources attached. The substitute continues from the plan, records topics at attendance in the same way, and the coverage figure for the division is unbroken.
Hand-over · PHY-311 · Div BMid-semester
Dr. A. Khan on exam duty · wk 10–11
Plan and diary handed to substitute
Substitute continues from L28
Topics recorded at attendance as usual
Coverage unbroken · Div B
HOD view shows one sequence
Dr. Khan resumes · wk 12
Picks up at L34
Frequently Asked Questions About Lesson Planning Software for Colleges
How does lesson planning software for colleges track syllabus completion?
The lesson planning software for colleges logs each lecture against the lesson plan, so it compares planned and delivered lectures through the semester and a lag shows up in week 9, not week 14.
How do faculty build a course plan and lecture-wise lesson plan for each course?
From the course's L-T-P in Academics: units and modules with hours, then a lesson per lecture, tutorial or lab session with topic, method and resource; faculty can also copy the plan from a previous semester.
Can HODs review and approve course plans before the semester starts?
Yes. In the lesson planning software for colleges, faculty submit and the HOD reviews and returns with comments or approves; the approved version then becomes the plan of record.
How do we see syllabus completion for every course and division in a department?
The department coverage view shows planned vs delivered per course and division by week, with lag alerts; the Dean and Principal see departments side by side.
Can faculty record the topic covered when they take attendance?
Yes. Picking the topic at lecture attendance marks the lesson delivered and also writes the work diary entry.
Can faculty share plans so a substitute or new faculty member can continue the course?
Yes. The faculty member hands over the plan with delivered lessons, the next lesson and attached resources, so coverage continues unbroken.
How does an affiliated college plan against the university syllabus, and an autonomous college against its own?
The syllabus source comes from Academics — the university scheme for an affiliated college, the institution's own regulation for an autonomous college or university; the course plan template is the same.
Is this the same as CO-PO mapping?
No. Course outcomes, CO-PO mapping and attainment are in OBE & Compliance Management, which reads the course and lesson list from this plan.
Explore EDU modules
One campus system, every module connected
Curriculum Planning & Sharing connects with every other EDU module through one campus record. Pick a module to see how it works.
Walk through a course plan built from L-T-P, its HOD approval, a lecture where the topic is recorded with attendance, and the week-9 coverage view that shows the lag while there is time to fix it.