Hello,

Our team found the answer to this in the Request FAQs - End User.

If anyone else is interested, you can read the answer in Can we capture resource demand during intake process? 

Took me a while to find what was referenced so i thought i would copy paste from Planview’s Request FAQs - End User: Can we capture resource demand during intake process? 

Yes, through project associations. Once a project is associated to a request, you can capture the role and/or resource demand within that project’s Staffing view.

You will want to make sure that the request category has the Project Associations section configured for it. Make sure that relevant project categories also have Request Associations sections turned on, as that dictates which project categories can be associated to a request. You’ll also want to map relevant fields if you’ll be creating a project. Then, for each gate that you want the Project Associations tab to show up in, make sure it is configured to show at that request category gate.

During the work intake process, permitted users can create new project associations and/or add existing project associations. They can open the project from within the request to edit the role/resource demand.

If you use the Request process for project approval, we recommend you use project Status to distinguish when a project is still being evaluated/in workflow versus when it has been approved.

At a relevant gate where you would want to capture your demand, you would create the initial project with a Status such as “In Request Workflow” or something similar. If the request is ultimately approved, change the project Status as relevant. If the request is ultimately rejected, you can delete the project, or, change its Status to something such as “Rejected” if you need to keep the project around for governance/audit purposes. Be sure to make these statuses Implied Closed, that way when you run any Capacity & Demand Analysis that filter only on Implied Open projects, they won’t be included. You could also just eliminate those status from your filter directly…AND, if it helps, you could include the “In Request Workflow” projects for your Cap/Dem analysis to see impacts.

Another approach is to have a simplified project category for use with Requests that just has basic Details (those you’d map from the request) and the Staffing section, nothing else (unless there is other info you want to capture). Then you can change the project category to another that has the same Details plus others and also Staffing plus other sections.