Workfront Proof (PHQ): Robust Reporting | Community
Skip to main content
New Participant
October 22, 2019
Approved

Workfront Proof (PHQ): Robust Reporting

  • October 22, 2019
  • 11 replies
  • 1905 views

Possible this is redundant to other proof ideas, but can't always tell what is for the built-in proof vs. Workfront Proof (formerly Proof HQ); this is for the latter:


We need more robust reporting back to Workfront. Things like:


  1. Current Stage Name
  2. Current Stage Start Date
  3. Current Stage Due Date
  4. Any previous stages and their name, start date, and complete/lock dates
  5. A true "complete" status (vs. the vaguer idea of a "lock") for the entire review/routing. And make this complete/lock information reportable.


The idea is that when a project manager (proof owner) has dozens of routings multiplied by 6-12 reviewers each that they should be able to have a report/dashboard that can report back robust information without diving into each individual project/task/document.

11 replies

KierstenKollins
New Participant
October 22, 2019

Upvoted!


Agreed.


We too are looking for more robust data around proofs to understand patterns and how are users are interacting or not.


We are looking for the volume of comments left on a proof to understand if there are misses in our process upstream. We also need a way to categorize the types of comments to see if users are staying within our guardrails for routing feedback.