Reviewing & Routing Requests
Written by Don
Updated over a week ago

Requests that are submitted by your Requestors will need to be reviewed and ultimately routed to be worked on by your production team. Let's begin by understanding where submitted requests will appear.

  • In the Requests Incoming Widget of the Desktop Application, you will see the submitted Request in the 'ToDo' tab. Click on a Request to open it:

  • Review the details of the Request. Upon review, you will make a decision to either 'Approve Request' or 'Route Back to Submitter'. 'Approve Request' means that you accept this Request as is and will move on to scheduling the work, but 'Route Back to Submitter' means that you require further details, clarification, etc and would like to send the Request back to the Requestor for re-submission

  • Requests can also be rejected outright. This can be accomplished through the dropdown highlighted below:


  • If a Job Request was submitted, it will activate the associated Job once the Job Request is approved. If a Project Request was submitted, it will activate the associated Project once the Project Request is approved. Find the appropriate Job or Project record and open it (in it's respective widget):

  • Upon opening the Job, you will see 4 tabs: Job Ticket / Shared Files / Production Files / Schedule. Notice that this is 'Job #1005 - Test Request', and it's associated to 'Request #115'

  • 'Job Ticket' will populate with details that were entered on the original Job Request. However, you may choose to enter additional information here. Once you are satisfied with the content of the Job Ticket, navigate to the 'Schedule' Tab

  • On the 'Schedule' tab, confirm that the appropriate Schedule Template has been applied (change the template if appropriate)

  • Once the correct template is present, and Durations are present for all activity steps, confirm either the 'Planned Start' or 'Planned Finish (Due)' Date. While in 'Edit' mode, click the Set Plan button next to Planned Start (to build activity dates based on the Start Date) or the Set Plan button next to Planned Finish (Due) (to build activity dates based on the Due Date).

  • Now you can assign the appropriate people to the Roles

  • When finished assigning Roles, click 'Save'

  • The Job is now ready to begin work, and the first step on the schedule should be active. As steps are completed, and the workflow progresses, the assigned users will see tasks appear in their ToDo widget on the Dashboard

  • For example, the first task (Design) is assigned to Andrea:

  • Andrea's ToDo Widget displays the Design task - the subsequent tasks in the workflow will not trigger until she clicks 'Finish' on the activity:

  • At which point, it moves on to the next assignee (Bill Dykema) for Internal Proofing:


Did this answer your question?