---
title: "Comment by Lakhyajit Changmai on \"A Status Column Is Not an Audit Trail: Designing for Accountability Across Regulated Products\" | Hashnode"
description: "The separation between “current state” and the transition evidence is a strong design point. In document workflows, I’d also be careful to audit metadata and de"
url: "https://hashnode.com/posts/a-status-column-is-not-an-audit-trail-designing-for-accountability-across-regulated-products/6af9e161b1ed162853cac5a4/comment/6afa870aa48f3ccb482cfebb"
---

[Discussion](https://hashnode.com/posts/a-status-column-is-not-an-audit-trail-designing-for-accountability-across-regulated-products/6af9e161b1ed162853cac5a4)

Comment [A Status Column Is Not an Audit Trail: Designing for Accountability Across Regulated Products](https://hashnode.com/posts/a-status-column-is-not-an-audit-trail-designing-for-accountability-across-regulated-products/6af9e161b1ed162853cac5a4)

[Lakhyajit Changmai](https://hashnode.com/@lakhyajit)

[44m ago](https://hashnode.com/posts/a-status-column-is-not-an-audit-trail-designing-for-accountability-across-regulated-products/6af9e161b1ed162853cac5a4/comment/6afa870aa48f3ccb482cfebb)

The separation between “current state” and the transition evidence is a strong design point. In document workflows, I’d also be careful to audit metadata and decision references without copying the document contents into the audit record; that keeps the evidence useful while limiting the sensitive data retained. How do you approach retention for those decision records?
