Working With Landscapes
Keep the question, comparator selection, and evidence context together.
On this page
Keep the question with the evidence
A landscape brings together a comparison question, its source/search context, candidate records, and associated evidence. Use a precise question so that the next person reviewing the work can understand why a record belongs.
Keep Atlas landscapes distinct from Workspace, the separate diligence and analysis product.
Navigate a saved landscape
When your product lane supports saved landscapes, its views have distinct purposes:
| View | What to inspect |
|---|---|
| Landscape | The question, source scope, and comparator candidates. |
| Evidence packets | Prepared evidence and coverage for selected records. |
| Research | Model-assisted research and its current or completed status. |
| Activity | Recorded actions and execution history. |
An entry in the recent list does not mean every downstream step completed. Read the status: a draft, a prepared packet, and a completed research run represent different outcomes.
Reopen or refresh
Reopening saved work should show its recorded question, selection, evidence, and source context. A refresh produces a successor revision rather than silently rewriting historical evidence.
When comparing revisions, inspect changes in the question, included sources, candidate selection, and source dates. A newer revision is not proof that all sources were refreshed successfully.
Recover from interrupted work
If a run is still pending, reopen its existing record and inspect the current status before starting another run. A browser reload or lost connection does not, by itself, prove that server work stopped.
A cancellation request also needs a terminal result. If the state remains unclear, use the recovery action shown or contact support with the displayed request/run identifier.