# dbt model change packet

Blank working document. Replace placeholders with your own evidence; an empty field is unknown, not a passing result.

Owner: [fill in]
Source revision: [fill in]
Environment: [fill in]
Evidence date: [fill in]

## Scope

Model/revision: ___
Grain/business rule: ___
dbt and adapter versions: ___
Disposable target schema: ___

## Fixtures

| Case | Input rows/reference | Expected rows/reference | Rule exercised |
| --- | --- | --- | --- |
| ___ | ___ | ___ | ___ |

## Execution

Parent relations prepared: ___
Selected command and tool scope: ___
Observed exit/output: not run
Objects created or replaced: ___

## Documentation

Manifest path/hash: ___
Descriptions changed: ___
Unknown column meanings: ___
Untracked/new YAML checked: ___
Domain-owner review: ___

## 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

Original worksheet: MIT. Linked resources retain their own licences and setup requirements.