A Landlord's Guide to Building Your Own Compliance Record (Without Buying Anything)

Most advice about landlord recordkeeping is either too abstract ("keep good records!") or a thinly veiled product pitch. This is neither. It's the actual mechanics of what to log, in what format, and why each piece matters — usable with a $0 budget and no new tools.

What Actually Makes a Record "Legally Credible" (Even Without Software)?

New York's business-records framework doesn't require a specific tool — it requires four properties: the record was made at or near the time of the event, it was made as a routine part of normal operations, making that kind of record is a regular practice (not a one-off), and it wasn't silently edited after the fact. A spreadsheet updated the same day an issue is reported and resolved meets all four just as well as expensive software does, provided it's actually kept up consistently.

What defeats a manual system isn't the medium — it's inconsistency. A log with three months of entries and then a two-month gap right before a dispute started is a much weaker record than a sparse-but-consistent one, because the gap itself becomes the story a hearing officer or judge notices.

The Five Things to Log for Every Maintenance Request

1. Date and channel received — when the request came in, and how (phone, text, in-person, portal)
2. What was reported — the tenant's description, as close to verbatim as practical
3. Your response — when you or your super first acted, and what that action was
4. Resolution — what was actually done, by whom, and when it was completed
5. Supporting evidence — a dated photo, a vendor invoice, or both, attached or referenced in the same entry

Every one of these five fields takes under a minute to fill in at the time it happens. Reconstructing them three months later, from memory, after a hearing is scheduled, takes much longer and produces a far weaker record.

A Simple Spreadsheet Template You Can Set Up Today

A single spreadsheet with one row per maintenance event covers most of what you need. Suggested columns: Date Reported · Unit · Channel · Description · Date Responded · Action Taken · Date Resolved · Vendor/Invoice # · Photo Link · Notes. Keep it in a shared location (a shared drive folder, not a personal laptop) so it survives a staff change, and back it up the same way you'd back up any other business record.

The format matters less than the discipline of filling in every row completely, the same day, every time — not just for the requests that seem like they might become disputes.

How to Log Access Attempts and Refusals (the Most Commonly Missed Piece)

Add a row every time you schedule a repair visit, whether or not it happens as planned: the date and time offered, whether the tenant confirmed, and the outcome — completed, rescheduled, no-show, or refused. This is the single most commonly missing category in landlord records, because a completed repair feels worth logging and a failed attempt doesn't, even though the failed attempt is often more important to the eventual record: an undocumented refused-access event simply doesn't exist later, and its absence can make a responsive landlord look unresponsive.

How to Handle Corrections Without Undermining Your Own Record

If you need to fix an entry — a wrong date, a typo in a unit number — don't delete or overwrite the original. Add a new row or a visible note: "Corrected 6/12: original entry listed wrong unit, should be 4B." A record with visible, timestamped corrections is more credible than one that looks untouched, because untouched can mean either "accurate from the start" or "edited without a trace" — and there's no way to tell which from the outside. A visible correction trail removes that ambiguity entirely.

What About Text Messages and Phone Calls?

Texts and calls are a normal part of landlord-tenant communication, but they're fragile as a standalone record — threads get deleted, phones get replaced, and a screenshot alone invites questions about whether it's complete or edited. If texts are a regular communication channel, the fix is simple: export or summarize relevant threads into your main log on a regular schedule (weekly is reasonable), rather than relying on the phone itself as the system of record.

How Long Should You Keep This Record?

At least six years is a reasonable baseline, roughly matching the general DHCR overcharge lookback period (verify current retention guidance for your specific situation, since requirements can vary and change). Compliance certificates — lead paint, window guards, boiler inspections — are worth keeping indefinitely rather than on any fixed schedule, since their relevance doesn't expire the way a routine maintenance ticket's does.

Where Manual Systems Break Down (And When That Starts to Matter)

A single building with one hands-on owner filling in a spreadsheet consistently can sustain this indefinitely — the discipline required doesn't scale with unit count on its own. Where manual systems tend to develop gaps is staff turnover (a new super who wasn't trained on the log format), multiple people logging into the same sheet inconsistently, and simple habit decay over months or years without anyone checking that entries are actually complete.

None of that is a software problem specifically — it's a consistency problem that software happens to help with by making the record a byproduct of doing the work rather than a separate task someone has to remember. If you're managing a handful of units yourself, the spreadsheet above, kept honestly, does the job. DERALO.AI exists for the portfolios where that consistency has already started to slip — it generates the same five fields automatically as maintenance requests, vendor dispatches, and access attempts happen, rather than relying on someone remembering to fill in a row.