Free Washington, D.C. Notice to Enter

This Washington, D.C. Notice to Enter gives a tenant clear written notice before the housing provider enters the rental unit. D.C. Code §42-3505.51 requires at least 48 hours’ written notice – shorter only with the tenant’s written consent – and entry only at a reasonable time, defined as 9:00 a.m. to 5:00 p.m., not on a Sunday or federal holiday. See our tenant screening laws by state hub and how to screen tenants guide to keep your D.C. tenancies documented from the start.

Complete the fields below to generate a Washington, D.C. Notice to Enter. D.C. Code §42-3505.51 requires at least 48 hours’ written notice of intent to enter, with entry only between 9:00 a.m. and 5:00 p.m. and not on a Sunday or federal holiday – so plan ahead and deliver clear written notice. The form records the date, time window, purpose, the persons entering, and how the notice is delivered.

Watch: Washington DC Notice to Enter explained

▶ Watch overview

Washington, D.C. does have a landlord-entry statute: D.C. Code § 42-3505.51, “Access by housing provider to dwelling unit.” It is a statute in the D.C. Official Code – section 531 of the Rental Housing Act of 1985, added by the Residential Lease Clarification Amendment Act of 2016 and effective in 2017 – not a municipal housing regulation. That distinction matters, because guides routinely cite a phantom regulation for a rule the Code states plainly. The statute sets a concrete standard: a housing provider may enter a rental unit during a tenancy only for a reasonable purpose, at a reasonable time, and after reasonable notice, and subsection (a) defines each of those three terms so they are not left to argument.

The first defined term is reasonable notice. Under § 42-3505.51(a), reasonable notice means written notice provided to the tenant at least 48 hours before the time the housing provider wishes to enter – or a shorter period only as agreed to by the tenant in writing. So the number to remember is 48 hours, and the only way below it is the tenant’s written agreement; a casual verbal okay does not satisfy the statute. This is not a 24-hour rule. Written notice does two things a vague verbal heads-up cannot: it states the date, time window, and purpose so the tenant knows exactly what to expect, and it leaves a dated record proving the housing provider gave the full 48 hours.

The third defined term is reasonable purpose, and § 42-3505.51(a) lists six categories: the duty to keep the entire property safe from damage; the duty to inspect the premises; the duty to make necessary or agreed repairs, decorations, alterations, renovations, or improvements; the duty to supply necessary or agreed services and maintenance; the need to exhibit the unit to prospective or actual purchasers, mortgagees, tenants, workmen, or contractors; and the need to gain entry for work ordered by a governmental entity. If a planned entry does not fit one of these, that is a strong signal it should not happen.

The written notice may be provided electronically – the statute expressly allows email and mobile text messaging – but if the tenant does not furnish a written acknowledgement, the housing provider must provide a paper notice. That paper fallback is built into the statute, not optional. The notice and time-of-day rules do not apply in a genuine emergency for the protection or preservation of the premises, or for the protection and safety of the tenants or other persons; document the emergency and what was done. D.C. law uses the terms “housing provider” and “tenant,” and a housing provider and a landlord mean the same thing here. The sections that follow walk through the permitted purposes, how the 48-hour-plus-9-to-5 timing keeps an entry reasonable, the emergency exception, showings, the code-violation access rule, what the lease can and cannot do, and – most important for a housing provider managing risk – exactly what remedy a D.C. tenant has when entry goes wrong, in § 42-3505.51(b).

Unlike states that leave “legitimate reason” to the courts, § 42-3505.51(a) lists the reasonable purposes for entry, so a D.C. housing provider can check a planned visit against the statute itself. The six categories track ordinary property management, and the unifying test is the same one the remedy implies: the housing provider must have a real, property-management reason to be inside the unit, not a pretext for checking up on or pressuring the tenant. When the reason fits a listed purpose and the notice is proper, entry is rarely controversial.

