Requesting a name
Three flavors of request, surfaced automatically based on what your proposed name screened as. You don't pick the type; the propose page shows the right form for the verdict.
1. Reservation request
When you'll see it: verdict APPROVED, or your typed name maps to a cataloged candidate that's currently AVAILABLE.
Fill in the Builder / project name (this becomes reserved by on the catalog row when staff approves) and any notes about target plat date, project specifics, etc. Submit. The request lands in the staff queue with status pending.
On approval the catalog row flips to RESERVED for the configured period (default 90 days, max 270). On denial the row stays AVAILABLE and you'll get an email if you've enabled notifications.
2. Review request
When you'll see it: verdict NEEDS_REVIEW (the proposed name is in the 60–75 risk band — flagged but not rejected).
The propose page shows the conflict(s) above the form, plus an inline "What addressing staff will check" policy box that names the conflicting road and its actual MSAG. The shape of the form is identical to the reservation request — the difference is in what staff does on approval:
-
Approve: the review flag is cleared (logged
as
review_clearedin the audit history) and the name is reserved for you in one step. - Deny: the catalog row stays flagged. You'll need to pick a different name.
What to put in your notes: the policy box on the propose page lays it out, but the short version is — if your project will be in a different MSAG community than the conflicting road, say so. If it's in the same MSAG but the address ranges are well-separated (no overlap, ≥ 1000 numbers between them), say that. Either of those gets you first-pass approval.
3. Supersession request
When you'll see it: verdict REJECTED, AND the blocking conflict is an unused catalog candidate (AVAILABLE or NEEDS_REVIEW), not a real centerline road.
Catalog candidates aren't real roads — they're proposed names sitting in the pre-screened pool waiting to be claimed. If your name is rejected only because it conflicts with one of these, you can ask staff to retire the cataloged candidate and take its place. The propose page shows a "Request to supersede" form spelling out exactly which row would be displaced.
What to put in your notes: the form requires a reason (so make it specific). Why is your name the better choice? Theme alignment with neighboring streets? Match for the subdivision name? Established marketing? Staff is balancing your project's needs against keeping the catalog useful.
What approval does: the displaced catalog row moves to WITHDRAWN with an audit-log entry naming your request. Then your name is added and reserved for you in the same operation. If after the displacement your name still has other conflicts (rare but possible), the approval fails cleanly and the displaced row stays withdrawn — staff can revert via the audit log.
Note: REJECTED against a real centerline road has no submission path. Real roads can't be retired through this flow. Pick a more distinctive name.
Tracking your requests
Every request you've submitted lives at My requests — a single page with status and decision dates. You can withdraw a pending request at any time from there.
If you've enabled notifications under Settings, you'll get an email when staff acts on your request.