The package built foryour next accreditation cycle.
Kenii Curriculum bundles every Kenii Catalog capability with the approval workflow your accreditor actually asks about: your real committee chain, a vote recorded against the member who cast it, and evidence you can pull up and hand over instead of rebuilding from memory the week before a site visit.
One license gets you the catalog and the approval trail behind it, built for the same site visit.
Not two vendors to reconcile before an accreditor asks.
Kenii Curriculum
Everything in Kenii Catalog, plus the approval workflow behind it.
- Your connected course, program, and credential data, on your own WordPress site and your own database
- Catalog years with a real lifecycle: draft next year while this year stays live, past years lock and stay readable
- Three-layer branding, your colors and fonts, plus custom CSS
- A searchable, filterable, mobile-first catalog with shareable URLs
- PDF export with public download
- Open-format export (JSON and CSV) and a REST API
- Proposals routed through your real committee chain: department, curriculum committee, chief academic officer, board, configurable to your bylaws
- A conditional accreditation-review step that inserts automatically for substantive changes
- Per-member votes, stored and retrievable by member, by proposal, and by meeting
- Validation with rule presets and catalog-code checks before a proposal ever reaches a vote
- Approved changes written directly into the real catalog record, no re-typing, with a tracked, dated addendum on any year already published to students
Every proposal builds
your accreditation file as it moves.
As a proposal clears department, curriculum committee, chief academic officer, and board, with a conditional accreditation-review step inserted for substantive changes, Kenii is quietly assembling the exact record your accreditor will ask for: who reviewed it, who voted, and when. There is nothing to reconstruct in the weeks before a site visit, because the proposal was never separate from the catalog to begin with.
Proposals
5 curriculum change proposals · 2026 to 2027
Every vote becomes
part of the evidence file.
Every vote is stored against the member who cast it and every routing stage against the date it cleared, and it lives in the same open, exportable data as your catalog, JSON and CSV whenever you want it. Pull the record per proposal, per meeting, or across a whole review cycle, and hand your accreditation team something they can act on the same afternoon, not a spreadsheet somebody has to rebuild from memory.
Catalog years
3 years, 1 locked
One package, built for the institutions that feel the clock.
One license, one accreditation-ready system
Catalog and Curriculum run on the same WordPress site and the same database under a single Kenii license, so your institution is not reconciling two vendor contracts, two logins, or two versions of the truth when a site visit is six weeks out.
Built for the coordinator who chases signatures today
If evidence for a program review currently means emailing five committee members to ask how they voted eighteen months ago, Kenii Curriculum removes that email. The record was written the day the vote was cast, and it stays attached to the proposal permanently.
No rebuild before every renewal cycle
Catalog years lock automatically and proposal history stays attached to the record it changed, so the work of proving what happened does not start over at every accreditation cycle. It accumulates, cycle after cycle, on its own.
Own it, on your own site
Curriculum runs on the WordPress site and database you already operate for Catalog. There is no separate vendor holding your committee history, and nothing new for IT to stand up to get it.
- What exactly is included in the Kenii Curriculum package?
- Every Kenii Catalog capability, your connected course, program, and credential data on your own WordPress site, catalog years with a real lifecycle, three-layer branding, PDF export, search and filter, open export and a REST API, plus the full Curriculum module on top: your real committee chain, per-member vote records, validation before a vote, and change history that lands as a tracked addendum rather than a silent edit.
- Do we need Catalog before we can add Curriculum?
- Curriculum is built on Catalog, so the package includes both under one license. If your institution already runs Kenii Catalog, adding Curriculum extends the same site and the same database rather than standing up something new.
- How soon before a site visit should we bring this in?
- The earlier your committee starts voting inside Kenii, the more of your review history is already on the record when the visit happens. Most institutions bring Curriculum in a full review cycle ahead of a site visit so the evidence has time to accumulate on its own.
- Can we keep our current committee structure and bylaws?
- Yes. The chain, department, curriculum committee, chief academic officer, board, is configured to match your governance exactly, including the conditional accreditation-review step for substantive changes. Kenii runs your process, not a generic one.
- What does the Curriculum package cost?
- Pricing builds on your Catalog license and scales with your institution size and process, so we send a written quote after a short conversation about your committee structure rather than publish a number that would be wrong for most institutions.
Bring your committee recordto the next site visit.
Request a demo and we will stand up a Kenii site with your logo and your colors, running on demo catalog and curriculum content, yours for fourteen days. Move a proposal through your own committee chain and watch the evidence file build itself. Afterward we send a written quote your purchasing office can act on.
Nothing to sign to get the demo site.