Topic: Data-integrity

Found 14 entries.

• NULL Is Not a Value, It Is an Excuse

  A blank database cell is a legal liability. We must abandon the NULL value and adopt explicit states to preserve our evidentiary chain.

• How to Hand Over a Project in One File Without Losing Relationships

  Exporting disconnected flat files destroys the chain of custody. We must package related data into a single database file to preserve evidence.

• Time Is Evidence. Not Decoration.

  A date on a document is a legal claim. Learn why local timezones create liability and why UTC is the only timeline that matters.

• “We Support CSV” and Other Comfortable Lies

  A spreadsheet is not a database. Why accepting a simple CSV export is a failure of duty that leaves the municipality with no audit trail and no legal defense.

• Two Crews, One Asset, Two Different Answers

  Offline work creates data conflicts. Crew A fixes the pump. Crew B logs it as broken. Who is right? We need conflict resolution that respects the timeline.

• ISO 8601 or It Did Not Happen

  Why '03/04/2026' is a legal liability, and why we must standardize on YYYY-MM-DD to protect the integrity of our data.

• The Fix: A Clean Document Trail Without Manual Re-Entry

  Manual re-entry of data is the fastest way to destroy trust. A $10 typo looks like fraud to an auditor. We implement a 'Source-First' protocol where data is captured, not typed.

• “Real-Time Cash Visibility” Is Often Just a Pretty Screen

  That colorful dashboard on your wall is lying to you. It shows accruals, not cash. Here is why 'Real-Time' is a marketing term, not a bank balance.

• The Rant: Manual Data Entry Is a Compliance Risk Wearing a Friendly Smile

  The clipboard is the enemy of the audit trail. Why relying on human copy-paste workflows introduces unavoidable error and liability.

• Stop “Fixing” Data by Hand: Why Your Manual Overwrites Are Creating a Black Hole

  A tiny manual tweak feels harmless, but it destroys the audit trail. We explore why 'hard-coding' corrections creates a future mystery that no one can solve.

• My Rant About Screenshots as Evidence: They Are Not Records

  A screenshot is a picture of a claim, not proof of a fact. To an auditor, a PNG file is unverifiable noise. We demand the source export.

• Daylight Saving Time Is Not a Feature. It Is an Ambush.

  Why the bi-annual clock change is a threat to data integrity, and how to prevent 'The Phantom Hour' from corrupting your payroll and logs.

• Sync Failed, Friday Afternoon

  Silence is dangerous. When an app doesn't tell you the sync failed, you find out on Monday morning. We need loud, visual status indicators.

• The Timezone Checklist for Forms, Spreadsheets, and PDFs

  A practical guide to stopping time-based data corruption. Use this checklist before you design your next form or report.