Proposing an ASEM Course

Faculty

Faculty who wish to propose an ASEM should email Dr. Rachael Liberman (rachael.liberman@du.edu), Faculty Director of ASEM and FSEM. The Faculty Director will enroll the interested faculty in the online ASEM training course in Canvas. After faculty complete the training and develop their syllabus and proposal, they will submit their ASEM proposal. 

Submitting an ASEM proposal

After completing the online ASEM training course, complete the following: 

  1. Download ASEM Course Proposal form and create a new document with your responses to the questions and prompts about your proposed course, and include your syllabus.
  2. Login to CourseLeaf/NextBulletin Course Proposal site and click at the button to propose a new course.
  3. Follow this CourseLeaf ASEM Proposal Guide to submit your new ASEM course proposal. Where it asks for a syllabus, upload the full ASEM Course Proposal document (with your syllabus)

Compensation

Faculty will receive $600 upon completion of the Canvas training and approval of their ASEM course proposal. They will receive an additional $600 after they teach their ASEM course and submit a teaching reflection. After teaching their ASEM the first time, faculty should email the Faculty Director of ASEM and FSEM to initiate the process for the second payment.

Proposal Review

The ASEM committee, with faculty representatives from CAHSS, Daniels, Korbel, and NSM, reviews proposals. About 30% of proposals are approved as submitted. About 60% need minor revision (often just a clarification or a addressing a minor omission). About 10% need a significant revision, usually due to a substantial missing element, lack of fully developed syllabus or because they significantly miss the nature of ASEM courses. The committee is happy to work with faculty proposers, and nearly 100% of proposals are ultimately approved. Only when a proposer chooses to withdraw a proposal is it ultimately not approved. The ASEM Committee looks for ways to say yes to your proposal. Taking a little time up front can save you time on backend revisions.