Adobe Experience Cloud
Workfront proof reports need the approver’s actual decision interval
Define which Workfront proof events support a per-approver open-to-decision report across versions.
November 11, 2026
A proof can finish on time while one stakeholder sits on it for days and another responds in minutes. A Workfront community question asks for the interval from each approver opening a proof to making a decision, grouped across versions. A proof-start-to-completion report cannot answer that question.
Specify the event grain
Define one row as proof ID, version, approver, stage and decision. For each row, ask for routed time, first open time, decision time and the timezone. Separate “time waiting to be opened” from “time after opening”; both may matter to an operations team, but they describe different constraints. Decide how to treat people who never opened the proof, reopened it, or changed a decision.
Adobe’s Proof Approval report documentation names Decision Date as an available field. Adobe’s proof reporting tutorial describes approval, stage and decision fields. Neither citation alone proves that a first-open timestamp is available in the same report type. Test the field inventory in your Workfront configuration before promising an open-to-decision metric.
Validate the report on one proof
Choose a proof with two versions and multiple approvers. Reconcile each reported date against its activity history. If first open is not exposed in standard reporting, document that gap and evaluate a supported event export or an agreed proxy metric. Do not label routed-to-decision as opened-to-decision.
Adovo’s view
The metric must preserve the human handoff it is meant to improve. A precise decision interval can reveal a bottleneck; an imprecise one can blame the wrong person. Get the event definitions right before building the dashboard.
