The short version
A useful evidence pack connects the legal entity, the approved mark, the requested domains and the people authorised to act. Follow the chosen issuer’s checklist and resolve inconsistencies before submission.
Freeze the application scope
Write a cover sheet naming the applicant entity, certificate type, exact domains and approved logo filename. Ask the issuer to confirm this scope before gathering documents. A project’s marketing name may differ from the registered applicant name, so record the relationship explicitly.
Keep the artwork version stable while the application is reviewed. If a domain or mark changes, tell the issuer and update the cover sheet rather than quietly substituting files midway through validation.
Collect evidence by the claim it supports
| Claim | What to organise |
|---|---|
| Applicant identity | Registered name, registration reference and current contact details |
| Domain control | Domain list and the administrator able to complete the requested check |
| Rights to the mark | Trademark reference or the prior-use evidence requested for the chosen route |
| Authority to apply | Named organisational contact and any required authorisation |
For example, Sectigo’s eligibility guidance covers organisation, domain, mark, contact and operational-existence checks. Other issuers may request different evidence or accept different validation methods.
Review consistency before completeness
A folder full of documents is not necessarily a coherent application. Compare entity names, addresses, domains and artwork across the pack. Flag an old address, a trading name or a recently redesigned logo for explanation before the reviewer encounters it.
Keep an evidence index containing the item, date, owner and claim it supports. Store sensitive documents in the issuer’s designated secure submission channel, not alongside publicly hosted BIMI assets. Share only what the validation process requests.
Separate application progress from deployment readiness
Track the current stage: submitted, awaiting evidence, validation completed or certificate issued. Ask for a specific missing item when an application stalls; a general “in progress” label is difficult to act on.
Once issued, verify the delivered domain scope and mark against the cover sheet before the hosting handoff. The team publishing the public certificate bundle should receive the issued files and instructions, not the entire application folder.
Sources & further reading
Provider guidance checked on . Requirements can change; check the original guidance when implementing. Planning checklists and examples are BIMI World’s editorial suggestions.