District of Columbia Unemployment Calculator

D.C. is a one-number state. Other programs average two quarters or apply a percentage to your whole wage record; the District takes the single quarter in your base period where you earned the most and divides it by 26. The statute — D.C. Code § 51-107(b)(1) — describes it as one twenty-sixth of the wages paid in your highest quarter, computed to the next higher dollar.

The division happens before the clamp. Say your best quarter produced $12,480: twelve thousand four hundred eighty divided by 26 is $480, which is above the ceiling, so DOES pays $444 and the extra $36 a week evaporates. On the other end, a $900 quarter divides to $34.62 and rounds to $35 — below the $50 floor — but $900 also fails the $1,300 entry test, so the claim never starts. The floor and the gate work together.

One more ceiling hides inside the formula. To be paid the full $444, your highest quarter must reach $11,544, because $11,544 ÷ 26 is exactly $444. DOES states the same figure in its benefit fact sheet. Below that, every dollar of additional best-quarter wages converts into about 3.8 cents of weekly benefit.

The 1.5× test is strict, but D.C. wrote a shock absorber around it. If your total base-period wages fall short of one and one-half times your best quarter by $70 or less, DOES approves the claim anyway and adjusts the weekly rate instead: a shortfall of $35 or less cuts the benefit by $1 a week, and a shortfall between $35 and $70 cuts it by $2 a week (§ 51-107(c)(2)).

The table shows where the rule activates. The “1.5× floor” column is the total you would need to pass outright; the safe zone reaches exactly $70 below it.

The District’s maximum went from $432 to $444 on January 5, 2020, and it has not moved since. The statute hands the decision to the DOES Director, who must weigh any increase in the Washington-area Consumer Price Index against the health of the District Unemployment Compensation Trust Fund (§ 51-107(b)(3)). A Director facing a thin fund can lawfully freeze the cap, and every year since 2020, that is exactly what has happened.

The result is a strange inversion. The District pays one of the higher top weekly benefits in the country, yet it has the highest average wages of any U.S. jurisdiction — private-sector pay averaged about $2,024 a week in 2026 federal wage data. Divide $444 by that paycheck and the cap replaces roughly 22 percent of an average D.C. salary, among the weakest replacement rates in the nation. The number looks generous next to Mississippi’s $235 and skimpy next to the rent in Shaw or Navy Yard.

For claimants, three practical rules follow. First, budget around $444 as a hard ceiling — no dependent add-on or training bonus lifts it. Second, if your best quarter exceeds $11,544, every extra dollar earned that quarter is money the formula cannot see. Third, remember the cap applies to the dependent’s-allowance era no longer; nothing stacks on top.

Since September 5, 2021, District law imposes a one-week waiting period at the front of every claim. The waiting week is the first week for which you would otherwise be eligible — in practice, the first week of your claim — and no payment is made for it. It is not reimbursed at the end the way some states credit it back, either. The week simply costs you one check.

Two mistakes turn the waiting week into a longer delay. The first is skipping the certification for that week because you assume there is nothing to certify; the week cannot serve as your waiting week unless you file for it, so your paid weeks slide back another week. The second is assuming the waiting week applies only to new claimants — it applies to every new benefit year, including reactivated claims after a return to work.

Price it out with Amara’s numbers: the waiting week withholds one $390 payment, effectively reducing the first benefit year’s take-home from $10,140 to $9,750 even though the “26 × weekly” arithmetic still defines her total award. Financial planners call this the silent haircut; DOES calls it the waiting period.

Older guides still promise a dependent allowance in the District. Here is the current truth. The original statute paid $5 a week for each dependent relative, up to $20 — and the same statute repealed that provision for benefit years beginning on or after January 5, 1997 (§ 51-107(f)). A temporary replacement, $15 per dependent up to $50, applied only to claims with benefit years starting between August 9, 2009 and January 1, 2011, a recession-era experiment recorded at § 51-107(f-1).

Today, no subsection revives it. A claimant supporting three children and a claimant supporting no one receive the same weekly amount if their wage records match. It is worth knowing because third-party sites keep recycling the $5 or $8 figures from stale pages, and planning around a phantom $20 can wreck a household budget.