Repairs, maintenance, and services cover the most common reasons for access. The statute names the duty to make necessary or agreed repairs, decorations, alterations, renovations, or improvements, and the duty to supply necessary or agreed services and maintenance. This includes responding to a tenant’s repair request, performing scheduled upkeep, and addressing conditions the housing provider is obligated to fix. Inspections are a separate listed purpose – the duty to inspect the premises – and so is the broader duty to keep the entire property safe from damage, which supports preventive work such as servicing heating and cooling systems and testing smoke and carbon-monoxide detectors.

Showings are a frequent flashpoint, and the statute addresses them squarely: the need to exhibit the unit to prospective or actual purchasers, mortgagees, tenants, workmen, or contractors is a listed reasonable purpose. A housing provider may need to show the unit to a prospective tenant near the end of a lease, to a prospective buyer if the property is on the market, or to a lender, appraiser, or contractor during a refinance or a planned repair. Each is legitimate, but each also brings strangers into the tenant’s home, so generous notice within the 48-hour rule and reasonable scheduling matter most here.

Government-ordered work rounds out the list: the need to gain entry for work ordered by a governmental entity is its own reasonable purpose, which covers access required to comply with a District inspection order or code-enforcement directive. Across all six purposes, the form lets the housing provider state the exact reason, describe the work, and list everyone who will enter – the single most effective way to turn a potentially contested entry into a routine, documented visit. It is worth being explicit about what is not a listed purpose: entering to check whether the tenant is keeping the unit “well enough” without a maintenance reason, to look for lease violations on a hunch, or to confront a tenant over a dispute does not fit any category in § 42-3505.51(a), and that is exactly the kind of pretextual entry the remedy in subsection (b) is built to reach.

The two numbers that do the work in D.C. are 48 hours and 9-to-5, and they operate together. The 48 hours is a minimum, not a target: count two full days before the entry, and do not shave the margin by treating “two days out” loosely. Because the statute lets the tenant agree in writing to a shorter period, a housing provider who genuinely needs faster access should ask for that written agreement rather than simply entering early – the writing is what protects both sides if the timing is later questioned.

The 9-to-5 window is just as firm. Entry must fall between 9:00 a.m. and 5:00 p.m. and not on a Sunday or a federal holiday, unless the tenant agrees to another time. Federal holidays are the ones recognized in the District, so a housing provider scheduling around the calendar should treat days like New Year’s Day, Memorial Day, Independence Day, Labor Day, Thanksgiving, and similar federal holidays as off-limits absent the tenant’s agreement. Saturdays are not excluded by the statute – only Sundays are – but a Saturday entry still has to land inside the 9-to-5 hours. Offering a window inside business hours rather than a single rigid minute makes the entry easier for the tenant to accommodate and reinforces that it is reasonable.

Reasonableness also has a frequency dimension. The remedy in § 42-3505.51(b) reaches not only an unlawful entry but also repeated unreasonable demands for entry, which means the number of entries and entry demands matters as much as the notice for any single one. A single, well-noticed entry to make a repair is plainly reasonable; a pattern of frequent entries or repeated demands can interfere with the tenant’s quiet enjoyment regardless of how each one is announced. The safe practice is to consolidate work, enter no more often than the task genuinely requires, and document each visit.

How the notice is delivered feeds directly into whether it is reasonable. The statute allows electronic written notice by email or mobile text message, but conditions it: if the tenant does not furnish a written acknowledgement, the housing provider must follow up with a paper notice. The practical lesson is to choose the channel most likely to reach this particular tenant and to keep a paper copy ready whenever an electronic notice goes unacknowledged. Personal delivery and posting on the door, alone or paired with email, remain reliable methods; whatever the channel, keep dated proof that you used it at least 48 hours ahead.

The clearest situation in which a D.C. housing provider may enter without 48 hours’ notice or the 9-to-5 limit is a genuine emergency. Section 42-3505.51 excuses both the notice and the time rules where entry is for the protection or preservation of the premises, or for the protection and safety of the tenants or other persons – the statute’s own words. A fire, a flood, a gas leak, a burst pipe, or any other immediate threat to people or the property justifies immediate entry, because waiting to give notice could turn a containable problem into a catastrophe.

