# Test and document a dbt model change — acceptance checklist

Record evidence for every checked item. Unchecked or untested is not a pass. This checklist does not execute an integration or authorise external actions.

## Required inputs

- [ ] A dbt SQL model, relevant refs/sources and a fixed project revision.

- [ ] Supported dbt/adapter versions and an isolated development schema with prepared parent relations.

## Output checks

- [ ] The target schema is isolated from retained production relations.

- [ ] Expected rows are derived independently of the implementation.

- [ ] All new and modified YAML files are included in review.

- [ ] Documentation states the model grain and preserves unresolved column meanings.

## Deliverables

- [ ] Business-rule fixtures

- [ ] Unit-test YAML and expected rows

- [ ] Model/column documentation diff

- [ ] Development execution receipt

## Evidence and decision

Evidence links: [fill in]
Untested paths: [fill in]
Unresolved findings: [fill in]
Reviewer: [fill in]
Decision and scope: [fill in]

## Boundaries

- Do not run --empty against relations that must be retained; dbt build/run and enabled MCP tools can replace warehouse objects or trigger jobs.

- Documentation coverage counts declared manifest columns with nonempty descriptions, not every physical column or semantic correctness. Platform features have separate credentials and entitlements.

Workflow: https://undominated.ai/workflows/#test-and-document-a-dbt-model