What does an edit-history test need to show?
Define the content type and the change you want to observe. A text edit, a replaced image and a changed link preview are different test cases. Ask which changes the platform exposes and which the archive can retain. Do not treat a successful text edit as proof of every kind of version history, or assume an archive can retrieve a version that was never captured.
Work through a realistic example
On an approved test account, publish a harmless notice saying a meeting begins at 10 and later change it to 11. Record both actions independently. Ask a reviewer to identify the available versions, explain their timestamps and determine which version a captured reply relates to. Keep the test distinct from any real public notice.
Run the workflow
- Agree a safe sample, supported edit operation and expected observation window with the account owner and vendor. Record the original item identifier and wording.
- Make the approved change and inspect the archive after the expected capture interval. Distinguish source publication, source modification and archive capture times when available.
- Export the sample and ask a second reviewer to reconstruct the change. Document missing fields, ambiguous ordering and unsupported operations.
Check the evidence
| Check | What to verify | Evidence to keep |
|---|---|---|
| Version identity | Earlier and later representations are distinguishable. | Identifiers and available timestamps. |
| Change context | The reviewer can explain what changed. | Side-by-side review or change record. |
| Export fidelity | Version relationships survive outside the application. | Independent package review. |
Record the decision and its limits
Record the exact operation that passed and the limitations that remain. Repeat the relevant check when the platform, account permissions or archiving integration changes. Keep the source-action log with the exported evidence.
Keep in mind: A current version is not evidence that all prior versions were retained. Describe a missing earlier version as a gap to investigate, not as proof that the content never existed.
Further reading and scope
Reviewed October 14, 2026. These practical exercises are editorial guidance, not a guarantee of platform coverage or a substitute for your approved records policy.
- NARA: social media capture practices — Background on capture and metadata; the test exercises above are Brolly editorial workflows.
Common questions
Can an archive recover an edit made before connection?
Only if the relevant historical data is available through the supported source and collection method. Confirm the actual lookback rather than promising recovery.
Are all timestamps interchangeable?
No. Publication, modification, capture and export can represent different events. Ask for definitions and preserve the time-zone information.
Put the guide to work
Use the downloadable workbook to record your requirements, test results and questions for shortlisted providers.