Track Shortcut Epic Progress Without Hiding Scope Changes
Open a Shortcut Epic’s Reports tab to compare remaining work, completed work and scope change. Progress needs interpretation alongside the Epic’s health and target date.
Most Epic reports need an Epic in a Started state with Stories moving through a workflow. Keep state and estimation conventions consistent before comparing charts.
Example: an Epic starts with 20 points, completes 8 and adds 10. The remaining scope is 22, so completion alone does not mean the target date is becoming safer.
Step-by-step guide
Check the Epic baseline
Open the Epic and review its Stories, current state and target date. Confirm the Stories represent the outcome you are reporting rather than an unrelated backlog bucket.
Read the ARC report
Open Reports and choose Story Count or Points. Compare added, removed and completed work with actual remaining scope; estimate increases also contribute to work added.
Inspect flow rather than only totals
Use Cycle Time or Lead Time to inspect delays, and the workflow-specific CFD for growing queues. Choose the actual workflow before interpreting a bottleneck.
Update health with an explanation
On the Epic detail page, set its health and add the specific risk or decision. Check the Roadmap display so stakeholders see the explanation alongside progress.
Common mistakes
Counting unestimated Stories as zero work
Points reports omit unestimated effort. Compare the Story Count view and resolve missing estimates before making a commitment from point totals.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.