DATA ENGINEERING · GOVERNANCE BRIEF
Data flow change review worksheet
A completed fictional example, then a blank grid to print or copy for one specific flow. This worksheet shows what must be checked, by whom, and where to find the evidence; it does not replace test results.
2-page worksheet: page 1, completed fictional example; page 2, 13 fields to fill in directly in the PDF. Typed text is kept when you save.
Completed example (fictional)
| Item | Fictional example: invoice_total |
|---|---|
| Flow concerned | invoice_total: invoicing application to the financial monitoring dashboard and the collections export. |
| Change lead | One person leads the transition and knows which points remain open. |
| Definition and grain | Total invoice amount including VAT, one invoice per record. |
| Unit, currency, version: before | Euros, currency EUR: 48.50 for an invoice of €48.50; current version. |
| Unit, currency, version: after | Euro cents, currency EUR: 4850 (4850 = €48.50); explicit version received and effective date. |
| Consumers and owners | Financial monitoring dashboard; collections export. One owner per consumer; integration team for the transformation; the owner of the invoicing application confirms the new representation. |
| Checks and evidence | Invoice €48.50, credit note -€12.00, zero amount, missing unit or unknown version, batch total with documented rounding, replay without duplicates. Evidence: input, version, expected and observed result in each consumer. |
| Transition, history, removal | Coordinated cutover or coexistence with an explicit-unit field or version and a migration schedule; handling of historical invoices; removal when no consumer depends on the old version any more. |
| Response and recovery | Batch concerned, outputs to suspend, action that stops propagation and who triggers it, correction without duplicates, post-deployment check. |
| Decision | Go-ahead only if every consumer has an owner, an expected unit and identified evidence. |
| Approvers and roles | Owner of the source application; integration team; owner of each use; transition lead. |
| Date | Review date, effective date of the new version, post-deployment checkpoint (fictional example: no real date). |
| Reservations | A file that is exported and then reworked by hand can escape the technical map: check it before the cutover. |
Blank grid
| Item | Your flow |
|---|---|
| Flow concerned | |
| Change lead | |
| Definition and grain | |
| Unit, currency, version: before | |
| Unit, currency, version: after | |
| Consumers and owners | |
| Checks and evidence | |
| Transition, history, removal | |
| Response and recovery | |
| Decision | |
| Approvers and roles | |
| Date | |
| Reservations |