Faculty Handbook

Learning Management System Guidelines

Some faculty may choose to utilize a Learning Management System (LMS) other than Moodle, the LBCC-supported LMS. 

Because of the lack of technical integration with other LBCC systems, the decision to use an alternative LMS results in additional responsibilities for faculty. Faculty should use this checklist to make an informed decision about using another LMS and/or to ensure that policies, federal regulations, and student needs are met when using another system.  

Communication 

All courses have a Moodle course shell. When courses are delivered through another LMS, faculty are responsible for communicating that information to students. 

  • Ensure students understand where the course is being delivered and how to login
    • Use Moodle as a communication and login “landing page” for students.
      • Link to the LMS and provide login instructions within the Moodle course (required for online courses)
      • Include a syllabus, office hours, contact info within the Moodle course (optional but recommended)
      • Make your Moodle course available to students. 
  • Share information with students through multiple channels (Moodle, email, etc.)
  • Share your rationale for using another LMS (use a positive tone and explain why it is effective for this class; refrain from commenting on Moodle - remember that students are likely using it for other classes)

Technology Support

When faculty use another LMS, students cannot get support from the Student Help Desk. Student Help Desk staff cannot access and are not trained to support other platforms. Faculty cannot get support from the Staff Help Desk or Moodle team. 

  • Evaluate your own confidence and independence in supporting students with the LMS and troubleshooting your own technology issues in the system
  • Ensure that any technology or software requirements are communicated to students in advance and provide access if appropriate
  • Provide technology and login support to students 
    • How accounts are created
    • How to access site
    • Who to contact for troubleshooting (in most cases, this will be the course instructor and should not be the student help desk)

Enrollment/Waitlist/Student Management

Faculty must ensure that the student enrollment in their course matches the student enrollment in Webrunner. Faculty should be checking Webrunner and their LMS course roster regularly and making changes to course access as needed. 

  • Ensure that all registered students have access to the system (Week 0-2)
  • Ensure that waitlisted students can access the course and either register for the course or lose access to the course (Week 0-2)
  • Remove access for students who officially drop the course (Week 0-2)
  • Remove access for students who withdraw from the course (Week 7 or earlier). 

Course Records/Student Work/Incompletes

Course records are maintained by LBCC when faculty use Moodle. If using another system, faculty are responsible for saving and storing course files to meet college and federal policies. See the end of this document for requirements specific to online courses. 

  • Keep course records with student data (activity, assignments, grades, etc.) for 1 year (Suggestion: upload the complete course file into the Moodle course shell after the conclusion of the course)
  • Manage incompletes and access to course beyond the end of the term

Student Success and Support

When using another platform, students may not see student-centered information and your courses may not be integrated into college student success efforts such as Early Alert. 

  • Use the reporting tools within the chosen LMS to track student activity and progress
  • Remind students of important dates and deadlines (e.g. find a way to share information that is posted in the LB Student News block in Moodle). 
  • Provide links and contact information for LBCC resources for students (e.g. CFAR, library, learning center, first resort)

Accessibility & Accommodations

When using a non-supported LMS, the faculty member is fully responsible for the accessibility of the system and any integrated tools. When using Moodle, the faculty member is responsible for accessible course design but not the functional accessibility of the LMS. Faculty must ensure that every student can use, access and perceive all content on your site at the time of delivery.

  • Ensure accessibility standards are met
  • Ensure student accommodations are met 

Policies

Access

Guests may need access to your course for a variety of reasons. In Moodle, there are various roles for guest access and clear timelines and guests access can be managed by the Moodle administrators. When using another system, you are responsible for managing guest access. 

  • Allow dean to access course upon request; manage access level and timeframe
  • Manage access for other course guests (e.g. librarian, outside speaker, other faculty)

Online-Specific

Online courses must meet additional requirements as defined by the college, the accrediting body (NWCCU), and federal policies. 

  • Course shells without student data must be kept for at least 5 years (federal financial aid requirement) 
    • Suggestion: upload downloaded course backup file to Moodle and it will be saved as part of the Moodle backup process
  • Meet RSI (regular substantive interaction) standards. This is a financial aid requirement and is required for all online courses. LBCC will be developing an audit process soon and you may need to grant access to your course if it is in another LMS.
©