Committees
Purpose and Outcomes
Committees gives an association a shared account of its governing bodies and the people who serve on them. Governance staff use that account to keep organizational structure, dated service and committee work connected. Readers can understand how a body is organized and how participation changes over time without maintaining a separate list of people. Administrators align shared governance choices with the association’s own practices.
The area also brings the records of collective work into that account. Meetings, formal decisions, conflicts and recruitment belong beside the bodies and participation they concern. This creates a basis for following governance work across changes in office, committee composition and staff responsibility. The desired outcome is an understandable record of who serves, what work belongs to the body and which neighboring application supplies the next part of the process.
Delivery is uneven across this scope. Staff already use the committee structure and service experience in the console. Meetings, decisions and recruitment have service implementations, while their hosted experiences and several portal uses await product decisions. Appointment-derived authority is likewise an implemented extension awaiting its release decision. These boundaries keep the overview useful without treating every implemented operation as an accepted customer experience.
Scope and Boundaries
The area owns governance records and their meaning: committee structure and service in one module, and collective work and recruitment in the other. It hands record consequences between those modules while retaining each owner’s responsibility.
CRM supplies people, organizations and affiliations and coordinates contact consolidation. Membership supplies organizational units and qualification facts. Platform supplies security, shared presentation, files, communication delivery, reporting, staff attention and durable execution. Submissions supplies forms and review outcomes. Websites hosts the portal and public website; Committees supplies the governance information those experiences consume.
Secret ballots depend on Surveys and Voting, and recruitment opportunities depend on Volunteers. The module charters describe these as proposed connections rather than completed services. A reference to an outside record does not transfer ownership of that record into Committees.
How the Area Is Divided
Committee Structure, Service and Proposed Authority is the starting point for understanding governing bodies, the places within them and dated participation. Open it when the question concerns governance structure, service history, staff oversight or the proposed connection between office holding and access. Its charter identifies the neighboring systems that supply identity, eligibility and shared infrastructure.
Meetings, Decisions and Recruitment covers the collective work attached to those bodies and the process of finding future participants. Open it when the question concerns meeting records, governance outcomes, conflicts or recruitment ownership. Its charter also explains the deferred surface decisions and the integration boundaries that make a service implementation different from a released experience.
Area-Level Invariants
The area keeps governance ownership with the module responsible for the record, including when a screen appears in another application. It uses CRM’s people and organizations as identity references. Platform remains responsible for authorization; committee parentage and staff responsibility routing do not establish access by themselves. Implementation evidence and release approval remain separate throughout the area.
Open Ownership Questions
Product still decides where staff administer meetings, decisions and recruitment, and which public and portal operations remain reachable before the portal stage. The release boundary for appointment-derived authority also remains open. Recruitment notices need an audience decision that distinguishes committee office holders from staff with assigned responsibility. The owning modules retain these questions and their options.