Include Buyer in ePro Req Workflow....Do or Don't Best Practice?

  Hi Community,

We are using ePro 9.1 and currently have reqs  that do not qualify for AuotSourcing routing to buyers for approval via workflow. The buyer is the last approver in the flow. This is primarily done as a req distribution process but also allows buyers to deny reqs that are not up to "procurement ready" standards. Example being incomplete descriptions or missing supporting documents. My concern is that this practice makes cycle time calculations problematic because the buyers actually start some purchasing activities once the req hits their worklist, but in advance of actually approving the req. Therefore, the "purchasing" cycle