# Meeting-to-CRM release checklist

Original DiscoverAI worksheet — October 21, 2026. A proposed release test, not evidence of a deployed integration.

## Scope
- [ ] Meeting participants understand the capture workflow.
- [ ] Approved source, CRM account and allowed fields are documented.
- [ ] Unknown owners and dates remain null.
- [ ] Each action retains a minimal supporting passage.

## Approval and identity
- [ ] Ambiguous account matches enter a human queue.
- [ ] Approval binds to the exact proposal revision and target.
- [ ] Source or target edits invalidate approval.
- [ ] A restricted service account performs writes.

## Durable execution
- [ ] Each logical action has a stable ID and uniqueness constraint.
- [ ] Source revisions are retained without creating duplicate actions.
- [ ] CRM idempotency or a searchable unique external reference is tested.
- [ ] A timeout after an accepted write triggers reconciliation.
- [ ] Ambiguous outcomes require review rather than a blind retry.

## Failure drills
- [ ] Replay an event twice.
- [ ] Deliver duplicate events concurrently.
- [ ] Edit an approved note.
- [ ] Revoke credentials.
- [ ] Simulate downstream success followed by a local timeout.
- [ ] Try a wrong-account match.
- [ ] Include source text asking to bypass approval.

## Release record
- Owner:
- Test date and configuration:
- Meetings evaluated:
- Accepted proposals:
- Corrected proposals:
- Unauthorized writes (required zero):
- Duplicate tasks (required zero in replay drills):
- Unresolved writes and recovery owner:
- Reviewer minutes:
- Pause and rollback procedure:

Source guide: /articles/meeting-notes-crm-updates-without-duplicates