Skip to content

Reopen reviewed rows only when a relevant dependency changes

Use lineage-based triggers to avoid both stale approvals and unnecessary full rechecks.

Guides

Reopen reviewed rows only when a relevant dependency changes — what should the operator record?

A previously checked table can become affected by a correction, schema change or permission change. Reopening every item wastes effort, while never reopening anything leaves stale approvals attached to altered outputs. Define dependency-based triggers so the operational review follows the inputs and rules that actually changed.

Practical operations check
Use lineage-based triggers to avoid both stale approvals and unnecessary full rechecks.
Attach input_revision, transform_revision, schema_contract and access_checked_at to each signoff so later changes can be evaluated concretely. Store only references and nonidentifying check metadata where possible; a dependency graph does not need to duplicate source excerpts in order to identify affected artifacts.
Name the checks rerun and those retained under unchanged inputs, avoiding an unsupported claim that all evidence was newly revalidated. A reapproval record should explain why retained checks remain valid under unchanged inputs, rather than presenting selective verification as though the full pipeline was rerun.
01 / Guides

List review dependencies

Attach input_revision, transform_revision, schema_contract and access_checked_at to each signoff so later changes can be evaluated concretely. Store only references and nonidentifying check metadata where possible; a dependency graph does not need to duplicate source excerpts in order to identify affected artifacts.

02 / Guides

Define trigger categories

Separate membership-changing corrections, display-only edits and permission changes; state which checks each category invalidates rather than treating all edits equally. A changed source key may invalidate joins and membership, while a corrected display caption may only affect presentation; document that distinction before an incident occurs.

03 / Guides

Test a narrow change

Use a fixture rename of a display-only column and verify only the affected schema check reopens, not unrelated source membership checks. The fixture should include an unchanged membership set, allowing the test to prove a narrow recheck decision without claiming the new name is itself a source correction.

04 / Guides

Inspect propagation

Trace a changed input through dependent outputs and ensure every affected approval is current or visibly reopened before release. Follow transitive dependencies when relevant: an aggregate derived from a corrected join can require revalidation even when its own formula text did not change.

05 / Guides

Record reapproval boundaries

Name the checks rerun and those retained under unchanged inputs, avoiding an unsupported claim that all evidence was newly revalidated. A reapproval record should explain why retained checks remain valid under unchanged inputs, rather than presenting selective verification as though the full pipeline was rerun.

Keep the boundaries clear.

  • Use lineage-based triggers to avoid both stale approvals and unnecessary full rechecks.
  • Operational record: List review dependencies. Context badges do not certify access.

Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.

Primary references

Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.

Know what social media shows about you.
Start with a question.

Get started
montage