What QC checkpoint Admin notes are for

Admin notes are the one checkpoint field the reviewer never sees. Every QC checkpoint has six fields, and five of them shape what a reviewer reads and scores. Admin notes are different: they are private comments for administrators about a checkpoint, hidden from the QC Agent doing the review. They exist purely for the people who build and maintain the scorecard.

Why a hidden field is useful

Scorecards get edited over time. A checkpoint that made perfect sense six months ago may be a mystery to the next admin who inherits it. Admin notes are where you record the reasoning that does not belong in front of a reviewer:

• Why a checkpoint exists — the policy or complaint that prompted it.
• How to interpret a borderline case, for the admins who calibrate reviewers.
• When the checkpoint was last changed and what changed.
• Which regulation or client requirement it maps to.

Admin notes versus checkpoint text

The split is the whole point. Checkpoint text is reviewer-facing — it is the question they grade. Admin notes are admin-facing — they are context about the question. Keeping them separate means you can document a checkpoint thoroughly without cluttering the reviewer's screen with internal detail. A reviewer wants a clear, short question to grade against; an admin wants the history and the reasoning. One field cannot do both jobs well, which is why the checkpoint gives you two.

There is also a practical reason to keep notes out of the reviewer's view. If you wrote the policy reference or the client name into the checkpoint text, you would be leaking internal detail to whoever grades the call, and you would risk biasing the score. A note that says "client requires this verbatim" belongs in Admin notes, not in front of the person grading.

flowchart LR
  A[Checkpoint] --> B[Checkpoint text]
  A --> C[Admin notes]
  B --> D[Shown to reviewer]
  C --> E[Admin only]
  E --> F[Never on evaluation screen]

Where to set them

Admin notes sit alongside Order, Active, checkpoint text, Points, and Instant kill on the MODIFY screen for a scorecard. For a new checkpoint, type the note in the ADD NEW CHECKPOINT form and click the green ADD button. For a checkpoint that already exists, edit the note in place — it saves automatically, no submit button needed.

Because Admin notes never reach the evaluation screen, they have no effect on scoring or on whether a call passes. They behave the same whether the scorecard is attached to a Campaign, a list, or an Ingroup, and they are irrelevant to whether a call is eligible for review at all — that still depends on the call's Disposition matching a QC status template.

For the wider picture of how checkpoints, scorecards, and the review queue connect, read the VICIdial quality control overview. For what every checkpoint field controls, see what each QC checkpoint field means.

VICIfast runs the whole QC stack on a managed, hardened VICIdial box, live in under 40 seconds. See our plans and pricing.