Feedback Request Overview
The Feedback Request Overview report page presents the visuals listed below. Each row gives the on-screen name, its underlying metric, and a short description; see the metric glossary for the full formula and interpretation.
Visuals:
| Name | Measure | Description |
|---|---|---|
| Total feedback requests | Count of feedback requests (one per request record) | Number of feedback requests made, in scope. It counts request items, not people, so someone who asked several times contributes several. It measures the volume of requesting activity, not how many distinct people requested. Read against # Users who requested feedback (distinct requesters) to separate heavy requesting by a few from broad participation. |
| Requests sent over Time | Count of feedback requests, by date (requests sent each period) | Number of feedback requests made in each period, plotted as a trend. Each point is that period's total, not a running total, so it shows the rhythm of requesting activity (spikes around review cycles, quiet stretches). It counts requests, not people, so heavy requesting by a few shows up here. Read against # Feedback sent over time to compare asking versus giving over time. |
| Feedback sent by role | Count of feedback items sent (one per feedback record) | Number of pieces of feedback given, in scope. It counts feedback items, not people, so a prolific sender who gave 20 pieces contributes 20. It measures volume of feedback activity, not reach. Read against # Users who sent feedback (distinct givers) to tell heavy use by a few apart from broad participation. |
| Requests read | Count of feedback requests that were read÷ count of all feedback requests | Share of feedback requests that the recipient has opened/read. It gauges whether requests are reaching attention, separate from whether they are answered: a request can be read but not replied to. A low value means requests are going unseen; compare it with the reply rate to tell "not seen" apart from "seen but ignored." |
| Requests with behaviors | Count of feedback requests that reference ≥1 behavior÷ count of all feedback requests | hare of feedback requests that specify at least one behavior to be assessed on, rather than being open-ended. It signals how structured and framework-aligned requesting is; a low rate means most requests are freeform, a higher rate means requesters point to specific behaviors. It counts requests, not behaviors or people. Read against # Requests with behaviors for the count and % Feedback with behaviors for the sent-side equivalent. |
| Reply rate | Count of feedback requests replied to÷ count of all feedback requests | Share of feedback requests that received a reply, i.e. how responsive people are to being asked for feedback. It puts the replied count in context so periods or teams with different request volumes compare fairly; a low rate means requests are going unanswered. It's measured at the request level, so someone who ignores several requests drags it down more than someone who ignores one. |
| Total behaviors requested | Sum of each request's requested-behavior count (total behaviors requested across requests) | Number of behaviors that feedback requests asked to be assessed on, in scope. Behaviors are the competency/value tags, so this counts behavior instances attached to requests, not the requests and not people; one request asking about three behaviors adds three. It shows how much requesting is anchored to the behavior framework. Read against # Feedback requests and # Requests with behaviors . |
| Total requests by behavior | Count of feedback requests, by requested behavior | How many feedback requests ask for feedback on each behavior, showing which behaviors people most want to be assessed on. It surfaces demand for feedback against the behavior framework. It counts requests, not behaviors or people, and a request naming several behaviors appears under each, so the bars can exceed the total request count. Read against # Feedback requests for the overall volume. |