Legal boundary: this guide is not legal advice or a substitute for local notice instructions. Rules can determine who must receive a repair request, how it must be sent, and what information it must contain. A saved copy can help organize a record, but it does not by itself establish that notice was legally sufficient.

Save every stage of the request

A useful maintenance request record shows the whole exchange. Keep the stages together, but do not relabel one stage as another.

  1. Request input. Before sending, save the exact text, date, unit or location description, contact details, and repair requested. If the portal does not offer a draft download, make a readable copy before selecting submit.
  2. Attachments. Keep the original photos or documents you attached, plus a simple list of their file names. Do not rely on portal thumbnails as the only copies.
  3. Confirmation or ticket. Save the full confirmation screen, email, message, or ticket number. Record the channel and the time shown. If no confirmation appears, note that fact instead of inventing a delivery status.
  4. Status history. Preserve later status changes with the date you observed each one. Labels such as “open,” “scheduled,” or “closed” describe what the system displayed; they do not establish the condition of the home.
  5. Replies and visits. Keep management replies, appointment messages, entry notices, work-order details, and a factual note of calls or visits. Preserve attachments and message headers when available.
  6. Closure and what followed. Save any closure message, then separately record what you observed after the visit or repair. If a condition returns, preserve it as a new occurrence instead of overwriting the earlier record.
  7. Exported copy. Download or print a complete, readable copy of the request and history while you still have access. Open the exported file and check that long messages, attachments, dates, ticket numbers, and status entries were not cut off.

Label screenshots for what they show

A screenshot is a display record: it shows what was visible on a screen when the image was made. By itself, it does not prove that a recipient received or read the request, that every statement is true, or that the request satisfied a legal notice rule.

  • Capture enough of the screen to identify the portal, request or ticket, relevant status, and displayed date when those details are available.
  • Keep separate screenshots when a page scrolls. Do not stitch them together in a way that hides gaps or changes the order.
  • Retain the original screenshot. If you crop or mark a copy for explanation, label the edited image and preserve the original separately.
  • Pair a screenshot with stronger channel records when available, such as a confirmation email, sent-message copy, certified-mail record, or full portal export.
  • Describe uncertainty plainly: “confirmation displayed,” “status viewed,” or “reply received” is more accurate than an unsupported claim that legal notice was completed.

Keep a copy beyond the phone or portal

Phones are lost, damaged, replaced, or reset. Property managers can change systems, and an old portal can become unavailable after an account, landlord, or tenancy changes. Export important records while the account works rather than assuming the portal will remain your archive.

  • Move texts, emails, voicemails, attachments, and portal downloads into a clearly named case folder you can still reach if the originating device fails.
  • Keep at least one protected copy separate from the phone or computer used to submit the request. Choose storage and access controls appropriate for the private information involved.
  • Use descriptive names that do not change the underlying file, such as a date, request number, record type, and short location label.
  • When a portal migration is announced, export before the cutoff and again after migration if the new system carries history forward. Keep both copies and note when each was obtained.
  • Review a shared copy before sending it. Remove unrelated private data only from a derivative copy, and keep the source record unchanged.

Privacy boundary: this static website has no form, account, tracker, or evidence upload. Do not submit tenant data through the project’s public GitHub pages or issues. Habitable’s current evaluation materials use synthetic records only.

Organize without rewriting the source

Keep source records as received, then add a separate index or chronology. The index can make a long exchange easier to review without pretending that your summary is the original.

  • List the event date separately from the date you saved or entered it.
  • Identify the source: tenant-created request, portal-generated confirmation, management reply, contractor message, or personal observation.
  • Use the same request or ticket identifier across related files when one exists.
  • Record missing stages explicitly—for example, “no confirmation displayed” or “portal export did not include attachments.”
  • Keep private originals separate from a smaller copy prepared for a particular recipient.

Recordkeeping sources and jurisdiction limits

The following resources support the general practice of keeping communications and copies. Their legal guidance is jurisdiction- or context-specific, so check current local instructions before relying on a communication method.