Back to Report Blocks
FeedbackVolumeTimeline
Trend
Report block
Shows how much feedback arrived in each completed time bucket.
What It Answers
- Is feedback volume stable?
- Were there enough recent examples to trust an alignment change?
- Which periods need more review coverage?
Use When
- Interpreting timeline metrics.
- Checking whether low confidence comes from low volume.
- Monitoring reviewer throughput.
Avoid When
- You need agreement quality; use FeedbackAlignmentTimeline.
- You need item-level rows; use RecentFeedback.
Run From The CLI
Direct report commands are the simplest path for one-off usage. Saved report configurations use `plexus report config create` and `plexus report run`.
plexus feedback report volume \
--scorecard "Customer Service QA" \
--score "Medication Review: Dosage" \
--bucket-type trailing_7d \
--bucket-count 8plexus report config create --name "FeedbackVolumeTimeline Example" --file feedback-volume-timeline.md
plexus report run --config "FeedbackVolumeTimeline Example"Minimal Configuration
class: FeedbackVolumeTimeline
scorecard: "Customer Service QA"
score: "Medication Review: Dosage"
bucket_type: trailing_7d
bucket_count: 8Live Rendered Example
Rendered with the same dashboard component used by generated reports.
FeedbackVolumeTimeline Example
Feedback volume over complete historical buckets
Total Feedback Items
92
Unchanged
77
Changed
11
Unclassified
4
Scorecard: Customer Service QA • Score: Medication Review: Dosage • Buckets: trailing_7d • Valid feedback items: 88
Bucket Metrics
| Bucket | Window | Total | Valid | Unchanged | Changed | Unclassified |
|---|---|---|---|---|---|---|
| Mar 2 | 3/2/2026 - 3/9/2026 | 20 | 19 | 14 | 5 | 1 |
| Mar 9 | 3/9/2026 - 3/16/2026 | 22 | 22 | 18 | 4 | 0 |
| Mar 16 | 3/16/2026 - 3/23/2026 | 23 | 21 | 18 | 3 | 2 |
| Mar 23 | 3/23/2026 - 3/30/2026 | 27 | 26 | 23 | 3 | 1 |
How To Interpret It
- A drop in feedback volume can make alignment gauges unstable.
- Use this with FeedbackAlignmentTimeline before treating a trend as real.