Every approval leaves its own evidence, automatically.
Kenii Curriculum builds your accreditation evidence as an automatic by-product of the approval process itself, not a project your staff run before a site visit. Every proposal, vote, and routing step stays permanently attached to the record it changed.
The archive is not a project. It builds itself every time a proposal moves.
The whole story of a decision, in one place.
Every routing step, every vote, every comment, and every field that changed appears as one timeline on the proposal, in order, with the person who did it named beside it. No tab-hopping to reconstruct it.
One report. Not a folder of screenshots.
Pull the evidence report for any proposal and get the complete chain as one structured document you can export to PDF: who proposed it, who voted and how, the route it cleared, and the date it wrote into the catalog record.
A published year gets a dated addendum.
When an approved change touches a year already published to students, it does not overwrite what they saw. It attaches as a dated addendum, and the evidence report marks exactly what was added, removed, and changed.
No pre-visit scramble. Nothing to maintain.
The archive is not a second system your staff maintain alongside curriculum work. The route freezes at submission, so an accreditor’s question gets a complete report instead of a coordinator’s best recollection.
A by-product of the process, not a project.
Kenii Curriculum runs natively on the exact same platform and database as your catalog software. Every proposal, vote, and routing step is stored as it happens, so the archive reflects what your committee actually approved.
What the archive is made of.
The evidence archive is one piece of Kenii Curriculum. Explore the proposals, the committee chain, and the votes it assembles into a report.
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, members, and accreditation steps configured to match your bylaws.
Vote records.
Store every yes, no, and abstain vote against the member who cast it and the meeting it belongs to, so the evidence exists the day the vote happens.
Catalog years.
Lock published catalog editions and stage the next academic year so students keep reading active requirements while staff draft upcoming changes.
See a proposal become a report, automatically.
Request a branded demo and we will stand up a live Kenii site carrying your college logo and colors, running on demo catalog content so you can move a proposal through committee and watch the evidence build behind it.