It helps to draw a bright line between a true emergency and mere urgency. A burst pipe actively flooding the unit, a gas smell, a fire alarm, or a report of a medical crisis behind a locked door are emergencies that justify immediate entry. A lease violation the housing provider is eager to confront, a repair the tenant has been slow to schedule, or a desire to get ahead of a deadline are urgent to the housing provider but are not emergencies, and using the emergency label to cover them is the kind of overreach the remedy in subsection (b) is meant to stop.

Because an emergency entry happens without the usual notice, documentation is the housing provider’s protection. Record the date and time, the nature of the emergency, what was found on entering, what was done, and who entered, and keep any photographs. Notify the tenant promptly afterward, explaining what happened and why immediate entry was necessary. Scope matters too: an emergency justifies the entry needed to address the emergency, not a general search of the unit. A housing provider who enters to stop a flood should deal with the water and leave, not take the opportunity to inspect the tenant’s belongings, because an emergency entry that balloons into a broader, unconnected search can lose its protection and revert to an ordinary unauthorized entry.

Showings put the housing provider’s legitimate business needs in the sharpest tension with the tenant’s right to be left in peaceful possession, which is why the statute lists exhibiting the unit to purchasers, mortgagees, prospective tenants, workmen, or contractors as its own reasonable purpose. When a lease is ending, the housing provider may reasonably need to show the unit so it does not sit vacant; when the property is for sale, a buyer’s lender or appraiser may need access too. All of these are legitimate, but every one brings outsiders into an occupied home, so the 48-hour written notice and the 9-to-5 timing apply with extra care because showings cluster. Group showings into defined windows, give as much lead time as possible, and offer a way to reschedule – a tenant who feels respected during a marketing period is far less likely to refuse access or claim harassment.

The statute also carries a code-violation access rule that cuts the other way. Once a tenant alleges a housing code violation, the tenant may not unreasonably prevent the housing provider from accessing the unit to assess and abate the alleged violation, and must provide access within 48 hours of the housing provider’s written request. The general 48-hour notice still frames the routine case, but a tenant who raised the violation cannot then stonewall the repair. For a housing provider, the practical move is to put the access request in writing, tie it to the specific alleged violation, and keep the request on file alongside the notice – the writing is what shows the request was made and the 48-hour clock started.

This rule reflects a sensible symmetry in the statute. The 48-hour notice protects the tenant’s possession against unwanted intrusions, but it is not a tool for a tenant to demand a repair and then block the access the repair requires. When the tenant is the one who raised the condition – through a complaint to the housing provider or to District officials – the access request is tied to fixing a problem the tenant identified, so the statute shortens the friction by giving the provider a clean 48-hour access window from a written request. The provider should still treat the request as a written notice in substance: name the unit, describe the alleged violation, state the date and time of the assessment or abatement visit, and deliver it the same way an ordinary notice would be delivered, so the file shows both that the request was made and that the entry that followed was for the reasonable purpose of inspecting and repairing. Used this way, the code-violation rule speeds legitimate repairs without becoming a back door around the 9-to-5 timing or the reasonable-purpose limit, both of which continue to apply to the visit itself.

The entry rules assume the tenant is still in possession. When a tenant truly abandons or surrenders the unit, the possessory interest the notice rule protects begins to dissolve, but abandonment is a conclusion a housing provider should reach carefully, because acting on a mistaken belief that a tenant has left can itself create liability. Abandonment generally requires both that the tenant has actually left and that the tenant intends not to return – shown by facts such as removed belongings, disconnected utilities, unpaid rent, and no response to contact. A tenant who is merely traveling, hospitalized, or temporarily away has not abandoned the unit. D.C. is strict about self-help: a housing provider may not retake possession or change the locks outside the legal eviction process, so until surrender or abandonment is genuinely clear, the ordinary entry rules continue to apply.

