Say which jurisdictions you are licensed in before the first scroll
The single highest value sentence on a DMV brokerage site names the jurisdictions the firm actually operates in.
Visitors here arrive with a building or a submarket in mind. Their first question is not whether you are good. It is whether you are relevant to Arlington, or to Montgomery County, or to a block in Shaw.
Put it in plain type near the top of the homepage and repeat it in the footer of every page. Licensing details differ by jurisdiction and change over time, so state your coverage and confirm the underlying position with your own counsel rather than describing anyone else's requirements.
Firms worry that narrowing looks small. In practice the opposite happens. Saying you work Northern Virginia and the District, and that Maryland work goes to a named referral partner, reads as competence rather than limitation.
The internal payoff is immediate. Fewer inquiries need triage, brokers stop discounting web leads, and the site starts being treated as a source of business rather than a brochure.
The filter that matters here is District, Maryland or Virginia
Availability search on a DMV brokerage site should let a visitor cut by jurisdiction before anything else.
Most brokerage sites filter by asset class and size first. In a single jurisdiction metro that is fine. Here it produces a results list mixing three legal environments, three tax situations and three permitting processes as though they were interchangeable.
Lead the filter set with jurisdiction, then submarket, then use, then size. A tenant with a Virginia mandate can eliminate two thirds of your inventory in one tap, which is a good outcome even though it shrinks the list.
Show the jurisdiction on the listing card itself, not only inside the detail page. Cards get screenshotted and forwarded, and the jurisdiction should survive that trip.
Keep the filter fast. Anything that reloads the whole page on each selection will be abandoned on a phone, which is where a meaningful share of this browsing happens.
Alley access and loading belong on the card for anything inside the District
Building stock in the core is old and awkward, and the constraints that decide a deal are usually missing from the listing.
Rowhouse and small mixed use buildings in the District come with narrow lots, shared walls, alley access and permit restricted street parking. A tenant used to a Fairfax County flex building has no way to picture any of it from a photo.
Put the practical facts on the template: how deliveries arrive, whether there is a loading area or an alley entrance, ceiling heights, whether the space is on a designated historic block. Say what is generally the case and note that requirements are worth confirming with the relevant historic preservation office or the building department.
Never publish a conclusion about what will be approved. Describe the constraint, link to the source where one exists, and stop there.
Suburban templates need their own fields rather than the same ones. Parking ratio, clear height, Metro walking distance and drive time to the Beltway do more work in Reston or Rockville than a description of the lobby finish.
Ask for jurisdiction, size and date, then get out of the way
A brokerage inquiry form should capture the three things that decide routing and nothing that the broker will learn in the first call anyway.
Jurisdiction, approximate size, and the date the space is needed. With those three, an inquiry can be routed to the right person in one hop without anyone reading it first.
Make jurisdiction a required choice rather than a free text field. It is the field that determines whether the inquiry is yours to work, and it is also the field visitors will skip if you let them.
Cut everything else. Budget, company size, how they heard about you, a message box with a minimum length: each one costs completions, and none of it changes who picks up the phone.
Offer a phone number next to the form and treat calls as first class inquiries. A principal with a real requirement will often call rather than type, and a site that hides the number behind a contact page loses those entirely.
A hero video of the Wharf loads before your availability does
Brokerage sites are slow for predictable reasons, and every one of them is a design decision someone made on a desktop.
Full width video, drone footage, uncompressed building photography and an interactive submarket map are the usual suspects. On office fiber they feel impressive. On a phone in a parking garage in Bethesda they are a blank screen.
Availability should be reachable and readable before decorative media has finished loading. That is a build order question more than a bandwidth question, and it is solvable without removing the imagery entirely.
Large flyers and site plans belong behind a link rather than embedded in the page. Let the visitor choose to download a thirty megabyte PDF instead of paying for it on arrival.
Test on a real phone on a real cellular connection, in a garage or on a Metro platform, not in a browser emulator on a desk. The results are usually sobering and immediately actionable.
Tour logistics belong on the site: parking, alley entry, and snow days
Telling visitors how a tour actually works in the District removes friction before the first call and proves you have worked there.
Parking in the core is genuinely difficult. Permit restrictions, limited loading, and buildings whose only practical access is through an alley. A short, honest note about where to park and how to get in reads as experience.
Winter is a real part of the calendar here in a way it is not in warmer markets. Say what happens to a scheduled tour when there is snow or ice, and who calls whom. It is a small paragraph that prevents a lot of confusion in January and February.
Cross jurisdiction scheduling deserves the same treatment. Getting from Tysons to Navy Yard in the middle of the day is not a twenty minute trip, and a site that acknowledges Beltway reality sets better expectations than one that does not.
Put this information where a visitor will find it, near the availability pages and the contact page, rather than in a blog post nobody will see twice.
Questions we actually get
- Should availability live on our site or should we point at a portal?
- On your site, with the portal as an additional channel rather than the destination. The availability pages are what visitors forward to colleagues, and sending them off site hands the relationship and the analytics to someone else. It also means the one page a serious prospect actually reads is a page you do not control or measure.
- How much should the inquiry form ask for?
- Jurisdiction, approximate size and required date, plus a name and a way to reach them. Everything beyond that costs completions and gets covered in the first call anyway. The one field worth being strict about is jurisdiction, because it decides routing and because visitors will skip it if it is optional.
- Do we need separate pages for each jurisdiction we cover?
- Yes, and for the submarkets underneath them. Separate pages let you say what you actually do in each place, they match how people search, and they give you somewhere honest to state your coverage. A single page covering the whole DMV cannot say anything specific enough to be useful to a tenant with a Montgomery County requirement.
- Our brokers want to update listings themselves. Is that realistic?
- It should be the default. Availability changes faster than any agency update cycle, and a site where changes require a ticket goes stale within a quarter. The practical answer is a simple editing interface limited to the fields that change, so a broker can mark a suite leased or adjust a rent line in under a minute from a phone.
- What happens to a listing page when the space leases?
- Keep it. Mark it clearly as leased, remove the inquiry form or repoint it, and link the page to the relevant submarket page. Deleting listing pages throws away whatever authority they accumulated and creates broken links in every email where the page was forwarded, which in commercial real estate is a lot of emails.
