A pipe bursts at 12:40 AM. The AI answers, recognizes the emergency by your rules, dispatches the on-call plumber, notifies the manager and logs everything — no answering-service relay, no soaked ceiling at 8 AM surprise.

Location, description, photos, access instructions and urgency captured on the first call — the vendor gets a workable ticket, not a callback chain.

Pool hours, gate codes for verified residents, assessment due dates, architectural application status, trash day: answered instantly from YOUR community documents, identically every time.

The letter quotes the exact section, references the photos on file, states the cure period from your policy — drafted in the community’s tone, queued for the manager to release.

Financial summary, delinquency report, open work orders, vendor bids side by side: the monthly packet drafted from the records days early, every figure cited.

Every AI-drafted letter, packet and summary lands in Output awaiting review. Nothing reaches a resident, board or vendor without your team’s decision.

Recorded CC&Rs as scans, minutes as Word files, reserve studies as 90-page PDFs, contracts as email attachments — the ingestion pipeline turns it all into queryable knowledge.

No source in the documents, no claim: the AI cites the CC&R section, the minute, the contract clause — or says it cannot answer. In a dispute-prone business, that discipline is the shield.

A board member queries their own community’s reserves; a manager queries the portfolio; a resident-facing answer stays public-safe: each scoped to the role, enforced server-side.

Board packet, violation letter batch, vendor bid comparison, delinquency summary, reserve-study digest: work types molded to your operation, each with default libraries and examples.

The AI’s workload is managed like the team’s: one-click views show what is urgent, late, today and tomorrow — no board meeting arrives with an unfinished packet.

Every work is a full session: reasoning streamed, sections cited, milestones tracked, linked to the community and the meeting calendar.

Collection policy, violation escalation steps, ARC review criteria, amenity rules, emergency procedures: one library per community, current versions on top, superseded ones outranked.

“What is the cure period before a second violation notice at Willow Creek?” — answered in seconds with the policy attached, before the wrong letter goes out.

Work types carry their default policies: the AI drafting a violation letter reads that community’s escalation procedure — by construction, not by memory.

A new manager inherits five communities and learns each one from the AI — governing documents, open issues, vendor history, board personalities on paper — productive in days, not a season.

“Who services the gates at Stonebridge, and what does the contract cover?” — asked to the assistant, answered from the vendor file, without calling the manager who left.

Private chats work on any device with a login — the knowledge follows the manager to the site visit, the board meeting and the after-hours emergency.

The logged violation drafts its letter, starts the cure period, schedules the re-inspection and escalates per the written policy — each step queued for approval, nothing skipped, nothing doubled.

Vendor dispatched, resident notified, completion photo requested, invoice matched to the work order — the loop closes itself and the ledger knows.

Meeting date set: notice drafted per the bylaws’ timeline, proxy attached, packet work scheduled, minutes work queued for after — every community, every month.

Owners with open balances, residents affected by the clubhouse closure, off-site owners for the annual meeting: audiences built from your own resident records — no list exports to a mailing tool.

Notice drafted per the bylaws’ timeline, proxy form attached, reminders paced until quorum — per community, in the residents’ languages, on the record.

Email, mail-merge-ready letters or portal notices per each resident’s preference; opt-outs enforced by the system, not by memory. Every send is on the record.

Residents, units, balances and work orders mapped field by field, with a dry-run preview before anything writes — push, pull or two-way, your choice.

Vendor invoices, insurance certificates, recorded amendments and inspection reports route through the intake pipeline to the right community — and the AI can draft the follow-ups.

A full API for whatever else the operation runs: payment portals, access-control systems, inspection apps — data in, results out, under scoped keys.

Workgroups map communities; the server redacts what a role cannot see — a board member reads their association’s ledger, never the management company’s other books.

A searchable log of every audited action, with configurable categories: who viewed the delinquency list, who edited the letter, who released the notice, when.

Five-level workgroups map regions, communities and boards; the on-premises option puts the whole system inside your building, air-gap capable.

Ask the chat: “the gate at the north entrance is stuck open” — watch it intake the work order, ask for the details a vendor needs, and confirm like your best manager on their best day.

Ask: “how would you assemble our board packet?” — it walks the workflow it would run in your tenant, grounded, cited, sign-off included.

The full demo loads a property-management tenant with sample communities: a violation letter draft, a bid comparison, CC&R answers with the section cited — your world, working.