Creating Workflows for Curriculum

Updated
Watermark Support

The workflow for curriculum will define which individuals the proposals should be sent to for approval, and the order of those approvals.

Workflows can be completely linear, or they can branch at different points to send to different user roles depending on how a certain field is answered in the proposal.

Linear Workflow:

A Flowchart showing a Linear workflow. It starts with “Submitter,” then moves to “Program Review,” followed by “Dean (Department Dependent),” “Dean for Distance Education,” “Executive VP Academic and Student Affairs,” and “Vice President for Institutional Effectiveness,” ending with “Approve.” Arrows indicate the sequence and allow movement back and forth between steps. A “Reject” option sits above the process and connects to multiple stages, indicating that a proposal can be removed and archived at various points.

Branching Workflow:

A branching workflow diagram showing two workflow examples, including a program workflow with steps such as submitter, department chair, dean, undergraduate curriculum committee, graduate curriculum committee, institutional research, faculty senate, provost, and approved or denied outcomes, and a course workflow with steps such as submitter, department chair, dean, deans review, general education committee, curriculum council, provost, and approved or denied outcomes.

Branches can be based on:

Committees/Departments/Areas of study:

A Flowchart segment showing a decision point involving the Dean. The “Dean (College Dependent)” step notes that the proposal can be returned to the submitter or remain at this step. From the Dean, the process branches based on academic level: one path leads to “Undergraduate Curriculum Committee” if the academic level is undergraduate, and the other leads to “Graduate Curriculum Committee” if the academic level is graduate. Arrows indicate movement between the Dean and each committee.

OR

Answers to other questions on the proposal form:

A Flowchart showing part of a process with a branching decision. The sequence begins at “Step 2,” then moves to “Step 3,” which notes the option to return to the submitter to move back through the workflow. From Step 3, the process continues to a “Branching step” based on a question and its answer. From this decision point, one path leads to “Step 4,” which does not allow sending back, and then proceeds to “Step 5,” where the proposal can be approved or completely rejected and removed from the workflow.

A separate workflow will have to be designated individually for each form you create, even if multiple forms use the exact same workflow steps.

After determining your workflow, a spreadsheet will be generated by us for you to fill out, designating which users should be assigned to which workflow steps to act as the approver for that step.

Was this article helpful?
0 out of 0 found this helpful

Articles in this section

See more
How to Contact Support
There are many ways to reach out! Click the icon above for our support options.
Watermark Academy
Click the icon above to access the Watermark Academy for consultation, training, and implementation companion courses.
Customer Community
Can’t find the answer? Ask fellow users how they’re making the most of Watermark in our Community!