Separate preparer and checker for a table release — what should the operator record?
An operator who built a transformation can miss the same assumption when reviewing it. A separate checker can focus on the declared contract and actual output. This is a local control for operational reliability, not a guarantee of source truth or a reason to share evidence beyond existing roles.
Require an independent operational check of membership and schema before handoff.
Record prepared_by_role and checked_by_role with artifact_revision, keeping both within the permitted access scope for the evidence. If the team cannot supply an authorized independent checker, mark that gate unverified rather than assigning a nominal reviewer who cannot inspect the required artifact.
State exactly which contract checks passed, naming unchecked dimensions so the independent review is not mistaken for universal factual certification. Keep checker signoff scoped to exact bytes or artifact revision, so subsequent edits cannot inherit approval simply because the document title remains the same.Identify the two roles
Record prepared_by_role and checked_by_role with artifact_revision, keeping both within the permitted access scope for the evidence. If the team cannot supply an authorized independent checker, mark that gate unverified rather than assigning a nominal reviewer who cannot inspect the required artifact.
Choose checkable assertions
Require the checker to verify qualified keys, required columns and visible exception states against the transformation contract rather than endorse the overall research conclusion. The checklist can name required_columns_present, qualified_keys_unique and exceptions_visible; each assertion should have a concrete pass, fail or unavailable result for this revision.
Run an independent comparison
Have the checker calculate membership differences from the declared input reference, not simply inspect the preparer's summary totals. Independent recomputation is more useful than confirming a screenshot's totals, especially when equal counts can hide one missing key and one unexpected extra key.
Resolve divergent findings
Keep any disagreement as an open operational item with the conflicting validation outputs until the owner approves a corrected revision or documented limitation. A disagreement about source interpretation may lie outside this gate; route it separately instead of forcing an operational checker to certify a substantive research conclusion.
Record the bounded signoff
State exactly which contract checks passed, naming unchecked dimensions so the independent review is not mistaken for universal factual certification. Keep checker signoff scoped to exact bytes or artifact revision, so subsequent edits cannot inherit approval simply because the document title remains the same.
Keep the boundaries clear.
- Require an independent operational check of membership and schema before handoff.
- Operational record: Identify the two roles. 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.