Back to Report Blocks

AcceptanceRate

Marketing
Report block

Measures the share of score results, and optionally items, accepted by reviewers without correction.

What It Answers

  • How often do reviewers accept AI decisions?
  • Can we show a simple positive trust metric?
  • Which recent items were fully accepted or corrected?

Use When

  • Stakeholder updates.
  • High-level adoption reporting.
  • Complementing technical alignment metrics.

Avoid When

  • You need chance-corrected agreement; use FeedbackAlignment.
  • You need class-level failure modes.

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 acceptance-rate \
  --scorecard "Customer Service QA" \
  --score "Medication Review: Dosage" \
  --days 30 \
  --include-item-acceptance-rate
plexus report config create --name "AcceptanceRate Example" --file acceptance-rate.md
plexus report run --config "AcceptanceRate Example"

Minimal Configuration

class: AcceptanceRate
scorecard: "Customer Service QA"
score: "Medication Review: Dosage"
days: 30
include_item_acceptance_rate: true
max_items: 25

Live Rendered Example

Rendered with the same dashboard component used by generated reports.

AcceptanceRate Example

Reviewer acceptance for selected score results.

March 1, 2026 to March 31, 2026

Item Acceptance Rate
85.00%
Score-Result Acceptance Rate
85.80%
Accepted Items
68 / 80
Accepted Score Results
103 / 120
Feedback Edits
80
Valid: 78
Value changed: 17
Scorecard: Customer Service QA • Score: Medication Review: Dosage • Feedback edits: 78/80 • Value-changing edits: 17 • Rendering 1 of 1 rows
Item DateItem IdentifiersFeedback EditsScore ResultsAcceptedCorrectedScore Result Acceptance Rate
CALL-001
0/0220100.00%
All rows loaded (1)

How To Interpret It

  • Acceptance rate is intuitive, but less diagnostic than AC1.
  • Use item acceptance when a human-friendly story matters more than score-result granularity.