Assurance Results

What it is

Assurance Results display the outcomes of assurance test runs. View validation status, review evidence, and track compliance posture over time.

How to use

1. Navigate to Assurance → Results in the sidebar
2. Browse recent assurance validation results
3. Filter by suite, test, status, or date
4. Click on a result to view details and review

Results Overview

Each result shows:

• Test: Which assurance test was executed
• Test status: The automated outcome of the validation (passed/failed/partial/error)
• Review status: The human review state used to document disposition (pending review, approved, rejected, etc.)
• Evidence: The evidence that was validated
• Timestamp: When the validation occurred
• Review history: Who changed review status, when, and why

Review Process

For results requiring manual review:

1. Click on the result to open details
2. Review the evidence and validation criteria
3. Set an appropriate review status (e.g., Approved / Rejected / Needs Investigation)
4. Add comments (and optionally a status-change reason) so the review is audit-ready

Key Features

• Manual review workflow: Approve or reject results that need human oversight
• Evidence linking: See the exact evidence that was validated
• Historical tracking: Review status change history and threaded comments
• Export: Generate reports for compliance documentation

Statuses

Assurance Results track two different “statuses”. This separation helps you distinguish what the system observed from how a reviewer dispositioned it.

Test Status (automated)

• Passed: Validation succeeded automatically
• Failed: Validation failed, action may be required
• Partial: Some checks passed and some failed (or partial evidence was available)
• Error: Validation encountered an unexpected error

Review Status (manual / disposition)

• Pending Review (pending_review): Awaiting review by a team member
• Approved (approved): Result has been reviewed and approved
• Rejected (rejected): Result has been reviewed and rejected
• Needs Investigation (needs_investigation): Requires further investigation before final disposition
• False Positive (false_positive): Marked as a false positive finding (commonly used for failed/error test statuses)
• Acknowledged (acknowledged): Result has been acknowledged (useful when a finding is known/accepted but not “approved”)

Commenting & Fully Documented Reviews

Comments and status-history are designed to make reviews self-contained for audits.

What gets recorded

• Review status history: Every review-status change records the previous status, the new status, who changed it, when it changed, and an optional reason.
• Comments: Add threaded comments to document investigation notes, links to external tickets, exception references, or remediation steps.
• Edits: Edited comments are marked as edited and include updated timestamps.

Recommended workflow

• When a result is Failed or Error, set review status to Needs Investigation while triaging.
• When you reach a conclusion, set review status to Approved, Rejected, or False Positive.
• Add a short comment that answers: what you checked, why you chose the disposition, and what follow-up (if any) is required.

“Needs attention” triage

Use the Needs attention filter to focus on results that are failing (or erroring) and are still pending review / under investigation.

Tips

• Review Pending Review results promptly
• Use Needs attention to triage failing/erroring results that aren’t dispositioned yet
• Add a comment whenever you change review status on a high-impact finding
• Track trends to identify recurring compliance issues
• Export results for audit documentation