Flow reports to know

Before we finish up our discussion of driving Flow usage in your organization, let's look through some recommended reports as you continue growing your Flow journey.

You can check out our full list of reports for additional context, but here are the four reports we recommend for most teams getting started. We've talked about some of them before in this Admin success center, but others will be new to you.

Tip: Refer to the Resources to enable your teams article for reports organized by strategic directions. The list in this article is mainly useful for organizations just getting started and trying to pick their first few reports to learn and focus on. As you grow and share Flow data with more people, more reports will become relevant and essential. In the meantime, ask your teams what reports they would be interested in and what they might want to use, with the list in this article as a guide. 

Work log

  • Use Work log to visualize activity patterns over week-long periods for users, teams, and repos.
  • This report doesn't directly surface team-level metrics, but is a great option to get an at-a-glance assessment of when the different parts of your work are happening.
  • If you're already looking at Coding days in Work log, start small by investigating your PR and PR comment activity patterns. 

Team health insights

  • Use Team health insights to get insights on your team metrics and patterns across several metrics categories.
  • This report doesn't surface individual-level data, but gives you a simple view of team and organization metrics over longer time periods. It's particularly useful to share insights with those interested in more high-level data.
  • If you're already looking at Coding days in Team health insights, try exploring one of the PR metrics. Unreviewed PRs is a great introduction to how your PRs are being reviewed.

Review collaboration

  • Use Review collaboration to explore your PR review patterns. The metrics at the top are also available in Team health insights, but the interactive mapping graph at the bottom lets you visualize who is submitting reviews, who is completing reviews, and who likes to work together most.
  • If you just need the PR metrics themselves, Team health insights is the report to use. But the real value in Review collaboration is combining the metrics insights with the visualization of how reviews are being submitted and completed. Use this to better understand how your team works together to uncover bottlenecks in the review process.
  • Start by exploring who submits and reviews the most PRs and see what surprises you. Then have conversations with your team to learn more.


  • Use Retrospective to understand patterns in your ticket completion. Understand what you're getting done, where things are getting stuck, and how your ticket patterns are changing over time.
  • While this report is full of useful information, it also needs additional configurations if you haven't explored your ticket data before. Review your ticket project configurations to make sure your data is correctly captured. 
  • Start by understanding how many tickets you're completing. If you're already comfortable with that information, explore Queue time to understand where your tickets are getting stuck in the process.

What's next?

Now that you've started engaging with Flow, it's time to make a plan for how you're going to continue to grow. 

back to top

If you need help, please contact Pluralsight Support.