Creating Workflows for Syllabus

Updated
Watermark Support

The workflow for syllabi 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:

The flowchart showing a linear approval workflow beginning with Submitter, then moving to Program Review, then to Dean with a note stating department dependent. The path continues to Dean for Distance Education, then to Executive VP Academic and Student Affairs, then to Vice President for Institutional Effectiveness, and ends at Approve. A Reject step appears above the main flow, connected by arrows to Program Review, Dean, Dean for Distance Education, and Executive VP Academic and Student Affairs, with a note stating removes the proposal from the workflow and archives.

Branching Workflow:

The flowchart showing two workflows, Program Workflow Example and Course Workflow Example. For the Program Workflow Example, the flow begins with Submitter, then moves to Department Chair, then to Dean with a note stating department dependent and college dependent. From the Dean step, the path branches to Undergraduate Curriculum Committee if the academic level is undergraduate and to Graduate Curriculum Committee if the academic level is graduate. Both branches move forward to Institutional Research, then to Faculty Senate with a note stating can return to the Dean, then to Provost, and then to Approved. Denied actions appear below Faculty Senate, and Provost, each noting the proposal is removed from workflow and archived. For the Course Workflow Example, the flow begins with Submitter, then moves to Department Chair, then to Dean with a note stating college dependent. The path continues to Deans Review, then to General Education Committee if the course requires general education requirements, then to Curriculum Council, then to Provost, and finally to Approved. Denied actions appear below Curriculum Council and Provost, each noting the proposal is removed from workflow and archived.

Branches can be based on:

Committees/Departments/Areas of study:

The flowchart segment showing the Dean step branching to two committees. The Dean box showing notes stating college dependent and can return to submitter to return to this step. One branch leading to Undergraduate Curriculum Committee with a note stating if academic level is undergraduate. The second branch leading to Graduate Curriculum Committee with a note stating if academic level is graduate.

OR

Answers to other questions on the proposal form:

The flowchart segment showing Step 2 moving to Step 3, which includes a note stating can return to submitter to move back through workflow. From Step 3, the path goes to a branching step that is based on a question and its answer. The branching step directs the flow back to Step 3 or forward to Step 4, which includes a note stating no send back option. Step 4 moves to Step 5, which includes a note stating can approve or completely reject the proposal and remove it from 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 1 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!