---
id: ADR-CRM-DQ-018
title: Treat merge plans as shared expiring work
product_area: crm
module: data-quality
revision: 1
status: proposed
design_intent: open
source_sha:
  services-crm: a8d1364f1dd44b723bb5f9acba12f983e9ec8d69
decision: >-
  Current plans are shared with qualified workspace administrators, record
  attributed answers, expire at their stored instant and remain retained after
  settlement.
constrains:
  - DOM-CRM-DQ-003
  - STATE-CRM-DQ-004
  - WF-CRM-DQ-005
  - WF-CRM-DQ-007
  - SVC-CRM-DQ-merges
origin: OQ-CRM-DQ-001 (open); FND-CRM-DQ-006; FND-CRM-DQ-041
alternatives:
  - option: Limit changes to the creator
    why_not: >-
      This prevents direct handover; Product has not resolved the competing
      access choices.
  - option: Delete settled plans after seven days
    why_not: >-
      The documented cleanup is absent and needs an explicit retention
      implementation.
consequences:
  - Colleagues can edit plans and refresh their approval boundary.
  - Settled plans retain working snapshots of personal information.
  - >-
    Current expiry counts from creation rather than the approved last-change
    rule.
supersedes: []
evidence:
  - >-
    services-crm at a8d1364f: modules/merges/aws/api/merges.routes.ts
    (requireAccessToPlan); services/persistence/record-merge-plans.ts.
---

# Treat merge plans as shared expiring work

## Context

Current workspace access and retention differ from the documented creator-only design.

## Decision

Current plans are shared with qualified workspace administrators, record attributed answers, expire at their stored instant and remain retained after settlement.

## Alternatives Considered

Limit changes to the creator. This prevents direct handover; Product has not resolved the competing access choices.

Delete settled plans after seven days. The documented cleanup is absent and needs an explicit retention implementation.

## Consequences

Colleagues can edit plans and refresh their approval boundary. Settled plans retain working snapshots of personal information. Current expiry counts from creation rather than the approved last-change rule.