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)
The page answers one question: can you trust your Revenue numbers right now? It reads the same checks that decide whether Revenue pages show a number or a notice, so the two always agree.
- Counting — which CRM Blocchi is counting. Blocchi never mixes records from two CRMs. If Blocchi CRM and an external CRM are both connected, an admin chooses one under Commercial model (
/app/commercial-model); until then Revenue numbers stay empty. - Last sync — when the counted CRM last synced. Blocchi CRM is written in place, so it is always live.
- Metric by metric — whether each Revenue number is complete, and if not, what is missing (unmapped fields, a stale sync, a size limit) with a link to the fix.
- Fix it at the source — Mapping, Record readiness, Sources and, with Data+, Quality resolution.
When an external CRM is the one counted, the page also links to its hygiene checks (activity, close dates, contacts). Those describe how the CRM is kept, not whether the numbers are complete; the Revenue page Can we trust the CRM data? covers them.
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