Provenance · 03 of 04
Document generative tools in the handover
Keep a clear production record and a named person responsible for review.
The idea
When generative tools contribute to a deliverable, record their role in the production notes.
Identify which assets or stages they affected and who reviewed the result. Agree with the client on any relevant disclosure and production requirements.
Review generated work for accuracy, suitability and the permissions relevant to its use. Check the tool's current terms and the supplied inputs rather than assuming every service grants the same rights. The responsible person still needs to make and verify the final choices. Keep the production record where the project team can find it.
How to see it
Terms used in this lesson
The parts
- Production record
- A description of how the deliverable was made.
- Reviewer
- The person responsible for checking the output.
- Scope
- The assets or stages to which a production note applies.
In practice
- Keep production notes with the project
- Identify the human reviewer
- Check relevant tool and input terms
Avoid
- Misrepresenting how work was produced
- Shipping output without review
- Assuming all generative tools share the same permissions
The test
Can the project team explain how each delivered asset was produced and who reviewed it, without reconstructing the process from memory?
Reviewed against all forty, on your product.
The audit is the cheapest thing we sell, and it regularly concludes that you do not need the project you came for.