Commercial vehicle work in Washington, DC combines dense urban routes, security-sensitive facilities, restricted streets, limited loading space and regional travel through Maryland and Virginia. The District participates in IRP but not IFTA. Carriers therefore need a clear registration and trip-permit path while maintaining fuel reporting through an eligible IFTA jurisdiction when required.
Separate DC IRP from IFTA treatment
DC DMV administers International Registration Plan accounts for qualifying vehicles based in the District. The District does not participate in IFTA. A carrier requiring IFTA licensing must use a member jurisdiction in which it qualifies rather than assuming DC registration creates a fuel-tax account.
Keep the IRP base, IFTA base, USDOT identity, vehicle, lease and responsible-carrier relationships documented together. Different base jurisdictions do not excuse inconsistent source records.
Confirm DC apportioned or trip-permit authority before entry
A covered vehicle operating in or through Washington, DC must have the registration or trip-permit authorization that fits its movement. Check the power unit, weight, axles, interstate activity and base registration before dispatch.
Do not transfer a trip permit to another vehicle or assume a prior authorization covers a changed unit. Keep the permit, cab card and shipping record accessible to the driver.
Build a legal urban route before accepting the delivery time
Restricted streets, low clearances, security zones, bridge limits, construction and loading restrictions can change the practical route. Dispatch should confirm vehicle dimensions and weight, approved access, delivery instructions, safe parking and driver hours.
A customer-provided route is not automatically suitable for a commercial vehicle. Record the carrier route decision and any public-space or oversize permission required for the movement.
Reconcile DC, Maryland and Virginia distance
Regional carriers can cross District boundaries several times in a shift. Preserve trip endpoints, route, readings, unit identity, jurisdiction distance and fuel evidence. Local mileage and yard movement should not disappear from the reporting trail.
Compare ELD or tracking data with toll, fuel, delivery, gate and permit records. Investigate unexplained edits and substituted units before the quarter closes.
DC IRP
DC DMV administers apportioned registration for qualifying heavy commercial vehicles based in the District.
No DC IFTA base
The District does not participate in IFTA; eligible carriers must use a qualifying member jurisdiction.
Trip permits
Non-apportioned covered vehicles may need DC authorization before entering.
Urban routes
Truck restrictions, security, weight, clearance, parking and delivery access need advance review.
Control secure and government-facility deliveries
Government, institutional and secure-site work can involve appointment windows, identity checks and long waits. Confirm driver credentials, vehicle access requirements, cargo documentation and available hours before dispatch. Do not assume a government customer makes a contracted vehicle exempt from normal carrier requirements.
Retain arrival, screening, waiting and release events with the log and delivery record. Any equipment or route exception should be documented for the actual trip.
Apply HOS and short-haul rules to the real regional day
A driver based near the District may perform local delivery and interstate work in the same week. Document the reporting location, radius, duty time and required records for any short-haul use, and monitor days that fall outside it.
Use ELD and HOS support when regional routes produce recurring unidentified driving, edits or mixed exception use. Keep dispatch evidence that explains delays without rewriting the log.
Test one DC delivery from permit to closeout
Select a heavy, secure or restricted-route movement. Retrieve registration or trip permit, route decision, driver file, testing status, log, inspection, maintenance and delivery evidence. Confirm the same unit and carrier identity throughout.
Use authority setup support, driver-file support or a mock audit for a defined gap, then verify the correction on a later trip.
Keep regional operating records available at the carrier
DC deliveries often involve brokers, facilities, parking coordinators and outside compliance providers. The carrier should retain route approvals, permits, gate or screening events, driver and vehicle evidence, and any filed account documents. Define when each third party returns records and who verifies completeness.
Sample one provider-managed or secure-site movement after closeout. Missing documents should remain an assigned exception until the record and the future handoff are corrected.
Review direct and regional work against documented scope
A new DC customer, secure facility or neighboring-state lane can change authority, insurance, route, driver and vehicle requirements. Record the compliance basis before the first load and identify who approves any permit or access condition.
Sample the first completed trip, including jurisdiction distance and delivery evidence. Correct mismatches before the work becomes a regular route.
Official sources: DC DMV International Registration Plan; DC DMV apportioned and exempt vehicles; DC DMV commercial carrier trip permits.