Stratus Cloud Solutions Stratus Docs
Documentation / Data Cleanser User Guide / Settings

Data Quality Score

Data quality score measures how complete, valid, unique, and fresh your CRM records are — per object and org-wide. Open the Quality tab to see scores, distribution, and a 30-day trend, then run scoring on demand or configure checks under Settings → Quality.

The Quality tab requires the Data Quality license. Without it, the tab is hidden and record score cards show an upgrade prompt.

Open the Quality dashboard

The Quality tab sits between Review and Settings in the app navigation. The dashboard has two main actions:

  • Configure scoring — opens Settings → Quality for the selected object.
  • Run scoring — queues a background batch job that evaluates every record in scope.

On first open, the dashboard shows an empty state. Run scoring to populate scores — batch jobs run in the background and may take a few minutes in large orgs.

Scope tabs

Use the scope bar at the top to switch between All objects, Accounts, Contacts, and Leads. Each scope shows:

  • Hero score — the average quality score for the scope, with a color band.
  • Distribution — how many records fall in each band.
  • Trend — daily snapshot averages for the last 30 days.
  • Per-object cards — when viewing All objects, a card per object with its score and record count.

Score bands

Band Range Meaning
Excellent 90–100 Records meet nearly all configured checks.
Good 70–89 Mostly healthy with a few gaps.
Fair 50–69 Noticeable completeness or validity issues.
Poor 0–49 Many records fail one or more checks.
Unscored Not yet evaluated — run scoring to populate.

Four scoring dimensions

Each record's score is a weighted blend of four dimensions:

Completeness
Are key fields populated? Default checks look for missing values on important fields.
Validity
Do values follow expected formats — email, phone, picklist, regex, or number range?
Uniqueness
Does the record duplicate another on configured unique fields?
Freshness
Has the record been updated within the freshness threshold (default 365 days)?

Run scoring

1

Choose a scope

Pick All objects or a single object tab.

2

Click Run scoring

A batch job queues in the background. A progress band shows percentage complete and records processed. You can navigate away — scoring continues.

3

Review results

When complete, the hero score, distribution, trend chart, and per-object cards refresh. Daily snapshots feed the trend — run scoring regularly to build history.

If a run fails, a banner appears with the error and a Retry button. Check Settings → Warnings for details.

Configure scoring

Open Settings → Quality (or click Configure scoring on the dashboard) to edit the scoring profile for each object.

Use case mode — start with sensible defaults

Use case mode shows the default checks for typical hygiene scenarios on the selected object. Switch to Advanced to edit dimension weights or add custom checks.

Advanced mode — weights and custom checks
Dimension weights
Completeness, Validity, Uniqueness, and Freshness weights must total 100%. Defaults are 30 / 30 / 25 / 15.
Check types
Populated, Email format, Phone format, Picklist valid, Regex, Number range, Freshness, and Uniqueness — each tied to a field and dimension.
Freshness threshold
Records older than this many days since last modified count as stale (default 365).
Reset to defaults
Restores the bundled check set and weights for the object.

Click Save to apply profile and check changes, then run scoring again.

Record-level score card

When the Data Quality license is active, a Data quality score card appears on Account, Contact, and Lead record pages. It shows:

  • An overall score gauge with the same band colors as the dashboard.
  • Per-dimension breakdown with pass/fail indicators.
  • A list of failed checks so reps know exactly what to fix.

Records are scored during the batch run. If a record has not been scored yet, the card shows a not-scored state until the next run completes.

Relationship to duplicate matching

Data quality scoring and duplicate matching are separate capabilities. Uniqueness checks flag records that share values on configured fields, but merging duplicates still happens in the Review tab. See The Duplicate Queue.