Even though D.C. fixes the entry duty by statute, the lease still shapes the day-to-day mechanics of access, and a tenant’s real-time consent still matters. The lease can spell out how showings, inspections, and maintenance visits are coordinated, can set notice practices more generous than 48 hours, and can establish the delivery channel the parties will use. What the lease cannot do is contract below the statutory floor: a clause purporting to allow entry on less than 48 hours’ written notice without the tenant’s written agreement, or to authorize routine entry outside the 9-to-5 window on Sundays or federal holidays, does not override § 42-3505.51.

A tenant’s written agreement is the statute’s own escape valve from the 48-hour minimum, so it deserves emphasis. Section 42-3505.51(a) lets the parties agree in writing to a shorter notice period and to a time outside the 9-to-5 window. The key word is writing: a text or email in which the tenant agrees to a specific earlier or off-hours entry both satisfies the statute and creates the record that an agreed-upon visit cannot later be recast as an intrusion. Standing arrangements for routine access can be built into the lease; one-off agreements can be documented as they are given.

There is a limit, however, that housing providers should not lose sight of. The remedy in § 42-3505.51(b) reaches repeated unreasonable demands for entry, which means a housing provider cannot use even a broadly worded lease as a shield for harassment. A housing provider who relies on a permissive clause to enter repeatedly, at unreasonable times, or to pressure a tenant is not merely exercising a contract right; that conduct can trigger an injunction and damages for breach of quiet enjoyment regardless of what the clause says. For that reason, the smarter drafting choice is a clause that tracks the statute – reasonable purpose, 48 hours’ written notice, the 9-to-5 window, an emergency carve-out, and a stated delivery method – which gives the housing provider everything a normal operation needs while signaling good faith to a court.

This is the part most often gotten wrong, and D.C. makes it easy to get right: the remedy is in the same statute as the duty. D.C. Code § 42-3505.51(b) provides that, on a showing by the tenant that the housing provider has entered a unit in violation of the section, or has repeatedly made unreasonable demands for entry, any court of competent jurisdiction may enjoin the housing provider from that behavior and may assess appropriate damages against the housing provider for breach of the tenant’s right to quiet enjoyment of the premises. The statute states no dollar figure – damages are what the tenant proves – and the remedy reaches both the entry made with no right and the campaign of harassing entry demands.

Note the subsection. The remedy is § 42-3505.51(b), the same subsection that states the operative entry rule; the statute has only subsections (a) and (b), so there is no (d) or (e) to cite. A guide that points a D.C. tenant to a phantom subsection, or to a municipal housing regulation, is sending the reader to authority that does not exist for the point. The right citation is the Official Code section and subsection (b).

The Consumer Protection Procedures Act

The statutory entry remedy is not the only one. The D.C. Consumer Protection Procedures Act, D.C. Code § 28-3905, applies to trade practices arising from landlord-tenant relations, and it lets a tenant recover treble damages or $1,500 per violation, whichever is greater, plus attorney fees and an injunction. Where a pattern of abusive entries can be framed as an unfair or deceptive trade practice, the CPPA can supply damages that exceed a small actual loss, and it often travels alongside a § 42-3505.51(b) claim. The CPPA is a separate consumer statute that reaches landlord conduct – not the entry remedy itself – so it is cited as § 28-3905, not as part of the entry section.

Retaliation under § 42-3505.02

If a housing provider weaponizes entry to retaliate, a distinct statute applies. D.C. Code § 42-3505.02 presumes retaliatory action when the housing provider acts within 6 months after a protected tenant act – a witnessed oral or written repair request, contacting District officials about violations, lawfully withholding rent after reasonable notice, organizing or participating in a tenant organization, enforcing rights under the lease, or bringing legal action. Once the tenant shows the timing, the trier of fact presumes retaliation and rules for the tenant unless the housing provider rebuts it with clear and convincing evidence. Retaliation is a connected protection that can stack on top of the entry remedy, not a substitute for it.

