14.2 Policies, Records, Inspections & Control Logs

Policies and procedures do different work

A policy states the organization's rule or decision boundary: for example, who may approve a rent adjustment. A procedure translates the policy into steps: required form, supporting evidence, system role, approval sequence, posting, resident communication, and review. A checklist can support the procedure but should not silently create a conflicting rule.

Every controlled document should identify title, owner, approving authority, effective date, version, superseded version, affected roles, and next review. Store the current version where employees can find it. Archive old versions so the property can show which rule applied at a historical date, but prevent accidental daily use.

Review is triggered not only by a calendar but also by law or contract changes, audit findings, incidents, new systems, ownership transitions, and recurring exceptions. Communicate changes and verify training before expecting compliance. Emergency interim instructions should name the authority, scope, start and end point, and later formal review.

Design an executable procedure

Map the process from trigger to closeout. Identify inputs, responsible role, approval, system of record, deadline, output, exception route, and evidence. Test the procedure with the people who perform it. A control that cannot be completed during actual operating conditions invites workarounds.

Separate mandatory steps from guidance. Build in checkpoints at the highest-risk moments: identity verification before releasing a key, authority confirmation before a concession, independent verification before changing vendor banking, inspection before paying final construction retainage, or accounting review before closing the month.

Exceptions need control, not concealment. Record why the normal process could not be followed, who authorized the deviation, temporary safeguards, and how the exception was resolved. Trend repeated exceptions; they may show that the procedure, staffing, system, or training needs correction.

Records and information governance

Property records include leases, applications, screening and accommodation files, notices, payments, invoices, contracts, inspections, work orders, communications, incident reports, insurance records, employment records, budgets, financial statements, and owner approvals. Classify them by sensitivity and business function. Use least-privilege access and separate especially sensitive medical, consumer-report, banking, personnel, and credential data.

A retention schedule is not one universal number. It must account for federal, state, and local law; tax and employment requirements; affordable-program rules; insurance and lender conditions; contracts; limitation periods; and client policy. When litigation, investigation, audit, claim, or subpoena is reasonably anticipated, issue and follow the applicable legal hold even if normal destruction is due. Authorized disposition should be secure and documented.

Maintain authenticity and searchability. Use consistent naming and property identifiers, preserve required metadata and approvals, prevent unauthorized editing, back up critical records, test restoration, and control exports. Personal devices, shared passwords, and unofficial messaging can create missing or exposed records.

Inspection programs

An inspection is a defined observation process, not proof that no hidden defect exists. Types can include move-in/move-out, common-area, unit, preventive, life-safety, accessibility, housekeeping under a valid program, contractor, capital-project, insurance, and regulatory inspections. The manager should identify purpose, scope, frequency, competent inspector, notice and entry authority, checklist or standard, evidence, and escalation.

Comply with lease and jurisdictional entry rules except where lawful emergency access applies. Apply inspection programs consistently and avoid selecting units or residents for discriminatory reasons. Respect resident dignity and photograph only what is relevant, with secure storage and documented context.

Classify findings by consequence and urgency:

• immediate danger or active damage requires scene control and emergency response;
• legal, code, or essential-service issues require prompt qualified correction;
• conditions likely to worsen need scheduled priority;
• routine wear or improvement may enter normal work or capital planning.

Assign each corrective action an owner, due date, budget or work order, and required proof. Closure requires verification, not simply changing status to “complete.” Reinspect when consequence or scope warrants it.

Control logs

Useful logs may track keys, access credentials, certificates of insurance, contracts and notice dates, licenses, inspections, preventive maintenance, incidents, accommodations, capital commitments, checks, deposits, refunds, and legal deadlines. A spreadsheet is not automatically a control. Define who enters data, required fields, edit rights, source reconciliation, review frequency, overdue escalation, and archive.

Example: a key log should identify the controlled key, issuance and return, authorized person, date/time, and exception. Periodically compare the log with physical inventory and access-system records. A signed line does not solve a missing master key; the exception must be escalated and mitigated.

Transitions and continuity

At management or staff transition, inventory funds, keys, contracts, resident records, open work, deposits, bank authority, permits, claims, passwords through approved transfer methods, and pending deadlines. Use a signed transfer checklist and reconcile totals. Revoke departing access and preserve records. Never delete unfavorable records to make a transition appear clean.

Exam approach

Prefer the response that uses an approved current procedure, preserves evidence, grants only necessary access, documents exceptions, assigns correction, and independently verifies closure. A record that exists but is inaccurate, inaccessible, or unreviewed does not satisfy the control.