Occupation manual 008 / Property operations

Prepare the handoff. Keep rights, safety, money, and messages human.

A proof-first operating route for property inquiries, hazards, work orders, inspections, vendors, governing documents, resident drafts, budgets, and incidents—without turning an AI summary into authority.

Short answer: let AI prepare evidence, not decide outcomes. Preserve the reporter’s exact words, open every applicable safety/rights/privacy/legal/vendor gate in parallel, cite the controlling property and jurisdiction sources, prepare the exact scope or message, and stop at approval_ready.

One intake can activate several gatesA water leak can also be an electrical hazard, accessibility request, insurance event, access issue, vendor job, budget variance, and resident communication. Never collapse those jobs into one opaque AI priority score.

Six parallel gates protect the operation

Route immediately

  • life safety and emergency-plan indicators
  • fair housing, accommodation, assistance-animal, VAWA, harassment, or retaliation sensitivity
  • restricted personal, applicant, resident, survivor, employee, or vendor data

Verify authority before work

  • lease, governing document, program, and jurisdiction
  • vendor scope, credentials, access, payment, and change control
  • routine operations, evidence requirements, and closure authority

Build the ten-part Property Operations & Resident/Vendor Handoff Desk

01

Load the authority card

Name the property/entity, jurisdictions, programs, governing documents, emergency plan, approval matrix, reviewers, retention rule, and approved systems. Conflicting or missing authority blocks action.

Output: property authority card
02

Preserve intake without judgment

Keep the exact statement, timestamp, channel, location, attachments, access/contact needs, staff paraphrase, and AI summary separate. Do not infer identity, motive, fault, urgency, or credibility.

Output: intake and parallel-gate record
03

Open the emergency and rights routes

Display the approved emergency plan for defined hazards. Route housing-rights, accommodation, assistance-animal, VAWA, screening, harassment, and retaliation signals to trained reviewers with no AI recommendation.

Output: safety and sensitive-request handoffs
04

Build the work-order evidence chain

Link the report to verified condition, priority authority, access permission, approved scope, worker/vendor, arrival log, changes, before/after evidence, completion test, acknowledgment, and follow-up.

Output: evidence-controlled work order
05

Record inspection and remediation

Cite the standard and version, inspector qualification, observed condition, evidence provenance, response-time source, repair plan, proof, reinspection, and closure approver. Never generalize a program-specific standard.

Output: inspection/remediation card
06

Freeze vendor and payment changes

Verify legal identity, credentials, insurance, scope, safety/access limits, resident-data limits, quote, change-order authority, completion proof, warranty, and invoice. New banking or contact details reset payment to blocked.

Output: vendor handoff and payment lock
07

Draft, review, and bind communications

Separate verified facts from pending items, flag promises and legal/safety issues, classify attachments, record accessibility/language needs, and bind approval to the exact payload. There is no send control.

Output: resident/vendor/board review card
08

Keep documents controlling

Version leases, governing documents, policies, resolutions, budgets, reserves, insurance, warranties, permits, inspections, contracts, and legal guidance. AI summaries remain convenience views.

Output: document and decision ledger
09

Separate arithmetic from money authority

Reconcile approved budget, commitments, invoices, payments, remaining amounts, restrictions, quotes, assumptions, reserve references, and required approvals. Calculation never becomes authorization.

Output: budget/reserve decision packet
10

Preserve incidents and exact approvals

Use an append-only timeline for observations, authorized protective actions, handoffs, restricted information, notices, recovery, drafts, and after-action findings. Bind the requested decision, scope, recipient, amount, approver, expiry, and rollback.

Output: incident timeline and approval packet

Give AI bounded clerk jobs

Clerk jobMay prepareMust never decideHuman gate
Intake clerkTranscript, fields, missing evidence, parallel flagsUrgency, credibility, fault, protected statusAuthorized operations reviewer
Work-order clerkScope draft, evidence checklist, status reconciliationEmergency action, access, dispatch, safe closureManager and qualified safety/technical reviewer
Document clerkClause extraction, versions, conflicts, expiry flagsLease/legal interpretation or enforcementDocument owner or qualified counsel
Vendor clerkCredential/source checklist, quote comparison, change logAward, engagement, access, bank change, paymentOwner/board/procurement/payment authority
Communication clerkDraft from verified facts and approved templateNotice, promise, admission, denial, demand, sendAuthorized sender and specialist reviewer
Budget clerkArithmetic, variance flags, packet assemblyFunding choice, transfer, assessment, approvalBoard/owner/accounting authority

Evidence states prevent false closure

Use explicit states: reported_unverified, observed_by_staff, verified_document, qualified_inspection, vendor_statement, resident_statement, approved_decision, completed_with_evidence, disputed, and uncertain.

An AI summary never upgrades evidenceAn invoice does not prove completed work. A photo does not establish code compliance. A resident statement does not establish fault. A “done” message cannot close safety-critical work without the required verification.

Program-specific rules stay in scope

Useful, with limits

HUD NSPIRE offers a health, safety, function, and deficiency vocabulary for covered HUD contexts. EPA lead rules create review paths for potentially covered pre-1978 work. CAI sources describe industry practices for associations, contracts, budgets, reserves, and continuity.

Never universalize them

NSPIRE is not a universal property code. CAI guidance is not law. VAWA coverage and procedures depend on the program and facts. Federal material does not replace state/local law, governing documents, qualified inspections, counsel, or emergency authorities.

Payment changes start over

Any new bank account, remittance address, contact channel, urgent invoice, or payment procedure resets the payment state to blocked. Verify out of band with a known contact and obtain the required dual approvals. Never rely on the contact details inside the change request.

Use this prompt for private preparation

Act as a property-operations preparation clerk, not a property manager, emergency authority, housing-rights decision-maker, lawyer, inspector, vendor, approver, payer, or sender.

Using only the supplied approved records, preserve the exact intake separately from paraphrase and AI summary. Open every applicable gate in parallel: life safety, fair housing/accommodation/VAWA, privacy, lease/governing document, vendor/payment, and routine operations. Create the authority card, evidence-state table, missing-information list, work-order or incident packet, exact draft communication, source ledger, and approval packet.

Do not infer protected status, fault, motive, urgency, legal meaning, code compliance, or payment authority. Do not send, dispatch, grant access, sign, pay, file, post, change an account, or use restricted data in an unapproved system. Stop at approval_ready.

Final review before any handoff leaves the desk

Official source desk

Prepare one synthetic property handoff before using real records.

Test the desk with a fictional common-area leak near an electrical fixture. Require parallel gates, evidence states, an exact resident draft, a payment lock, and a complete approval packet—without dispatching or sending anything.