UMF · Course Management
Course Management
How faculty run their programs day to day inside the CampusOS LMS — and how each part of that work satisfies MSCHE standards, UMF SOPs and institutional policy.
10
Topics
CampusOS
Platform
MSCHE
Aligned
Start Here · New to CampusOS?
How to Set Up Your Classroom
The fast, practical walkthrough of a fully built classroom — modules, units and materials you can open just like the real LMS. Get the shape of a course first; the policies and standards come after.
Purpose of this section
Course Development shows you how to build a compliant course. This section shows you how to run it. It covers the live delivery of a course in CampusOS — interaction, attendance, grading, student progress and course review — and makes explicit which MSCHE standard and which UMF SOP or policy each activity answers to.
Outline — content in development. The topics below define what this section will cover and how each part ties back to MSCHE standards and UMF policy. Documents, procedures and guides will be added under each topic as they are written.
Section Outline
1
Getting Started in CampusOSStd III
What a faculty member does first when a course shell is handed over — before students arrive. Most student-facing problems in week one trace back to one of these steps being skipped.
- Accessing your course shell and confirming the roster
- Verifying the syllabus is uploaded and current
- Checking the course is published for the correct term
- Confirming prerequisites and enrolment are correct
- Update every due date for the current term. A shell cloned from a previous term carries that term’s dates. Every assignment, quiz, discussion and exam must be reset against the current academic calendar — including the availability/open dates, not just the due date
- Clone the assignments and confirm each one displays to students. A cloned item can exist in the shell but stay unpublished or hidden, so students never see it. Publish each item and verify it in student view before the term opens
- Do a final pass in student view — if a student cannot see it, it does not exist
2
Regular & Substantive Interaction (RSI)Std III
The federal and MSCHE requirement that distinguishes a real course from correspondence study. RSI evidence in CampusOS is explicitly named in MSCHE Standard III.
- What counts as regular (predictable, scheduled) interaction
- What counts as substantive (teaching, assessing, facilitating discussion)
- Instructor-initiated contact — announcements, feedback, direct outreach
- How RSI is evidenced inside CampusOS for an accreditor
- Minimum expectations per week and how they are logged
3
Weekly Course Operations
The rhythm of running a live course week to week.
- Posting weekly announcements and guidance
- Facilitating and moderating discussion boards
- Instructor guidance hours and availability
- Responding to student questions within the expected window
4
Attendance & Participation TrackingStd IV
How attendance is defined in an online setting, recorded, and reported — and why it matters for federal reporting.
- What constitutes attendance/participation in a distance course
- Recording participation in CampusOS
- Faculty submission deadlines to the Registrar
- Handling non-participation and last date of attendance
5
Grading, Feedback & the GradebookStd V
Grading practice that is timely, consistent and defensible under assessment review.
- Gradebook setup and weighting aligned to the syllabus
- Turnaround expectations for grading and feedback
- Quality of substantive feedback (this also counts as RSI)
- Rubrics and consistency across sections
- Grade changes, incompletes and appeals
6
Student Progress, Retention & SAPStd IV
Spotting students who are slipping and acting on it under the retention and satisfactory-academic-progress procedure.
- Identifying at-risk students early
- Documented intervention and outreach steps
- Referral pathways and who to notify
- How SAP standards apply and are evaluated
7
Workload & Credit-Hour ComplianceStd III
Keeping the running course honest to the hours it claims — the standard is roughly 45 hours of total student work per credit hour per semester.
- Staying aligned to the approved Credit Hour Measurement Chart
- Applying the reading and writing time standards when adjusting work
- What to do when a course drifts above or below the required hours
- Documenting any mid-term change to assignments
8
Course Review & Continuous ImprovementStd V
Every course is reviewed at least once a year, timed for the middle of the semester while real student data is available.
- What the mid-semester review examines
- Using student performance data and course evaluations
- Recording findings and the changes made as a result
- Who signs off and when
9
Evidence & Documentation for MSCHEStd III · V
What a faculty member should be able to produce if the course is pulled for accreditation review.
- Syllabus of record and approved credit-hour chart
- RSI evidence exported from CampusOS
- Gradebook, rubrics and samples of student work with feedback
- Attendance/participation records
- Course review record and resulting changes
10
How to Ask for Support on CampusOS
Support is raised as a ticket through the Help section inside CampusOS. How you write that ticket — and when you raise it — largely determines how quickly it gets resolved.
- Raise the ticket in CampusOS → Help section. That is the route to the CampusOS support team. If it is not raised as a ticket, it is not tracked and it will not get worked
- Always attach a screenshot. A picture of the actual screen showing the problem resolves a ticket far faster than a written description alone. Capture the full screen, including the address bar where possible
- Give complete detail. Course code and term, the exact page or screen, what you expected to happen, what actually happened, when it started, and whether it affects one student or the whole class
- Keep every message professional. Support staff are colleagues working a queue. Rude, abrupt or unprofessional tone is not acceptable and will not be tolerated — and a courteous, factual ticket gets a better and faster result
- Support runs during office hours, Monday to Friday. A ticket raised on a Friday may not receive a response until Monday
- So check your course early in the week. Verify due dates, assignment visibility and links during weekday office hours — not Friday afternoon or over the weekend — so there is time to get a fix before students are affected