When a workflow changes, what should happen to its old records?
by•
When a team revises a recurring process, the new version usually makes the next run clearer. But it can make last month’s records hard to read: a question has been renamed, split into two, or removed altogether.
I’ve found that treating history as something to preserve, not merely migrate, makes later reviews more honest. It forces you to distinguish what was observed then from how you would ask it now.
How have you kept historical records useful after changing a workflow, without freezing the workflow in place?
2 views
Replies
Old records should stay exactly as they were when they were created. Changing history can make audits and past invoices confusing. New workflows should apply only to future records.