Trial evaluation
Decide with evidence from your real workflow, not a feature list.
The evaluation plan gradually moves from read-only review to recovery and migration exercises.
Days 1-7: visibility
Confirm discovery, status, filters, and background refresh on representative projects.
- Record indexing time and actual change counts
- Verify the interface remains usable during refresh
- Save the views you expect to reuse
Days 8-21: protection
Test backup creation, retention information, safe deletion, and conflict-aware restore.
- Use non-critical records
- Compare original and restored integrity
- Review the operation history and failure messages
Days 22-30: operational fit
Evaluate support diagnostics, handoff quality, and a controlled migration export.
- Preview redaction in the support package
- Have another person follow a handoff summary
- Document the purchase or no-purchase decision
Before day 1
Define the projects, success criteria, and non-critical records used during the evaluation.
- Record the installed build and Windows version
- Reserve space for test backups
- Decide who will review handoff and support outputs
Keep a scorecard
Measure outcomes that matter to daily operation instead of counting screens or buttons.
- Time how long it takes to locate and resume work
- Record backup growth and refresh interruption
- Note whether another person can follow the generated handoff
Respect trial safety boundaries
Use copies or non-critical records for deletion, restore, and migration exercises.
- Do not compress an active Codex database
- Verify backups before removing source data
- Keep the original migration source until import is confirmed
Finish the evaluation
Review evidence, remove unneeded test backups, and document the final decision.
- Export the scorecard and important operation results
- Deactivate or uninstall according to the selected outcome
- Retain purchase evidence only when an order is placed
Organize Codex conversations, handoffs, and backups