Folder archive report checklist: what to review before signoff
Use the archive report as a reviewable record of scope, file status, bytes, conversions, skips, failures, and SHA-256 values before signoff.
Safe Archive guide
Keep the copy, keep the context, and keep a record of what arrived.
Founder of ARCED Foundation, ARCED International, and Solutions of Things Lab (SoTLab). Built FolderManifest to help teams protect file integrity and stay audit-ready.
Published August 20, 2026
Scope first
Decide what you are allowed to copy before starting the archive.
Copy second
Use a destination that will remain available after access changes.
Verify last
Keep a report that names the files copied, converted, skipped, or failed.
Quick answer
Treat the archive report as part of the backup, not as a closing message. Check the approved scope, the destination, totals, copied and converted items, skipped and failed files, and the per-file SHA-256 rows before signoff.
1. Check the scope before reading the totals
A report can accurately describe a copy of the wrong folder. Start by comparing the source paths, date, and expected file set with the archive record. Note any approved exclusions before you interpret a missing item as a failure.
- Source folder or Google Drive scope
- Destination path, bucket, or Drive folder
- Archive date and owner
- Expected exclusions and file conversions
This is the difference between checking whether a tool ran and checking whether the right records were archived.
2. Read the report summary
Open _archive-report.html in the destination. Use the summary as a quick check for total files, bytes, converted items, skipped items, failures, and the final run state.
Keep _archive-report.csv with the HTML report. It gives reviewers a sortable, row-by-row record of paths, sizes, SHA-256 values, and statuses.
The summary is a starting point, not the whole review. A matching count or folder size does not explain what happened to an individual file.
3. Review every exception
- Read the failed and skipped sections first.
- Check converted Google-native files and confirm the selected output format.
- Open a sample of important destination files.
- Compare selected SHA-256 values with a fresh checksum when the review requires it.
The backup exception report guide explains how to fix and retry incomplete work. Use it before accepting a partial result.
Make the archive reviewable
FolderManifest copies the folder locally or to a supported destination, then creates a report with the files that arrived and the files that need attention.
4. Retain the report with the archive
Keep the HTML and CSV reports in the destination and record the reviewer, date, source scope, and unresolved decisions outside the report. The report should still make sense to someone who did not watch the copy run.
If the source is later retired, retain the report according to the project or records policy. Source deletion is separate from archive verification.
Frequently asked questions
Which files make up a Safe Archive report?
Safe Archive writes _archive-report.html for a readable review and _archive-report.csv for row-by-row follow-up. Both are written into the destination with the archived files.
What should I check first in an archive report?
Start with the source scope, destination, totals, and run status. Then review copied, converted, skipped, and failed items before treating the archive as complete.
Does the archive report include checksums?
Yes. Ordinary archived files are recorded with SHA-256 values. The report gives you a per-file record that can be checked again later.
Can I delete the source after the report looks clean?
The report supports the review, but source deletion is a separate retention decision. Keep the source until the owner or policy approves the next step.