Methodology

Source hierarchy

We research per-state procedure in this priority order:

1. State legislature primary sources (statute URLs point at the official state legislative site, not Justia mirrors).
2. State court self-help portals (.gov, court rule references, official forms).
3. Justia 50-state name-change forms survey (cross-check, never primary).
4. State bar publications (cross-check for procedural details, never primary).

Verification cadence

Every state page displays a “Last verified: [date]” pin. Filing fees drift between annual fee schedules — the verified date is the date of last full review. Statutes are stable; fees and court self-help URLs shift more often. Operators run a quarterly re-verification pass against state court self-help portals.

No-fabrication policy

We do not invent statutes, citations, fees, court venues, or case law. Where a primary-source URL is not available for a specific field, that field is rendered as “Varies by county” or carries a verification-pending pin. We never present unverified data as fact.

Equal-weight reasons editorial policy

NameChangeMap.us is built on an explicit editorial policy: every reason for legal name change is rendered at equal procedural depth. This is the core editorial commitment of the project — reflecting the legal reality that courts evaluate petitioners against statutory criteria rather than against the merit of the reason itself.

The most common reason in the marriage-name-change SaaS market is, historically, marriage. Several incumbents (HitchSwitch, NewlyNamed, MissNowMrs) treat marriage as the “primary use case” and other reasons as “additional” or “edge.” That framing is incorrect for a procedural reference: state statutes do not rank reasons. Several states (California, New York, Illinois, Wisconsin, Oregon) have explicit safety-concern provisions that, in practice, are most relevant to gender-affirming and divorce-revert contexts — but the procedural framework treats those reasons identically to any other.

Concretely, this means:

• Reasons are listed alphabetically, never by perceived primacy.
• Marriage never leads the homepage hero, hub copy, or state-page reasons sections.
• Gender-affirming context is rendered with the same procedural register as every other reason — no “special section” framing, no softer copy, no coded markers.
• We do not use othering language: “for trans users,” “if you are transgender,” “for the LGBTQ community,” “this section is for” — none of these appear anywhere on the site. Procedural copy is universal.
• Reason-coded color, icons, or palette (rainbow as brand element, pink-blue as gendered marker, wedding rings, divorce gavels) are not used.
• Safety-concern publication-waiver coverage is a first-class component, not a footnote.

Privacy

We do not log identifying detail tied to which reason a visitor is researching, which combinations of state pages they visit, or which publication-waiver / safety-concern surfaces they read. Aggregate page-view counts only. The audience for this site is sensitive to surveillance; the appearance of granular tracking on these surfaces would be disqualifying.

Corrections

If you find an out-of-date filing fee, a stale statute citation, or a procedural error, email [email protected] with the page URL and the correct value (with a primary-source link if you have one). We respond to every correction request and update the relevant page when warranted.

Affiliate disclosure

NameChangeMap.us has a paid referral relationship with LegalZoom via Impact.com. When a visitor engages LegalZoom through our referral, the partner network pays us a referral fee. This does not change the price the visitor pays or the licensed attorney's independent professional duty. Full disclaimer.