The Sourcing Plan approval workflow design documents the City’s required approval process for sourcing plans.


At a high level, the sourcing plan workflow incorporates the following process steps.  Project plans can vary greatly.  Pre-bid and post-bid tasks will vary from project to project.


This depicts a detailed view of the Sourcing Plan Approval:


 

Security


An Event Approver should be able to approve or deny a posted event.


Alerts & Notifications


When a sourcing plan is approved or denied, an email notification should be sent to the Plan Owner.


Once a sourcing administrator has completed the project plan, he or she will post it.  If the criteria for the approval process is not met, then the plan will be automatically approved and the approver and plan owner will be notified.  The plan status will change to Posted.


If the criteria for the approval process is met, then the approval workflow engine will route the approval task to the approvers defined in the approval process.  The plan status will change to Pending.  The workflow should require a user with the Event Approver role to approve or deny the plan.  Once the plan has been approved, then the plan status will change to Posted.