DMV Fee Calculator Editorial Policy

The DMV Fee Calculator Editorial Team publishes independent explanations of registration components. Accuracy means choosing the right jurisdiction, record, transaction and effective period before doing arithmetic. We prefer an incomplete but correctly labeled subtotal to a complete-looking number assembled from unrelated fee schedules. State sources and scope notes are part of the answer, not optional background.

Source hierarchy

We start with enacted statutes, regulations, agency fee charts, agency implementation notices and published county instructions. Search snippets, third-party summaries and an earlier version of our own page can identify a question, but they do not establish a current rate. A bill is not treated as enacted merely because its introduced text contains a number. An agency chart can carry both an old and a new column; we compare its effective dates to the chosen registration period.

For example, DC's current shipping-weight table has different amounts from its 2023 column. Tennessee publishes a future $274 battery-EV addition, while Pennsylvania ties later road-user charges to an indexed amount that must be obtained when published. Minnesota's minimum electric surcharge is only one side of a greater-of formula. Our review asks whether the complete condition changes the answer rather than copying a conspicuous number from a table.

Verification cadence and automation

Dated and indexed fee schedules require review before a supported period ends. Our date-horizon test flags a model boundary approaching within 45 days unless the next period has a verified handoff. Standing schedules are checked when legislation or agency instructions change and at periodic source review. The displayed page update date is preserved on a no-change rebuild. Effective dates, source dates and page update dates describe different events.

AI and automation assist source discovery, extracting public text, editing code and running comparisons. They can misread a PDF row, confuse model year with expiration year or overlook a special-class exclusion. We therefore use literal worked examples, boundary tests and a committed browser suite. A successful HTTP response or passing build does not by itself establish that a rate is correct. Blocked sources and ambiguous interpretations are recorded as limitations and handled using the agency assessment where appropriate.

Corrections and independence

Report a figure, rule, source or software problem through the correction form. Include the affected page, transaction period, public agency reference and a reproducible example. Avoid plate numbers, VINs, personal notices and account information. We check the reported authority, adjust the affected model and explanation, and verify the new output before release. Reports are saved in the publisher's corrections table; a reply address is optional. No response deadline is promised.

We do not sell registration services, claim a government affiliation or invent reviewers and professional credentials. Current advertising is disabled. If a later commercial arrangement is introduced, it must be disclosed and must not change the source hierarchy. Application decisions, exemptions, official assessments, payments and appeals remain with the agency.