From a committee voteto a published catalog.
Kenii Curriculum runs every course and program change through your real committee chain, records how each member voted, and writes the approved change straight into your catalog. No re-typing, no spreadsheet in between, no silent edits.
The vote that approved the change is the record that publishes it.
No spreadsheet in between.
Your committee chain.
Not a generic workflow.
A proposal moves through department, curriculum committee, chief academic officer, and board exactly as your institution runs it today, with the order and the members configurable. Substantive changes route through an accreditation review automatically, before publication rather than after.
Proposals
5 curriculum change proposals · 2026 to 2027
Every vote,
kept as it was cast.
Per-member votes are stored against the proposal and the meeting they belong to, so when an accreditor or a new department chair asks who approved a change and when, the evidence already exists rather than being reconstructed.
Meetings
5 meetings · Board of Trustees · 2026
Approved changes
land in the catalog.
Once a proposal clears the chain it writes into the real course or program record, with nothing to re-type. If it touches a year already published to students, it lands as a tracked, dated addendum instead of a silent edit.
Catalog years
3 years, 1 locked
See exactly where
a proposal is stuck.
A live report shows every active proposal, the stage it sits in, and how long it has waited, so a chair or a dean can see what is waiting on whom. A bottleneck surfaces before it costs a catalog deadline.
Alerts
1 live · 1 scheduled
Site-wide alert bar
LiveCampus closed Friday for winter weather
Showing on every page of the college site
Popup
ScheduledSpring registration closes March 14
Shown once per visitor, on program pages
Built, and running on the same platform as your catalog.
Curriculum is built and demonstrable today. It runs on the same Kenii platform and the same database as your catalog, which is what lets an approved proposal write into a real course record instead of a copy of one.
Everything a modern curriculum process should do.
Curriculum is one module of the platform. Explore the pieces that carry a change from a draft proposal to the page a student reads.
Curriculum proposals
Draft course and program changes as structured proposals that validate themselves against catalog rules before they ever reach a committee agenda.
Approval routing
Move every proposal through your real committee chain, with the order, the members, and the accreditation step configured to match how you actually govern.
Vote records
Store every yes, no, and abstain against the member who cast it and the meeting it belongs to, so the evidence exists the day the vote happens.
Evidence archive
Keep the proposal, the discussion, the routing history, and the approved change attached to the record they changed, searchable long after the meeting ends.
See your committee chainas a published catalog.
Request a demo and we stand up a Kenii site carrying your logo and your colors, running on demo catalog content, free for fourteen days with nothing to sign. Walk a proposal from a vote to a published record.