5 / 7

Lesson · 12 min

Diligence

Disclose, document, and do the last check before it leaves you.

Diligence is the professional close: you know what Grok did, you say so when it matters, and you take the last pass. A diligence statement can be one line in a doc ('Drafted with Grok; figures checked against the Q2 export'). In a class, it may be required. In a regulated shop, it may be policy. Even when it is not, it is how you stay honest with future-you.

  • Keep the prompt and the source next to the deliverable when the work is serious.
  • Do not paste secrets. Do not paste customer PII 'just this once.'
  • If Grok wrote code, you still run it. If it wrote a number, you still recompute it.
  • Credit people. Grok is not a co-author; it is a tool. Humans stay on the byline.