Name Collision Alert Triage Log
A running log for every brand name match you find, with columns for the source, how close the match is, what the other party sells, the priority you assigned, and the next step with its date.
Reviewed for 2026, updated September 8, 2026.
An alert is a starting point, not a verdict. Most runs surface more matches than real conflicts, and the value of a log is that each one gets a considered decision instead of a reaction. The columns below capture the facts that decide priority: how close the name is, where it turned up, what the other party actually sells, and how much that overlaps with your goods, customers, and channels. The last column forces a next step and a date, which is the part most people skip.
Keep one sheet per brand name, or one shared sheet for all of them if your list is short, and add a row the day a match is found rather than at the end of the month. The example rows show the kinds of entries that typically land in each priority bucket; replace them with your own. The article on reading a trademark alert on our blog explains the fields on a USPTO record that feed the match type and goods columns, and our complete guide to brand name monitoring walks through the low, medium, and high triage scale the priority column uses. If a high-priority row starts to look like a forced name change, the Forced Rebrand Cost Estimator in our Tools section puts a number on what is at stake.
| Date found | Name or mark found | Source | Match type | Their goods or services | Priority | Next step and follow-up date |
|---|---|---|---|---|---|---|
| 2026-09-08 | Your name, exact spelling | USPTO application | Exact | Their listed class and goods (copy from the record) | High | Screenshots saved; confirm publication date; attorney call booked for (date) |
| 2026-09-08 | Your name with one letter swapped | Web search | Near identical | Same category, sells to your customers | High | First-use proof gathered; polite letter drafted by (date) |
| 2026-09-01 | Your name plus a generic suffix | App store | Similar | Adjacent category, different buyers | Medium | Recheck on (date); escalate if they add your category |
| 2026-09-01 | Phonetic twin of your name | Social platform | Similar | Personal account, nothing for sale | Low | Logged; no action unless it becomes a business |
| 2026-08-25 | Your name on a different domain ending | Domain registration | Exact | Parked page, no content | Low | Recheck in 90 days for a live site |
| 2026-08-25 | Your product name | Marketplace listing | Exact | Unrelated product type, unrelated buyers | Low | Logged; note their class if they ever file |
| 2026-08-18 | Your company name | State business registry | Exact | Unknown; no website found yet | Medium | Search for their site monthly; recheck on (date) |
| 2026-08-18 | Your name with a hyphen | Web search | Near identical | Same category, but only in one region | Medium | Watch for expansion; consider coexistence talk; recheck on (date) |
| Your date | Your match | Your source | Exact / Near identical / Similar | What they sell and to whom | Low / Medium / High | Your next step and the date it is due |
https://namewatchr.com/templates/name-collision-alert-triage-log/Use it in your business, share it with your team, or link to it from your own site.
Also from NameWatchr
- Brand Name Monitoring Run Checklist: A printable checklist for one complete brand name monitoring run, from refreshing the variant list to logging what was found and what was decided.
- Free calculators