How to Document a Rental Repair Request: Dates, Messages & Follow-Ups

A repair problem is much easier to review when the history is not scattered across memory, texts, calls and a maintenance portal. The goal is simple: keep a dated record of what happened, what you reported, how the landlord or manager responded and what is still unresolved.

That record can help you communicate clearly and reconstruct the sequence later. It does not tell you which notice method satisfies local law or how quickly a landlord legally has to act. Those rules depend on your lease and jurisdiction.

Keep the original message, not just a summary

For every repair request, keep the actual message when possible and add a short entry to your log.

Email. Save the sent message and any reply. The timestamp makes it easy to place in a chronology.

Text message. Keep the conversation or export/screenshots where practical. Whether a text satisfies a formal notice requirement depends on local rules and the lease.

Letter. Keep a copy of what you sent and any delivery record you chose to use.

Portal or maintenance ticket. Save the confirmation number or screenshot. Access to a tenant portal may disappear later.

Phone call or in-person conversation. Log the date, who you spoke with and what was said. A verbal conversation is still part of the history even when it is not a written message.

The important distinction is between what you can verify and what you only remember.

The date is an organizational reference point

The GentleTools Repair Request Log can count elapsed days from a written-message date. That is useful for follow-up planning, but it is not a legal deadline calculator.

Its built-in 2-, 14- and 30-day priority points are simply reminder intervals:

Priority	Reminder point	What it means
High	2 days	Bring the unresolved item back to your attention quickly
Medium	14 days	Prompt a follow-up on an issue you do not want to lose in old messages
Routine	30 days	Keep a lower-priority unresolved item visible over time

A local law, lease or housing program may use completely different rules — or no fixed number at all. Treat the reminder as your own workflow setting, not a statement of legal entitlement.

What to write down each time

A useful repair entry is short and factual. Capture:

1. Date — when the event happened.
2. Channel — email, text, call, portal, visit or letter.
3. Person — who you communicated with, if known.
4. What happened — the observable event.
5. What was promised — including any date or next action.
6. What remains open — if the issue was only partly resolved.

For example:

Oct 14 — called office 2:15pm, spoke to Dana. Dana said a plumber would come Thursday the 17th.

Oct 18 — no visit on Thursday. Sent an email asking for a new date.

This is more useful than “called again, still nothing” because someone reviewing the log later can see the sequence without guessing.

Keep observations separate from conclusions

Write what you can directly describe:

• “water runs cold after about 30 seconds”;
• “contractor did not arrive”;
• “photo taken after the ceiling stain expanded”;
• “manager said the part was ordered.”

Avoid using the log itself to declare that a law was violated, a unit was legally uninhabitable or a particular remedy is available. Those conclusions may require local rules or professional advice.

If the earlier history was never documented

Do not invent precision you do not have. Reconstruct what you remember and label it as reconstructed. Keep verified dates separate from approximate ones.

If you send a new written summary, save a copy and log the date. That creates a documented reference point going forward without pretending it changes the legal status of earlier conversations.

When the issue becomes more than recordkeeping

A tracker can organize facts, but it cannot tell you whether to withhold rent, use repair-and-deduct, terminate a lease, file a formal complaint or start a court case. Those options vary by jurisdiction and can carry serious consequences if used incorrectly.

Before taking legal or financial action, check current local tenant guidance, legal aid, a tenant organization or another qualified local source.

If the situation involves immediate safety, health or security concerns, use the appropriate emergency, housing or professional channel rather than waiting on a reminder inside a browser tool.

Keep the record after the repair

A completed repair can still be useful context later. Keep the chronology, original messages, dated photos, receipts and any inspection or contractor records in storage you control.

At move-out, consider keeping a separate dated condition record and the correspondence required by your lease or local rules. The repair log can support your own memory of what happened, but it should not be the only copy of important evidence.

Questions renters ask

Does a text message count as written notice?
That depends on your lease and local law. For recordkeeping, save a dated copy of whatever you sent and, when practical, use a method that lets you show the content and date.

I have been discussing the problem for months but never kept a written record. What now?
Reconstruct the history honestly, marking approximate dates as approximate. Save any new written message and use that as a documented reference point in your own chronology.

Can I stop paying rent until it is fixed?
Do not rely on a generic article or tracker for that decision. Rent withholding, escrow and related remedies vary by jurisdiction. Check current local guidance or legal aid before acting.

How long does a landlord have to repair something?
There is no reliable national answer. The applicable lease, local law, issue type and circumstances can all matter. The reminder intervals in GentleTools are organizational only.

Should I contact a housing or inspection authority?
That depends on the issue and what services exist where you live. If you do contact one, keep the date, reference number, response and any inspection record in your chronology.

Keep the workflow in one place

Start with the free Repair Request Log when you mainly need one repair timeline with messages and follow-ups.

If the situation grows into several repairs, evidence references, out-of-pocket costs, access attempts and multiple open follow-ups, TenantNest keeps those records connected in one private local-first file.

You can compare the full path — free tools, practical guides and focused offline apps — in the Private Record Tools & Apps hub.

Recordkeeping aid only, not legal advice. Tenant rules vary by jurisdiction; verify local requirements before taking legal or financial action.