Implement Field-Level Timestamping for Data Quality Assurance

[GigiUxR]

Problem Statement:
Currently, no way to track when specific fields (e.g., eligibility) were last updated, leading to stale or outdated listings.

Examples of what problems we need to solve by doing this?

Impact:
Volunteers do not know which listings require urgent validation.
Users may receive outdated eligibility information, reducing trust.

Solution Action-Items:

• Add field-level auto timestamping for each field in organization edit form.
• Surface timestamps in admin tools to assist with prioritization.
• Define validation cadences to ensure all data is refreshed periodically.

Related Issues

• Standardize Eligibility & Improve Discoverability for Food Seekers and Volunteers #2346
• Volunteer Validation & Training on Eligibility Rules #2347
• Improve Food Seeker Experience Through Eligibility Filtering & Tagging #2348

Success Metrics:
% of eligibility fields with timestamps after implementation

UI discussion
UI-wise, we want to somehow be able to show a 'diff'/change history (comparing previous version and current) that shows some history of changes over time. The immediate use would be so that the admin can see what fields were changed since the last publication.

This will be useful when volunteers make updates — so that admin can tell what was changed. This can also be used to look at change history. —Bryan