---
title: "Comment by Azhar Abbas on \"A Status Column Is Not an Audit Trail: Designing for Accountability Across Regulated Products\" | Hashnode"
description: "A status history is what makes a regulated workflow explainable. The actor, timestamp, prior value, and reason for each transition seem just as important as the"
url: "https://hashnode.com/posts/a-status-column-is-not-an-audit-trail-designing-for-accountability-across-regulated-products/6af9e161b1ed162853cac5a4/comment/6af9e814a8d9c171e0704dc3"
---

[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)

[Azhar Abbas](https://hashnode.com/@azharabbas)

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

A status history is what makes a regulated workflow explainable. The actor, timestamp, prior value, and reason for each transition seem just as important as the final state.
