The Build Sheet #3: A change without an author is a record you cannot defend

The Build Sheet. Behind the build of operational readiness.

Build Sheet #1: a status without a reason. Build Sheet #2: a date without a source. The next gap in that same record is a change without an author.

Someone updates a credential end date. Someone flips a person from active to light duty. Someone deletes a row. The cell changes. The who is missing.

Six months later that looks fine until it does not. A compliance review asks who changed the date. A grievance asks who moved someone off the recall list. A new training officer inherits a spreadsheet that “just got updated” and has no way to reconstruct the chain. The event is captured. The accountability is not.

Public safety agencies live with this in a hundred places. Status without a reason. Date without a source. Change without an author. The meaning and the custody of the record are the parts somebody will need later.

This is a working note on the record, not a ship announcement. We have not finished an authorship rule in the product yet. The hunch is simple: if a readiness-impacting field can change, the system should keep who changed it, when, and from what — even when that makes audit slightly louder than a quiet spreadsheet.

The uncomfortable version of the question: if the person who made that change left in June, can anyone still stand behind the current value?

We are building Parallax ORP to be usable by the person who inherits the system, not just the person who set it up. Status without a reason was the first hole. Date without a source was the second. Change without an author is the third one I keep running into in the same record.

If you have ever had to swear to a certification date nobody can attribute, you already know why this is next.