Why RentCap paused paid Tacoma notice packets

What is clear

Tacoma's rental-housing guidance describes changes effective January 1, 2026, including a 180-day rent-increase notice, use of a city notice form, and relocation-assistance information for significant increases. Washington's statewide cap, first-year, form, and service rules also apply where the tenancy is covered.

The free checker can still calculate the statewide percentage, review dates, and identify the local relocation issue. That information has value to both sides as long as it is not presented as a complete Tacoma service packet.

What remains unresolved for automation

Tacoma materials associated with TMC 1.95 and TMC 1.100 describe overlapping local notice concepts. The sources reviewed by RentCap have not yielded a sufficiently clear, current answer about whether and how a second earlier notice must be served alongside the 180-day city-form path for every covered scenario.

That question affects when service must begin and what documents belong in the packet. Guessing the more convenient reading could cause a landlord to lose months and could give a renter a falsely clean result.

Why a disclosure alone is not enough

A disclaimer at the bottom of an automatically generated notice does not cure a known gap in the workflow. The product would still be taking money for a bundle whose central promise is a notice the user can print and deliver. The uncertainty belongs before payment, not inside the archive after checkout.

This is also why RentCap distinguishes a free informational check from a paid document. The calculation can be useful while the packet remains inappropriate. Users should not have to infer that distinction from a disabled button.

What Tacoma users can do now

Landlords can run the free check, open Tacoma's current city page and code, obtain the city's form, and ask the city or qualified counsel to confirm the required notice sequence for the property and proposed increase. Do not substitute a Washington-only notice packet for the local process.

Renters can compare the amount, effective date, city form, relocation information, and delivery evidence with the official materials. Preserve every notice because multiple documents and dates may be important to the sequence.

The standard for reopening checkout

RentCap will reopen Tacoma packet sales only after the current city authority supports a specific implementation and the packet, instructions, tests, and disclosures are updated together. The source and review date will be recorded in the changelog.

That is a narrower promise than saying the law will never change. The goal is traceable certainty about the product's current output. Until then, the pause is a product-quality control, not a claim that every Tacoma increase is unlawful.

How RentCap handles uncertainty elsewhere

The Tacoma decision reflects a general product rule: missing user facts are labeled as needs-facts, but a known gap in the product's legal implementation can disable the paid output. Those are different problems. The user can supply a certificate date; the user should not be asked to resolve contradictory source interpretation hidden inside the software.

Source review is also dated. A future Tacoma code amendment, formal city FAQ, administrative interpretation, or legal review could resolve the sequence and reopen the packet. When that happens, the change should be visible in the law timeline, changelog, tests, packet language, and readiness checks—not only in marketing copy or a checkout flag.

How to evaluate a future Tacoma update

A reliable update should cite the controlling city code and any official implementing guidance, identify its effective date, describe which properties and increases it covers, and explain the timing and contents of every required notice. It should also resolve how the city steps interact with Washington's form and service rules.

RentCap would then update the jurisdiction data, notice documents, delivery instructions, result copy, checkout eligibility, sample packet, and tests in one release. A manual toggle without those coordinated changes would reopen the same risk that caused the pause.

Users can monitor the public changelog and Tacoma guide instead of repeatedly testing checkout. The city source remains linked even while the packet is disabled. This approach keeps the free educational result useful and gives the eventual reopening a verifiable record rather than relying on a quiet product change.