The calculator above mirrors reality: there is no dependents input, because entering one would only manufacture an expectation DOES cannot pay. If the District ever restores the allowance, the change will arrive as an amendment to § 51-107 and this page will show it.

The District retired phone filing for initial claims. DOES no longer accepts a first-time unemployment claim through its contact center — a security decision, announced with the rollout of single-sign-on identity checks. Every new claim starts at does.dcnetworks.org under the “Claim Unemployment Benefits” tab.

Since September 4, 2025, logging into DCNetworks and the Unemployment Insurance Benefits System runs through ID.me single-sign-on with multi-factor authentication. One credential set covers both systems. If you already hold an ID.me account from the IRS or Social Security Administration, it works here; if you lose the password, ID.me support resets it — DOES cannot, a fact the agency repeats because lost credentials used to flood its phone lines.

DOES requires every claimant to complete at least two work-search activities each week they claim benefits, alongside registration in the DCNetworks employment services. The rule, reinstated as pandemic flexibilities ended, applies from the first claimed week — there is no grace period while you “wait for something to turn up.”

Activities that count are concrete: applying for a specific job with an identified employer, interviewing, attending a DOES-sponsored reemployment workshop, or registering with a hiring event through the District’s American Job Centers. Scrolling a job board without applying does not count, and neither does repeating one application to the same employer week after week.

Keep a log with dates, employer names, contact methods, and outcomes. The audit horizon is long — DOES can request your records months after a week was paid, and a claimant who cannot reconstruct two activities a week can be ordered to repay the benefits those weeks carried. A spreadsheet or even a dated notes app satisfies the requirement; memory alone does not.

Two income streams reduce a D.C. benefit, and both are written into § 51-107. The first is retirement income: a pension or annuity from any employer in your base period — contributed to or provided by that employer — prorates against your weekly benefit for the weeks it covers. The statute carves out Social Security title II explicitly, so retirement benefits you funded through FICA do not touch the check.

The second is dismissal money: wages in lieu of notice, defined as separation payments the employer was not legally required to make. A negotiated severance is the classic case. It offsets benefits during the weeks it covers, which is why the filing checklist asks for severance details up front — reporting it late converts a smooth claim into an overpayment case.

Neither offset changes your weekly benefit amount itself; DOES reduces what it pays for the affected week and, for pensions, applies the same reduction against your total award. The structure matters at tax time too, because the offsets change the 1099-G figures your return will show.

An overpayment notice usually starts with a wage mismatch: earnings reported late, severance disclosed after the fact, or work-search records that cannot be produced on request. DOES reconciles certifications against employer filings each quarter, so the gap surfaces on the agency’s timetable, not yours — often months after the week was paid.

Identity fraud runs the other direction, with someone filing under your Social Security number. The remedy is speed: report it through DOES’s Prevent Fraud channel, keep the confirmation, and flag the 1099-G that arrives for benefits you never received so your taxes are not computed on phantom income.

If the notice is real, respond rather than ignore. Repayment schedules and, in some cases, waivers exist for non-fraud overpayments; silence only adds collection steps. And if the notice itself is wrong — the agency miscounted your earnings — the 15-day appeal window described above applies to that determination too.

The standard 26 weeks is the floor program, and federal law layers an emergency valve on top. Extended Benefits (EB) pays up to 13 additional weeks when the District’s insured-unemployment rate crosses the statutory triggers defined at § 51-107(g) — an “on” indicator switches the extra weeks on, and a matching “off” indicator turns them off. In the 2026 economy those triggers are dormant, but the machinery is permanent, and it activated in both of the last two recessions.

Shared Work runs in the opposite direction: instead of extending benefits after a layoff, it prevents the layoff. Employers enroll and, in place of cutting staff, reduce hours across a team; affected workers collect partial benefits for the lost fraction of their week. For claimants it feels like the 66 percent rule with an employer-side agreement attached, and it keeps work histories intact.

Neither program requires action now. But both change the arithmetic mid-claim — EB adds weeks, Shared Work changes the weekly deduction — so revisit this section if your employer mentions “work sharing” or if the news reports an EB trigger for the District.