The Workflow Library

Library / Data quality / data-quality-034

Data-verified checkbox with periodic review reminder

Data qualityContactData Hub ProfessionalSimple~20 min to buildFull spec

Outcome. Contacts marked as verified automatically come back up for review after a fixed interval, instead of a verified checkbox staying checked forever after the one time someone actually checked it.

Workflow map Enrollment, branches and actions at a glance data-quality-034
flowchart TD
    A[Data verified checked] --> B[Set Last verified date]
    B --> C[Delay 90 days]
    C --> D[Uncheck Data verified]
    D --> E[Create re-verify task]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it for a manually-set verified, reviewed, or confirmed-accurate checkbox where the underlying data can go stale, a job title, a phone number, even though nobody unchecks the box.
  • UseUse it when a fixed review cadence, quarterly for example, is an acceptable proxy for "needs a fresh look" rather than tracking exactly which field changed since the last check.
  • SkipDo not use it if the fields you actually care about already have their own dedicated freshness tracking, such as a last-verified date tied to enrichment. This fiche is for a simple manual attestation, not a computed signal.
  • SkipDo not use it with a review interval shorter than your team can realistically act on. A reminder nobody clears becomes noise the same way an unchecked box never gets attention.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.2 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.4 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the data quality pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.