Case 05

Executive Communication

Complex Issue

Several teams have reported inconsistent client information across CRM, onboarding records, and service request systems. The issue appears to be linked to duplicate client records created over time when clients used different identifiers, relationship managers changed teams, or onboarding data was amended after account opening.

A preliminary review found 1,240 potential duplicate record pairs across the active client base. Roughly 320 pairs appear high confidence based on name, date of birth, contact details, and internal identifiers. Another 580 pairs require human review. The remaining 340 are low confidence and may include family members, companies with similar names, or legitimate separate entities.

There are three possible paths: do nothing and continue manual reconciliation; run a one-time clean-up for high-confidence duplicates only; or create an ongoing data quality process with ownership, exception review, and monthly duplicate monitoring.

Prompt

Turn this complex issue into clear executive communication.

First, summarise it in plain English. Then convert it into a simple “what, so what, now what” structure.

Include:
- Key points
- Business impact
- Decision needed
- Risks
- Recommended next step
- 3-minute briefing version for a business head
- Short Teams update version
- 5-slide presentation outline with slide titles, key messages, suggested visuals, and speaker notes

Avoid unnecessary technical detail. Focus on decisions, impact, and action.

Example output from ChatGPT

Executive Briefing: Client Data Inconsistency and Duplicate Records

Decision required

Preliminary assessment | Client data quality

1. Plain-English summary

We have a client data consistency problem. The same client may appear under different records across CRM, onboarding, and service systems, sometimes with conflicting information.

An initial review identified 1,240 potential duplicate record pairs, of which 320 are high-confidence matches. These issues may lead to wasted staff effort, inconsistent client servicing, and potentially incorrect decisions based on incomplete client information.

We can continue fixing records manually, run a one-time clean-up, or establish an ongoing process to identify, verify, and resolve duplicates.

Recommendation: Establish an ongoing data quality process, beginning with controlled validation of the 320 high-confidence pairs. Assign clear ownership, introduce exception reviews, and monitor duplicates monthly.

This addresses the immediate problem while reducing the likelihood of it recurring.

2. What, so what, now what

WHAT – We have inconsistent client records

Three systems contain potentially duplicated or conflicting client information. The initial review identified 1,240 potential duplicate pairs with varying confidence levels.

SO WHAT – This affects servicing, efficiency, and control

Staff may spend unnecessary time reconciling records. Relationship managers may work from incomplete information, and incorrect consolidation could create client, privacy, or operational risks.

NOW WHAT – Fix the problem and establish ownership

Approve a phased remediation programme: validate high-confidence matches first, review exceptions, assign accountable owners, and introduce recurring monitoring.

3. Key points and evidence

Potential pairs

1,240

Require assessment

High confidence

320

Initial priority

Require further review

920

Medium and low confidence

Potential duplicate pairs by confidence

Preliminary identification, not confirmed duplicate client counts.

0200400600800HighMediumLow

These are record pairs, not necessarily 1,240 unique clients or confirmed duplicates. One record may appear in multiple pairs.

The underlying causes appear to include changing client identifiers, RM transfers, and post-onboarding updates. These are preliminary explanations, not yet verified root causes.

4. Business impact and key risks

AreaPotential business impactRisk
Client experienceDifferent teams may see different client informationHigh
Operational efficiencyRepeated manual checks and reconciliationHigh
RM productivityTime spent investigating inconsistencies rather than servicing clientsMedium
Risk and complianceIncorrect client information may affect onboarding, controls, or reportingHigh
Data integrityIncorrectly merging family members or legitimate separate entitiesHigh

Risk levels are preliminary judgments based on potential impact, not measured exposure. Actual incident rates, financial impact, and affected client counts have not yet been established.

5. Decision needed from leadership

Approve Option 3: A phased, ongoing data quality process, subject to confirming resource requirements and safeguards.

OptionBenefitLimitationAssessment
1. Continue manual reconciliationNo immediate programme investmentRecurring effort and unresolved inconsistenciesNot recommended
2. One-time clean-upAddresses known high-confidence casesNew duplicates can continue accumulatingPartial solution
3. Ongoing processAddresses existing cases and future recurrenceRequires clear ownership and recurring capacityRecommended

Leadership needs to decide whether to sponsor the programme, nominate an accountable business owner, and authorise a short validation phase before wider remediation.

Recommended next step

  1. Appoint a business data owner accountable for client record consistency across the three systems.
  2. Run a proposed two-week validation phase on the 320 high-confidence pairs, including checks for false positives and downstream dependencies.
  3. Establish a controlled review queue for the 580 medium-confidence pairs and define when low-confidence cases need investigation.
  4. Return to leadership with validated findings: actual duplicates, remediation effort, proposed controls, resource requirements, and monthly monitoring measures.

No automatic merging or deletion should occur solely on the basis of preliminary match confidence.

6. Three-minute briefing for a business head

Ready-to-deliver speaking script | Approximately 3 minutes at a measured pace

Opening – 30 seconds

What

We have identified a client information consistency issue across our CRM, onboarding, and service request systems.

Our initial review found 1,240 potential duplicate record pairs. Of these, 320 appear to be strong matches, while the remaining 920 require further assessment.

