How should I back up work before a risky task?

Keep a recoverable copy of inputs before allowing a tool to rewrite important files. Separate original inputs, proposed outputs and reviewed deliverables so a retry cannot hide what changed.

Before you begin

A workspace determines where a teammate executes work and saves files. The environment is captured with a task, so changing a teammate later does not rewrite an earlier task. Local execution and Docker isolation have different permissions; read the selected mode before submitting real project data.

Steps

1. Copy or version the source files.
2. Specify a new output directory in the brief.
3. Request a list of changed files.
4. Review before replacing originals.

Example

For a bulk documentation cleanup, work on a branch or project copy and ask for a diff plus a summary of unresolved links.

Check the result

Restore a small sample from the backup and compare the proposed output with the original before accepting changes.

Limits and troubleshooting

Task history is not a substitute for a file backup. Files moved or deleted outside OfficeCubs can disappear from a recorded result path.