Property record

Nobody can delete a property.

The property is the root, and it is not defined by who is attached to it right now. Owners, managers, tenants and vendors are relationships, each with its own period and authority. They begin and they end. The record they were attached to does not.

Permanent identifier

YU-PROP-4K2M9X01

Created 2019 · never deleted

People attached and detached · the record did not move

  • Owner2019 — 2023

    M. Alvarez

  • Owner2023 — now

    Rivera Holdings

  • Manager2019 — 2022

    Coastal PM

  • Manager2022 — now

    Harbor Group

  • Tenant2020 — 2023

    J. Okafor

  • Tenant2023 — now

    D. Sousa

6

Relationships

4

Already ended

1

Record

The root

People are relationships, not fields.

In most systems the owner is a column on the property row. Change the owner and the previous one is simply gone, along with the reason anything was decided while they were there. Here each participant is a relationship with a start, an end and an authority of its own — which is why a handoff loses nothing.

  1. 01

    It cannot be deleted

    No owner, manager, tenant, vendor or team member can destroy a property record. A relationship can end. The record it was attached to does not end with it.

  2. 02

    The identifier never returns

    Every property carries one permanent identifier. When a relationship ends the identifier is not recycled into the next property, so an old document can never point at a new building.

  3. 03

    A signed document is closed

    Once a document is signed or filed it becomes immutable. Replacing it marks the old version and links the new one to it, and every earlier version stays reachable.

  4. 04

    A correction adds, never rewrites

    Fixing a record writes a correction on top of it. The earlier state stays visible, because a history that can be quietly edited is not evidence of anything.

What hangs off it

Everything files itself against the unit.

Not against a thread, a folder or a person. That is the whole difference between a record you can trust in four years and a search through an inbox.

Applications and criteria

Versioned rental criteria, versioned submissions and review actions, plus delivery evidence for the decision that was actually sent to the applicant.

Screening and its charge

The screening fee charged through Stripe stays tied to the application it paid for, so a cost on the statement always has a reason attached.

Move-in condition

The move-in inspection and its checklist live on the unit, which is what makes a deposit conversation two years later a matter of record instead of memory.

Appointments

Property appointments, arrival windows and the Google Calendar sync behind them, recorded against the unit rather than a personal calendar.

Work orders and evidence

Service awards, the vendor commercial chain and the completion evidence photographed on site, filed where the next person will look for them.

Photos and documents

Unit photos, lease packets, notices and invoices. The document belongs to the property, not to the inbox of whoever happened to send it.

A detail that shows the rest

8am means 8am at the property.

A property carries its own authoritative timezone. Not the state it sits in, and not the timezone of whoever happens to be looking at the screen. If the address cannot be verified, the property is saved as a draft and a timezone-dependent appointment simply cannot be confirmed yet.

It would be easier to guess from the state and move on. That guess is how a vendor arrives an hour late to a building nobody warned, and how a notice deadline lands on the wrong day.

Resolved timezone

America/New_York

  • Verified from the address, not the state
  • Never replaced by the viewer device timezone
  • Unverified address stays an explicit draft
  • No appointment is confirmed on a guess

It is yours to take

A record you cannot get out is a hostage.

Three separate things, because a summary, the underlying files and a temporary download are not the same object and should not share a lifecycle.

A filtered report

A history report is a summary built to a filter — what happened, over a period you choose.

The source files

An evidence package is separate on purpose: it selects the permitted source files themselves, not a description of them.

A download that expires

The prepared file is a third thing with a short life. When it expires, nothing in the record expires with it.

Even after you leave

A departing tenant can export their own tenancy records, an incoming owner can request the prior history, and a former owner can still take theirs.

The notification that your package is ready carries no attachment, no download link, no signed URL, no file list and no property detail. An email is not a safe place to put any of that, so it does not go there.

Authority stays separate

Anyone can report a problem. That is not the same as closing a property.

A manager, a co-owner, a vendor and the tenant can all report an error, a duplicate, a fraud concern or an unauthorized record. None of that grants the authority to close the property, which stays with the verified primary owner alone. Two acts that look like one, kept apart on purpose.

Report a concern

Open to the manager, team member, co-owner, tenant, vendor and payer. It reaches Yellow review and never touches ownership authority.

Request closure

The verified primary owner, and nobody else. Closing is a decision about the asset, not a reaction to a complaint about the record.

Early access

Give the building a memory it keeps.

Start with one property. The record begins the day you add it, and it does not depend on anyone staying.