Home › CMP

Content Manager Pro

Hold What You Teach.
Prove How It Was Governed.

A course is built once and held for as long as it is taught, and after it is retired. CMP holds it: what it was built against, who approved it, what changed and when, where it is deployed, and when it is next due. Your faculty and designers author the course, working in conversation with CMP against your mission, your student population, your program outcomes, and the requirements you supply. Each course goes in front of the people at your institution who are authorized to approve it.

What CMP is

A Learning System of Record, Not an Authoring Tool.

An authoring tool produces a course and stops. CMP holds the course for its entire life: what it was built against, who approved it, what changed and when, how it maps to the outcomes you publish, where it is deployed, and when it is next due for review.

That distinction is the whole product. It is why a platform change becomes a redeploy instead of a rebuild, why a requirement change becomes a routed review instead of a search, and why an evidence request becomes an export instead of a project.

Building new courses is one door in. Importing what you already own, adopting publisher or open material, and reshaping a course you already run all land in the same record and are governed the same way. See the cases →

Four capabilities, one record

Buildauthored by your faculty to your requirements
Governapproved by your experts
Keep currentshown when a review is due
Deploy & proveto your LMS, with the trail
↑Nothing reaches a learner without a human decision from someone at your institution, and every decision is on the record with a name and a date. Course Management →

How it works

From Your Requirements to Your LMS, With Your Experts in Charge.

One loop, entered two ways. What sits beneath the loop is how a course gets into it.

↻

The loop: a course needs to be reviewed, its reviewer starts a revision, the change is approved and recorded, and the approved version is deployed. This is the part of CMP an institution uses each year, and it is the part whose return recurs year after year. The four steps below happen once per course. See Course Management.

How a course enters the loop

1

Configure

Mission, student population, program outcomes, and the requirements you supply, set once and carried into the courses beneath them. Onboarding takes one to two weeks once we have your onboarding sheet.

2

Build or import

Your faculty and designers author a new course in conversation with CMP, or you bring in a course you already run, as it stands. Either way it goes to your reviewers.

3

Review

Your designated reviewers edit, reject, or approve. Every decision is on the record, with version history and an audit trail behind it.

4

Deploy

By the path your platform supports: directly to Canvas and Moodle, and to other learning platforms through standard course formats.

CMP holds the design and governance record. Delivery, grades, and student records stay in your LMS and SIS.

Consistency without policing

Set Once at the Top. Locked Where It Must Not Vary.

CMP mirrors how the institution is actually organized. Course-level defaults pass down through institution, school, department, and program, and any level can lock a field that must not be changed beneath it. Content level, credit unit and credit hours, citation style, assessment settings, grade weights, source recency, the approved publisher list, and the rest of the course defaults are set where the decision belongs and inherited by the courses below.

This is the answer to the question a provost asks when four colleges do not agree with each other. Consistency stops depending on individual diligence and becomes a property of the system your departments work inside.

Where a default can be set, and locked

Institutionthe norm beneath it
Schoolwhere a college differs
Departmentwhere a discipline differs
Programwhere a credential differs
↑A locked field cannot be diluted below. An institution standard takes precedence over a course-level instruction, a conflicting note is rejected at input, and an unlocked conflict is flagged for review rather than absorbed quietly.

What it is like to use

What a Faculty Member Actually Does.

CMP keeps the record so the work is not reconstructed from memory. This is what the faculty member does, described the way the person doing it would describe it.

1

Say what you need

The course starts from a conversation rather than a form. You describe what you are teaching, the platform asks for what it still needs, and the design record is built from your answers.

2

Work with your requirements in view

Your outcomes, your requirements, and your institution's own settings are already in the record, so you build with them in front of you rather than looking them up.

3

Change it in your own words

Any field can be edited by plain-language instruction: the module overview, the lecture, the reading, the assignment, the rubric, the discussion prompt, an assessment item, the audio script. Change one line of a script and only that line's audio is redone.

4

Decide, and be recorded deciding

Your edit, rejection, or approval carries your name and the date. If your judgment is that no change is needed, that goes on the record too, which is itself the evidence that the review happened.

Questions live on the course itself rather than in a separate thread, progress is visible while a step runs, and collaborators see the same state you do. Authorship stays with you throughout, and nothing is approved on your behalf.

What stays yours

What Stays Inside Your Institution.

Authorship

Your experts own the content

Content produced in CMP belongs to the institution. Your designated reviewers hold approval authority, and CMP records the decision rather than making it.

Seat: Deans · Faculty · Designers

Data surface

Course records, not student records

CMP holds design and governance records. Grades, enrollment, and student data stay in the LMS and SIS where they already live and are already governed.

Seat: CIO

Portability

No lock-in, including to us

Open export formats. If you leave, you leave with the record: content, versions, approvals, and alignment. A vendor should be re-earned, not hold you hostage.

Seat: CIO · CFO

Isolation

Your own deployment, kept apart from every other institution

Each institution has its own CMP, and your institution sets its own password policy. Your institution's information is kept separate from every other institution's, and is shared only with the providers needed to run the platform, under agreements that protect it.

Seat: CIO

Request a working session

Bring Us the Piece You Are Least Sure About.

Two ways in. We work on your material, in front of you, not on someone else's course. Your provost, your accreditation lead, your CFO, or your faculty are welcome to join.

1
Start here

Bring a course to review and update

Bring a course you already run. We work on it as it stands, review it against the outcomes and requirements you supply, and show you what the record and the reports look like on your own material.

You leave with: a clear picture of where that course stands.

2

Bring a course to build

Bring a course you need to create. Your faculty and instructional designers take part in a live design conversation with CMP, and the course moves through your approval path and out to your platform.

You leave with: a course designed with your own people, and the record of how it was designed.

Set up the session

We reply from a person, usually the same day.

Prefer email? info@lumnitek.com

We use what you share to respond to your request. See how we handle your information.

What the first conversation is like

Newberry College was mid-move to a new LMS on a short timeline. Here is how their vice president described working with us.

"I don't often do testimonials for vendors, but I want to give a shout out to the good folks at LumniTEK. Newberry College is in the process of moving to a new Learning Management System (Canvas) on a very short timeline. We were a bit overwhelmed by the pace and inherent limitations of a small college budget. We really didn't have the bandwidth or budget to complete the migration in the time we had. The Lumnitek team helped change that. When we first met with their team, they listened first, seeking to understand the specific challenges we were facing. Based on what they heard, they outlined a creative, manageable plan that streamlined the work our staff had been slogging through manually. We put their plan in place in less than a week. Almost overnight, they helped us to free up significant time for our staff, allowing us to redirect people back to the priorities that actually move our programs forward. A massive project that was going to consume months of staff effort took a fraction of that time. Our team finally has room to breathe and return their focus on students and faculty. I only wish we'd found them sooner. 10/10 would work with Lumnitek again."
John LaNear, Vice President of Academic Affairs, Newberry College