Board member Medler's emails, and what the record can and cannot say about open meetings
Two different emails from Board Vice President Alex Medler have been run together in group discussion: the April 8, 2026 critique that uses "close Mesa" as an example, and a February 10, 2026 message sent from his employer's address. Both are reproduced here verbatim, with everything in the production that surrounds them, every other record in which two or more board members appear, and the Colorado Open Meetings Law test those records would have to meet.
- The "close Mesa" email is #215, April 8, 2026, from Medler's district address (alex.medler@bvsd.org) to Superintendent Rob Anderson, the morning after the District Accountability Committee's dry run of the engagement exercise. The Mesa line is his worked example of what "consolidation" and "redistribution" mean ("Real world example in my neighborhood: You close Mesa and its students are assigned to Bear Creek"), offered because "even the principals didn't know what we meant by" the options. It is not a proposal. #215
- The non-district email is a different thread, #80 and #83, February 10, 2026, sent from alex.medler@nn4da.org (National Network for District Authorizing, where he is founder and executive director) to Anderson and Barber about a private school's marketing: "This is all the more reason to control the messaging and chatter among our internal stakeholders." #80 #83
- Neither is a "meeting" under the Open Meetings Law on its own. The law reaches gatherings, including by email, of "a quorum or three or more members of any local public body, whichever is fewer" discussing public business. Both emails are one board member writing to staff. The production contains no email in which two or more board members discuss public business with each other.
- The one item worth checking: a May 2025 email from the CFO to two board members (Medler and Quinlan Aweida) and a community member to schedule a Board Audit Committee meeting. A Board committee is itself a "local public body"; whether that meeting was noticed is checkable on BoardDocs. #6
- The production is the wrong instrument for the question. It searched four staff mailboxes (Anderson, Barber, Price, Shafer), not any board member's, and no calendar items were produced. Board-member-to-board-member communication would appear here only if a custodian was copied. Section 5 sets out what a targeted request would ask for.
1. The April 8 email, verbatim
Nice job last night. On balance, I think the discussions went as hoped and people were super engaged in what we wanted them to discuss, and not what would have otherwise happened if we just asked for public input on a "district school closure plan". This is such a good idea, and I'm proud to be even indirectly associated with it. I also think the materials used at the table created by ERS were very helpful.
My suggestions for change are all in the spirit of how to get the most out of less-expert groups than our DAC, in the time available. I think we want folks to spend more time talking and less time receiving updates or being told what to do. Let table-top facilitators do more of the explanation of process, and condense the lecture on the issue a lot.
Maybe the whole thing does shorten to 90 minutes, but I do think 2 hours is actually o.k., and it is o.k. if people are tired when it is done. I especially would protect 2 hours if we make them feel heard somehow by summarizing what we heard or how input will be analyzed and considered. I know others think it should just be 90, but this is big stuff. Or we do the first one or two for 2 hours and decide whether to shorten for the last 4 meetings
A. My biggest concern, facilitation by ERS.
1. The facilitation by ERS was sub-par. Table facilitation by the principals was great as I observed it. Maybe responsibilities can be shifted to the tables. Specifics facilitation issues:
a. Letting people combine into too large of tables, undermines everyone's ability to truly engage as a single person. By combining every table we effectively cut every participant's speaking time in half. The facilitators didn't recognize how big a problem this was, or they were unwilling or unable to fix it. That gave me serious concerns right out the gate. The DAC is used to being in three large subgroups, so they handled the problem o.k. themselves.
b. Not being able to focus people when trying to reconvene the whole group. Wastes time, makes it seem chaotic, and the audience doesn't hear the next directions.
c. Ability to explain some of the concepts and options with concrete examples was limited. Lack of knowledge of our details made it harder to share a concrete example that may have worked for some of the audience. sd
d. Using too much of the time to repeat issues in process, directions, or details.
B. The second concern was the amount of content, repetitiveness, and time participants were being "told to" by district and ERS folks. Specific concerns or suggestions:
1. Even though the audiences won't be as expert as DAC or LRAC, they are motivated to attend. If we have 50-60 folks at 6 meetings, that is 300 to 360 of our most motivated parents. That is probably the most informed or agitated 5 to 10% of parents. Given all the coverage, communication, I think we can assume a reasonable proportion of them have heard a version of our speal. Of course some have not, and will need information, and everybody could use a reminder of facts we want them to know. Still I'd cut it by 50-75%.
2. Perhaps use the 2 minute video and see how many slides it addresses. I think you could replace at least 10 minutes of set up with the video.
3. Less time on the timeline and process, but discuss in a concise way and still share the timeline.
4. Do explain how this input is going to be gathered, analyzed, and reported. Tell them how they will be able to see the output that comes from this process.
5. While one outcome is they know and understand more, they must also feel like a primary outcome is we know more about what they think, feel, want, and fear. I think folks left yesterday with inadequate closure, or less sense the district would benefit from what they had just done. In that sense make it both an educational experience, and a data-gathering exercise. I think reading people as they left, some felt too much like their education (and pacification) was the goal, and data-gathering was less important to the district. I would still achieve both, but participants should feel the intent and purpose is reversed: more data-gathering, by deepening knowledge and understanding. The last thing we want is for them to come away feeling like it is an exercise for its own sake or make-work.
C. A couple of the options are not clearly understood or defined, and even the principals didn't know what we meant by them.
a. Co-locating two schools in one building: is that two separate schools with their own admin and system like BCSIS and High Peaks; or is it two programs in the same institution (like Platt and Platt Choice)? Folks wasted a lot of time trying to define those two things and wondered what we meant by that option. If we mean both, then we should explain with the real-examples like those two iI mentioned above. Or add, Community Montessori co-locating in Mesa's campus with an ongoing Mesa.
d. Consolidation and redistribution: In all these cases, it would help to say: "close one of the schools, and consolidate or redistribute the students", it seems like we are sugar coating that by not starting with, "close a school, and then..." it makes more sense. And just use the figures right away to explain these concisely and use examples of real schools to help focus people. By not using the close word, and staying so conceptual, we lose a lot of concrete thinkers. The ERS facilitators weren't great at this part either, but principals did better. The audience is sophisticated to see through the effort to not emphasize the closure and focus on the what we do after a closure. To the extent a 'school' lives in a new building, that is much less relevant if it is a neighborhood school before or after it "moves".
i. if you have schools A and B. Consolidation means you close A, and the students from both schools (and perhaps staff and program) are combined into school B. Real world example in my neighborhood: You close Mesa and its students are assigned to Bear Creek.
ii. Redistribution: you have schools A, B, C, and D. You close A, and their students (and perhaps staff and program) are redistributed to schools B,C, and D. YOu close Mesa, and students from catchment zone are too many to all fit in Bear Creek, and instead they are distributed among Bear Creek and Creekside or Community Montessori.
iii. Moving choice schools: Explain BCSIS and High Peaks were combined into one campus, and community montessori moved from other school sites it had shared, to its own campus when New Vista moved from the Paddock campus. Concrete example: community Motessori, could relocate east, where most of its current parents come from.
Yes, being concrete with names may risk participants getting defensive and undermining all the trade-off discussion, but 20% of the time in that stage of the discussion I observed was spent on clarifying questions about what the option really was, and folks never got to a single or clear answer. Perhaps just use schools, A,B,C and D. Or neighborhood School A, and Focus School B. Some Principals didn't know any better what we meant than the participants.
C. Reorient time for the different table assignments.
1. Spend less time on the Life-of a student or teacher. I think we should still do it, but figure out a way to make it shorter, and don't give options of which ones to pick, just have one student and one teacher.
2. For the prioritization let the facilitators know they are doing the set up, and still give it more time.
3. Give a lot more time to the last task of shared discussion of the trade-offs. Doing those alone, and then with turn-and-share made, it less engaged, although that did get everybody talking in the large tables.
4. Add a real report out/debrief and explain what we will do with input
D. A couple issues/facts to add (concisely). The scale of open enrollment and education/school options in the district
1. I do think there are a few considerations for which people could use a reminder. These two things came up in the table discussion. In particular, many people don't understand the scale of open-enrollment that is going on, nor the breadth and scope of our various alternative programs. I saw the conversations, as usual from parents in Boulder, from folks attending neighborhood schools, being dismissive of the parents who open-enroll, and discounting the attributes of schools that make them different, and how much people value that. Folks in neighborhood schools often wish the choices were gone and all families attended their neighborhood school.
2. Like myself, I saw the folks representing our special schools take (a slight) umbrage. While the tension between neighborhood and specialized schools is one of the big issues to address, I think these issues can quickly start reflecting ideology, and produce unnecessary divisiveness, if not set up correctly.
3. Since it is possible that our actions may impact neighborhood and specialized schools differently, to avoid the specialized schools getting defensive, I think it would help to quickly give a couple facts in the set up that make sure everybody in the room knows how many BVSD parents are choosing a school other than their neighborhood school, and the number and impact on families of our specialized schools, and that both these things are best considered a feature in BVSD, rather than a glitch.
Sorry for overly-detailed sharing here (definitely in the weeds). Nice work, great idea, well done and strong engagement. Some of the points above may be relatively easy to implement to get an even better outcome,
Alex
Typos are in the original. #215
Hey Alex,
Thanks for the feedback. We have made significant improvements and adjustments to the presentation. I think we are ready for next week!
Rob
"Next week" is the first regional session, New Vista High School, Monday April 13. #215
What it does and does not say about Mesa
Medler's Mesa sentences are illustrations of two option definitions, offered because participants and principals "wasted a lot of time trying to define" them. He also floats "Community Montessori co-locating in Mesa's campus with an ongoing Mesa" and Community Montessori relocating "east." Nothing in the email proposes closing Mesa; nothing in Anderson's reply engages with the examples. Read as evidence of predetermination, it is weak. Read as evidence of what a sitting board member believed the exercise was for ("engaged in what we wanted them to discuss"; "education (and pacification)"; "sugar coating"), and of a board member advising on the design of the district's engagement before it ran, it is the strongest single document in the production. That is the distinction to make when it is cited.
2. The February 10 emails from a non-district address, verbatim
I saw this today in my Linked in Feed.
This is Bixby's effort to leverage our actions around declining enrollment.
FYI,
Followed by the text of Bixby School's LinkedIn post, "Small School, Big Belonging: Finding Stability During Boulder Valley's School Consolidations," which markets a 6:1 ratio to families feeling the "consolidation crunch." Signature block: "Alex Medler, Ph.D., Founder and Executive Director, National Network for District Authorizing." #80
Thanks Alex. Don't love all of the language they used, especially the "consolidation crunch"...
Yep, that was my reaction. But not surprising. I assume all the privates will do the same.
This is all the more reason to control the messaging and chatter among our internal stakeholders. I mentioned this to David Stewart when we met yesterday, and he said he'd help in his communication.
Alex
David Stewart is not otherwise identified in the production. #83
On the address: NN4DA is Medler's employer, so this is a work account, not a personal one, and the emails reached the production only because the two staff custodians received them. That is the practical problem with district business on outside accounts: anything he sent from it to people who were not custodians of this request was not searched. It is a records-capture question, not by itself an open-meetings question.
3. What surrounds the April 8 email
- Barber to the DAC co-chair, hours before the session: "How do folks in DAC typically sit? By region? We are just thinking about whether to change things up tonight or let folks do their normal thing." #201
- DAC meeting: the district and ERS run the engagement exercise on the committee as a dry run. Barber records it with Fireflies.ai; the recap: "Community engagement through October; recommendations to board in August, with decisions expected by October." #205
- The DAC exec's "civility" op-ed, reviewed in draft by Anderson and Barber and placed with the Camera by Barber, is published. #210
- DAC co-chairs' minutes: "Thank you for your incredible engagement with the declining enrollment/school consolidations activities last night!" #210
- Medler's critique to Anderson. #215
- Anderson: "significant improvements and adjustments… ready for next week!" #215
- Six regional sessions. Barber to a videographer on Apr 11: "I definitely don't want to give anyone a platform to sell their individual schools." (Explorer #227.)
- DAC co-chair to Anderson and Medler (district address): will BVSD hold elementary staffing steady ahead of consolidation? Anderson: "Yes, I can do that." #322
4. Every other appearance of a board member in the production
| Date | Members involved | What it is | Direction |
|---|---|---|---|
| May 9–14, 2025 | All seven (Rajpal, Niznik, Medler, Unger, Quinlan Aweida, Sargent, Chavez) | Fireside parents' class-size letters, addressed to staff and every board member; a staff form reply #1 | Inbound to the board; no member replies in the record |
| May 12–19, 2025 | Medler, Quinlan Aweida (+ Robert Smartt, community member) | CFO schedules the Board Audit Committee ("Meet tomorrow (Tuesday) afternoon at about 1:15" or Thursday); purchasing-policy redline and Q3 financials attached #6 | Staff to two members; the meeting itself is a committee meeting |
| May 23–27, 2025 | All seven | A resident's complaint to bvs.board about a dumpster; Shafer forwards to a principal #7 | Inbound |
| Sept 22, 2025 | Medler | Attends the LRAC meeting; "the Board has received very few letters concerning attendance boundaries" LRAC minutes | One member at a noticed committee meeting |
| Nov 17, 2025 – Mar 9, 2026 | Sargent and Niznik (terms ended Nov 2025), Rajpal (Jan 12), Chavez (Mar 9) | Board members at LRAC meetings; Sargent joins as a committee member after leaving the Board LRAC minutes | Noticed committee meetings; never more than one sitting member plus former members |
| Jan 27, 2026 | Rajpal | Forwards a Mesa parent's public-comment pre-read to Price, "FYI" (explorer #56) | President to staff |
| Feb 10, 2026 | Medler (nn4da.org) | Bixby LinkedIn thread #80 #83 | Member to staff |
| Feb–May 2026 | bvs.board list | Twenty-two letters from parents and organizations to the Board address (Whittier, Fireside, BVGT, boundaries); three receive Price's form reply | Inbound; no member replies in the record |
| Apr 8–10, 2026 | Medler | The critique above #215 | Member to staff |
| Apr 30–May 1, 2026 | Medler (cc) | DAC staffing question #322 | Parent to staff and one member |
| Jun 24–Jul 28, 2026 | Rajpal | City of Boulder DDA briefings; Rajpal and Anderson meet City staff Jul 27; "if/when our board will need to take a position" (explorer #367, #397) | President to City and staff |
| Jul 23, 2026 | Rajpal | Reporter's future-use question forwarded to Barber and Anderson, "FYI" (explorer #387, #389) | President to staff |
What is absent: any email among two or more sitting board members about closures, consolidation, buildings or the engagement; any board-member calendar item; anything from the mailboxes of Unger, Bucher, Temu Otting, Quinlan Aweida or Chavez other than as addressees of parent letters. Given who the custodians were, absence here is not evidence of absence.
5. The open-meetings test, and where to look
The statute. Colorado's Open Meetings Law, C.R.S. § 24-6-402(2)(b): "All meetings of a quorum or three or more members of any local public body, whichever is fewer, at which any public business is discussed or at which any formal action may be taken are declared to be public meetings open to the public at all times." Such meetings need "full and timely notice" (§ 24-6-402(2)(c)). "Meeting" means "any kind of gathering, convened to discuss public business, in person, by telephone, electronically, or by other means of communication" (§ 24-6-402(1)(b)). On email, § 24-6-402(2)(d)(III): "If elected officials use electronic mail to discuss pending legislation or other public business among themselves, the electronic mail shall be subject to the requirements of this section." A "local public body" includes "any board, committee, commission, authority, or other advisory, policy-making, rule-making, or formally constituted body of any political subdivision of the state" but "does not include persons on the administrative staff of the local public body" (§ 24-6-402(1)(a)). Statute text.
Applied to this record. The Board has seven members, so three members discussing public business, by any means, is a meeting. One member writing to the superintendent is not, and the superintendent and staff are outside the definition. Neither Medler email meets the test. The Audit Committee is a formally constituted committee of the Board; if it has three members (Medler, Quinlan Aweida and Mr. Smartt appear to be its members), two is a quorum and its meetings require notice. The May 20 or 22, 2025 meeting the CFO was scheduling is the one item in the production that a notice check could turn into something. BoardDocs shows a Board special meeting on the morning of May 20, 2025; whether the committee meeting that afternoon was posted is not in the production. BoardDocs.
What would answer the question. A records request aimed at the board rather than at staff: for each of the seven members, emails, texts and messaging-app messages, on district and any non-district accounts used for district business, and calendar entries, from October 1, 2025 to the present, concerning closures, consolidation, the Resilient Schools proposal, the engagement sessions, specific school names, or building use, together with any Audit Committee, Board-committee or board-retreat notices and minutes for the same period. The August 25 work session and September 8 meeting transcripts on the working group's transcripts page are the public-meeting side of the same question.
This is a reading of the statute against the documents, not legal advice; the working group should have counsel confirm the test before alleging a violation.
Documents
| # | Sent | Document | What it adds |
|---|---|---|---|
| #1 | 2025-05-09 10:19 | Fwd_Cuts_to_Fireside_school_budget.pdf | Example of the inbound letters addressed to all seven board members plus staff (Fireside parents, May 9, 2025) |
| #6 | 2025-05-19 10:23 | Re_Audit_Committee.pdf | CFO Sutter to Medler, Quinlan Aweida and Robert Smartt, May 12–19, 2025: scheduling the Board Audit Committee meeting; DJ/DJE purchasing-policy redline and Q3 financials attached |
| #7 | 2025-05-23 19:12 | Such_a_disappointment.pdf | Example of a letter to bvs.board and all board members (May 23, 2025); Shafer forwards it to a principal |
| #80 | 2026-02-10 08:15 | Bixby_Linked_in.pdf | Medler to Anderson, cc Barber, Feb 10, 2026, 8:15 AM, from alex.medler@nn4da.org: the Bixby LinkedIn post |
| #81 | 2026-02-10 08:28 | Re_Bixby_Linked_in_02102026_0928AM.pdf | Barber's reply, Feb 10 (thanks) |
| #82 | 2026-02-10 09:15 | Re_Bixby_Linked_in (2).pdf | Anderson's reply, Feb 10, 9:15 AM: 'Don't love all of the language they used' |
| #83 | 2026-02-10 09:33 | RE_Bixby_Linked_in.pdf | Medler, Feb 10, 9:33 AM, from nn4da.org: 'all the more reason to control the messaging and chatter among our internal stakeholders' |
| #201 | 2026-04-07 15:16 | Re_Feedback_Requested_Letter_to_Parents_04072026_0416PM.pdf | Barber to the DAC co-chair, Apr 7, 2026, 3:16 PM: 'How do folks in DAC typically sit? By region? We are just thinking about whether to change things up tonight' |
| #205 | 2026-04-07 22:23 | Your_meeting_recap_DAC_Recording_2026_04_07_17_10_MDT_Recording_2_mp4.pdf | Fireflies.ai recap of the DAC session Barber recorded on Apr 7, 2026 (the session Medler is reacting to) |
| #210 | 2026-04-08 10:04 | DAC_April_Meeting_Minutes_Action_Items.pdf | DAC co-chairs' minutes of the Apr 7, 2026 session, sent Apr 8, with the Daily Camera op-ed attached |
| #215 | 2026-04-10 13:46 | Re_Feedback.pdf | The email: Medler to Anderson, Apr 8, 2026 ('sugar coating'; 'You close Mesa and its students are assigned to Bear Creek') and Anderson's Apr 10 reply |
| #322 | 2026-05-01 12:41 | Re_Parent_Questions_for_DAC_Next_Week.pdf | DAC co-chair to Anderson and Medler, Apr 30, 2026: will BVSD hold elementary staffing steady before consolidation? Anderson: 'Yes, I can do that.' |
| LRAC | 2025-09-22 | 2025-09-22-minutes.pdf | LRAC minutes, Sept 22, 2025: 'Board Members in Attendance: Alex Medler'; his remark on boundary letters |
| LRAC | 2026-03-09 | 2026-03-09-minutes.pdf | LRAC draft minutes, Mar 9, 2026: 'a perception that the district already knows what schools are closing and is keeping it from the community' |