Write every proposal on the real catalog record.
Kenii Curriculum opens every proposal directly on the live course or program it modifies. It checks every change against your institutional rules and active database, catching duplicate course codes and credit total violations before a committee ever meets.
A proposal that knows your catalog catches its own mistakes before the meeting.
Every proposal opens on the real course.
A proposal here is not a form sitting beside your catalog. It opens directly on the live course or program record, so the credit hours, requirements, and descriptions your committee reviews are the exact ones active today.
Curriculum, priced and packaged
A new degree program is not a bigger course revision.
A course revision and a new degree program are not the same document, so Kenii does not put them on the same form. Select what you are changing and the proposal fields adapt to match the requirements for that modification type.
Checked against your catalog before a person has to.
Every proposal runs against your validation presets the moment it is submitted. A duplicate course code or a missing required field gets flagged immediately, not twenty minutes into a faculty committee meeting.
The paperwork stays with the proposal.
Attach syllabi, labor market studies, and advisory board letters directly to the proposal record. Every supporting document stays permanently attached to the course history long after final approval, so the file and the decision never separate.
Where the evidence lands
Built on the catalog, not beside it.
Kenii Curriculum runs natively on the exact same platform and database as your catalog software. Proposals read and write live records directly rather than relying on disconnected prototypes or external form builders.
One record, from proposal to published page.
Proposals are one piece of Kenii Curriculum. See how a curriculum change moves through approval chains, records member votes, and publishes into locked catalog editions.
Approval routing.
Move every proposal through your real governance chain, with steps, voting members, and accreditation reviews configured to match your institutional policy.
Vote records.
Store every yes, no, and abstain vote against the specific committee member and meeting, ensuring an auditable record exists the moment the vote occurs.
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.
See the proposal meet the real catalog.
Request a branded demo and we will stand up a live Kenii site carrying your college logo and colors, pre-loaded with demo catalog content so you can test drive proposal submission and automated validation with zero IT setup.