Skip to content
Skip to main content
First Response & Preservation Operational Explainer

What should be preserved from cloud version history?

Preserve the full ordered version list, identifiers, timestamps, named editors, labels and retention limits without restoring, renaming or deleting anything.

Record current object before history

Capture service, account, document ID, current version and time. If history is opened, note timezone, size, named and automatic versions, restored status and completeness or filtering.

Earlier versions may retain deleted content, filenames, owners, comments and different timestamps.

Interpret system labels narrowly

Do not download or restore simply to inspect; those actions create audit events and change current state. Seek provider preservation for central native history.

A named editor may represent shared credentials, automation or delegation rather than the human who made each change.

Key takeaway

Preserve version history as an ordered provider record and avoid restoration or attribution claims beyond what its identifiers support.

Reference: FRP-130First Response & Preservation