Home › The Record
The thing being bought
One Record.
The Rest Is How It Is Filled and Read.
Your faculty and instructional designers build courses in CMP, and CMP keeps the record as they work. The record shows what each course was built against, who authored it, who approved it, what was checked, what changed and when, where it is deployed, and when it is next due.
What is captured
Written by the Work, Not Added Afterward.
The entries below are produced as the platform operates. They do not depend on someone remembering to record something, and they are not assembled at the end.
Design
What the course was accountable to
- The mission, student population, and program outcomes in force when the course was designed
- The requirements, standards, and reference documents the institution supplied
- Course learning outcomes, and the program outcomes they advance
- Outcomes carried down to modules and assessments
- The workload the course was designed for, set against its credit
- The works the course may assign, with edition and date
Governance
Who decided, and on what
- The stages a course moves through, with who moved it and when
- Reviewer decisions to edit, reject, or approve
- The reviewer’s written comment when a course is sent back
- Review flags, who resolved them, and the resolution note
- A change log of edits, publications, copies, and archivals
- A history that stays intact
Quality
What was checked, and what came back
- Results of the checks on each module and assessment
- Checks across the whole course and against its design
- A visible status when a check did not apply or was not run, so a gap shows
- The adjustments made when something was sent back for correction
- A record of where AI supported the work, kept with the course
History and delivery
What changed, and where it went
- A version for each published change, with who made it and why
- A revision history that shows improvement over time rather than estimating it
- Any earlier version, as it stood on a given date
- Deployment, recorded separately from approval
- The live version, shown to be the version that was approved
Who reads it
The Same Record, at the Altitude Each Seat Needs.
Reporting reads the record the work is done in, so no office is reconciling one system against another. A read-only role opens reports and courses without any edit or approval rights, which is the role most leadership seats actually want.
| Seat | What it opens the record for |
|---|---|
| Board and president | Portfolio state, governance integrity, continuity and key-person risk, and the condition of the asset in writing. |
| Provost and CAO | Outcome coverage from program to assessment item, currency as a share of courses inside their own review window, and reviewer decisions with the rationale attached. |
| CFO and CBO | Meet timeline and market needs to achieve revenue projections while lowering program development and currency costs. |
| Accreditation and IE | Dated, versioned evidence of how each course was governed, filtered by department, program, or period, with the verification trail behind it. |
| Deans, faculty, designers | The current state of their own work, what changed, what is flagged, and what is waiting on a decision from them. |
| CIO | Where each version is deployed, what was exported, and confirmation that the version deployed is the version that was approved. |
Getting it out
The Record Leaves With You.
A record you cannot take with you is not really yours. Content, versions, approvals, and alignment export in open formats, and deployment runs by the path your platform already supports rather than through a proprietary channel that only works while you are a customer.
The same property is what makes a platform change a redeploy instead of a rebuild, and what makes teach-out readiness a standing condition instead of a project assembled under pressure.
What it exports and deploys
The boundary
What the Record Deliberately Does Not Hold.
A narrow record is easier to defend, easier to explain to a reviewer, and easier to adopt. Keeping it narrow is a design decision rather than a limitation.
Not held
Student records and student work
Grades, enrollment, completion, pass rates, placement, and portfolio submissions stay in the LMS and the SIS, where they already live and are already governed. Every upload point in the platform says so, and the help documentation carries the policy in full.
Not held
The judgment
Approval is a required gate held by your designated reviewers. Cut scores, credit decisions, and whether a course should change at all remain institutional. The platform records the decision rather than making it, and it cannot approve anything on a faculty member's behalf.
Not held
Your institution's own words
The mission, the self-study narrative, the interpretation of a standard, and the relationship with an accreditor belong to the institution. CMP does not represent itself to any accrediting body and does not interpret a standard on your behalf.
Next step
See the Record Built on Something of Yours.
A working session on your own material. Bring a course you want reviewed and updated, or a course you need built, and watch what the record captures while the work happens rather than after it.