# CRM validation test sheet

Ops Automators | Updated September 7, 2026

Use synthetic records in a sandbox. Record expected values before running tests; do not accept matching counts as proof of correct relationships.

Guide: https://www.opsautomators.com/guides/crm-automation

## Worked example

| Case | Source record | Change | Expected destination behavior | Actual result | Owner | Evidence |
| --- | --- | --- | --- | --- | --- | --- |
| Duplicate event | Account A-104 | Replay identical update | Same destination record; no duplicate |  |  |  |
| Omitted field | Account A-104 | Address absent | Preserve verified destination address |  |  |  |
| Conflicting edit | Account A-104 | Both systems change name | Apply documented ownership or review |  |  |  |
| Deletion | Account A-104 | Record removed | Follow deletion policy; no silent recreation |  |  |  |

## Blank brief

### Case

[Complete this field.]

### Source record

[Complete this field.]

### Change

[Complete this field.]

### Expected destination behavior

[Complete this field.]

### Actual result

[Complete this field.]

### Owner

[Complete this field.]

### Evidence

[Complete this field.]


## Acceptance

- Owner:
- Date:
- Evidence:
- Open decisions: