A notice is more than a sheet of paper. It is the visible result of a chain of facts: the lease, the rent ledger, the reason for notice, the source used, the deadline calculation, the exact document delivered, and proof of delivery. When those records live in separate inboxes and phone galleries, even a correct notice becomes hard to explain. A notice evidence file keeps the chain intact.

The evidence-file rule: preserve the original inputs, the reasoning, the exact output, and every later change. Keep originals read-only; add dated updates rather than editing history.

The eight-part file

01Property and partiesAddress, owner/agent authority, tenant names, unit, program status
02Lease and amendmentsSigned agreement, renewals, addenda, notice clauses
03Ledger and triggerCharges, payments, allocation, event that supports the notice
04Rule researchStatute, court rule, local overlay, calculation worksheet
05Final noticeThe exact version delivered, locked after service
06Service proofWho, when, where, how, mailing record, photo, witness
07Post-service eventsPayments, messages, repairs, agreements, returned mail
08Index and chronologyOne-page timeline linking every important fact to a file

1. Property and party record

Start with facts that seem obvious but often appear differently across documents. Record the full street address, unit number, county, city, legal owner, management agent, every named tenant, and known adult occupant. Add the lease start date, current tenancy status, and any housing-program or property classification that may affect procedure.

Authority matters as much as identity. If a property manager signs or serves the notice, save the management agreement or written authorization showing the relationship to the owner. This avoids rebuilding the chain later from emails.

2. Lease, amendments, and the controlling clause

Save the entire signed lease, not only the page that appears relevant. Then create a short extract containing:

  • rent amount, due date, place and permitted methods of payment;
  • late-fee and additional-rent language;
  • notice addresses and delivery clauses;
  • default, cure, termination, and renewal provisions;
  • all addenda, amendments, concessions, and later written agreements.

Mark the extract with page and paragraph numbers. The extract is a navigation tool; the full signed agreement remains the evidence.

3. A ledger that explains itself

A useful ledger lets a reader reproduce the balance line by line. Separate rent from late fees, utilities, repairs, deposits, legal costs, and other charges. Use one row per event rather than overwriting a running total.

DateTypeDescriptionChargePaymentApplied toBalance
DATERentMonthly rent$AMOUNTMONTH$BALANCE
DATEPaymentOnline payment REF$AMOUNTMONTH rent$BALANCE
DATEFeeLate fee under lease ¶ X$AMOUNTSeparate charge$BALANCE

If the formal notice demands rent only, the file should make that amount independently visible. A mixed balance obscures what the notice actually asks the tenant to cure.

Include the seven-field research note from How to Verify a Notice Deadline and the calculation sheet from How to Count Notice Days. Save PDFs or screenshots of the source pages with the URL and access date visible. Web pages change; the file should show what was reviewed when the notice was prepared.

5. Freeze the exact notice served

Give every draft a clear status:

  • DRAFT-01 — working copy;
  • REVIEWED — checked against the source and ledger;
  • SERVED — exact copy delivered to the tenant.

After service, keep the served version read-only. If a mistake is found or circumstances change, create a new document with a new date. Editing the old file destroys the ability to show what the tenant actually received.

6. Service proof should answer six questions

Whoserved the notice?
Whatexact document was delivered?
Whendate and time?
Wherepremises, person, or mailing address?
Howpersonal, substituted, posting, mail?
Then whatmailing, photo, receipt, witness?

Preserve the signed service declaration, delivery log, mailing receipt, tracking record, returned envelope, contemporaneous photo, and witness details that fit the method. A photograph should show context and timestamp information where available; it should supplement the required service steps rather than replace them.

7. Start a post-service event log

Service does not freeze the facts. A payment, repair request, payment plan, returned notice, tenant response, or new agreement may change the next step. Use an append-only event log:

Date/timeEventSource fileEffect to review
DATE/TIMEPartial payment receivedPAYMENT-RECEIPT.pdfBalance and notice status
DATE/TIMETenant email disputes amountEMAIL-THREAD.pdfLedger and response
DATE/TIMEMail returnedRETURNED-ENVELOPE.jpgService sufficiency

Record the event before deciding its legal effect. Facts and conclusions belong in separate columns.

8. Build a one-page chronology

The final index should let a reviewer understand the matter in two minutes. List the lease date, rent due date, payments, notice preparation, source check, service event, response deadline, later communications, and current status. Link each entry to a file name.

YYYY-MM-DD — Rent due. See LEDGER.xlsx, row 18.

YYYY-MM-DD — Official source reviewed. See RESEARCH-NOTE.pdf.

YYYY-MM-DD HH:MM — Notice personally served. See SERVICE-DECLARATION.pdf.

YYYY-MM-DD — Calculated response deadline. See DEADLINE-WORKSHEET.pdf.

File naming and privacy

Use sortable names such as 2026-08-04_NOTICE_SERVED.pdf. Keep working records in access-controlled storage, encrypt backups, and avoid placing tenant records in shared folders used for marketing or general property photos. Retain only the personal information needed for the documented purpose and follow applicable retention rules.

Source examples for service documentation

Practical goal: a well-built file shows what happened, what source was used, what was delivered, and how every date was calculated. The notice workspace can generate the draft and a service-record worksheet; the evidence file preserves the surrounding proof.