intermediate / August 2026

CRM Retention and Correction Checks Quiz

CRM records age, change, and sometimes get challenged by the people they describe. Review retention, correction, restriction, erasure, stale records, and shared-data follow-up before cleanup.

Before you start

Start a 10-question practice round.

Sign in before starting if you want a leaderboard score.

New

Sign in to get ranked
Questions
10
Time limit
7 min
Scoring
First signed-in attempt counts
Edition
August 2026

What this quiz checks

Handle stale or challenged CRM records clearly

CRM retention QACorrection request triageRestriction handlingErasure readinessShared-data follow-up
  • Keep Data Only While It Has A PurposeRetention Checks start by asking what personal data is held, why it is still needed, and when it should be erased or anonymised.
  • Correct Facts Before They Drive WorkWhen a person challenges CRM data, the team needs to check the evidence and avoid using disputed facts as if they were settled.
  • Restrict Or Erase With CareSome disputed or no-longer-needed records need processing limits before the final correction or erasure decision is complete.

Study first

Review the ideas behind the questions

Review how to handle CRM records that are stale, challenged, or no longer needed. Focus on the purpose for keeping the data, whether the facts are accurate, whether processing should pause, and whether shared recipients need follow-up.

Keep Data Only While It Has A Purpose

Retention Checks start by asking what personal data is held, why it is still needed, and when it should be erased or anonymised.

  • Personal data must not be kept for longer than it is needed for the purpose.
  • Retention periods should be justified and documented wherever possible.
  • Old CRM data should be reviewed and erased or anonymised when it is no longer needed.

In Practice

Ask Why The Record Still Exists

A stale contact should not stay in the CRM just because storage is cheap. Name the active purpose or move it into a deletion or anonymisation review.

Use A Retention Schedule

A retention schedule gives marketers and sales operations a shared rule for record categories, expected use, and review timing.

Common mistakes

  • Keeping old leads forever because they might be useful someday.

    Keep personal data only while there is a justified purpose, then erase or anonymise it when it is no longer needed.

Q&A

Does UK GDPR set one fixed CRM retention period?

No. The retention period depends on why the organisation needs the data, and the organisation should justify and document that period.

What should happen to personal data the CRM no longer needs?

It should be reviewed and erased or anonymised when it no longer supports a justified purpose.

Correct Facts Before They Drive Work

When a person challenges CRM data, the team needs to check the evidence and avoid using disputed facts as if they were settled.

  • Individuals have the right to have inaccurate personal data corrected, or completed if it is incomplete.
  • A rectification request can be made verbally or in writing and needs a response within one calendar month.
  • The team should consider the person's arguments and evidence before deciding whether CRM data is accurate.

In Practice

Record Corrections Clearly

If a mistake affected prior follow-up, the CRM may need to show both what happened and the correction so later teams do not repeat the wrong action.

Use The Data Purpose To Set Effort

More important CRM decisions deserve stronger checking. A disputed field used for account status, priority routing, or eligibility needs more care than a harmless display note.

Common mistakes

  • Treating a phone call correction request as informal feedback that can wait.

    Recognise verbal correction requests and route them through the same response process as written requests.

Q&A

Should a CRM correction request require a specific legal phrase?

No. A request can be verbal or written, so teams need a process to recognise and record it.

Restrict Or Erase With Care

Some disputed or no-longer-needed records need processing limits before the final correction or erasure decision is complete.

  • When processing is restricted, personal data may be stored but not used.
  • Restriction can apply while the organisation verifies the accuracy of challenged personal data.
  • Erasure can apply when personal data is no longer necessary for the original purpose.

In Practice

Pause Use During A Dispute

If a person disputes a key account-status field, store the record while the team checks it, but do not use that disputed field for routing until the issue is resolved.

Notify Shared Recipients When Needed

If inaccurate or erased CRM data was already shared with another organisation, the follow-up plan should include recipient notification unless an exception applies.

Common mistakes

  • Using a disputed CRM field for routing while the team checks whether it is accurate.

    Restrict use of the disputed personal data while its accuracy is being verified, especially if it would drive routing or outreach.

Q&A

What does restriction mean for a disputed CRM record?

The data can be stored, but the disputed personal data should not be used while the restriction applies.

When can an erasure request matter for old CRM records?

It can matter when the personal data is no longer necessary for the purpose it was originally collected or processed for.

Question quality

Reviewed before publishing

Reviewed by
Aniruddh Sharma
Last checked
August 22, 2026

Checked against ICO and GOV.UK guidance because this quiz tests portable CRM retention, correction, restriction, and erasure QA rather than a specific CRM vendor's audit-log or record-management UI.

The source pages for this edition were checked as part of the same review. Official product docs are linked where available.

Sources

Sources used for this quiz

These pages support the quiz content and study notes.