Outcome. New companies missing a domain or an industry value are flagged and routed to a cleanup queue instead of sitting incomplete through their first reporting cycle.
flowchart TD
A[Company created] --> B{Domain and industry present?}
B -->|both missing| C[Flag: Missing domain and industry + list + task]
B -->|domain only| D[Flag: Missing industry + list]
B -->|industry only| E[Flag: Missing domain + list]
B -->|both present| F[Flag: Complete]

When to use it, when not to
- UseUse it when reps create company records manually and skip fields that later reporting and segmentation rely on.
- UseUse it when import processes bypass form validation and create sparse company records.
- SkipDo not use it expecting it to block record creation. Workflows react after a record exists; they cannot prevent creation. For hard blocking, enforce required properties at the point of creation in your CRM's record-creation settings where supported (check in your portal: whether a company-create required-property enforcement exists outside forms in the current UI).
- SkipDo not use it for revenue or employee count completeness. That is a broader completeness check, see data-quality-022 for a scored version across several fields at once.
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.





