You could handle that with an audit log (there's some standard ways to do this in SQL databases). And then expose that in the admin interface via the low code tools (which have SQL-to-UI builders).
Here's an example of an audit log I put together for an in app activity feed (in Postgres):
Thanks i appreciate the help. We'll take a look at it. Realistically it's probably too much lift to do all this directly. Key benefits of django-simple-history are single line add to other tables/models as well as reifying historical items.