Course Proposals


GAAC Course Proposal and/or Revision Form

The course form is required for the following types of proposals:

  • A new course
  • Revision to an existing course, such as:
    • Change in course code, title, course description, prerequisites, or course content
    • Approval for online or hybrid delivery

Drafting Your Proposal

  • Before you begin, it may be helpful to see a preview of the form’s questions: GAAC Course Form Preview.
  • Though the form submission is through Google Forms, you will be able to edit your submission or return to it at a later date. Here’s how:
    • When you submit the Google Form, your responses will automatically populate into a new Google Doc. You will receive via email an invitation to edit this Doc, which now serves as your proposal. If you are not ready for all of the questions on the Form, you may enter a placeholder such as “x” and edit your response later on the Google Doc.
    • You must reach the end of the form and hit “submit” to receive your Google Doc.

Submission Requirements

Your proposal will be added to a GAAC agenda when the following requirements have been met:

  • Proposal: You must submit a course proposal online via Google Form (see link at top of page)
  • Syllabus: All course proposals require a syllabus for the term in which the change would be implemented. Old syllabi will not be accepted for course revision proposals. E-mail all syllabi or other attachments to
  • Signatures: Signatures are still required in order for a proposal to go to the committee.
    • Your proposal (the Google Doc created from your form responses) will be shared with the required reviewers. The reviewers, who will have “suggesting” access, will be some combination of the following, depending on the nature of your proposal: Department Chair(s)/Program Director(s), Academic Dean, Registrar’s Office, and LFC/E-Learning Team.
      • The reviewers will receive an email invitation to review and sign your proposal. After this initial point of contact, it is the proposer’s responsibility to ensure that the required signatures have been made.
    • Signatures may appear directly on the Doc or sent via e-mail from the reviewer’s Augsburg account with a short message indicating their approval. Forward all e-mail approvals to