The likely causes include historical changes in client identifiers, movement of relationship managers between teams, and updates made after onboarding.

Business implications – 45 seconds

So what

This matters because the quality of our client information directly affects how effectively we serve clients and manage risk.

When information differs across systems, teams spend time manually reconciling records. Relationship managers may not have a complete view of the client, and operational staff may be relying on different versions of the same information.

There is also a control risk. Incorrect client consolidation could create additional problems, especially when dealing with related individuals, family accounts, or separate legal entities.

We have identified the exposure, but we still need to quantify its actual business impact.

Options – 45 seconds

Choices

We have three choices.

First, we could continue reconciling records manually. This avoids immediate project investment but leaves the recurring issue unresolved.

Second, we could clean up the strongest duplicate candidates. That would improve the current position but would not stop new duplicates from appearing.

Third, we could create a sustainable data quality process that combines controlled clean-up, clear ownership, exception management, and ongoing monitoring.

My recommendation is the third approach, delivered in phases.

Proposed action – 40 seconds

Now what

We should start by validating the 320 high-confidence pairs, without automatically merging anything.

In parallel, we should nominate an accountable business owner and agree on review and escalation rules.

This would give us a reliable baseline for the size of the issue, the resources required, and the controls we need going forward.

We can then introduce a monthly review of new duplicate candidates, outstanding exceptions, and remediation progress.

Decision request – 20 seconds

Ask

What I am seeking today is approval to proceed with a short validation phase, nominate a business owner, and return with a costed remediation proposal.

The objective is not simply to clean up records. It is to establish a reliable client information foundation that stays reliable.

7. Short Teams update

Client Data Quality – Initial Findings & Proposed Action

Our preliminary review identified 1,240 potential duplicate client record pairs across CRM, onboarding, and service systems.

  • 320 high-confidence potential matches
  • 580 require further review
  • 340 low-confidence matches, potentially legitimate separate entities

Business impact: Inconsistent client information creates manual reconciliation work, servicing inefficiencies, and potential operational and control risks.

Recommendation: Move beyond one-time clean-up and establish an ongoing data quality process, starting with controlled validation of the 320 high-confidence pairs.

Decision needed: Approval for an initial validation phase and nomination of an accountable business owner.

Next step: Confirm the actual duplicates, remediation effort, safeguards, and ongoing monitoring requirements before full implementation.

8. Five-slide executive presentation outline

SLIDE 1

One Client. Multiple Records. Inconsistent Information.

Key message: Client information differs across three systems, affecting the reliability of our client view.

Visual: Three systems feeding different records into one client profile.

Speaker notes: Explain the issue and likely contributing factors. Emphasise that the problem spans systems and ownership, not just record matching.

SLIDE 2

1,240 Potential Duplicate Pairs → 320 Initial Priorities

Key message: We have identified a measurable problem, but the findings need validation.

Visual: Stacked horizontal bar showing 320 high, 580 medium, and 340 low-confidence pairs.

Speaker notes: Distinguish potential duplicates from confirmed duplicates. Explain that the first wave focuses on the strongest candidates.

SLIDE 3

Why It Matters: Client Experience, Efficiency, and Risk

Key message: Inaccurate or fragmented client information can create real operational and control exposure.

Visual: Three impact pillars – Client Experience, Operational Efficiency, Risk & Controls.

Speaker notes: Use practical examples of manual reconciliation and incomplete client views. Acknowledge that actual impact has not yet been quantified.

SLIDE 4

Three Options. One Sustainable Direction.

Key message: Ongoing ownership and controls offer a more sustainable solution than repeated manual fixes.

Visual: Three-option comparison – Manual Reconciliation / One-Time Clean-up / Ongoing Data Quality, with the third highlighted.

Speaker notes: Position the recommended approach as staged rather than a large upfront transformation. Explain the trade-off between immediate effort and recurring issues.

SLIDE 5

Decision Required: Approve Validation and Assign Ownership

Key message: Start with evidence and safeguards before committing to full remediation.

Visual: Three-phase roadmap – Validate → Remediate → Monitor, with a decision gate after validation.

Speaker notes: Request approval for the initial phase and nomination of a business owner. State that costs, timelines, and downstream changes will be brought back for approval after validation.

9. Questions leadership may ask

Likely questionRecommended response
How many clients are actually affected?We have 1,240 potential record pairs, not a validated count of affected clients.
Has this caused any client incidents?We have not yet established the incident or financial impact. This is part of validation.
Why can't we simply merge the 320 pairs?High confidence is not certainty. An incorrect merge could combine separate clients or legal entities.
Why do we need an ongoing process?A one-time clean-up does not address how new duplicates are created or who owns resolution.
How much will this cost?We need validation results and resource estimates before presenting a reliable cost.
How will we measure success?Confirmed duplicates resolved, outstanding exceptions, resolution time, new duplicate rate, and associated servicing errors.

Executive takeaway

The strategic decision is not whether to clean up 320 records. It is whether we want to keep reconciling inconsistent client information or establish a controlled process that addresses the issue at its source.

My recommended leadership ask is narrow and actionable: approve validation, assign ownership, and require a costed remediation plan with defined controls before full rollout.