Skip to main content
Back to help centre
Data QualityPlatform admins5 min

Verifying And Documenting Data Quality

Use the verification workflow, methodology field, and notes properly so users understand the quality and provenance of a dataset.

Verification should be reserved for datasets that have actually been reviewed. Overusing the badge reduces trust in the entire portal.

The platform records verification status, verifier identity, date, and optional notes in the dataset metadata.

Guide Structure

When To Apply Verification

Use verification only after the dataset has been reviewed against your internal quality criteria. The exact criteria can vary, but the badge should never be applied casually.

Methodology and verification notes are the two most useful supporting fields because they explain both provenance and review context.

How To Mark A Dataset As Verified

Verification controls are only available to sysadmins. When a dataset is saved as verified, the portal records who verified it and when.

Steps

  1. 1Open the dataset in the admin area.
  2. 2Review or update the methodology field.
  3. 3Enable the verified checkbox.
  4. 4Add concise verification notes if they help explain the review.
  5. 5Save and confirm the public view shows the expected badge and metadata.

Screenshot Slot

Verification controls in admin form

Dataset edit form showing verification controls, notes, and methodology together.

Screenshot Slot

Verification metadata on public page

Public dataset page displaying the Verified Data badge and supporting verification metadata.

Keep The Badge Trustworthy

If a dataset becomes outdated or disputed, remove the verified status until it is reviewed again. Verification should reflect current confidence, not historical effort alone.

Tips

  • • Use methodology for data collection detail.
  • • Use verification notes for review-specific context.
  • • Re-check verified datasets when major updates are published.