Glossary
Terms used across these docs. Each entry links to the page where the term is covered in depth.
Auto-rule
Section titled “Auto-rule”A backend rule that applies a Property to a Session item automatically. VoiceQC ships with two built-in Auto-rules: the Mismatch rule and the Non-Verbal rule. Auto-rules tag items based on simple comparisons, not waveform analysis.
The recipient of a Share. A Guest has no VoiceQC account and sees a read-only view of one Session at /guest/:token/session/:sessionId. They can play audio, read transcriptions, and view Properties. They cannot edit, sign up from the guest view, or see other Sessions.
Mismatch rule
Section titled “Mismatch rule”The Auto-rule that compares an uploaded Script line to its transcription and flags items whose normalized strings differ. Normalization options (case, punctuation, whitespace) control how strict the comparison is. See Configure a Mismatch rule.
The category portion of a Property. Examples: Status, Take, Speaker. A Name in your Property library carries one or more Values.
Non-Verbal rule
Section titled “Non-Verbal rule”The Auto-rule that flags Session items whose speech confidence falls below a configurable threshold (0–1). Useful for surfacing breath, silence, or non-speech sounds that slipped into a take. See Configure a Non-Verbal rule.
Your account’s billing tier. A Plan controls character and item limits per Usage period, plus whether overage is allowed. The live Plan menu is at the Pricing page; your current Plan and status live on the Billing settings page. See Plans and limits.
Property
Section titled “Property”A structured tag on a Session item (or a Session) — a Name / Value pair drawn from your Property library. Examples: Status / Approved, Speaker / Hero. Multiple Properties can be applied to the same item. See Property model.
Property library
Section titled “Property library”The set of Names and Values defined across your account. Everyone on the account picks Properties from this library when tagging. Created implicitly the first time someone adds a Property; grows as the team extends it. See Build your Property library.
Script
Section titled “Script”A CSV file you upload alongside audio to declare the expected line for each take. The Mismatch rule compares the Script against the transcription and flags differences. See Script CSV format.
Session
Section titled “Session”A project container for one or more audio files. Sessions are listed on the Logs page; the active Session is at /session/:sessionId. The upload zone, transcription progress, Property editor, Share management, and CSV export all live in the Session view.
Session item
Section titled “Session item”One audio file inside a Session. Each Session item carries its filename, transcription, optional Script line, and any Properties you’ve applied to it. One row in the Session items table = one Session item.
A magic-link grant that lets a non-account holder (Guest) read one Session without signing in. Shares are time-limited (7–90 days), optionally password-protected (no password, auto-generated, or custom), and revocable. See Manage Shares.
Transcription
Section titled “Transcription”The text VoiceQC produces from an audio file. Appears in the Session items table the moment it’s ready — you don’t need to refresh. See How transcription works.
Usage period
Section titled “Usage period”The billing window over which character and item counts accumulate toward Plan limits. Typically one month. Visible on the Usage page (/usage).
The choice within a Name in a Property. Examples: Approved, Take 1, Hero. Values are scoped to their parent Name — Approved under Status is independent of any Approved under a different Name.
Terms not in the product
Section titled “Terms not in the product”A few terms are common in adjacent tools but are deliberately not part of VoiceQC’s vocabulary. If you see them in older notes or in the codebase, treat them as residue.
Schema
Section titled “Schema”Internal-only term for what the docs call Property library. Don’t use “schema” in user-facing language.
A third level above Name in the internal data model. The UI hides Type today because user testing found three levels confusing. May surface in the future via an advanced mode.
What VoiceQC doesn’t detect
Section titled “What VoiceQC doesn’t detect”VoiceQC works at the transcript layer. It does not detect clipping, mouth-clicks, mix balance, loudness, mispronunciation phonemes, or any DSP-level audio property. If you need those, you need a different tool. The Auto-rules flag items based on transcript and speech-confidence comparisons, not audio analysis.