Create and Submit a Proposal

Create and Submit a Proposal

Start a new proposal

1. Go to Proposals and click New Proposal (or click New Proposal directly in the sidebar).
2. Set Proposal type:
   • New Course: introduces a course that does not exist in the catalog.
   • Revise Course: changes an existing course.
   • Discontinue Course: retires an existing course.
3. If you chose Revise Course or Discontinue Course, the Target course
   field appears. Select the existing course this proposal changes.
   • For Revise Course, selecting a target course prefills the course fields
     below (title, code, description, hours, prerequisites, corequisites)
     from that course’s current record. Edit any of the prefilled values.
4. Set Target catalog year to the year this change should take effect in.
5. Write the Rationale: the plain-language reason for the change.

Fill in the course fields

For New Course and Revise Course proposals, fill in the Proposed course
section: Course Code, Course Title, Description, and the Hours grid
(Credits, Class, Lab, Clinic, Work). Add Prerequisites and
Corequisites as free text if the course has them.

Discontinue Course proposals have no course fields, only a target course and
a rationale.

Save the draft

Click Save (or Cmd/Ctrl+S). A proposal must be saved at least once before
you can submit it.

While a proposal is a draft, you can keep editing it and saving again. Once it
leaves the draft state, editing is locked. See
Why proposals stay isolated until approval.

If you need to delete a draft instead, use Delete from the Proposals list.
A proposal can only be deleted while it is still a draft and has no recorded
committee votes.

Submit for approval

1. Open the saved draft and click Submit for Approval.
2. Confirm in the dialog. It shows the workflow name and the full list of
   steps your proposal will be routed through. This route is frozen at the
   moment you submit; later edits to the workflow will not change it.
3. If your institution has configured validation rules, submission checks
   the proposal against them first:
   • If a blocking rule fails, submission does not go through. A red
     banner lists what needs to be fixed. Correct the fields (Course Code,
     Course Title, hours, and so on, depending on what’s required), save
     again, and resubmit.
   • If an advisory rule fails, submission still succeeds. An amber
     banner lists the advisory warnings so you and your committee can review
     them.
   • See Configure Validation Rules for how
     these rules are set.
4. On success, the proposal moves to the In review state and shows its
   approval route with the first step marked current.

What happens next

Once submitted, the proposal is evaluated against your institution’s
substantive-change signals automatically. See
About substantive change flagging.
If a signal crosses its threshold, an extra review step may be inserted into
the route, depending on how your workflow’s conditional steps are configured.
See Build an Approval Workflow.

To move the proposal through its route, see
Run Committee Review and Meetings.