Approvals that run your real committee chain.
Kenii Curriculum routes every proposal through your college’s approval chain, from department to board, configured to match your exact bylaws. Proposals meeting your substantive-change threshold pick up an accreditation review step automatically.
Every approval follows the chain your committee already uses. Not a workflow standing in for your bylaws.
Configured to your bylaws. Not to ours.
Set the exact governance chain your college votes through: department, curriculum committee, chief academic officer, board, in your order and with your step names. A proposal cannot skip a step or reach a vote it has not earned.
What Curriculum includes
Approve, return, hold, or reject outright.
Not every proposal passes on the first review. A reviewer can approve a proposal, return it for revision, hold it pending additional information, or reject it outright, with each decision recorded alongside the reviewer’s reasoning.
Every vote stored against the roster of that day.
Each vote is stored by member, by proposal, and by meeting, under the quorum thresholds you set and against the committee roster as it stood at submission. Roster updates later never alter a recorded vote tally.
How each vote is stored
Approved changes write the real record.
An approved change updates the actual catalog record with zero re-typing. For a catalog year already published to students, the edit lands automatically as a tracked, dated addendum instead of a silent rewrite nobody can audit.
Your governance, on the catalog database.
Kenii Curriculum runs natively on the exact same platform and database as your catalog software. The chain you configure is the exact path the software walks, with complete visibility into every live proposal.
The rest of the curriculum record.
Approval routing is one piece of Kenii Curriculum. Explore what a proposal carries before the first vote, and what the record holds after the final approval.
Curriculum proposals.
Draft course and program changes as structured proposals that validate themselves against catalog rules before they ever reach a committee agenda.
Vote records.
Store every yes, no, and abstain vote against the member who cast it and the meeting it belongs to, ensuring clear evidence on the day of the vote.
Evidence archive.
Keep the proposal, discussion history, routing logs, and approved changes attached directly to the course record for permanent accreditation audits.
Catalog years.
Lock published catalog editions and stage the next academic year so students keep reading active requirements while staff draft upcoming changes.
Give your committee a record it can trust.
Request a branded demo and we will stand up a live Kenii site carrying your college logo and colors, running on demo catalog content with an approval chain live so you can watch a proposal move from department to board.