Use run history
Project history lists analyses over time, including their status, capability, requirement revision, and creation date. Open an older run to review the report that existed for that exact evidence and configuration.
What creates a revision
- Correcting or expanding an approved requirement set.
- Changing human-reviewed candidate boundaries or classifications.
- Resuming a run after a reviewable interruption when the evidence scope changes.
- Reassessing with an intentionally updated rubric while preserving the prior result.
Compare responsibly
- Confirm the runs use the same capability and project scope.
- Check the requirement-set revision before comparing scores.
- Review additions, removals, and weight changes between revisions.
- Separate changes caused by new evidence from changes caused by a new rubric.
- Record the reason for any reviewer override or final status change.
Audit records
DocIQ records security- and decision-relevant actions such as membership changes, run transitions, credit movements, support access, and reviewer overrides. Audit records are intended to answer who did what, when, and within which tenant, workspace, and project boundary.
Note: Do not delete or replace source documents to rewrite history. Create a new immutable version and keep the reason for the change.