No Charge Unexplained

Expectation. The building shall ensure that every charge is explained, every document is accessible, and every lifecycle deadline is communicated — so the resident never wonders what they owe, what applies to them, or what happens next.

Required.

• Every invoice includes itemized charges with plain-language descriptions. No line item is unexplained, abbreviated to a code, or labeled generically. The resident can understand what they are paying for without contacting staff.
• The resident has access to their lease, building rules, applicable certificates, and any other documents the building is required to provide — current versions, at any time, without contacting staff.
• When a lifecycle deadline approaches — lease expiry, renewal window, payment due date, notice period — the resident is notified through the primary interface with the deadline, the action required, and the consequences of inaction. The building publishes the lead time for each type of notification.
• When charges change — rent adjustment, service charge revision, new fee — the resident is notified through the primary interface with the new amount, the reason, the effective date, and the notice period. No charge changes without prior communication.
• When a document is updated — revised building rules, new certificate, amended lease terms — the resident is notified and only the current version is accessible. No resident acts on an outdated document because a superseded version was the one they found.
• When a payment fails — declined card, insufficient funds, processing error — the resident is notified through the primary interface with the reason for failure and the action required to resolve it.

Recommended.

• The building provides a payment history that the resident can export in a standard format — for tax purposes, financial records, or dispute resolution.
• When a service charge is levied, the building publishes the budget or cost basis that determined the charge — so the resident can see not just what they pay, but why.
• Pre-move-in communication includes a structured summary of what the resident needs to know before arrival: move-in logistics, credential activation, first invoice timing, key contacts, and building rules.

In practice.

A resident views their monthly invoice. Each line item is described: rent — unit 7B, service charge — building maintenance (breakdown available), parking — assigned space P-42, amenity access — included. The total matches what the resident expects. They did not need to call anyone to decode an abbreviation.

A resident's lease expires in four months. They receive a notification: lease expiry date July 31, renewal options available in the interface, response requested by June 1. Sixty days later, a reminder: renewal deadline in 30 days, current options still available. The resident reviews their options, selects a 12-month renewal, and confirms through the interface. They were not surprised by an expiry they had forgotten.

A new resident receives a pre-move-in summary one week before arrival: credential activation confirmed, parking space P-42 assigned, first invoice due April 1, building rules accessible in the interface, key contact for move-in day logistics. They arrive prepared.

The building revises its building rules to add a new noise policy for shared spaces. Residents are notified: building rules updated, effective May 1, see section 4.3 for changes. The interface serves the updated document. No resident is penalized under a rule they were not informed of.

A resident's autopay fails due to an expired card. Within hours, a notification appears: payment for April not processed — card declined, please update payment method by April 5 to avoid late fee. The resident updates their card and retries. They were not surprised by a late fee notice three weeks later for a failure they did not know about.

Failure modes.

Opaque invoice. Invoice line item: "Misc. charges — $47.50." The resident contacts the office. Three days for a response: "That's the amenity fee adjustment." The resident cannot determine what adjustment was made, on what basis, or why the amount changed from the previous month. The resident stops trusting the numbers because the numbers do not explain themselves.

Buried documents. A resident needs their lease to verify a clause about early termination. The lease was emailed as a PDF attachment 11 months ago. The building's interface has no document section. The resident searches their email, finds three versions, and cannot determine which is current.

Deadline ambush. The resident's lease expires in three weeks. No notification was sent. The office sends a renewal notice with a 10-day deadline and a rent increase. The resident intended to renew but is now considering leaving on principle. The building's failure to communicate early turned a renewal into a confrontation.

Stale document. The building updated its guest policy six months ago. The interface still serves the previous version. A resident follows the outdated rules and is told at the door that the policy has changed. The resident was compliant with the document the building provided. The building enforced a version it had not distributed.

Silent payment failure. A resident's autopay fails due to an expired card. No notification is sent. Three weeks later, a late fee appears on the next invoice. The resident did not know the payment failed. The building knew — the payment processor returned an error — but did not inform the resident. The first the resident heard of the problem was its financial consequence.

Test.

1. View an invoice. Confirm: every line item includes a plain-language description. No unexplained codes or generic labels.
2. View the document repository. Confirm: lease, building rules, and applicable certificates are accessible and downloadable without contacting staff.
3. Set a lifecycle deadline (e.g., lease expiry). Confirm: the resident receives notification at the building's published lead time with deadline, required action, and consequences.
4. Change a charge. Confirm: the resident is notified before the change takes effect with the new amount, reason, and effective date.
5. Update a document. Confirm: the current version is served in the interface and the resident is notified of the change.
6. Trigger a payment failure. Confirm: the resident is notified with the reason for failure and the action required.