Let's Talk About Committees

Most neighbors who serve on a committee are doing something specific: they're researching a question, gathering feedback, or drafting a recommendation. They show up, do the work, and bring it to the board. That's how community governance is supposed to function — members contributing at a level that fits their time and capacity, with the board making the final call.

Washington law recognizes two fundamentally different kinds of committees, and the distinction changes everything about how we can support our volunteers.

An advisory committee

gathers information and makes recommendations. It has no decision-making authority. It cannot spend money, create policy, or bind the association to anything. Its work product is an input to the board, not an output of the board. Because of that, it carries no quorum requirement and no formal voting structure. It is, by design, accessible — something a neighbor can participate in without needing to understand parliamentary procedure.

The finance committee is an advisory committee. It reviews budgets, tracks spending, and brings recommendations to the board. A neighbor who joins it is offering their financial literacy in service of the community — not making decisions on the community's behalf. The board votes on the budget. The finance committee helps the board understand what it's voting on. RCW 64.90 doesn't require advisory committees to operate under board-level procedural rules because advisory committees don't exercise board-level authority.

We have now added those requirements ourselves, in the Committee Communication Policy - a top-down board policy.

A delegated committee

is different. When a board formally votes to vest a committee with decision-making authority, that committee is acting on the board's behalf. It needs structure because it has power. Minutes matter because they record binding actions. Procedural rules matter because they protect member rights. That overhead isn't bureaucracy — it's accountability for authority that has real consequences.

The Architectural Compliance Committee (ACC) is a delegated committee. This committee is required to make decisions in publicly noticed meetings, just like the board, so you can see their reasoning and appeal if needed.

RCW 64.38, the statute that governs LCC, the board holds the association's decision-making authority and may delegate portions of it to committees — but that delegation has to be intentional and documented. The ACC is delegated in our current bylaws.

What happens when we apply delegated committee standards to advisory ones?

When every committee — regardless of what it actually does — requires two weeks advance notice, formal minutes, and documentation submitted on the board's schedule, the ask to volunteers quietly doubles. The neighbors most likely to step back are the ones with the least margin: working parents, people with caregiving responsibilities, anyone for whom one more administrative requirement is the thing that tips the balance.

Update 6/6/26 - Now the Advisory committees have advisory committees.

We are aware of at least 2 committees who have held more informal, unannounced, work sessions in order to complete work without the additional notice and minutes commitments.

We can do this differently.

Matching procedural requirements to actual committee function isn't a radical idea — it's what the law already envisions. Advisory committees should be easy to join, easy to run, and focused on the work. Delegated committees should have the structure their authority requires. Keeping those two things separate is how we make participation genuinely available to everyone who wants to contribute.

Ken Lake has neighbors who want to be involved. The governance structures we build can make that easier.

Sources: LCC Bylaws (First Amended), Section 4.7; RCW 64.38; RCW 24.03A; RCW 64.90.