Managing Watches
Details that improve matching
Which watch details we use to find the right obituary, and which ones are just for you.
Last updated October 8, 2026
Plan: All plans · For: Everyone · Time: 3 min read
Many people share a name. The details you add to a watch are how we tell them apart.
Details we use for matching
| Detail | Why it helps |
|---|---|
| First and last name (required) | The starting point. We also recognize common nickname variations of first names |
| Middle name | A matching middle name raises the score. A different middle name lowers it |
| Maiden or previous last name | We search under this name too, so we don't miss an obituary published under a former name |
| Nicknames | Tried when the obituary uses a different first name, such as "Peggy" for Margaret |
| Location (city and state) | One of the strongest signals. A name in the right city and state scores much higher. Add every place the person lived, especially recent ones |
| Date of birth | Exact date, year only, or unknown. An age or birth year in the obituary that fits raises the score. One that clearly contradicts it can rule a match out |
| Relatives | Obituaries list survivors. Each relative's name we find adds to the score |
| Match sensitivity | Close, Recommended (default), or Broad. Sets how strong a candidate must be before it's listed as a match |
Details that don't affect matching
On Professional plans, the Case management fields on the watch form (case number, client name, case type, priority, assigned to, date of interest, deadline, and Internal notes) are for organizing your work. They aren't used to find or score matches. To improve accuracy, add a location, a date of birth, or relatives instead.
Tips
- No location? Add the state at least. A name-only result in a different state isn't treated as a match.
- Common name? Add a date of birth and at least one relative, and consider Close sensitivity.
- Very little to go on? Use Broad sensitivity and expect to review more candidates.
Related
Was this article helpful?