Preparing UDRP Evidence: Building a File Around the Three Elements
Prepare a UDRP file with separate evidence for rights, legitimate interests and bad faith, supported by a clear chronology.
What’s in this article?
Direct answer
A UDRP file should connect each allegation to identified evidence. Trademark-related similarity, the respondent's rights or legitimate interests, and bad-faith registration and use need separate examination. A strong document under one element does not automatically repair another element's evidential gap.
Match rights and parties
Compare the proposed complainant with the rights holder shown in the documents. Explain licences, group relationships or authority where names differ. Similar corporate names do not establish shared ownership of a trademark. Set out the protected sign, relevant dates and supporting records clearly rather than leaving the reviewer to reconstruct them.
Investigate permission
Check dealer, licensing, partnership and campaign records. Distinguish a confirmed absence of permission from an unanswered internal enquiry. Limit personal-data collection to information relevant to the dispute. Uncertain findings should become questions for counsel, not definitive statements in a complaint.
Build a balanced chronology
Place trademark history, registration or acquisition, page changes and commercial contacts on the same timeline. Renewal and acquisition by a different holder should not be conflated. If the domain predates the asserted rights, address that fact openly. Include information that weakens the proposed complaint as well as evidence supporting it.
Fictional filing structure
A business could label rights documents Annex A, registration data Annex B, dated website captures Annex C and permission enquiries Annex D. Each assertion points to the appropriate annex. Describe observed behaviour, such as a logo, relationship claim or payment request, rather than replacing evidence with the label “fake website”.
Final review
- Are the complainant, rights holder and authority consistent?
- Does every annex identify its source, date and domain?
- Has adverse evidence been considered?
- Are uncertain facts clearly marked?
- Have language requirements and current provider limits been checked?
Test annex readability
Ask someone who did not prepare the complaint to verify five selected allegations using only the annex index. If a date is missing, add an explanatory record rather than altering the original to make it appear dated. Where an annex contains several domains, identify the relevant entries. Use accurate cross-references instead of repeatedly submitting an entire large file.
Compare translations against their originals. Check party names, registration identifiers and dates internally without carrying unnecessary personal data into public reporting. At final approval, distinguish “the document exists” from “the document supports this particular allegation”. The two checks should never be treated as interchangeable.
Questions
Is a registration certificate enough? It supports the rights issue; it does not establish every element.
Does a detailed technical report guarantee success? No. The panel decides the actual case on the applicable rules and evidence.
Official sources
Related guides
- Resolving Domain Name Disputes: A Decision Guide for Brand Teams
- Digital Evidence and Timelines in Domain Name Disputes
- RDAP and Redacted Registrant Data: What Can an Investigation Establish?
- Assessing Domain Bad Faith: Registration, Acquisition and Use
Brand protection and monitoring
General information only. Rights, authority and current procedure require case-specific assessment. Fictional examples are not B10 client cases or claimed successes.