Owners Committee Operations

The problem behind the system.

Owners committees need to track issues, ownership, follow-ups and governance decisions over long periods. Chat is useful for conversation, but it is a poor system of record: assignments disappear in threads, documents become hard to find and it is difficult to reconstruct why a decision was made.

How I approached it.

• Started with a committee-only issue tracker covering assignment, category, priority, status, due dates, comments, photo/file attachments, activity history, search, My Issues and overdue work.
• Designed the issue timeline as an auditable record: tracked changes create activity events, comments remain append-only, and supporting files stay attached to the work they relate to.
• Expanded the product model beyond issue tracking into committee governance — meetings, decisions, action items and voting — so an agreed decision can become accountable follow-up work instead of another message in a group chat.
• Added document-management flows so committee files can live alongside the issues, comments and decisions that give them context.
• Built it as a responsive React + TypeScript PWA backed by Spring Boot, PostgreSQL and authenticated APIs, with the product intentionally scoped around committee operations rather than becoming a full property-management platform.

What the system enabled.

The app is becoming a shared operating record for the committee: one place to see what needs attention, who owns it, what evidence or documents are attached, what the committee decided and what still needs to happen. It is also a product-design exercise in turning informal building governance into simple, traceable software workflows.

The product is being developed iteratively for committee use. Resident, vendor and full community-management workflows are intentionally outside the initial product scope.