1.6 Documented AI Usage: The First Standard

In professional environments, AI use does not end with the output — it ends with the documentation. Whoever fails to record where and how AI entered a piece of work makes that work unverifiable for everyone else. This chapter establishes documentation as a basic habit.

Why we document AI usage

(Contributed by Prof. Inwah Kim)

1. Transparency and Accountability — Documenting AI use makes the creation process clear and builds trust.
   • Disclose where AI was used
   • Explain how AI contributed
   • Clarify human review and final responsibility
2. Responsible and Policy-Compliant Use — Documentation helps ensure that AI is used ethically and in accordance with organizational policies.
   • Acknowledge AI assistance when required
   • Respect copyright and licensing
   • Follow institutional or workplace AI policies
3. Team Collaboration and Knowledge Sharing — Well-documented AI workflows make it easier for others to understand, reproduce, and improve the work.
   • Enable others to reproduce results
   • Share effective prompts and workflows
   • Support smoother collaboration and handoffs

Two additions connect this to the rest of the course. First, error diagnosis: Chapter 1.2 showed that AI errors are structural. When an error surfaces downstream, documentation decides whether its source can be reconstructed — which model, which prompt, which verification step. The principle is familiar from software development: a codebase without documentation is nearly worthless to successors, and the same logic applies to AI-assisted work products. Second, the regulatory link: Article 4 demands documented competence measures, and the transparency obligations of the AI Act (Art. 50, applicable from 2 August 2026) require labeling AI-generated content in certain cases; universities, likewise, increasingly require disclosure of AI tools in examination regulations.

Why documentation matters in real-world AI applications

One of the most common requirements I see across client AI initiatives is the need for documentation and auditability.

Organizations want a clear record of how AI was used, what information was generated etc. This documentation creates transparency and enables effective review processes.

At this stage of AI development, organizations should not place complete trust in AI-generated outputs. Human review and approval processes remain critical. Maintaining logs and documentation provides a clear audit trail, allowing teams to trace recommendations back to their source, assess decision quality, and improve governance over time.

For most enterprise AI deployments, auditability is not just a best practice — it is a standard requirement.

How to document: the minimum standard

For a start, a five-field standard suffices — one line per use, kept in a document appendix, a commit message, or a usage log:

• Tool and model: e.g., "Claude (Anthropic), web search enabled."
• Date of use: relevant because of model updates and knowledge cutoffs.
• Task: What was the tool used for? ("First draft of the summary," "rephrasing of Section 3," "research starting points.")
• Extent of adoption: taken over unchanged, edited, or used as idea generator only.
• Verification performed: Which claims were validated against which sources? (The direct link to output validation from Chapter 1.2.)

Two boundary lines sharpen the standard. Not subject to documentation, as a rule, is trivial use without substantive influence — spell-checking, formatting help. Subject to documentation is everything that shaped the content, structure, or conclusions of a work product. In doubt: document. A superfluous line costs seconds; a missing one can devalue an entire piece of work.