One list, two exports: a CSV file and a Google Sheet.
The archive preserves both files with the same date. It does not need to expose the rows, names, or values to document what happened.
A CSV is useful because it is plain and portable. It can move between systems, be inspected as text, and serve as an input to another process. A spreadsheet is useful because it is easier to review, sort, annotate, and share with the people doing the work.
Keeping both versions created a simple handoff. The CSV represented the export as produced. The sheet made the same working material easier to examine in a browser.
The first check was structural. Column names needed to survive the conversion. Dates and other values needed to keep their intended meaning. Empty cells could not quietly shift the remaining fields into the wrong columns.
The second check was practical. A person opening the sheet needed to see a recognizable table rather than a raw file that required another tool or explanation. That did not require changing the underlying information.
Exports are ordinary operational artifacts. They often sit between a product and the next piece of work. Their value comes from being predictable enough that the recipient can use them without reconstructing how they were created.
The contents of this list remain private. The public record includes only the date, the paired file types, and the fact that the export became a reviewable spreadsheet.
This was also a useful archive boundary. The CSV and the sheet preserve the same event in different forms. One is closer to a machine-readable transfer. The other is closer to the way people inspect and coordinate around a list.
Both exports were created and kept together. The files show a small data operation completed at the end of the month without revealing the people or information inside it.