A watchlist is useful when every entry has a reason for attention and a defined next review.
Give each entry a purpose
Record why the case belongs on the watchlist. Tie it to a treasury relationship, protocol review, investigation lead, or another concrete operational question.
Avoid using the watchlist as a general archive. A saved case preserves a record; a watched case should make a future review easier to prioritize.
Define the review practice
Describe when the team should revisit the case and what evidence it expects to examine. Cadence belongs to the organization’s operating process and may differ between investigations.
GroundTruth’s watchlist supports manual review and on-demand snapshot refresh. Record the review condition in the notes so another analyst understands the intended routine.
- Reason for watching
- Decision the review supports
- Review cadence or triggering condition
- Evidence to revisit
Refresh with the original question in view
Retrieve a new snapshot when the review calls for it. Inspect the block context and the source coverage before comparing the new evidence with your earlier assessment.
A refreshed snapshot replaces the current evidence record. Export the earlier case first if your process requires retaining it as a separate reference.
Decide whether the case still belongs
After review, record the current assessment and next action. Escalate a material question with the references needed to examine it.
Remove an entry from the watchlist when it no longer supports an ongoing decision. Preserve the case according to your team’s retention practice rather than leaving an unexplained item in an active queue.
GroundTruth field notes describe an investigation method. Apply the review scope, source licensing, and information-handling requirements appropriate to your organization.