The short answer
Freeze source schedules and subscriptions, map each report definition, parameters, cadence, timezone, recipient role, format, and access method to the target, assign every boundary occurrence to source, target, intentional skip, or manual replacement, then reconcile generated artifact identity and per-recipient send, delivery, bounce, access, and supersession evidence before retiring the source schedule.
Operational checklist
Mark your progress, then save a working copy. Selections reset when you leave this page. A checked box is not an approval or evidence of completion.
0 of 8 marked
Key takeaways
Build a source-to-target subscription crosswalk
Record source/target schedule IDs, report definition/version, parameters, property/entity scope, timezone, cadence, next run, output format, attachment/link mode, recipients or role query, owner, and activation/deactivation boundary.
Minimize recipient data and preserve restricted exports appropriately.
Reconcile each boundary occurrence
| Layer | Expected evidence | Exception | Disposition |
|---|---|---|---|
| Generation | One intended artifact/version | Missing, duplicate, wrong parameters | Regenerate or hold |
| Audience | Resolved authorized recipients | Missing/excess/stale role | Correct subscription/permissions |
| Transport | Provider send/delivery/bounce event | Rejected, delayed, unknown | Retry under policy or alternate channel |
| Access | Authorized recipient can open intended version | Broken link or overbroad access | Contain and correct |
Do not overstate provider events
Provider send evidence means the provider accepted a send request; delivery evidence has the provider’s documented meaning. Neither proves the human opened, understood, or acted on the report. Track required acknowledgment separately.
Amazon SES documentation illustrates provider-specific event types, batching, and ordering limits. Verify the actual delivery provider contract.
Close with one intended report, authorized audience, and supported outcome per occurrence
Name the population, cutoff, evidence version, owner, decision, unresolved exceptions, next checkpoint, and downstream records updated. Preserve the earlier state rather than replacing it with a clean current screen.
Reopen the record when a late event, changed source, new affected item, or downstream consequence invalidates the signed conclusion.
Edge cases
Sources and references
Follow each source to check the underlying claim. Access checks and professional review are different steps.