Common-law quiet enjoyment and trespass

Two common-law theories run alongside the statute. Every D.C. residential lease carries an implied covenant of quiet enjoyment; the D.C. Court of Appeals confirmed in Sobelsohn v. American Rental Management Co., 926 A.2d 713 (D.C. 2007), that the covenant continues to be implied in residential leases and that the landlord may not invade the possessory interest the lease conveyed. Section 42-3505.51(b) ties its own damages directly to that right to quiet enjoyment. Separately, a housing provider who enters a unit the tenant lawfully possesses, without a right of access, can be liable in common-law trespass, because possession – not title – founds a trespass claim, which is exactly why a tenant in possession can sue a housing provider who holds title. For most D.C. over-entry disputes the statutory remedy in § 42-3505.51(b) is the cleanest hook, with quiet enjoyment and trespass as supporting theories rather than the primary claim.

How damages and injunctions are measured

Because § 42-3505.51(b) states no dollar figure, the damages a court assesses for breach of quiet enjoyment are tied to what the tenant can actually prove. In a single-entry case the provable harm may be modest, but the statute reaches conduct that is rarely a one-off: the inclusion of repeated unreasonable demands for entry as an independent trigger signals that the legislature was most concerned with patterns, where the cumulative interference with the tenant’s use of the home is the real injury. A tenant who documents a course of intrusions – dates, times, what was demanded, and how the household was disrupted – gives a court a concrete basis to value the breach rather than leaving it to a token figure. The injunctive half of the remedy is independent of damages: a court may order the housing provider to stop the behavior even where the past harm is hard to monetize, which is often the relief a tenant facing an ongoing pattern most wants. The two halves work together – an injunction to end the conduct and damages to compensate the interference already suffered.

The practical lesson for a housing provider is that the exposure scales with the pattern, not the politeness of any single visit. A provider who enters once, late, for a real repair faces little; a provider who repeatedly demands access, schedules around the tenant’s objections, or treats the 9-to-5 and 48-hour rules as suggestions builds exactly the record a court uses to justify both an injunction and meaningful damages. Every dated notice on file is a data point on the right side of that ledger, showing reasonable purpose, full notice, and timing inside the window; every undocumented or off-hours entry is a data point on the wrong side.

How the Consumer Protection Procedures Act multiplies exposure

The reason the entry remedy can carry more financial weight than its silent-on-damages text suggests is the overlay of the Consumer Protection Procedures Act, § 28-3905. The CPPA applies to trade practices arising from landlord-tenant relations, and where a pattern of unlawful or harassing entries can be characterized as an unfair or deceptive trade practice, the tenant is no longer limited to provable actual loss. The CPPA authorizes treble damages or $1,500 per violation, whichever is greater, plus reasonable attorney fees and injunctive relief. That structure changes the arithmetic of an entry dispute: a course of conduct that produced only small actual damages can still generate a meaningful award once each violation carries a $1,500 statutory floor, and the availability of attorney fees makes it economically feasible for a tenant to bring the claim in the first place.

It is important to keep the two statutes in their lanes. Section 42-3505.51(b) is the purpose-built entry remedy and the natural home for an over-entry claim; § 28-3905 is a separate consumer statute that reaches the conduct because the landlord-tenant relationship is a trade practice. A well-pleaded D.C. entry case often invokes the entry remedy for the injunction and quiet-enjoyment damages and the CPPA for the statutory-damages multiplier and fees, with the common-law theories of quiet enjoyment and trespass as background support. For the housing provider, the takeaway is not to fear the CPPA in isolation but to recognize that disciplined, documented compliance with the 48-hour and 9-to-5 rules removes the predicate conduct that any of these remedies needs to attach.

