A works council asks about November
Nobody evaluates software by asking "what does it do when something goes wrong later." The question on every demo is what it does on an ordinary Tuesday. Fair enough, but the Tuesday features are all table stakes, and it's the boring recordkeeping underneath that decides how the uncomfortable meeting goes.
So here's the uncomfortable meeting. A works council member believes November's overtime numbers were adjusted after the fact. Payroll says they weren't. Someone asks the software.
What the software can answer
If November was closed in ArbeitszeitCheck, the admin lock that finalises a month, then every correction after that lock exists as a visible correction. Not a silent edit, not a gap where a number used to be: an entry that says what changed, when, and by whom. The works council doesn't get "the numbers probably didn't change." They get the list of what changed and the names attached.
That's the entire feature, and it only exists because the correction was recorded when it happened, months before anyone thought to ask about it.
The same mechanism, three more places
We build this in a few different shapes depending on what the app is for:
TourCheck writes its attestation log as a hash-chained, append-only record. Every entry references the previous entry's hash, so rewriting history breaks the chain in a way that shows, instead of passing quietly. A guard tour log is exactly the kind of record that gets questioned after an incident, "was this round actually done at 2 a.m.?", and the chain is the difference between "yes, here's the attestation" and "the night shift says so."
InventoryCheck keeps its movement ledger append-only: receipt, issue, transfer, adjustment. Corrections are new entries, never edits to old ones, which means the stock history stays reconstructible instead of settling into whatever the last person typed.
DutyCheck freezes a roster when it's published. The snapshot is the version everyone was notified about, so "nobody told me the roster changed" has a checkable answer, and later edits can't quietly rewrite what people already saw.
Why this never appears in a demo
An audit trail earns nothing on the day it's written. It earns everything the first time someone asks "who approved this, and when", a payroll dispute, an inventory discrepancy from last quarter, a roster that changed after publication. The appended entry is then the difference between producing evidence and reconstructing a story from memory.
Which is why the engineering time goes into append-only registers instead of another dashboard widget. Dashboards get screenshotted in sales decks. Audit trails get you through the meeting where somebody's overtime is in question.
If your compliance people are the ones who'd ask that question, the DutyCheck and InventoryCheck pages show where each mechanism lives in the product.