The question a board member always asks isn't "what does the document say." It's "how do I know you're right — and which document wins if they disagree?" I built the answer to that question into the system itself.
HOA and condominium governing documents are not written to be understood. They are written to be legally defensible — which means they are dense, cross-referential, layered across multiple document types, amended over decades, and frequently contradictory when a newer rule conflicts with an older declaration.
Every time a board member, association manager, or homeowner asks "can we do this?" — the real question underneath it is a chain of harder questions: What does the declaration say? What do the bylaws say? Do they agree? Are there amendments? Which version of the rules applies? If two documents say different things, which one has higher legal authority?
I managed this problem manually for 14 years. I know exactly how many board meetings go sideways because someone challenges an interpretation, or because no one can immediately cite the exact section that supports the decision being made. The friction is expensive, it erodes board confidence, and it slows every governance decision it touches.
There's a second, quieter problem underneath the first one. Every board operates with institutional memory that lives entirely in the heads of whoever happens to be sitting at the table. A manager leaves. A long-serving board president terms out. The person who remembers why the short-term rental policy was amended in 2019 — and what the board actually intended — is gone. The documents remain. The context doesn't.
And there's a third problem that nobody tracks systematically: governing documents don't just answer questions. They create obligations — annual notice requirements, biennial reserve study mandates, threshold-triggered procedures — that accumulate across decades. Most boards have no complete picture of what their documents require them to do, let alone when it's due.
The core insight driving BoardPath's architecture is that document quality, retrieval precision, and document authority are three separate problems that all have to be solved before you can trust an answer.
Stage 1 — Extraction Pipeline (The Quality Problem)
A governing document corpus is not a clean PDF corpus. It includes scans from the 1980s, handwritten amendments, faxed notices, and documents that have been photocopied so many times the text is barely legible. A single extraction model fails on this material.
BoardPath uses a three-stage OCR pipeline: LlamaParse handles primary extraction for clean and semi-clean documents. Low-confidence outputs route to a MistralAI-powered redundancy layer for enhanced extraction. Documents that still fall below the confidence threshold route to Google Vision as a tertiary fallback — the strongest available tool for worst-quality scan material. Every document in the corpus gets the extraction quality it requires, not a one-size-fits-all pass.
Before any document enters the OCR cascade, it passes through the Document Intelligence Pre-Flight Agent — a Claude Haiku-powered classifier whose primary function is mapping the structural fingerprint of each governing document before any extraction begins.
HOA governing documents are structurally non-standardized in ways that matter enormously to extraction accuracy. Some organize by ARTICLE and SECTION. Others use CHAPTER and numbered sub-provisions. Some use alpha-numeric outlines. Others use flat numbered-paragraph structures with no hierarchical nesting. Older documents often mix conventions within a single file — a declaration written in 1974 may follow a completely different structural logic than the bylaws amended in 2021 sitting in the same corpus. No governing standard exists.
The Pre-Flight Agent reads the document first — scanning its structural patterns, identifying the heading convention in use, and constructing a normalized description of the document's outline: what the top-level divisions are called, how subsections are labeled, how deep the nesting goes, and what typical heading text looks like versus body text. This structural brief is passed forward to the parsing coordinator before it sees a single extracted section. The coordinator enters the OCR and parsing pipeline knowing what to look for — what constitutes a section boundary, what's a heading versus a subheading versus noise — rather than discovering the document's logic mid-extraction. It distills signal from structure before any content is processed, and that front-loaded clarity propagates through every downstream stage: OCR, chunking, section extraction, indexing.
Document type detection, authority rank assignment, and corpus metadata pre-fill are secondary outputs of the same agent pass — useful, but incidental to the structural analysis that constitutes its primary contribution.
Stage 2 — Hierarchical Document Weighting (The Authority Problem)
Not all governing documents carry equal legal weight. A declaration supersedes bylaws. Bylaws supersede rules and regulations. Amendments modify — and in some cases override — the documents they amend, but only for the specific provisions they address.
BoardPath assigns an integer authority rank to every document type in a client's corpus upon ingestion. When an answer draws from multiple sources, the system knows which document's language controls — and surfaces that explicitly in the citation layer, not just in the answer text. Amendment chains are tracked with full lineage: every provision links back to the document it amended, and orphaned amendments (those referencing a provision that no longer exists in its original form) are flagged for board review.
State community association law sits above every governing document a community uploads — it can override what any declaration, bylaw, or rule says. BoardPath resolves this by ingesting the relevant state statutes as first-class documents at the highest authority rank in the system. Answers draw from statute when relevant and explicitly signal whether statutory provisions were available in the retrieval context or not.
Stage 3 — Hybrid Retrieval (The Precision Problem)
The most sophisticated challenge isn't finding documents that mention the right words. It's finding the right sections even when a user doesn't use the exact right words — and then ranking results correctly by what matters in law, not just by what's mathematically closest.
BoardPath runs two parallel search passes every time a question is asked. The first uses semantic search: every document section and every incoming question are converted into mathematical vectors that capture meaning, not just keywords. The second uses traditional full-text keyword matching across the entire indexed corpus. Results from both passes are merged and re-scored against authority rank, amendment recency, and cross-path agreement — sections that both retrieval methods independently surfaced receive a signal boost, because independent agreement is strong evidence of genuine relevance.
The retrieval pipeline is a narrowing funnel, not a fixed-width pipe. A minimum relevance threshold gates how many sections reach the AI model at all. Sections below the floor don't get passed even if fewer candidates remain — the model sees only signal, never noise.
The diagram below maps the full pipeline from document upload to user-facing response. Gold-bordered nodes are primary decision points — where authority, hierarchy, or confidence is computed deterministically before the language model is consulted.
Gold border — primary decision point computed before model call · Dark fill — persistent storage layer
The hardest design problem in BoardPath wasn't extraction quality or retrieval accuracy. It was trust. Specifically: how do you get a board member who has been skeptical of technology their entire adult life to act on an AI-generated answer?
The answer I arrived at was counterintuitive: don't hide the uncertainty. Surface it. Show exactly how the answer was constructed, how confident the system is in each element of it, and why. A layperson shouldn't need to understand AI to evaluate the output — they should be able to read a plain-language scorecard and make their own judgment.
Every BoardPath answer carries two confidence badges that answer the two questions a board member needs answered before acting on a response. The first is Answer Confidence — given what's in the documents, how reliable is this answer? It evaluates the authority rank of cited sources, whether the two retrieval paths independently agreed, and whether the model flagged ambiguity or conflict. The second is Corpus Readiness — how complete is the uploaded document set for questions like this one? The two badges are deliberately separate: a strong answer from a thin corpus means the board should upload more documents before relying on what it found. Confident silence from a complete corpus means the policy gap is real, not a missing upload. Those distinctions are invisible in a single score.
A documents_silent
boolean field enforces structured silence when the corpus genuinely doesn't address a
topic. This replaces the prior approach of a low confidence score — which can be
miscalibrated — with a field that cannot equivocate. The answer card shows "Not Addressed"
in a neutral gray rather than a red warning, because the absence of a policy is different
from a wrong answer, and the board should read it that way.
During pre-launch stress testing — 49 adversarial questions covering edge cases across conflict detection, amendment inheritance, and authority hierarchy — every question passed until a proxy holder scenario exposed a failure mode in multi-document conflict resolution. Four documents each addressed proxy holding differently, with misaligned authority ranks. The model correctly identified the conflict but under a prescriptive system prompt template, filled in the hierarchy backwards — declaring the highest-authority document overridden by the lowest. High Confidence. Wrong answer. In a legal context, that's not a miss. That's a trap.
Two iterations of system prompt escalation made it worse. The more explicit the template instruction, the more confidently the model misapplied the pattern. The fix wasn't a better prompt — it was recognizing that hierarchy resolution is a database operation, not a language problem.
Authority rank is an integer column. MIN(rank) determines
the controlling document. This computation runs in code before the model call fires, and the
result is injected into the user prompt as an established fact — not as an instruction for the
model to interpret. A post-parse inversion check then scans the model's response for the failure
signature: the controlling document's name appearing within 80 characters of the words "overridden"
or "no legal effect." If the check fires, one corrective retry runs. If the retry fails, the
response is flagged for human review. The behavior is guaranteed at every branch. The system
prompt plays no role in this decision — it can't be misread because it isn't consulted.
The principle generalizes: any decision that can be pre-computed from structured data in the database belongs in the code, not in a prompt. The model's job is language production around a pre-established fact. When you separate those two tasks cleanly, both get done correctly.
A second guardrail operates before retrieval begins. When a board member submits a maximally vague question — "What are the rules?" or "What can I do?" — the pipeline embeds it, retrieves sections that contain those literal words, and returns a high-confidence answer that addresses the wrong question. The pre-pipeline vagueness gate intercepts inputs with low word count and no identifiable governance topic keyword before any retrieval fires. Instead of a misfired answer, the board member receives a clarification prompt with the twelve topic chips as clickable options. The retrieval pipeline is never called. No hallucination risk exists on a query that never reached the model.
Before any external user saw BoardPath answer a governance question, the Q&A pipeline ran a formal adversarial testing protocol — a structured hardening gate with documented acceptance criteria and explicit disqualifying conditions. The design goal was not a high pass rate. It was documented known behavior at every meaningful failure mode, with a clear line between what's acceptable and what isn't.
The battery covers ten behavioral categories, each targeting a specific failure mode that matters in a governance context: silent topics the corpus doesn't address, vague questions the model shouldn't answer, adversarially framed questions designed to lead toward a predetermined conclusion, cross-document hierarchy conflicts, amendment supersession chains, compound multi-part questions, out-of-scope requests, overconfidence on weak evidence, follow-up context contamination, and direct fabrication detection.
Two categories have no acceptable failure rate. Any substantive model response to an out-of-scope question — "how do I pay my assessment," "what's the weather this weekend" — is an automatic gate failure. Any substantive response to a question about a topic confirmed absent from the corpus is a hard failure. These aren't performance targets. They're the foundation of the trust model. If either breaks, nothing else about the product's accuracy matters.
The hardening process surfaced several critical vulnerabilities that weren't apparent during development: a retrieval threshold set low enough that the Declaration authority bonus alone cleared it (meaning a section with zero semantic relevance would be passed to the model as a high-authority source); hardcoded state statute citations in the system prompt that would produce jurisdiction-wrong legal references for every non-Ohio association; and a vague question detection gap where maximally vague inputs ("What are the rules?") returned high-confidence answers that addressed the wrong question entirely.
A pre-pipeline vagueness gate now intercepts questions that contain no identifiable governance topic before they reach the retrieval system, returning a clarification prompt with topic suggestions rather than a misfired answer. Every vulnerability that surfaced in hardening became a code-level fix — not a prompt adjustment.
Architecture Note 07 — Full writeup: how I stress-tested a production AI system →
BoardPath's primary interface is The Boardroom, an AI-powered governance workspace designed around the actual rhythm of a board meeting. A corpus readiness header surfaces document health before the session begins. Twelve topic chips — Pets, Parking, Architecture, Assessments, Short-Term Rentals, Leasing, Noise, Common Areas, Elections, Fines, Maintenance, and Rule Amendments — provide one-click navigation to the most common governance questions.
Every answer includes a Why This Answer? panel that traces the citation chain, surfaces any detected conflicts, and flags where counsel review is recommended. Citations are color-coded by document type — Declaration in gold, Bylaws in teal, Rules in slate, amendments in amber — so the authority hierarchy is immediately legible without reading any labels. Only sections that the model actually cited appear in the panel; retrieved sections that were not cited are never shown to the user.
Topic Briefs extends the workspace further: twelve pre-generated governance intelligence briefs, one per topic chip, pulling the relevant provisions from across the full document stack and assembling them into a structured summary with citation grounding and controlling authority callouts. A board member preparing for an annual meeting can walk in with a complete brief on Elections — every relevant provision, its authority rank, any detected conflicts, common questions — without asking a single question. Every brief is downloadable as a formatted DOCX on association letterhead.
The Pre-Meeting Governance Briefing goes one step further: a single on-demand report that assembles the association's most pressing governance items — upcoming obligation deadlines, open document conflicts, recent questions asked in the workspace, amendment chain status — into a single structured briefing document a manager or board president can read before walking into a meeting. Generated in seconds from live database state; downloaded as a formatted DOCX.
The correspondence layer generates professional DOCX letters on association letterhead, populated via a homeowner roster picker. A manager handling twelve associations can produce a violation notice, a demand letter, or a board resolution draft without leaving the platform.
The Document Library surfaces the full indexed corpus with every document ranked by authority level, color-coded by type (Declaration in gold, Bylaws in teal, Rules in slate, amendments in amber), with amendments grouped beneath the parent documents they modify. A document with active amendments shows an indicator linking directly to the Consolidated Document View. Any document that has been amended displays a banner at the top of its viewer identifying every active amendment and linking to it — so a board member reading original Declaration language is never unaware that a 2008 amendment modified it.
Every answer is shareable. A board member can generate a secure link to any cited, sourced response and send it to a homeowner, an attorney, or a fellow board member — no login required on the receiving end, no raw document access granted. The link presents the full answer with its citation chain and confidence badges, formatted for reading rather than for navigation.
The Warning Center is the governance health monitor — a dedicated surface that surfaces problems across the corpus and the answer record before they surface in a meeting. Unlinked amendments (uploaded but not connected to their parent document), documents without effective dates, answers flagged as stale by a subsequent upload, missing state statutes, and the count of open conflicts all appear here, severity-ranked, with direct links to the relevant fix. The Warning Center is the first place a manager looks when onboarding a new association corpus or after a document upload — it confirms what's set up correctly and flags what isn't.
Board meetings are where governance decisions are made — and where institutional memory is most at risk of being lost. A motion captured in a recording secretary's handwritten notes may or may not make it into formal minutes. An informal board consensus reached during discussion almost certainly won't. BoardPath's meeting intelligence layer captures what happens in the room, not just what was documented after the fact.
Motion Recorder operates inside an active Boardroom session — the board declares the meeting open, and the recorder becomes available. Each motion is logged in real time: the motion text, who made it, who seconded, vote outcome (passed / failed / tabled), and individual vote counts. Everything a recording secretary needs, captured during the meeting rather than reconstructed from memory afterward.
Meeting Minutes Drafting turns a completed session into a draft set of formal meeting minutes in one click. The system assembles all recorded motions and the governance questions the board worked through into a structured parliamentary-format document — call to order, quorum statement, agenda items derived from session content, each motion in formal language with its vote outcome, extracted action items, and adjournment. Sections requiring manual input (attendance, time, location) are clearly marked with placeholder brackets so nothing is fabricated. The draft downloads as a formatted DOCX on association letterhead, ready for the recording secretary to review and finalize.
Meeting minutes are a formal legal record. They can be introduced as evidence in disputes, referenced in litigation, and audited by state regulators. The minutes drafting route uses GPT-4o, not the faster and cheaper GPT-4o-mini used for most other operations. The model is instructed not to introduce any governance authority not already present in the session's cited answers, and to clearly mark every section that requires manual completion. The trade-off in speed and cost is accepted because the output cannot afford to be imprecise.
Transcript Ingest handles meetings recorded externally via tools like Otter.ai or Read.ai. A paste of the raw transcript goes to an extraction agent that identifies every motion, vote, and formal decision in the text, presents them in a structured review table, and waits for confirmation before saving anything. Nothing is auto-inserted. The board confirms what was extracted before it enters the permanent record.
Governing documents don't just answer questions. They create obligations — annual notice requirements, biennial reserve study mandates, notice periods that must be followed before a fine can be assessed, thresholds that trigger required board action. Most associations have no complete picture of what their documents legally require them to do, let alone a system for tracking it. BoardPath solves this at the source.
The Obligation Matrix extracts every binding obligation embedded in a community's governing documents — every "shall," "must," "required," and "within X days" that creates a deadline, recurring requirement, or procedural restriction. An AI extraction agent reads every indexed document section and classifies what it finds into obligation types: deadlines, recurring requirements, notice obligations, triggered procedures, and standing restrictions. These surface in a calendar-organized interface by status (upcoming, overdue, completed), each linked back to the exact document section that created it.
The Weekly Governance Digest assembles this operational picture into a plain-language summary addressed to the board president: upcoming obligation deadlines for the next thirty days, overdue items, open document conflicts, and recent homeowner inquiry patterns. It arrives as an email without requiring a login — the board president gets the governance pulse of their community delivered on a schedule, without navigating a dashboard.
The Conflict Finder scans the full document corpus for provisions that address the same governance topic differently across documents with different authority levels. When a rules-and-regulations provision says one thing and the higher-authority declaration says something different on the same subject, the system identifies and catalogs the conflict — both sections displayed side by side, the controlling authority clearly identified, the conflict described in plain English. Open conflicts appear in a badge on the navigation so boards are never surprised by a conflict surfacing during a contested question.
The Boardroom answers questions the board already knows to ask. The Obligation Matrix, Conflict Finder, and Weekly Digest answer questions the board doesn't know they should be asking yet. A conflict between a 1998 declaration and a 2011 rules amendment that nobody has challenged in fourteen years is still a conflict — and it will surface at the worst possible moment if it isn't found first. Finding it before the dispute is the entire point.
When a conflict is identified between governing documents, BoardPath can draft a proposed resolution: a formal amendment to the lower-authority document that brings its language into alignment with the controlling provision. This accelerates the attorney drafting process significantly. It does not replace it.
The distinction matters — and it required a deliberate design decision about how to enforce it.
The Amendment Generator requires passing through a required legal disclaimer gate before any draft is generated. The gate presents the full disclaimer text — that the output is a draft only, not legal advice, not enforceable without board ratification and state-law compliance, and requires review by a licensed attorney — and requires the user to scroll through it in full, check an acknowledgment box, and enter their initials. The acknowledgment is recorded server-side with the user's identity and timestamp on every draft generated. The gate cannot be bypassed from the interface or by calling the API directly — the server validates the acknowledgment fields before any draft generation begins. There is no configuration option to disable this check.
The draft itself follows formal HOA amendment conventions: WHEREAS recitals explaining the purpose, a NOW THEREFORE clause, a specific citation of the article and section being amended, replacement language, and an effective-date provision noting that ratification must follow the association's governing documents and applicable state law. Sections where a specific legal threshold cannot be confirmed from the indexed documents are explicitly marked [ATTORNEY REVIEW REQUIRED] rather than filled with a plausible guess.
Every downloaded DOCX is watermarked "FOR ATTORNEY REVIEW ONLY — NOT VALID UNTIL RATIFIED" on every page of the document. This is not a cover page disclaimer — it's repeated throughout the body so no page of the draft can be mistaken for a finalized document.
A conflict found by the Conflict Finder seeds the amendment form directly — the conflict context, the source sections, and the controlling authority are pre-populated. The path from "we found a conflict" to "we have a draft to take to our attorney" is a single workflow, not a separate research exercise.
A board asks a question. The system retrieves from the current corpus, generates an answer, cites the relevant provisions. Three weeks later, an amendment is uploaded that supersedes one of those cited provisions. The prior answer is now wrong — and nothing in most systems would ever indicate that.
BoardPath resolves this with a staleness detection pass that runs automatically after every document ingestion. When a new document is uploaded, the system checks whether it amends any existing documents, and whether its content overlaps topically with sections that supported prior answers. Answers that may have been overtaken by the new upload are flagged with an amber warning banner — visible on the answer card, logged in the Warning Center, and badged in the session history. The message is specific: which document was uploaded after the answer was generated, and why the board should verify before relying on it.
The Consolidated Document View addresses the related problem of reading governing documents in their current effective state. When a declaration has been amended twice over thirty years, the official legal document is the declaration plus both amendments — but that's three separate PDFs in the document library. The Consolidated View generates a merged, single-document view of any base document and all its active amendments, with amendment-modified sections clearly indicated and linked to their source amendment. The consolidated version is downloadable as a DOCX. Every new document ingestion automatically invalidates and regenerates any consolidated views it would affect.
The Counsel Packet Export is available on answers that warrant attorney review — specifically, answers where hierarchy conflicts were detected or where the AI recommended legal counsel. The export assembles a formal seven-section governance issue summary formatted for attorney handoff: the question presented, a plain-language issue summary, the direct answer verbatim, the controlling authority with full section text excerpts, any detected hierarchy conflict, the Transparent Confidence™ scorecard breakdown, and a statutory note indicating whether state statutes were available in the retrieval context. A footer on every page notes the document was prepared by governance software, not by an attorney, and does not constitute legal advice.
Association managers and board members field the same homeowner questions on a loop: can I install a fence, are dogs allowed, what's the guest parking rule. Most of these questions have clear answers in the governing documents. The board shouldn't have to answer them by hand every time.
Community and Pro tier associations can activate a public-facing homeowner portal — a separate question-answering interface accessible via a dedicated URL, with no login required. Homeowners type their question in plain language; the system answers from the same indexed corpus with appropriate scope limitations.
The homeowner interface is deliberately simpler than The Boardroom. There is no confidence scorecard detail panel, no session history, no meeting mode. There is a plain-language answer with its source document cited, a clear flag when the governing documents don't address the question clearly enough for a reliable answer, and a direct path to contact the board when the situation requires human judgment. Rate limiting prevents abuse without disrupting legitimate homeowner use.
The homeowner portal and The Boardroom query the same indexed corpus and the same AI pipeline. The difference is the interface layer: the board-facing workspace shows the full confidence scorecard breakdown, citation chain, and all governance context because board members are accountable decision-makers who need to understand the reasoning. The homeowner-facing interface shows the answer and its source because homeowners need to know whether they can install the fence — not why the retrieval system ranked the Declaration above the Rules for this query. Same intelligence. Different presentation for different jobs.
Homeowner usage generates one kind of data that's valuable to a board: what topics homeowners ask about most, and how often those questions can't be answered from the documents. BoardPath captures this as aggregate topic signals — topic slug, confidence level, whether the question needed board referral, which channel it came from. No question text is stored. No email address. No unit number. No identifiable information at any level. A board can see that 40% of homeowner questions this month were about parking, and that 30% of those couldn't be answered from the corpus — without knowing which homeowner asked what. The pattern is useful. The individual record isn't — and it doesn't exist.
The portal is one access channel. The second is email. Each association is configured with a dedicated inbound email address. A homeowner sends their question as a plain email — no app, no URL, no account. The message hits the inbound pipeline, runs through the same retrieval and answer generation as every other BoardPath query, and a formatted reply lands in the homeowner's inbox within seconds: the direct answer, the source document cited verbatim, and a plain-language explanation. The board never touches it. The homeowner never needs to know what's behind it.
This flow is live and publicly demonstrable. The interactive demo walks through it in real time — an inbound email question triggers the full pipeline and delivers a cited AI response to a real inbox.
Live interactive demo — see the email Q&A flow in action →
Boards activate the portal and email channel via a settings toggle. When enabled, the platform generates a ready-to-distribute homeowner welcome package — a two-page formatted DOCX on association letterhead that explains what BoardPath is, what it can and cannot answer, and how to reach it via URL or email, complete with a scannable QR code. One click, printed and handed out at the next meeting.
Community and Pro tiers solve the document retrieval problem. BoardPath Chronicle solves a different one: what happens to everything the community has decided, argued over, amended, and resolved across years of board terms — when the people who remember it are gone.
Chronicle is the institutional memory layer. It preserves and makes accessible the complete governance history of an HOA community — every formal board decision, every amendment chain, every exception grant, every vote — across any number of manager changes and board turnovers.
"Your last manager walked out the door with 10 years of institutional memory. BoardPath Chronicle didn't let them take it."
Historical Q&A with Timeline Awareness lets a board query the corpus as it existed on any past date — retrieving from the document set that was in force at that moment, including provisions that have since been superseded by later amendments. A board member who wants to understand what the rules said about short-term rentals when a disputed approval was granted in 2019 gets an answer grounded in the 2019 document state, not the current one.
Amendment Chain Visualization surfaces the full lineage of any governing document — from original language through every subsequent amendment — as a navigable timeline. Each node shows the document, its effective date, its current status (active, superseded, or pending), and a summary of what it changed. Orphaned amendments — those that reference a provision no longer traceable in the original document — are surfaced in amber with a prompt to link them to their parent.
The Board Decision Audit Log maintains a searchable, semantically indexed record of every formal motion, vote, exception, and policy adopted — extracted from Boardroom sessions and ingested meeting minutes, stored with full-text and semantic retrieval so a search for "parking exception" surfaces every decision ever recorded on that topic across any number of board terms.
The Governance Health Check scores corpus completeness across five dimensions — Document Coverage, Amendment Completeness, Currency, Decision Record, and Ingestion Quality — and emits a labeled score (Strong / Moderate / Needs Attention / Critical) with specific gap callouts and recommended actions for each dimension that falls short.
When a new board member is seated, Chronicle generates an Institutional Memory Report automatically — a structured DOCX briefing covering the community's governing document summary, amendment history, recent decisions, standing policies, and open items. The trigger is a new membership record in the platform, which fires the report generation pipeline without manual intervention. A new board president on day one has the same institutional context as the president who served for a decade — because it was never stored only in one person's head.
Annual meetings are the single point of maximum governance risk for most associations. The notice must be sent the right number of days in advance per the bylaws. The agenda must include specific items required by both the governing documents and state law. The proxy form must match the bylaws' exact proxy language. The ballot must reflect the correct candidate requirements and vote threshold. Most HOA annual meeting failures trace back to one source: the board used a template that didn't match what their documents actually required.
The Annual Meeting Wizard — launching September 2026 — generates the complete set of annual meeting materials directly from the association's indexed governing documents. Meeting notice with the correct advance notice period. Formal agenda with all statutorily and bylaw-required items. Proxy form matching the bylaws' proxy requirements. Candidate ballot with correct quorum and vote threshold language. A quorum calculator based on the current homeowner roster, with a flag if quorum is at risk. And a board candidate packet — nomination form, responsibilities summary, and an orientation excerpt from Chronicle for incoming candidates.
Every output is derived from the documents, not from generic templates. The difference is whether the notice period is correct for this association's bylaws, not for the average HOA's bylaws.
BoardPath is designed to match how associations actually adopt new technology — cautiously, by capability tier, with a clear path to more as trust is established.
Built for self-managed HOA boards. Full document Q&A, Transparent Confidence™ scoring, The Boardroom workspace with twelve Topic Briefs, conflict detection in answers, amendment chain tracking in the document library, Stale Answer Detection, Consolidated Document View, DOCX correspondence generation with homeowner roster, and the public Homeowner Portal. Designed for the volunteer board that needs authoritative answers at 9PM the night before a meeting.
Built for community association managers and multi-association portfolios. Everything in Community, plus multi-association corpus management, Pre-Meeting Governance Briefing, Meeting Intelligence (Motion Recorder, Minutes Drafting, Transcript Ingest), Obligation Matrix with Weekly Governance Digest, Conflict Finder, Amendment Generator, Counsel Packet Export, and the full Document Readiness dashboard. The management company running twenty associations has a unified governance operations layer, not twenty separate conversations with a chatbot.
The institutional memory layer. Everything in Pro, plus Historical Q&A with timeline awareness, Amendment Chain Visualization, Board Decision Audit Log with semantic search, Institutional Memory Reports auto-generated on board turnover, Governance Health Check scoring, and the Compliance Calendar. For the association with twenty-five years of history and a board that just turned over completely — this is how it doesn't start over.
BoardPath handles the full governance intelligence workflow end-to-end: document ingestion and classification, three-stage OCR extraction, authority hierarchy assignment, amendment chain tracking, hybrid retrieval with authority-weighted ranking, answer generation with citation grounding, deterministic conflict resolution, two-tier confidence scoring, correspondence generation, meeting intelligence capture, obligation tracking, conflict detection, amendment drafting, document safety monitoring, homeowner portal access, and institutional memory preservation across board terms.
The Transparent Confidence™ scoring layer remains the product's primary trust mechanism — not because it's technically impressive, but because it solves a human problem. The boards that will pay for this aren't the ones who trust AI. They're the ones who want to verify it before they act on it. The system is designed for exactly that skeptic.
Chronicle is the long-term moat. Community and Pro answer the question every board asks today. Chronicle answers the question every board eventually faces: what did we decide — and why — and who was in the room when we did it? That question doesn't have a good answer anywhere in the current market. Now it does.
The Annual Meeting Wizard closes the last major gap: not just answering governance questions, but generating the governance artifacts those questions are supposed to produce. By the end of 2026, a board using BoardPath should be able to handle the full annual governance cycle — from the first board question of the year to the annual meeting's formal documents — without leaving the platform.