Lesson planning software for university lecturers must hold a whole semester in one plan. Lectimax's Cadence keeps that chain live without dictating your teaching.
Most lecturers plan a semester in a document or a spreadsheet, and many rebuild the same Week 1 to 14 grid every term. That works for a single class. At semester scale the plan and the learning outcomes sit in separate files, and the weekly sessions drift out of step with them. Cadence, Lectimax's semester course planner, replaces that grid. You enter your course details and course learning outcomes (CLOs), and Cadence generates a full 12 to 16 week plan in one pass, with CLO coverage bars that show which outcomes each week covers. It then exports working material: a Moodle .mbz package, slide decks, a lab guide and the weeks themselves.
A university planning tool needs three things, in order. First, it needs a home for the whole semester, meaning the full run of weekly sessions rather than one session at a time. Each week carries outcomes, content, and an assessment with a mark. Second, it needs a connection to outcomes. A plan that records which outcome each week serves makes coverage visible, and gaps become findable before the term ends. Third, it needs to produce material you can use. A plan that stops at a table of topics still leaves you building the slides, the lab sheets and the course by hand.
That third need is where reuse matters. Modules return each year with small changes, and a plan whose outputs are editable files saves hours that are better spent on teaching, feedback, and research.
Where does planning in a document or spreadsheet strain?
Most planning starts in a word processor or a spreadsheet, and each gets you a first draft. A document gives you prose and freedom, while a spreadsheet gives you columns for weeks, outcomes, and deadlines. Both strain in the same place. A document lists weeks without connecting them to outcomes or assessments. A spreadsheet grows rows while nobody notes what each column means, and the dates are typed in by hand, public holidays included. Neither file records why a figure changed. Learning management systems hold schedules and assessment slots, and a platform like Moodle gives you a course layout. Even so, the plan itself is left unaddressed. What is missing is a place to think in weeks and outcomes before the course reaches students at all.
What does Cadence do differently?
| Feature | Lectimax's Cadence | Moodle | Canvas |
|---|
| Built for | Planning a whole university semester | Open-source course delivery | Institutional course delivery |
| Plan generation | A full 12 to 16 week plan in one pass from the course details and outcomes | Each week built by the lecturer | Each week built by the lecturer |
| Outcome coverage | A bar per week and cumulatively, plus a coverage heatmap across the semester | Alignment left to the lecturer | Alignment left to the lecturer |
| Weekly workspace | Lecture, tutorial or practical, readings and assessment per week | A course page per section | A module page per section |
| Delivery material | Slide decks, a lab guide, week notes and the full course outline | Content pages and files | Pages, files and modules |
| How it reaches students | Publishes into Lectimax's own course workspace and student app, plus a Moodle .mbz export and PDF and PowerPoint | Course delivery inside Moodle | Course delivery inside Canvas |
| Reacting to the cohort | Lectimax's Acuity signals land as recommendations you promote into a week | AI arrives as add-on plugins | AI arrives as add-ons |
| Price model | Credits per run | Free to host, support costs apply | Institutional licence |
| How you get it | Sign up yourself as an individual lecturer, from $13.99 a month, with 200 free credits (limited-time promo) and no institutional approval | Free to host, but it takes an institution to run it | Bought by the university; you use what it licenses |
| Reusability | Your Rubrica rubric loads into Lectimax's Gauge, a Cadence week into Forge and Quest, and Acuity signals into next semester's plan | A course is built and delivered inside the LMS | A course is built and delivered inside the LMS |
| Best for | Lecturers who want the semester planned and aligned | Institutions on open source | Institutions on Instructure |
Cadence fills that gap by holding a whole semester rather than a single session. From your course details and CLOs it generates the 12 to 16 week plan in one shot, so you edit a complete draft instead of filling an empty grid. Dates are computed from the semester start and account for public holidays.
Each week has its own workspace with four tabs: Lecture Content, Tutorial/Practical, Readings and Assessment. A lecture segment builder lays out the session, and the AI can generate more bullets for any topic. A Build Quiz button seeds Quest, another Lectimax module, with that week's context.
Coverage stays visible. CLO alignment bars show how many outcomes each week covers and how many are covered cumulatively. The course overview adds a CLO coverage heatmap across the semester, and a semester assessment strip lists dates and weights, so you can see whether the assessment load is spread or bunched.
The plan then leaves Cadence as files you can use. Each week exports as an editable PowerPoint slide deck, a PDF lab guide and week markdown. The full course outline exports as a PDF, and the Moodle .mbz backup package carries the course into Moodle for offline import.
Cadence also connects to Acuity, Lectimax's cohort analytics module. It is the only AI course planner that links to live cohort analytics and suggests adjustments to specific weeks based on what the cohort actually struggled with.
The limit is a plain one. A plan is only as good as the thinking behind it. Cadence generates the draft and keeps the structure connected, and you bring the judgement about what belongs in each week. It does not dictate method. Because the structure is shared across the semester, a colleague covering a session can open that week's workspace or the course outline PDF and see what the week is meant to achieve.
What does a real semester look like in a planner?
A worked example shows how this plays out. You are planning a 14 week semester with a midterm and a final, and the calendar loses a week to a national holiday. In a spreadsheet, you find every date after that week by eye and edit each one, then check again that the outcomes still line up with the sessions that follow. In Cadence, the week by week dates are computed from the semester start with public holidays, and the CLO alignment bars show whether every outcome still has a week that covers it.
The assessment strip covers the same ground for marks. A term that quietly crams three assessments into one fortnight shows itself, and there is still time to rebalance.
Planning continues once teaching starts. Say that by week six the cohort struggles with one topic. Acuity picks up that weakness, and the signal arrives in Cadence as a Recommendation. You can promote it into a tutorial, class activity, practical, reading or assessment without rerunning analytics or paying again.
Can you use Cadence without your institution?
Lectimax can be adopted by an individual lecturer or bought by the university. You are not waiting on a procurement cycle, and there is no form for your department or LMS administrator to sign before you start. You sign up with your own email, get 200 free AI credits (limited-time promo) to test on real work, and pay from $13.99 a month if you keep it. Basic, Starter and Professional are single lecturer plans, and Team and Department let an institution buy the platform centrally, with one shared credit pool, when it is ready.
Moodle and Canvas arrive through the institution that hosts them. A lecturer cannot adopt either alone, and adding an AI planning layer means asking for a plugin, a budget line and an administrator.
That difference follows you after the trial. Your rubrics, question banks, course plans and marked batches stay with your own account, so the work you put in during a semester is not tied to an institutional tenant that may switch platforms. If your department later decides to buy, the Team and Department plans pool the same credits across a group.
How does it connect to the other modules?
Lectimax's Connect layer moves artifacts between the modules, so each one is both a tool in its own right and part of the wider platform. A rubric you build in Lectimax's Rubrica loads straight into Gauge with no export and no import step, and it stays attached to the grading job rather than being copied into it. The same rubric returns for the next batch, the next assignment and the next module, so a standard you set once keeps working.
Cadence sits at the front of the flow. A week seeds a Forge brief or a Quest quiz without retyping it, and Lectimax's Acuity syncs what the cohort struggled with back into the plan as recommendations. Moodle and Canvas hold their content inside the LMS, so a plan made elsewhere arrives as an upload.
FAQ
What do lesson plans in a document miss? A document holds the content of a session. It does not hold the alignment behind it, so outcomes and weeks drift apart across files, and nobody notices until late in term. Cadence is built for the semester case, with the full plan and the CLO coverage bars generated together from the same course details.
Does Cadence tell me how to teach? No. It generates a draft plan and holds the outcomes and the pace. You make the call on what each session contains. It does not dictate method.
How is Cadence different from a course schedule? A schedule lists what happens in each week. Cadence builds the plan that connects weeks to outcomes, and it feeds the course that follows, including Lectimax's own course workspace and a Moodle .mbz export for institutions that run Moodle.
Where to go next
Explore the full Lectimax feature set or see what the platform costs on the pricing page.