For a leader whose customer relationship management system contains records but does not reliably guide action.
01Name the decision in operational terms
“Improve visibility” is difficult to configure or test. “Decide which active opportunities need a follow-up this week” is clearer. It identifies a person, a recurring choice and a point at which information should lead to action.
Ask the person making that decision to show how it happens today. Which records do they consult? What do they ask colleagues? Where do they distrust the system and return to a private spreadsheet? These workarounds can reveal missing definitions, stale information or a routine the software does not support.
Start with one decision and one responsible role. A customer relationship management system may eventually support several teams, but attempting to define every possible use at once can obscure the first useful change.
02Work backward to the minimum useful information
For the follow-up decision, the team might need a current opportunity owner, an agreed next action, a due date and a status with a clear meaning. Those are candidate fields, not a universal CRM specification. Your process may need more, less or different information.
For each field, record its definition, source, responsible role and update trigger. “Qualified” means little if one person uses it for a promising conversation and another for a confirmed fit. A mandatory field can be complete and still misleading when people fill it with a guess to move on.
The UK Government Data Quality Framework treats quality as fitness for purpose and distinguishes completeness from accuracy.1 We apply that general principle to CRM design here. It is not a certification, a software recommendation or a legal requirement imposed on your business.
A decision-to-data contract
- Decision
- Which active opportunities need action before the next review?
- Minimum inputs
- Responsible role · agreed next action · due date · defined status
- Meaning and source
- A shared definition for each field; the approved record of the latest agreement
- Maintenance
- Named role and update trigger; a way to mark uncertainty
- Quality check
- Can another authorized colleague understand the next action, verify it against the approved source and see whether it is still current?
- Action
- Resolve overdue, missing or disputed actions at the agreed review
03Agree what the team will do with the information
A field should have a use beyond satisfying a reporting request. State the action it enables: identify overdue follow-ups, assign an unowned opportunity or ask whether a stalled item still belongs in the active pipeline. If nobody can explain the use, question whether the field belongs in this workflow.
Agree a review routine with the people who maintain the records. Who checks exceptions? Who resolves a disputed status? What happens when information is unavailable? An honest “not yet confirmed” can be more useful than a fabricated completion.
The decision-to-data contract below connects those responsibilities. It is an editorial design aid, not a claim that the organization has granted authority or that a particular system can implement every requirement.
04An illustrative contract: follow-up that leads to action
Imagine a sales manager who begins a weekly review by asking everyone for updates that should already be in the CRM. The team chooses one decision: which active opportunities require action before the next review?
They define “next action” as an agreed activity with a responsible role and due date, rather than a general note such as “follow up”. They decide when a conversation should trigger an update and how to flag an opportunity whose next action is genuinely unknown. The review then focuses on overdue, missing or disputed actions.
A small trial checks whether another authorized colleague can use the record to understand what should happen next. It also checks the burden of maintaining it. If the fields take too long to update or do not change a decision, the design needs revision. This is an invented example, not a customer result.
05Treat data access and retention as design questions
Before importing personal information, ask your counsel and security owner which fields may be collected, who should have access, and what retention and deletion rules apply to your business. A technically available import is not sufficient reason to copy everything.
The FTC’s business guidance recommends understanding personal-data flows, limiting collection to business need and planning access, retention and disposal.2 That guidance informs these questions; it does not establish the specific obligations applicable to your organization or customers.
Use anonymous examples while testing field definitions. Keep credentials and sensitive customer records out of the worksheet below. The exercise needs a description of the information, not the information itself.
06Test the operating routine before a large migration
Try the proposed contract on a bounded set of work in an approved environment. Check whether the responsible people can maintain the fields, whether the decision maker can understand them and whether the resulting action is appropriate. Examine stale or incorrect records as well as complete ones.
The strongest objection is that definitions alone cannot repair a system that lacks required integration, permissions or reliability. That is true. A clear contract helps specify those gaps so a technical team can assess them; it does not make them disappear.
Once the routine is understandable, compare the current system’s capabilities with the requirement. That creates a firmer basis for configuration, training or replacement. Start below with the decision that would make the next management meeting more useful.
Specify one useful CRM decision
Describe fields and roles only. Do not enter customer information, credentials or private pipeline details.
No submission or account is needed. This page does not send or store your answers. Download or print them before leaving; they are not saved by this tool. Your browser or extensions may retain form data.
Sources and limits
Source pages checked 10 October 2026 UTC. The worksheets are editorial aids; they have not been validated as predictive assessments.
- UK Government · The Government Data Quality Framework. 2020-12-03. Official data-quality guidance. Operational adaptation to CRM, not certification or a statement of the reader’s legal obligations.
- US Federal Trade Commission · Protecting Personal Information: A Guide for Business. October 2016. Official business security guidance. Used to frame questions for counsel/security owner. Does not determine applicable law or a particular retention period.
Our interest
Heritage Intelligence is taking first conversations about paid CRM and systems work, so we would like you to find this problem. The decision-to-data contract is the first step and needs no software vendor or consultant, including us.
Service work, The Read included, is a separate relationship: if we become interested in buying a business we are working with, we stop that work and tell the owner plainly before any purchase discussion begins.
This article is educational. It is not individual legal, tax or investment advice, an offer or a promise of results.
Your accountant, attorney, and family make every real decision with you.