Data quality and record readiness
Understand what blocks trustworthy analysis, and define when a record is ready for a process.
Blocchi separates three questions that are often mixed up:
| Concept | Question |
|---|---|
| Data quality | Is the underlying data correct, complete, consistent, fresh and trustworthy? |
| Metric readiness | Does Blocchi have enough mapped evidence to compute this metric? |
| Record readiness | Is this specific record fit to move forward in a business process? |
Data quality (/app/data/quality)
Quality is not an isolated score. The page shows which issues affect which parts of the product, so you fix what matters first — usually through Mapping or at the source. The Revenue page Can we trust the CRM data? shows the same issues from a sales perspective.
Record readiness (/app/data/readiness)
Define what it means for a record to be ready — for example Opportunity qualification readiness or Customer onboarding readiness.
- Create zero, one or many checklists per semantic entity. Checklists attach to Blocchi entities, not provider objects, so they stay portable.
- Each check has a condition, optional applicability criteria, a severity (blocking, required or recommended), a weight, remediation guidance and an order.
- Start from a suggested template; applying it creates your own copy that you can customize.
A record is evaluated to one of four states:
| Status | Meaning |
|---|---|
| Ready | No applicable check failed and no required or blocking evidence is unknown. |
| Needs attention | A non-blocking check failed, or required evidence is unavailable. |
| Blocked | At least one blocking check failed. |
| Not applicable | No check applies to the record. |
The percentage score is secondary: a blocking failure is never hidden by a high score. Readiness is used, for example, when moving an opportunity between stages in the Pipeline.
Related
Last updated on