Because § 42-3505.51 makes reasonable notice a written requirement, the form of the notice and the proof that it was given are not afterthoughts – they are the substance of compliance. The statute is explicit that notice may be delivered electronically, including by email and mobile text message, which makes routine entry coordination convenient. But the same sentence attaches a condition that is easy to overlook: if the tenant does not furnish a written acknowledgement of the electronic notice, the housing provider must provide a paper notice. The electronic channel does not stand alone; it is paired with a paper backstop that the provider, not the tenant, is responsible for supplying.

The cleanest way to satisfy this is to treat the acknowledgement as the trigger. Send the electronic notice, and watch for a reply that confirms receipt – a returned text, an email response, or any writing in which the tenant acknowledges the notice. If that acknowledgement arrives, the electronic notice has done its job and the writing requirement is met. If it does not arrive within a reasonable time before the planned entry, the provider should follow up with a paper notice – personally delivered or posted – so that the 48 hours run from a notice the statute recognizes. Building this two-step into the standard workflow means a provider never has to guess whether an unacknowledged text was enough; the paper follow-up resolves it.

Recordkeeping flows from the same logic. For each entry, keep the notice itself, the timestamp showing it went out at least 48 hours ahead, any written acknowledgement the tenant returned, and – where the electronic notice went unacknowledged – the paper notice and proof of its delivery. Where the tenant agreed in writing to a shorter period or an off-hours time, keep that writing too, because it is the only thing that authorizes departing from the 48-hour or 9-to-5 default. For an entry that followed a tenant’s allegation of a housing code violation, keep the written access request and note the 48-hour window it started. This file is what answers a later claim under § 42-3505.51(b) or the CPPA: it shows reasonable purpose, written notice with the required acknowledgement-or-paper step, timing inside the statutory window, and a frequency no court would call harassment. The form on this page is built to generate the centerpiece of that file – a dated, signed written notice – for every entry a D.C. housing provider makes.

D.C. entry law is unusually self-contained: the duty and the remedy live in the same short statute, D.C. Code § 42-3505.51, with subsection (a) holding the definitions and subsection (b) holding both the operative rule and the remedy. But a complete picture of what happens when entry goes wrong reaches a few connected authorities – the Consumer Protection Procedures Act, the retaliation bar, the general covenant of quiet enjoyment, and D.C. common law. The table below collects the authorities that actually govern entry in the District so a housing provider can see where each rule comes from and avoid the common error of citing a municipal housing regulation, or an invented subsection, for a rule the Official Code states plainly.

Read together, these authorities tell a coherent story. The District legislated landlord entry, so the duty is statutory and concrete – reasonable purpose, reasonable time, and reasonable notice, with reasonable notice defined as at least 48 hours’ written notice and reasonable time defined as 9 a.m. to 5 p.m. excluding Sundays and federal holidays. Unlike some jurisdictions where the remedy hides in a separate chapter, D.C. keeps the remedy in the same section: § 42-3505.51(b) lets a court enjoin the conduct and assess damages for breach of the right to quiet enjoyment. A housing provider who reads only subsection (a) sees the definitions but misses the teeth in subsection (b); a tenant who reads only the definitions may not realize the same statute supplies the remedy.

A word on using this reference responsibly, because the entry area invites citation traps. The controlling authority is the D.C. Official Code section, § 42-3505.51 – not a municipal housing regulation, which is where guides often wrongly send a reader for a rule the statute already states. The remedy is subsection (b), not an invented later subsection like (d) or (e); the statute simply has no such subsections. The Consumer Protection Procedures Act remedy is § 28-3905, a separate consumer statute that happens to reach landlord-tenant practices, and retaliation is § 42-3505.02, a distinct protection – neither is the entry remedy, though both can run alongside it. On the common-law side, quiet enjoyment and trespass are background theories that support, but do not replace, the statutory remedy in § 42-3505.51(b). Any template that fills these gaps with a municipal regulation, a phantom subsection, or a remedy borrowed from another state is not making the page stronger; it is making it wrong.

