# Review Diagnosis findings and evidence

Review the saved investigation result, its evidence, and its run trace.

## Before you start

### Intended audience

Responders who assess a completed or historical Diagnosis run.

### Required permissions

You need permission to view the incident and its Diagnosis data.


### Prerequisites

- Open an incident with a saved Diagnosis result.

## Procedure

<a id="phase-assess-the-finding"></a>

### Assess the finding

<a id="step-open-the-result"></a>

1. **Open the result.** Select Diagnosis. Find Investigation result.

<a id="step-identify-the-observation-time"></a>

2. **Identify the observation time.** Review the observation status and assessed time. If the result is labeled Historical snapshot, treat it as past scope, not current state.

<a id="step-use-the-review-sequence"></a>

3. **Use the review sequence.** Use this order: observation status → assessed time and scope → Evidence and checks → conclusion → suggested action, shown as Suggested fix.

<a id="phase-verify-evidence-and-provenance"></a>

### Verify evidence and provenance

<a id="step-open-checked-evidence"></a>

4. **Open checked evidence.** Select View checked evidence. You can also open Evidence and checks.

<a id="step-review-supporting-context"></a>

5. **Review supporting context.** Open Related signals and ruled out causes. Review what supports or weakens the conclusion.

<a id="step-review-run-provenance"></a>

6. **Review run provenance.** Open Run details. Review Raw local tool trace before you rely on an important claim.

## You are done when…

You can trace each important finding to checked evidence and the local run that produced it.

## Troubleshooting

<a id="troubleshooting-the-result-is-inconclusive"></a>

### The result is inconclusive.

Use Tool activity to find the missing source check, fix the local tool setup, and run a follow-up diagnosis.

<a id="troubleshooting-a-finding-has-no-evidence"></a>

### A finding has no evidence.

Treat it as a hypothesis until a responder checks a source and records supporting evidence.

<a id="troubleshooting-the-result-describes-old-scope"></a>

### The result describes old scope.

Use the assessed time to confirm that the result covers old scope. Start a new run for current evidence.

<a id="troubleshooting-a-finding-lacks-adequate-support"></a>

### A finding lacks adequate support.

Review Evidence and checks. Record missing evidence before accepting the recommendation.

## Related articles

- **Recommended next task:** [Run a local Diagnosis for an incident](https://tellagen.com/help/run-local-diagnosis)
- [Record a timeline event and evidence](https://tellagen.com/help/record-timeline-evidence)
- [Manage response actions](https://tellagen.com/help/manage-response-actions)


## Continue through the incident lifecycle

- **Previous task:** [Run a local Diagnosis for an incident](https://tellagen.com/help/run-local-diagnosis)
- **Next task:** [Create a collaborative postmortem](https://tellagen.com/help/create-collaborative-postmortem)
- [Back to Support Center](https://tellagen.com/help#help-search)

## Last verified date

2026-08-29