None of this substitutes for advice on a specific situation. These authorities describe the general shape of D.C. entry law, but the outcome of any real dispute turns on the exact lease language, the facts of the entries, and how a particular D.C. court reads them. The official statute text on the D.C. Law Library portal is the best free starting point for both sides, and a qualified D.C. landlord-tenant attorney is the right resource when an actual conflict is on the table. Used alongside disciplined, well-documented notice, this form gives a D.C. housing provider a clean, defensible record for every entry – the most reliable protection the law actually allows.

A Washington, D.C. Notice to Enter is the written notice a housing provider or property manager gives a tenant before entering the rental unit. The District regulates entry by statute – D.C. Code §42-3505.51, titled Access by housing provider to dwelling unit – so the requirement lives in the D.C. Official Code, not in a municipal housing regulation and not in the lease alone. The statute lets the housing provider reach the unit for legitimate reasons while protecting the tenant’s right to quiet enjoyment, and it defines reasonable notice, reasonable time, and reasonable purpose so none of the three is left to argument.

The numbers to remember are 48 hours and 9-to-5. Reasonable notice means written notice at least 48 hours before entry – not a 24-hour rule – and shorter notice is allowed only if the tenant agrees in writing. Reasonable time means between 9:00 a.m. and 5:00 p.m., and not on a Sunday or a federal holiday, unless the tenant agrees to another time. The detailed walkthrough of how those two rules apply, including the written-agreement escape valve and the built-in paper fallback for electronic notice, is in the sections below.

This form lets you state the exact purpose, describe the work, list who will enter, and note whether the tenant’s presence is requested and how pets should be handled, so a routine entry stays documented rather than disputed. The body of this page covers the six reasonable purposes the statute lists, the emergency exception, showings and the code-violation access rule, what the lease can and cannot do, and – the part most guides get wrong – the tenant’s remedy. That remedy sits in the same statute: §42-3505.51(b) lets a court enjoin an unlawful entry or repeated unreasonable demands for entry and assess damages for breach of quiet enjoyment, and the D.C. Consumer Protection Procedures Act and the retaliation bar can apply on top of it.

For every routine entry, a dated, signed notice that meets the 48-hour written-notice rule and the 9-to-5 window is the simple, durable record that shows you followed §42-3505.51. Pair a consistent entry practice with disciplined tenant screening and a documented screening process so your Washington, D.C. tenancies are well-run from application through move-out.

• Entry only for a reasonable purpose – the six categories listed in D.C. Code §42-3505.51(a).
• At least 48 hours’ written notice of intent to enter; shorter only if the tenant agrees in writing.
• Entry only at a reasonable time: 9:00 a.m. to 5:00 p.m., not on a Sunday or federal holiday, unless the tenant agrees.
• Electronic notice (email or text) is allowed, but a paper notice is required if the tenant does not acknowledge it.
• A genuine emergency for the premises or persons’ safety excuses both the notice and the time rules.

• Personal delivery to the tenant.
• Posting on the door, alone or combined with email.
• Electronic written notice (such as email) with a paper fallback, as the statute allows.
• Certified mail for a documented record when the 48-hour timing allows.

• Citing a municipal housing regulation instead of the controlling Official Code section, §42-3505.51.
• Looking for the remedy in a phantom subsection (d) or (e); it is in §42-3505.51(b).
• Treating the lease as able to cut below the 48-hour or 9-to-5 floor without the tenant’s written agreement.
• Sending electronic notice and skipping the required paper notice when the tenant does not acknowledge it.
• Using repeated entry demands to pressure a tenant – the conduct §42-3505.51(b) lets a court enjoin.

• Default to at least 48 hours’ written notice and schedule entry within the 9am-5pm window.
• Avoid Sundays and federal holidays unless the tenant agrees in writing to another time.
• Use electronic notice with a paper fallback, and state the purpose, time window, and persons entering.
• Keep every signed notice on file for the life of the tenancy.

Published by Tenant Screening Background Check

Established 2004 · 20+ Years · All U.S. States & Territories · Statute-Based · Attorney-Reviewed

A Private Eye Reports™ service trusted by landlords, property managers, and attorneys.