RecordWell Data

Police Civilian Oversight Board — Agenda Packet

City of Charlottesville · Charlottesville City County · Police Civilian Oversight Board · meeting of Aug 13, 2026 · Agenda packets

Open the original document More from City of Charlottesville

This document is no longer listed on City of Charlottesville's website. We kept the copy we read.

Text

Extracted automatically from the original. Tables and formatting may not survive; the original document is authoritative.

Regular Meeting Agenda Police Civilian Oversight Board August 13, 2026 CitySpace 100 5th St NE Charlottesville, VA 22902 Police Civilian Oversight Board Dr. Jeffrey Fracher, Chair Dr. Kyle Dobson, Vice Chair George Dillard Jr., LE Rep Andrew Frye, At Large Albe LaFave, At Large Caron LeNoir-Kelly, Community Nathalie Reaves, Community Ruairi Vaughan, At Large 6:30 PM Regular Session I. Call to Order | Roll Call II. Agenda | Minutes Approval III. Announcements IV. First Public Comment Period V. Complaint Investigation Case Review: Moving to Implementation VI. Community Survey: An Essential Tool for Engagement VII. School Resource Officers: Questions and Initial Perspective VIII. Miscellaneous Considerations Following Prior Meeting Discussion IX. Second Public Comment Period X. Adjournment Notice: For members of the public participating virtually, if you experience technical difficulties, you may call (434) 970-3115, and a staff person will assist you. Individuals with disabilities who require assistance or special arrangements to participate in the public meeting may call the ADA Coordinator at (434) 987-1267 or submit a request via email to ada@charlottesville.gov. The City of Charlottesville requests that you provide a 48-hour notice so that proper arrangements may be made. Approval of agenda: August 13, 2026• Approval of minutes: July 9, 2026• September 8 @ 6:30 PM - Expected date for PCOB ordinance first reading at City Council• November 8 @ 1:00 PM to 7:00 PM - Tentative date for Board retreat• Results of Board member survey• Upcoming community engagement opportunities (Board calendar of events)• Overview of complaint case review goals, process, and cadence• Exercise case evaluation through a sample investigation• Board vote to adopt the case review framework process (subject to modifications for SOP)• Overview of community input survey importance and purpose• Report on survey data collected to date• Board member community survey collection through all forms of engagement• Overview of Board framework for engaging in SRO oversight• Board vote to send initial questions and comments to CPD and CCS• Board vote on final draft of purpose statement for proposed ordinance revision• Board vote on position statement regarding CPD data management and analytics tools• -- 1 of 2 -- PCOB Meeting Public Participation Rules Please adhere to respectful conduct, treat other attendees with courtesy, listen actively, avoid interruptions, and refrain from personal attacks or inflammatory language. For the public comment periods, for which there will be two opportunities, please wait for the designated time on the agenda to provide your comments. There is a three-minute time limit for individual comments, but all public participants are welcome to speak during both opportunities. When you speak, we request that you clearly state your name, your organization affiliation, if any, and whether you're a resident of Charlottesville, Albemarle County, or another jurisdiction. During public comment, the Board will not enter into dialogue. The Board will listen carefully to all comments. If there are specific questions, please submit them in writing to the PCOB Office staff after the meeting. Questions or additional comments can be sent to: pcob@charlottesville.gov Using the “Email PCOB” form on the right side of our website homepage: https://www.charlottesville.gov/1440/Police-Civilian-Oversight-Board Acronyms & Abbreviations ADA - Americans with Disabilities Act CCS - Charlottesville City Schools CPD - Charlottesville Police Department LE - Law Enforcement MOU - Memorandum of Understanding PCOB - Police Civilian Oversight Board SOP - Standard Operating Procedure(s) SRO - School Resource Officer -- 2 of 2 -- CHARLOTTESVILLE POLICE CIVILIAN OVERSIGHT BOARD MEETING MINUTES Date: July 9, 2026 Scheduled Time: 6:30 p.m. Location: CitySpace – 100 5th Street NE, Charlottesville, VA 22902 Board Members Attending: Dr. Jeffrey Fracher (Chair), Dr. Kyle Dobson (Vice Chair), Andrew Frye, Albe LaFave, Caron LeNoir-Kelly, Nathalie Reaves, Ruairi Vaughan. Board Members Not Attending: George Dillard Jr. Staff Present: James Walker, Acting Director. Guests: Kim Powell, Chief Operations Officer, Charlottesville City Schools (CCS); Rodney Jordan, Director of Facilities Operations, CCS; Lieutenant Greg Wade, CPD. Call to Order: • The meeting was called to order at 6:31 p.m. by Chair Dr. Jeffrey Fracher, who reviewed the ground rules for participation, including respectful conduct, the two public comment periods available in person and virtually, the three-minute limit for individual comments, the practice that the Board does not enter into dialogue during public comment, and the request that speakers state their name, affiliation, and jurisdiction of residence. Comments may be directed to pcob@charlottesville.gov. • Mr. Walker called the roll. Seven Board members were present, constituting a quorum. Mr. Dillard had advised earlier in the day that he would not be present. Agenda & Minutes Approval: • A motion was made by Mr. Vaughan to approve the agenda for the July 9, 2026 regular meeting as written. Motion seconded by Mr. LaFave and approved unanimously by members present. • A motion was made by Mr. Frye to approve the minutes from the June 11, 2026 regular meeting as written. Motion seconded by Mr. LaFave and approved unanimously by members present. Announcements: • Mr. Walker reported that the proposed ordinance revisions are under simultaneous legal review by the City Attorney’s Office and the Board’s independent counsel, both expected to conclude near the end of July. A final draft will come to the Board at the August meeting for a final vote, distributed well in advance with any changes from the legal review highlighted. Following Board approval, the ordinance will proceed to City Council for a first and second reading, with September identified as the target. • Mr. Walker announced National Night Out, hosted by the Charlottesville Police Department at Booker T. Washington Park on Tuesday, August 4, 2026, beginning at 5:00 p.m. The PCOB has historically attended and staffed a table. • Mr. Walker advised that he will circulate a poll by email and text regarding dates for a Board retreat and shirt sizes for Board apparel. Dr. Fracher added that he and Mr. Walker are seeking an experienced retreat facilitator and asked members to share recommendations for facilitators or locations. • Mr. Walker reminded the Board that work on the upper levels of the Market Street Garage from July 13 through August 28 will substantially limit parking, and noted that parking at the Water Street Garage can be validated. No additional announcements were made. Public Comment (First Period): • One attendee was present online but did not wish to speak. A member of the public commented on retreat facilitation, observing that an effective facilitator functions primarily as a moderator ensuring all participants can express themselves. School Resource Officer MOU – Supporting Implementation: • Dr. Fracher welcomed Ms. Kim Powell, Chief Operations Officer for Charlottesville City Schools (CCS), and Lieutenant Greg Wade of the Charlottesville Police Department (CPD), and asked them to describe the Memorandum of Understanding (MOU) between the two organizations and the status of the School Resource Officer (SRO) program. Background and Memorandum of Understanding • Ms. Powell explained that the SRO program was discontinued in 2020 while students were out of school during the pandemic, and that the protocols adopted in its place proved difficult to apply once students returned. She emphasized that no single incident prompted the officers’ return. She reported that the current working group involved substantially more community engagement than the prior process and that community concerns materially shaped the MOU. • Ms. Powell acknowledged that some community members oppose the return of SROs. She explained that educators are not trained to perform functions required by state code and practical necessity, and noted that families have repeatedly described valuable relationships with prior SROs. She stated that this does not discount instances in which police conduct has fallen short, and identified the Board’s oversight role as part of continuous improvement. • At Dr. Fracher’s request, Ms. Powell summarized the MOU’s principal features. She identified the clarification of roles and responsibilities as the most significant difference from the prior program, and described a new feedback process, distinct from a formal complaint form, giving the school community two avenues for raising concerns or sharing positive observations: the existing CPD process or a school-based process. She introduced Mr. Rodney Jordan, formerly principal of what is now Charlottesville Middle School and now the division’s Director of Facilities Operations. • Lieutenant Wade emphasized the MOU’s clarity on roles and responsibilities, contrasting it with programs elsewhere that place an officer in a school without ensuring the right person is selected, and described the process through the signing of the MOU shortly before Christmas 2025 as collaborative between CCS and CPD. • Lieutenant Wade explained that the two SROs were selected through two separate panel interviews rather than an internal CPD decision. The first panel included Dr. Malone, principal of Charlottesville High School, and Ms. Jodie Murphy, the division coordinator for mental wellness; the second included Mr. Jordan, parent representatives, a special education teacher, a student representative to the School Board, and the incoming middle school principal. Panel members scored candidates’ responses, and both panels reached a unanimous decision. In response to a question from Dr. Fracher regarding whether candidates were self-selected or designated, Lieutenant Wade explained that CPD announces open positions department-wide and officers express interest through the chain of command; two officers applied and both were selected, and the panels were expressly advised they could select both, one, or neither. Board Questions and Discussion • Mrs. LeNoir-Kelly asked what protocols are in place or changing with respect to sexual misconduct by adults within the schools and what protections exist for affected children’s privacy, referencing recent events in Albemarle County. Lieutenant Wade responded that CPD has two detectives assigned specifically to crimes against children who work closely with the division’s mental wellness coordinator, and expressed confidence that the relationships established between CPD and the schools would serve both organizations well should such a matter arise. • Ms. Powell added that required background checks cannot alone guarantee prevention, and described steps being taken, including ensuring that spaces used for one-on-one meetings with students have glass in the door or a sidelight, and a refresher on volunteer vetting to be led by Mr. Jordan at an upcoming division safety summit. Mr. Jordan described the published volunteer approval process and longstanding practices, including never meeting alone with a child or an adult, requiring a second employee for home visits and student transportation, and referring all reports to the division office. • Mrs. LeNoir-Kelly observed that events in the County had caused a break in public trust and emphasized the importance of re-establishing it, particularly given the controversy surrounding the return of SROs, so that families and staff have confidence that students will be believed. A member of the public asked that acronyms be explained for those following the discussion; Ms. Powell reviewed the terms in use. • Ms. Powell stated that maintaining community confidence that meaningful oversight exists is valuable, and noted that the division’s feedback process is intended to dovetail with the Board’s. Dr. Fracher responded that the Board has substantial access to police body-worn camera records and reviews complaints as they are received, including any arising from an SRO’s physical contact with a student, and offered the Board as an ally. Ms. Powell noted that such questions historically arise in ambiguous situations, that the division cannot release the underlying records because they are protected under FERPA, and that staff training will emphasize that the return of SROs does not permit staff to defer situations they would otherwise handle. • Mr. Walker noted that the Board is a civilian-led body with a distinctive legal structure under state code and unusual access, that its jurisdiction extends to the Police Department rather than the schools, and that it can provide perspective, recommendations, and opinions in a structured and confidential format. Staffing, Response, and Daily Operations • Dr. Fracher asked whether a single officer at each school represents adequate coverage. Lieutenant Wade responded that the officers will adhere to the Department’s mission of building relationships and trust at Charlottesville High School (CHS) and Charlottesville Middle School (CMS), acknowledged that circumstances may call for more than one officer but stated that one is better than none, and noted that any expansion would depend on program performance and the will of the schools and community. • Mr. LaFave asked what objections community members have raised and how those are being addressed. Lieutenant Wade identified two: that an officer’s presence would convert matters ordinarily handled through school discipline into arrests, and that SROs will be armed in a school setting. He stated that the MOU is explicit that where a matter can be handled as school discipline it will be, and that firearms reflect state code and Department policy. • Mrs. LeNoir-Kelly raised community concerns regarding profiling on the basis of race and of sexual and gender identity. Ms. Powell confirmed those concerns have been expressed publicly and added that families in the immigrant community have raised concerns regarding federal immigration enforcement. She stated that there is no agreement for CPD to assist with immigration enforcement, that the division could terminate the MOU should that change, and that the program is a school resource function rather than school policing. • Ms. Powell directed the Board to the June 4, 2026 School Board meeting, which included the division’s first comprehensive presentation of the underlying data. Calls for service at Charlottesville High School were 64 (2019), 65 (2020, a partial year), 41 (2021), 95 (2022), 82 (2023), 76 (2024), 55 (2025), and 12 through the first quarter of 2026. She indicated that arrests over the same period were minimal and should not be expected to increase as a result of the program, and noted that the MOU calls for quarterly reporting. • Mr. Vaughan asked whether any comparison exists between disciplinary trends in Charlottesville City Schools and in nearby localities that retained their SRO programs, clarifying that his interest was in incident trends. Ms. Powell responded that no such comparison has been conducted and observed that, because the MOU excludes SROs from school discipline, discipline data may not be the appropriate measure. Mr. Walker offered the Office’s and Board’s assistance in reviewing comparable localities, asking only that the resulting data be shared. • Mr. LaFave asked how quickly a single SRO can respond to an incident and what de- escalation techniques would be used. Lieutenant Wade explained that SROs carry both a police radio and a school radio and know the building layout, giving them direct awareness of developing situations and allowing a faster response than a patrol officer dispatched through a 911 call. • Dr. Fracher asked Mr. Jordan how a feedback loop with the central office would function. Mr. Jordan confirmed that he will be in regular communication with the SROs, Lieutenant Wade, and the building principals, and that the SRO reports directly to the principal. Lieutenant Wade added that the MOU governs what it terms official contact with a student (an investigative stop or other police action) and requires the officer both to articulate a constitutional basis and to clear the contact with the principal in advance, absent an emergent situation. He stated that nothing done in an enforcement capacity would go unmonitored or unrecorded, and that any pattern of profiling would be identified early through those safeguards. • Mrs. LeNoir-Kelly asked what activities the SROs will undertake to integrate into the school community, including informal engagement with students. Lieutenant Wade identified the back-to-school period as an immediate opportunity, citing National Night Out and back-to- school events. Ms. Powell described focus groups arranged with student leaders shortly after the officers were selected, in which students advised the SROs on how best to integrate, and Mr. Jordan described pep rallies, athletic events, and performing arts productions as further opportunities. Mrs. LeNoir-Kelly noted that her daughter recently graduated from Charlottesville High School and had observed that students were not consulted when SROs were removed or returned. • Mr. Jordan noted that the SRO should not ordinarily be the first responder to a typical school incident, explaining that care and safety assistants assigned to specific locations should respond first. Ms. Powell identified this as a significant change: the division now employs care and safety assistants who are DCJS-certified school security officers, a resource that did not exist previously and part of why a single SRO per school may be sufficient. She noted that the community does not want SROs patrolling hallways, that student searches remain governed by a reasonable suspicion standard, and that vape detector alerts and cell phone policy are handled by administrators, not the SRO. • Dr. Dobson observed that the data reflects substantial demand for service alongside very low arrest activity. He noted that some community members will not trust the institutions represented in the room to uphold the MOU, and that the Board’s role is to hold both accountable. He argued that institutions measure discipline and arrests far better than the mentorship functions the MOU assigns to SROs, and urged that those outcomes be defined and measured early. Dr. Fracher agreed that messaging remains essential. • Mr. Frye asked about how connections between officers and students will be continuing practice? Ms. Powell noted that Ms. Bianca Johnson, who oversees restorative practices for the division, attended the student focus groups and took notes, and reported recommending that the incoming middle school principal include the SRO in her weekly message to staff and families. Ms. Powell also described a process for engaging officers through classes, specific student groups already formed for other purposes, but noted this process needs to be more fully developed over time. • Mr. Vaughan asked how readily the MOU could be adjusted if a provision proved unworkable, using officer deployment within the building as an example, and clarified that his concern was the ability to revisit provisions following a case review that generated community concern. Ms. Powell responded that the principal determines where the SRO is assigned and may redeploy the officer as circumstances require, described an order of operations under which life-safety emergencies take precedence, followed by threat assessments and scheduled activities, and noted that the agreement is reviewed annually. • Mr. Vaughan asked about the renewal process for the MOU, which concludes in 2028, and how SROs will be apprised of in-classroom strategies used by educational staff. Ms. Powell responded that quarterly reports and an annual review are the principal mechanisms and that the agreement continues absent termination by either party, and that the SROs will participate in pre-week safety training, DCJS training, and restorative justice training. Mr. Frye asked how the student focus group engagement would be sustained; Ms. Powell noted that state-required school climate surveys include questions on students’ perceptions of their SRO, and acknowledged that ongoing student dialogue has not yet been formalized. • Mr. Vaughan asked whether that training identifies the threshold at which law enforcement becomes involved. Lieutenant Wade described two circumstances: where conduct presents a serious threat of bodily harm to another, in which case involvement does not automatically result in charges; and where a victim wishes to seek prosecution, in which case officers are obligated by law to assist. • Lieutenant Wade confirmed that the SROs will be assigned within the Community Services Bureau. Dr. Fracher thanked the guests and noted a low level of community awareness that the Board will provide oversight of the program; Ms. Powell suggested collaborating on messaging so that the community is reminded of the Board’s role. Mr. Walker noted that the MOU provides that concerns proceed through CPD’s process and does not address the Board’s role, although the Board’s jurisdiction over the officers creates a clear connection. Work Plan Updates – Office and Board: • Mr. Walker reported that he has reviewed the MOU and identified questions for the Board, including that it does not address body-worn camera activation, and raised whether the Board could serve as an additional avenue for receiving complaints alongside the schools’ feedback process. • Mr. Walker described the binders distributed to Board members, intended to provide a consistent and updated set of reference materials including the Office work plan and goals, which he will collect and update at each meeting and can also share digitally. He thanked Mrs. LeNoir-Kelly for her assistance. • Mr. Walker reported that he is completing his FY27 work plan, due the following week and serving as the basis for his evaluation through the City Manager’s Office, and will share it with the Board. He recommended that the Board revisit the work plan it developed at the beginning of the year, noting Mr. LaFave’s earlier emphasis on establishing priorities and that School Resource Officer matters have become time-sensitive with the school year approaching. He proposed identifying a date for a work session focused on a small number of priorities and will include the question in the scheduling poll. Advancing Priorities: • Community Connections: Mr. Walker reported that the community listening survey has been finalized and is available in digital and print formats. He noted that surveys are a collection tool rather than a substitute for building relationships, and asked the Board to consider ways to distribute it alongside opportunities for direct conversation. • Policy Review: Mr. Walker identified the CPD policies connected to the SRO program as a near-term focus, including whether any conflicts exist between the MOU and Department policy. • Direct Oversight: Dr. Dobson stated that case review is likely the function the community most expects of the Board. Measured against a model of parallel review of all complaints received by CPD, the Board is approximately fourteen cases behind for the year, of which four fall within the courtesy category. He proposed beginning with those four and proceeding systematically through the remaining categories, and suggested identifying a date outside the regular meeting and whether a small group or the full Board would conduct the review. Parallel review would also allow the Board to provide complainants with more than the single-page disposition letter currently issued. The proposal was offered for discussion rather than as a matter requiring a vote. • Dr. Fracher asked whether clarification had been obtained regarding closed sessions and case review. Mr. Walker responded that the applicable statute is restrictive and permits closed session only in limited circumstances, but noted that matters involving school resource officers and juveniles may create new pathways for closed session, which benefits confidentiality and privacy. • Dr. Fracher asked how material reviewed individually or in pairs would be brought together for a public position. Mr. Walker described the scorecard process, a draft of which is in the Board binders. Board members would review body-worn camera footage and the case summary at the Office individually or in pairs, scoring the case and taking notes with the understanding that the material will be used in public session and must contain no identifying information, subject to redaction. The subsequent public discussion would address findings, decisions, and policy implications in general terms. • Dr. Fracher reported preliminary discussion regarding the second position in the Office, including its job description and role, with the goal of shifting day-to-day work from the Acting Director and supporting case review preparation. He noted that the title and placement within the City’s structure remain under consideration and expressed hope the position could be filled by the end of the year. • Dr. Fracher and Mr. Walker urged Board members to complete their ride-alongs by the end of July. Dr. Dobson asked that members document observations from ride-alongs, conversations, and community events so that the knowledge gained is captured for the Board rather than retained individually; Dr. Dobson concurred. • Mr. Walker indicated he would circulate dates for back-to-school events, noting that they allow for brief contact and distribution of materials rather than extended dialogue but remain valuable. He identified an event at Southwood in Albemarle County, which draws significant participation from the immigrant and Hispanic community, as well as events downtown. Dr. Fracher cautioned that a member of that community, with whom they had spoken that morning, described a high level of fear following recent federal immigration enforcement activity in Greene County, and advised that anxiety within the community may limit turnout. • Dr. Dobson indicated he would follow up on dates for case review, noting that if a first review is completed within one to two months, the September or October regular meeting could serve as the public session at which the four cases are reviewed. Public Comment (Second Period): • Mr. Clarence Johnson addressed the Board, describing prior experience in community activism dating to 1995 and commending the Board for taking a proactive rather than a reactive approach. He encouraged the Board to hold town halls or similar forums so that community members can see how they benefit and become involved, which he suggested would also generate volunteers. He emphasized keeping lines of communication open. No additional public comment was received, either in person or online. Adjournment: • A motion to adjourn was made by Mr. Frye and seconded by Mr. LaFave. The motion was approved unanimously by members present. • Meeting adjourned at approximately 8:20 p.m. Certified by James Walker, Acting PCOB Director Date Adopted: ____________________________ Certified: ________________________________ CHARLOTTESVILLE POLICE CIVILIAN OVERSIGHT BOARD AUGUST 2026 Board Member SurveyResults What Board members told us about their training needs, agenda priorities, and how they want to contribute 5 of 5 Board members completed the survey 10 training topics rated — every one judged useful by every member 5 of 5 rated internal affairs complaint data a high agenda priority Board Member Survey conducted July–August 2026 (n = 5). BOARD MEMBER SURVEY · TRAINING NEEDS Every training topic rated useful; two rated essential most often No Board member rated any topic “not useful.” Standards for reviewing investigations and communicating the Board’s work drew the most “essential” ratings; procedural topics like Robert’s Rules and administrative law ranked lowest. Somewhat useful Very useful Essential Standards for reviewing & evaluating investigations Communicating the Board’s work to audiences Police policies, practices & procedures Internal affairs & administrative investigations Virginia FOIA & open meetings requirements Police technology, records & data systems Constitutional policing & oversight law Board ordinance, bylaws, authority & limits Robert’s Rules & public meeting procedures Administrative law & due process Each bar shows all 5 Board members’ ratings, ordered by share rating the topic essential. Board Member Survey, July–August 2026 (n = 5) 08 / 11 BOARD MEMBER SURVEY · LEARNING & CONTRIBUTION Hands-on learning, outward-facing work PREFERRED TRAINING FORMATS Members chose all that apply (n = 5) In-person workshop 5 Live virtual training 5 Case studies & exercises 5 Site visits / observation 4 Recorded / self-paced 3 Short written guides 1 Individual coaching 1 Every member chose interactive formats; passive materials trailed far behind. WHERE MEMBERS WANT TO CONTRIBUTE Ranked preference, next 12 months — weighted score of 8 Community outreach & education 6.4 Complaint & incident review 6.4 Monitoring police operations 5.2 Policy review & development 5.0 Police data & research 4.8 Oversight data & best practices 4.2 Board governance & meetings 2.8 Strategic planning 2.4 Members gravitate toward public-facing, case-level work over internal governance tasks. Board Member Survey, July–August 2026 (n = 5) 09 / 11 BOARD MEMBER SURVEY · AGENDA PRIORITIES Complaint data is the unanimous top priority Low priority Moderate priority High priority Internal affairs complaint & incident data General police activity data & trends Community perspectives & presentations Police policies, practices & procedures Civilian oversight law & best practices Subject-matter expert presentations Officer training, recruitment & culture Board strategic planning & priority setting Oversight office activities & workload Police budget & financial reporting All 5 members’ ratings per topic, ordered by share rating it high priority. HOW LEADERSHIP CAN SUPPORT MEMBERS Meet more often — “Once a month is not enough to make any effective change.” Staff the oversight office — add support so the director can focus on operations rather than administrative tasks. 3 of 5 answered; the third response: “More of the same!” Board Member Survey, July–August 2026 (n = 5) 10 / 11 CITY OF CHARLOTTESVILLE, VIRGINIA DRAFT Case Review Cycle: Process & Cadence Framework Office of Police Civilian Oversight & Police Civilian Oversight Board CONTENTS 1 Purpose 1 2 Definitions 2 3 The Monthly Cadence 3 4 Case Review Cycle Model 4 5 The Directorʼs Summarization Role 5 6 Voting 5 7 Contingencies 6 8 Internal Affairs Finding Definitions 6 A Case Evaluation Card 7–8 B Evaluation Rubric 9–13 C Statement Starters for Findings 14 D Case Summary Sheet 15 E Case Batch Summary 16–18 1. Purpose This framework establishes the recurring monthly cycle by which administrative investigation cases closed by the Internal Affairs Bureau of the Charlottesville Police Department are grouped into batches, reviewed individually by members of the Police Civilian Oversight Board, summarized by the Director of the Office of Police Civilian Oversight, refined through a Board comment period, and voted on for approval of the Board's final Determinations, Findings, and Recommendations. Approved outcomes are transmitted to the Chief of Police, the complainant, and, as applicable, the City Manager and City Council, and posted publicly to the PCOB website. Every date is anchored to the Board's regular meeting on the second Thursday of each month, so the cadence repeats from month to month. Each batch takes seven weeks to move from its cutoff to a final vote, spanning two regular meetings; when a five-week gap falls between two meetings inside that span, it takes eight. The spare week goes to whichever phase spans the gap: review runs four weeks if the gap precedes the evaluation deadline, or a buffer week precedes the vote if it follows. Because a new batch begins each month, three batches are in motion at any given time, and every regular meeting serves double duty: the Board votes on the batch finalized that cycle and simultaneously reaches the evaluation deadline for the batch currently under individual review. OFFICE OF POLICE CIVILIAN OVERSIGHT · CASE REVIEW CYCLE FRAMEWORK DRAFT — AUGUST 2026 · PAGE 1 OF 18 2. Definitions Batch All cases whose closure date falls after the prior batch cutoff, through the current batch cutoff, together with any case returned by an unsuccessful vote under Section 6. Batches are named by their evaluation deadline (e.g., Batch 2026-09-10). Batch cutoff One week after a regular meeting, the same date the prior batch's Case Batch Summary is issued. Cases closing after a cutoff roll forward to the next batch. Case Evaluation Card Each member's individual review instrument for a case: Yes / No determinations on each evaluation factor with supporting Findings, plus the member's own Determination and Recommendations. Case Batch Summary The Director's draft consolidation, issued for Board comment: members' factor determinations plus their mediated, consolidated Findings for each case. Comment period The two weeks after a summary is issued, during which members propose changes, additions, or redactions. Final Case Review Package The Case Batch Summary as revised through the comment period, together with a per-case Determination, Findings, and Recommendations drawn from members' cards and comments. This is what the Board votes on. Determination The Board's concurrence or non-concurrence with the outcome of a case, allegation by allegation: whether the Board concurs with the Internal Affairs finding on each allegation — Sustained, Unfounded, Exonerated, or Not Resolved, as defined in Section 8 — and, for each sustained allegation, whether it concurs with the discipline imposed. Where the investigation is incomplete or unsatisfactory and supports no clear determination, the Board records that instead. Findings The objective facts, observations, data, or analysis — related to Department policy, practice, and procedure, and to the allegation, evidence, and investigation — that support the Determination. Every Determination carries Findings; non-concurrence must rest on Findings that support it. Recommendations Requested changes or resolutions arising from the review — policy, practice, procedure, systems, investigation methods, discipline, or training — that the Board raises to the Chief of Police and, as appropriate, the City Manager and City Council. Recommendations must be supported by the Findings. Regular meeting The Board's monthly public meeting, held the second Thursday of each month. OFFICE OF POLICE CIVILIAN OVERSIGHT · CASE REVIEW CYCLE FRAMEWORK DRAFT — AUGUST 2026 · PAGE 2 OF 18 3. The Monthly Cadence Each batch moves through six phases. Individual review runs three or four weeks depending on the interval between meetings; every later phase runs a fixed length. When five weeks separate two meetings, the spare week goes to the phase spanning that gap — review stretches to four weeks if the gap precedes the evaluation deadline, or a buffer week precedes the vote if it follows. Phase What happens Responsible Timing rule 1 · Batch Formation Cases closing after the prior cutoff, through the current cutoff, plus any case returned by an unsuccessful vote, form the batch and are available for review in the PCOB Office. Director Cutoff = 1 week after a regular meeting 2 · Individual Review Available members review every case in the batch in person at the PCOB Office, given the confidential nature of the content, and complete an evaluation card for each case. Available members Cutoff → next regular meeting (deadline); 3–4 weeks 3 · Summary Compilation Director consolidates and mediates members' factor determinations and Findings into the draft Case Batch Summary. Director 1 week after the meeting; issuance date = next batch's cutoff 4 · Comment Period Members review the Case Batch Summary and propose changes, additions, or redactions. Available members 2 weeks from summary issuance 5 · Finalization Director resolves comments and completes the Final Case Review Package: the revised summary plus per-case Determination, Findings, and Recommendations. Director 1 week after comments close; a spare week before the vote is buffer 6 · Vote & Transmittal Board votes on each case in the Final Case Review Package. Approved cases are transmitted to the Chief of Police, the complainant, and, as applicable, the City Manager and City Council, and posted publicly. Cases not approved return to the next batch. Board Regular meeting following finalization HOLIDAY RULE — Any cutoff, deadline, or issuance date falling on a City holiday or office closure shifts to the next business day. Meeting dates are governed by the Board's adopted schedule. OFFICE OF POLICE CIVILIAN OVERSIGHT · CASE REVIEW CYCLE FRAMEWORK DRAFT — AUGUST 2026 · PAGE 3 OF 18 4. Case Review Cycle Model This model shows three consecutive batches through the full cycle. Each column is one week; navy markers are regular meetings. Read one row left to right: (1) cases close during the collection period (dotted line) and the batch is fixed at its cutoff (red line) one week after a meeting — Batch Aʼs began earlier; (2) members review the cases in person using evaluation cards, with the next meeting as the deadline; (3) the Director compiles the draft summary in one week; (4) members comment for two weeks; (5) the Director finalizes in one week; and (6) the Board votes at the next meeting. When five weeks separate meetings the spare week goes to the phase spanning it: for Batch C that falls after the evaluation deadline, so a buffer week precedes the vote; earlier, review runs four weeks. Every batch shown here has a four-week gap before its deadline, so each review block is three weeks. MEETINGS ▼ MTG 1 ▼ MTG 2 ▼ MTG 3 ▼ MTG 4 ▼ MTG 5 ▼ Batch A votes at Mtg 3 ⋯ review comment VOTE Batch B votes at Mtg 4 case closures review comment VOTE Batch C votes at Mtg 5 case closures review comment VOTE WEEK ▶ 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 KEY BOARD: Individual review with evaluation cards Comment period on Case Batch Summary DIRECTOR: Case Batch Summary compilation Finalization after Board comments CORE DATES: Case batch cutoff Case closure collection period Vote & transmittal Buffer week (five-week gap before the vote) Batch Case closure window ReviewEvaluation deadline (meeting) Summary issued Comments close Board vote (meeting) 2026-09-10Jul 17 – Aug 20 ▸▸Sep 10, 2026 Sep 17, 2026 Oct 1, 2026 Oct 8, 2026 2026-10-08Aug 21 – Sep 17 ▸▸Oct 8, 2026 Oct 15, 2026 Oct 29, 2026 Nov 12, 2026 † 2026-11-12 Sep 18 – Oct 15 ▸▸Nov 12, 2026 ‡ Nov 19, 2026 Dec 3, 2026 Dec 10, 2026 2026-12-10Oct 16 – Nov 19 ▸▸Dec 10, 2026 Dec 17, 2026 Dec 31, 2026 Jan 14, 2027 † 2027-01-14Nov 20 – Dec 17 ▸▸Jan 14, 2027 ‡ Jan 21, 2027 Feb 4, 2027 Feb 11, 2027 2027-02-11 Dec 18 – Jan 21 ▸▸Feb 11, 2027 Feb 18, 2027 Mar 4, 2027 Mar 11, 2027 2027-03-11 Jan 22 – Feb 18 ▸▸Mar 11, 2027 Mar 18, 2027 Apr 1, 2027 Apr 8, 2027 2027-04-08Feb 19 – Mar 18 ▸▸Apr 8, 2027 Apr 15, 2027 Apr 29, 2027 May 13, 2027 † 2027-05-13Mar 19 – Apr 15 ▸▸May 13, 2027 ‡ May 20, 2027 Jun 3, 2027 Jun 10, 2027 2027-06-10Apr 16 – May 20 ▸▸Jun 10, 2027 Jun 17, 2027 Jul 1, 2027 Jul 8, 2027 2027-07-08May 21 – Jun 17 ▸▸Jul 8, 2027 Jul 15, 2027 Jul 29, 2027 Aug 12, 2027 † † Five weeks separate the evaluation deadline from the vote; the week after finalization is buffer. ‡ Five weeks separate the cutoff meeting from the evaluation deadline; review runs four weeks, not three. Marked batches take eight weeks cutoff-to-vote, not seven. OFFICE OF POLICE CIVILIAN OVERSIGHT · CASE REVIEW CYCLE FRAMEWORK DRAFT — AUGUST 2026 · PAGE 4 OF 18 5. The Director's Summarization Role In compiling each Case Batch Summary (Appendix E) the Director acts as summarizer and mediator, presenting members' Yes / No factor determinations and a consolidated account of their Findings in which the Director: Consolidates similar or duplicative Findings; Highlights conflicts or differences among member views and recommends a resolution; Frames or redacts content to stay within the ordinance and best represent the Board's view; May advise members on specific Recommendations that are relevant and feasible; and Protects confidential and personally identifiable information (PII) throughout. All Board input is logged and retained; the summary is the mediated account of that record. Each reviewing member records their own Determination, Findings, and Recommendations on their card; the Director consolidates these into a single set per case, reconciling differences and keeping the result within the Board's authority — introducing no substance of their own. The summary is a draft issued for comment; the Director then revises it and states the per-case Determination, Findings, and Recommendations from members' cards and comments — the Final Case Review Package the Board votes on. 6. Voting The Board votes on each case in the Final Case Review Package at the regular meeting following finalization. Who may vote Any member who has reviewed the Final Case Review Package may vote; review of the underlying case file is not required, which lets routine cases move efficiently. A member may approve the Determination, Findings, and Recommendations — the reviewing members' work as consolidated by the Director — abstain, or vote against. Number of reviewers Cases are reviewed by any members able and available during the review period. A batch proceeds so long as at least one member completes review; if none is able, the contingency in Section 7 governs. Approval threshold Approval of a case requires a simple majority of the members present at a meeting with quorum. If the investigation supports no determination Where the Determination is that the investigation was incomplete or unsatisfactory and supports no clear determination, the Board votes on that conclusion and the Recommendations that follow from it. If a case is not approved The case falls back into review with the following batch and repeats this process. The comments and record from the unsuccessful vote are logged and carried forward. OFFICE OF POLICE CIVILIAN OVERSIGHT · CASE REVIEW CYCLE FRAMEWORK DRAFT — AUGUST 2026 · PAGE 5 OF 18 7. Contingencies Meeting canceled or no quorum Deadlines anchored to that meeting shift to the next meeting held (regular or special). Batch cutoffs already passed remain fixed, so batch composition is unchanged. The Director circulates revised dates to all members within three business days of the cancellation. Batch not reviewed If no member is able to review a batch during its review period, the batch carries forward and is reviewed together with the following batch on the next cycle. Its cutoff and composition remain fixed. Expedited (out-of-batch) review A case may be reviewed outside the standing batch cadence if agreed upon by the Director, Chair, and Vice Chair. An expedited case follows the same sequence of evaluation cards, summary, comment, finalization, and vote, on a compressed schedule set at the time of the referral. 8. Reference: Internal Affairs Finding Definitions Internal affairs complaint investigations may result in one of the following findings. Board members should consider these definitions when evaluating the Sufficiency of the investigation's analysis and outcome. Sustained The allegation is supported by the evidence and violated Department policy. Unfounded The allegation is not supported by the evidence. Exonerated The allegation is supported by the evidence but is within Department policy. Not Resolved There is not enough evidence to render a clear finding. OFFICE OF POLICE CIVILIAN OVERSIGHT · CASE REVIEW CYCLE FRAMEWORK DRAFT — AUGUST 2026 · PAGE 6 OF 18 APPENDIX A DRAFT Case Evaluation Card CASE & REVIEWER REVIEWING BOARD MEMBER (PRINTED): SIGNATURE OF REVIEWER: IA CASE NUMBER: DATE OF COMPLAINT: DATE OF REVIEW: EVALUATION FACTORS Mark each factor Yes or No using the Evaluation Rubric (Appendix B) and explain your rationale in the Findings column. Appendix C offers statement starters. Evaluation Factor Yes / No Findings 1. Accuracy Was the factual basis of the investigation accurate Yes  /  No 2. Completeness Was the evidence needed to resolve each allegation collected Yes  /  No 3. Impartiality Was the process objective Yes  /  No 4. Sufficiency Was the analysis of that evidence adequate and any discipline sufficient Yes  /  No ADDITIONAL FINDINGS Objective facts, observations, data, or analysis from the case record that inform your Determination NOTE TO BOARD MEMBERS — Refer to parties by role — Officer A, Witness B, the complainant — and to the case by IA case number. Do not record names or other personally identifying details. OFFICE OF POLICE CIVILIAN OVERSIGHT · APPENDIX A · CASE EVALUATION CARD DRAFT — AUGUST 2026 · PAGE 7 OF 18 APPENDIX A — CASE EVALUATION CARD, CONTINUED Each reviewing member records their own Determination and Recommendations below. The Director consolidates each member's Determination, Findings, and Recommendations into a single set for each case in the Final Case Review Package, reconciling differences without adding substance of their own. DETERMINATION ☐ Concurs with all allegation findings and disciplinary action of the Internal Affairs Investigation. ☐ Does not concur with some or all of the allegation findings and/or does not concur with all or some of the disciplinary actions of sustained allegations.  ALLEGATION FINDINGS — AS NUMBERED ON THE CASE SUMMARY SHEET (APPENDIX D) ALLEGATION # CONCURDOES NOT CONCUR ☐ ☐ ☐ ☐ ☐ ☐ ☐ ☐ ALLEGATION # CONCURDOES NOT CONCUR ☐ ☐ ☐ ☐ ☐ ☐ ☐ ☐ DISCIPLINE — SUSTAINED ALLEGATIONS ONLY ALLEGATION # CONCURDOES NOT CONCUR ☐ ☐ ☐ ☐ ALLEGATION # CONCURDOES NOT CONCUR ☐ ☐ ☐ ☐ ☐ Investigation incomplete or unsatisfactory and does not support a clear determination above. RECOMMENDATIONS Requested changes to policy, practice, procedure, systems, investigation methods, discipline, or training, if any OFFICE OF POLICE CIVILIAN OVERSIGHT · APPENDIX A · CASE EVALUATION CARD DRAFT — AUGUST 2026 · PAGE 8 OF 18 APPENDIX B DRAFT Evaluation Rubric Standard of review, definitions, criteria, and guiding questions for the four evaluation factors on the Case Evaluation Card (Appendix A). This rubric provides definitions, Yes / No criteria, and guiding questions for each of the four evaluation factors derived from the Board's oversight authority under Charlottesville City Code Article XVI. These factors reflect standards recognized in professional oversight practice, including frameworks from NACOLE, the Council of the Inspectors General on Integrity and Efficiency (CIGIE), and the DOJ Office of Community Oriented Policing Services (COPS Office). Examples throughout this appendix draw on a single scenario: a complaint alleging that an officer used excessive force by deploying a taser during an arrest. STANDARD OF REVIEW All four factors ask one underlying question: did the investigation do enough to support the conclusion it reached — and, where an allegation was sustained, does the discipline imposed fit the infraction? None of them asks whether the investigation was exhaustive. Internal Affairs investigators work with finite time, staffing, and access, and every case requires a judgment about how much inquiry a given allegation warrants. Some allegations demand extensive work; others are resolved by a single recording. The threshold is a well- supported conclusion, not a perfect one. An investigation is not deficient because a reviewer can imagine another question that might have been asked, another witness who might have been interviewed, or another record that might have been pulled. It is deficient when something left undone leaves a question unresolved that a reasonable reviewer would need answered in order to accept the finding. The operative test is materiality: would the missing piece plausibly have changed the outcome, or cast real doubt on it? HOW TO APPLY THIS STANDARD Judge the investigation that was run, not the one you would have run. Ask whether the record in front of you supports the finding — not whether you would have approached the case differently. Test every omission for materiality. For anything not done, ask whether it plausibly would have changed the finding. If it would not, that omission does not make the factor a No. Expect proportionality. A straightforward allegation resolved by clear evidence warrants less investigative effort than a contested one. Scale your expectations to what the allegation actually required. When it is close, mark Yes and write the concern. If the record supports the conclusion but you see something that could have been done better, mark Yes and record the concern in your Findings or Recommendations. Reserve No for deficiencies that undermine the finding itself. A No is not a judgment about how hard the investigator worked. It is a statement that the record, as it stands, does not support the conclusion reached. Findings are required either way. OFFICE OF POLICE CIVILIAN OVERSIGHT · APPENDIX B · EVALUATION RUBRIC DRAFT — AUGUST 2026 · PAGE 9 OF 18 APPENDIX B — EVALUATION RUBRIC, CONTINUED FACTOR 1: ACCURACY Definition: Accuracy measures the degree to which the investigation's conclusions, observations, characterizations, and findings are grounded in documented, verifiable facts rather than assumptions, opinions, or unsupported inferences. An accurate investigation distinguishes between what the evidence establishes and what the investigator interprets, and it represents witness statements and other evidence faithfully in its analysis and summary. Yes / No Description Yes All material factual claims in the investigative report are supported by documented, verifiable evidence. The report distinguishes what the evidence establishes from what the investigator interprets, and witness statements are represented faithfully. Any interpretive language is minor and does not affect the findings or outcome. No One or more material conclusions rest on assumption, inference, or opinion rather than documented evidence. This includes speculative language, characterizations of credibility without adequate basis, or a narrative that oversteps what the evidence establishes in ways that could affect the outcome. GUIDING QUESTIONS Do the factual statements that carry the finding trace to specific evidence — report, recording, interview, or record? Where the report characterizes behavior (“aggressive,” “resisting”), is that characterization supported by what the evidence actually shows? Are witness and officer statements represented as given, without paraphrase that changes their meaning? Does the report separate what the evidence establishes from what the investigator concludes? Where a statement is unsupported, does it affect the finding — or is it incidental detail that does not? EXAMPLES YES — ACCURATE “Body-worn camera at 03:12 shows the subject pulling his right arm away from Officer Aʼs grip; Officer A announced ʻTaser, Taserʼ before deploying.” WHY The characterization of resistance is tied to a timestamped recording, and the warning is verifiable on that same footage rather than asserted. NO — NOT ACCURATE “The subject was combative and left the officer no choice but to deploy the taser.” WHY “Combative” and “no choice” are conclusions with no cited evidence. The report never identifies what the subject did or points to footage, and presents the investigatorʼs judgment as established fact. OFFICE OF POLICE CIVILIAN OVERSIGHT · APPENDIX B · EVALUATION RUBRIC DRAFT — AUGUST 2026 · PAGE 10 OF 18 APPENDIX B — EVALUATION RUBRIC, CONTINUED FACTOR 2: COMPLETENESS Definition: Completeness measures whether the investigation gathered the evidence needed to resolve each allegation. A complete investigation pursues the sources of evidence that are material to the allegations and reasonably available to the investigator — testimonial, physical, documentary, and digital — and questions the parties in enough detail to address each element of each allegation. It also considers timeliness: whether evidence at risk of being lost, degraded, or contaminated was collected while it was still available. Completeness is measured against what the allegation required, not against an inventory of everything that theoretically could have been collected. It asks only whether the evidence was gathered; what the investigation then did with that evidence is Factor 4. Yes / No Description Yes The evidence needed to resolve each allegation was collected. The witnesses and records material to the allegations were pursued, evidence at risk of loss was collected in time, and interviews were detailed enough to address each element of each allegation. Anything not gathered — whether by investigative judgment, unavailability, or an uncooperative party — would not reasonably have changed the outcome. No Evidence material to an allegation was not gathered or preserved, leaving a question unresolved that a reasonable reviewer would need answered to accept the finding. For example: a witness whose account could have changed the outcome was never contacted; an interview stopped short of an issue central to the allegation; or recorded evidence was allowed to lapse past its retention window. GUIDING QUESTIONS Was the evidence the finding actually turns on obtained — the accounts and records needed to resolve each allegation? Where a witness was not interviewed or a record not pulled, is there reason to think it would have changed the outcome? Do the interviews address each element of the allegation, or stop short of an issue central to it? Was evidence at risk of loss (retention windows, medical records, scene photographs) collected while it was still available? Where evidence is missing because a source did not exist or a party declined to cooperate, is that documented rather than left unexplained? Is your concern that evidence is missing, or that the investigation mishandled the evidence it had? The latter belongs under Sufficiency. EXAMPLES YES — COMPLETE “Body-worn camera from all four responding units, the taser deployment log, dispatch audio, and the complainantʼs emergency department records were obtained within the retention window; the complainant, both involved officers, and two independent witnesses were interviewed.” WHY Every reasonably available source was pursued and secured in time, and the interviews covered each element of the allegation. NO — NOT COMPLETE “Officer A and Officer B were interviewed. The complainant declined to provide a statement.” WHY No body-worn camera, taser log, or dispatch audio was obtained, and the two bystanders named in the initial report were never contacted. The record cannot resolve the central factual dispute. OFFICE OF POLICE CIVILIAN OVERSIGHT · APPENDIX B · EVALUATION RUBRIC DRAFT — AUGUST 2026 · PAGE 11 OF 18 APPENDIX B — EVALUATION RUBRIC, CONTINUED FACTOR 3: IMPARTIALITY Definition: Impartiality measures the objectivity and fairness of the investigative process and its outcome. An impartial investigation treats all parties consistently, weighs evidence without favoritism, avoids prejudgment, and reaches a conclusion that follows from the evidence rather than from a predetermined narrative. It encompasses both procedural fairness (how the investigation was conducted) and analytical fairness (how the evidence was interpreted). Yes / No Description Yes The investigation was conducted and concluded without indication of bias, prejudgment, or favoritism toward any party. All witnesses — complainant and officer alike — were treated consistently. The evidence was weighed and interpreted evenhandedly, and the finding flows logically from the evidence without any appearance of a predetermined outcome. Any minor concerns (e.g., differences in interview tone) did not influence the analysis or outcome. No Indicators of bias or imbalance are present in the process or the analysis. This may include leading questions directed at one party, one account given greater weight without clear justification, selective emphasis on evidence favoring a particular outcome, dismissal of credible testimony without adequate explanation, or conclusions that appear driven by a predetermined outcome rather than the evidence. GUIDING QUESTIONS Were the complainant and the involved officer questioned with comparable rigor? Was evidence that cuts against the eventual finding engaged with, or set aside without explanation? Does the analysis follow the evidence, or read as though the conclusion came first? Were credibility judgments applied to one party only, and on grounds relevant to this incident? Is your concern about bias, or about how much investigation was done? The latter belongs under Completeness. EXAMPLES YES — IMPARTIAL “The report notes that Officer Aʼs account of a closed fist is not visible on body-worn camera, and evaluates both the officerʼs and the complainantʼs accounts against the footage before reaching a finding.” WHY Evidence unfavorable to the officer is surfaced and weighed rather than omitted, and both accounts are tested against the same objective record. NO — NOT IMPARTIAL “The complainant has two prior complaints against the Department and his account was therefore given limited weight. Officer A is a decorated ten-year veteran.” WHY One partyʼs credibility is discounted on grounds unrelated to this incident while the otherʼs is bolstered by service history. Neither judgment is tied to the evidence in this case. OFFICE OF POLICE CIVILIAN OVERSIGHT · APPENDIX B · EVALUATION RUBRIC DRAFT — AUGUST 2026 · PAGE 12 OF 18 APPENDIX B — EVALUATION RUBRIC, CONTINUED FACTOR 4: SUFFICIENCY Definition: Sufficiency measures what the investigation did with the evidence it collected: whether its application and analysis of that evidence are adequate to reach the conclusion it reached, and whether the discipline imposed on a sustained allegation is sufficient for the infraction. Where Completeness asks whether the right evidence was gathered, Sufficiency asks whether the reasoning connects that evidence to the finding, whether the response fits the conduct, and whether the investigation recognized the policy, training, and supervisory implications its own findings carried. Yes / No Description Yes The analysis carries the conclusion: the finding (Sustained, Unfounded, Exonerated, or Not Resolved) follows clearly and logically from the evidence gathered, and the reasoning connecting the two is stated rather than assumed. Where an allegation was sustained, the discipline or corrective action is sufficient for the infraction and consistent with departmental standards and comparable cases. Where the evidence reveals policy gaps or training needs, the investigation identifies them and appropriate corrective action is taken or recommended. No The analysis does not carry the conclusion, or the response does not fit the conduct. The classification may not follow from the evidence the investigation itself gathered, the reasoning may be absent or left implicit, discipline on a sustained allegation may be insufficient or excessive relative to the infraction and to comparable cases, or systemic policy, training, or supervisory issues apparent from the findings may be overlooked. A gap in the evidence itself is Completeness, not Sufficiency. GUIDING QUESTIONS Does the report explain how the evidence leads to the finding, or does it state the conclusion and leave the reasoning implicit? Does the finding follow from the evidence actually in the record? Is the discipline or corrective action sufficient for the infraction, and consistent with how comparable cases were handled? Did the investigation identify the policy, training, or supervisory issues the facts revealed? If the allegation was Not Resolved, does the evidence genuinely conflict — or was a conclusion available on this record? (Evidence never gathered belongs under Completeness.) Would you reach the same finding on this record, even if you would have built the record differently? EXAMPLES YES — SUFFICIENT “Sustained. Deployment did not meet the policy threshold of active aggression. Officer A received a written reprimand and remedial taser training; the investigation also flagged that the policyʼs definition of active aggression is not covered in annual refresher training and recommended revision.” WHY The analysis carries the finding, the response fits the conduct, and the systemic gap the facts revealed is identified and addressed. NO — NOT SUFFICIENT “Exonerated. Taser use was within policy.” WHY The record shows the subject was seated and handcuffed at the moment of deployment. The evidence needed to decide the allegation was collected — the investigation simply did not reckon with it. No reasoning connects the finding to the footage, the outcome contradicts the weight of the evidence, and no policy or training concern is raised despite facts that plainly raise one. OFFICE OF POLICE CIVILIAN OVERSIGHT · APPENDIX B · EVALUATION RUBRIC DRAFT — AUGUST 2026 · PAGE 13 OF 18 APPENDIX C DRAFT Statement Starters for Findings Optional openings for the Findings column of the Case Evaluation Card, grouped by evaluation factor. Findings should point to what is in the case record — a document, a recording, a statement, a date, a comparison — not to how the case felt to read. These starters are prompts, not required language. Complete the thought with the specific fact from the record, referring to parties by role rather than by name; if a starter does not fit the case, write your own in the same register. FACTOR 1 — ACCURACY “The report states…; the recording shows…” “The summary and the case file differ on…” “The finding cites… as the basis for…” “The policy quoted in the finding reads…” “Officer A and Witness B agree that… and diverge on…” “The timeline in the file places… at…” “The allegation as written describes…” FACTOR 2 — COMPLETENESS “The file contains statements from…, but none from…” “Available footage covers…; it does not cover…” “The investigation obtained…” “No record appears in the file of…” “The absent… would have spoken directly to…” “This omission does not change the finding because…” “Each allegation is addressed except…” FACTOR 3 — IMPARTIALITY “Questioning of the complainant and the officer covered…” “Both accounts were tested against…” “The summary describes… in the same terms it uses for…” “The investigator followed up on… after…” “The finding characterizes… as… without citing…” “Evidence favoring… is treated the same as evidence favoring…” “The file documents… regarding conflict of interest.” FACTOR 4 — SUFFICIENCY “The finding of… rests on…” “The report connects… to the finding by…” “The discipline imposed was…; comparable cases in the record…” “Not Resolved follows from conflicting…” “The record shows…, which the finding does not address.” “The investigation identified… as a policy or training issue.” “On this record I would reach the same finding because…” KEEPING STATEMENTS OBJECTIVE INSTEAD OF “The investigation felt rushed.” WRITE “The file shows one interview, conducted…” INSTEAD OF “The officer was clearly out of line.” WRITE “The recording captures…, which policy… addresses.” INSTEAD OF “More should have been done.” WRITE “No statement from… appears, and it bears on…” INSTEAD OF “The witness statements didnʼt add up.” WRITE “Witness A places the officer at…, which conflicts with the CAD log timestamped…” INSTEAD OF “The officer should have known better.” WRITE “Policy… requires…, and the recording shows…” INSTEAD OF “This looks like a pattern.” WRITE “The file lists… prior sustained findings for Officer A, dated…” OFFICE OF POLICE CIVILIAN OVERSIGHT · APPENDIX C · STATEMENT STARTERS DRAFT — AUGUST 2026 · PAGE 14 OF 18 APPENDIX D DRAFT Case Summary Sheet Prepared by the PCOB Office from the Internal Affairs file — one sheet per case, available with the case file during individual review. The allegation and discipline numbers assigned here are the numbers members cite on the Case Evaluation Card (Appendix A). CASE IDENTIFICATION IA CASE NUMBER: COMPLAINT TYPE: DATE OF COMPLAINT: DATE OPENED: DATE CLOSED: NUMBER OF OFFICERS INVOLVED: ALLEGATIONS & IA FINDINGS # Allegation IA Disposition 1 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved 2 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved 3 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved 4 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved # Allegation IA Disposition 5 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved 6 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved 7 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved 8 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved TOTALS:Sustained Unfounded Exonerated Not Resolved Total allegations DISCIPLINE & CORRECTIVE ACTION — SUSTAINED ALLEGATIONS # Allegation # Discipline imposed or corrective action taken 1 2 3 4 EVIDENCE REVIEWED Interviews conducted, body-worn camera and other recordings, dispatch and device records, reports, photographs, medical or other documentary evidence. Note evidence sought but unavailable, and why. OFFICE OF POLICE CIVILIAN OVERSIGHT · APPENDIX D · CASE SUMMARY SHEET DRAFT — AUGUST 2026 · PAGE 15 OF 18 APPENDIX E DRAFT Case Batch Summary The Directorʼs draft consolidation of membersʼ Case Evaluation Cards (Appendix A), issued for Board comment per Section 5. Complete Processing once per batch; the remaining sections repeat for each case in the batch. Bracketed tags — [M1], [M1 · M3], [ALL] — trace every consolidated point to the member card(s) it came from. Parties appear by role only; no names or identifying details. PROCESSING BATCH Named by evaluation deadline (e.g., Batch 2026-09-10) · number of cases in the batch REVIEWING MEMBERS How many members reviewed · date each completed review SUMMARY ISSUED One week after the regular meeting — the same date as the next batchʼs cutoff COMMENTS CLOSE Two weeks from issuance BOARD VOTE Regular meeting following finalization, on the Final Case Review Package CASE IDENTIFICATION — ONE BLOCK PER CASE IA CASE NUMBER COMPLAINT SUBMITTED Date · intake channel INVESTIGATION COMPLETED Date Allegations Allegation & policy cited IA finding ALLEGATION 1 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved ALLEGATION 2 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved ALLEGATION 3 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved DISCIPLINE IMPOSED For each sustained allegation: discipline and corrective action, as stated in the file MEMBER FACTOR DETERMINATIONS Evaluation Factor Member 1 Member 2 Member 3 Result 1 · Accuracy 2 · Completeness 3 · Impartiality 4 · Sufficiency One column per reviewing member — add or remove columns to match the batch. Yes / No in each cell; Result records the count (e.g., Yes — unanimous; No — 2 of 3, with the divergence noted in the Findings). OFFICE OF POLICE CIVILIAN OVERSIGHT · APPENDIX E · CASE BATCH SUMMARY DRAFT — AUGUST 2026 · PAGE 16 OF 18 APPENDIX E — CASE BATCH SUMMARY (CONTINUED) CONSOLIDATED FINDINGS — ONE SET PER CASE For each factor, give the merged account of member Findings: duplicative points stated once, in the membersʼ own terms where possible, each tagged to its source card(s). Record the factor result beside each heading. Member observations outside the allegations before the Board are retained under Additional findings and inform the Recommendations rather than the Determination. Factor 1 — AccuracyResult:  Merged member Findings, each point tagged — e.g., [ALL], [M1 · M3] Factor 2 — CompletenessResult:  Factor 3 — ImpartialityResult:  Factor 4 — SufficiencyResult:  Additional findings Member observations outside the allegations before the Board — retained here and routed to the Recommendations POINT OF DIVERGENCE & DIRECTOR’S PROPOSED RESOLUTION Where member views conflict: state each position in the membersʼ own terms with its tags, then the Directorʼs proposed resolution — typically following the majority of reviewing members, with the minority position preserved for the record and the vote — and the specific question members are asked to address during the comment period. OFFICE OF POLICE CIVILIAN OVERSIGHT · APPENDIX E · CASE BATCH SUMMARY DRAFT — AUGUST 2026 · PAGE 17 OF 18 APPENDIX E — CASE BATCH SUMMARY (CONTINUED) PROPOSED DETERMINATION — ONE PER CASE Allegation by allegation: whether the Board concurs with the Internal Affairs finding and, for each sustained allegation, with the discipline imposed. Where members divided, record the split (e.g., 2–1) and state the majority basis — resting on the consolidated Findings — with the minority position preserved for the record and the vote. If the investigation is incomplete or unsatisfactory and supports no clear determination, record that conclusion instead. ALLEGATION 1 Allegation · IA finding · proposed position and its basis ☐ Concurs ☐ Does not concur ALLEGATION 2 ☐ Concurs ☐ Does not concur ALLEGATION 3 ☐ Concurs ☐ Does not concur DISCIPLINE — SUSTAINED ALLEGATIONS Concurrence with the discipline imposed, noting any range of member emphasis from Factor 4 ☐ Concurs ☐ Does not concur NO CLEAR DETERMINATION If the investigation is incomplete or unsatisfactory and supports no clear determination, record that conclusion and the Recommendations that follow from it (Section 6) PROPOSED CONSOLIDATED RECOMMENDATIONS Forward-looking only — future investigations, policy, practice, procedure, systems, discipline, and training. Consolidate duplicative member recommendations into single items, each tagged to its source card(s); note how many member recommendations consolidate to how many items. 1 2 3 4 5 6 DIRECTOR’S ADVISORY ON FEASIBILITY The one place the Directorʼs own voice appears: whether each item is within the Boardʼs recommending authority; which are investigative-practice changes achievable within Internal Affairs procedure and which require policy or reporting amendments adopted by the Chief. The Director may assist members in refining wording during the comment period. COMMENT PERIOD — WHAT HAPPENS NEXT This summary is a draft. Members may propose changes, additions, or redactions through the comments-close date above. The Director resolves comments and completes the revised summary, together with the per-case Determination, Findings, and Recommendations, as the Final Case Review Package for the Boardʼs vote at the following regular meeting. All member input — including positions not adopted in this consolidation — is logged and retained. OFFICE OF POLICE CIVILIAN OVERSIGHT · APPENDIX E · CASE BATCH SUMMARY DRAFT — AUGUST 2026 · PAGE 18 OF 18 FICTIONAL TRAINING CASE INTERNAL AFFAIRS INVESTIGATION FILE Charlottesville Police Department Police Oversight Board Training Exercise CASE IA-26-014 Subject: Officer Daniel Mercer, Badge 417 Allegations: Abuse of Position; Truthfulness Incident: February 12, 2026 | Complaint: February 14, 2026 Investigation Completed: March 20, 2026 Location: West Main Street and 10th Street NW, Charlottesville, Virginia All names, badge numbers, businesses, records, and events in this file are fictitious. The policy language was supplied for the training exercise. This document is not an actual police record. FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 Case File Contents FILE SECTION CONTENTS Case Control Sheet Dates, participants, allegations, outcome summary, and review standard. Applicable Policies Policy 320.7.26, Abuse of Position, and Policy 320.7.45, Truthfulness. Document 1 Citizen Complaint submitted through the online complaint portal. Document 2 Incident Summary, investigative actions, and evidence source abstracts. Document 3 Investigation Analysis and findings of fact. Document 4 Interview of Officer Summary. Document 5 Conclusion. Document 6 Findings and classifications. Document 7 Disciplinary Action memorandum. Administrative Review Standard For this training case, the Department applies a preponderance-of-the-evidence standard. A fact is established when the available evidence shows that it is more likely true than not true. The reviewing board is not limited to deciding whether the final result is plausible; it may also evaluate whether the investigation was accurate, complete, sufficient, and impartial, and whether the discipline was reasonable and adequately supported. CLASSIFICATION TRAINING DEFINITION Sustained The evidence establishes that the alleged conduct occurred and violated policy. Unfounded The evidence establishes that the alleged conduct did not occur or that the specific allegation was false. Exonerated The alleged conduct occurred, but the conduct was lawful and within policy. Not Resolved The available evidence is insufficient to prove or disprove the allegation. FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 CASE CONTROL Case Control Sheet Professional Standards / Internal Affairs Division Case Number IA-26-014 Date and Time of Incident Thursday, February 12, 2026, approximately 7:11 p.m. to 7:34 p.m. Location Private surface parking lot at West Main Street and 10th Street NW, Charlottesville, Virginia Complaint Submitted Saturday, February 14, 2026, through the online complaint portal Investigation Completed Friday, March 20, 2026 (34 days after complaint submission) Complainant Maya Brooks (civilian) Subject Officer Officer Daniel Mercer, Badge 417, Patrol Officer II Assigned Investigator Sergeant Alan Price, Internal Affairs Standard of Proof Preponderance of the evidence Final Review Authority Deputy Chief Monica Hale Allegations and Final Classifications NO. POLICY ALLEGATION FINDING SUMMARY BASIS 1 320.7.26 Abuse of Position SUSTAINED Officer used the authority and influence of his on-duty status to obtain a no-fee vehicle release for his domestic partner. 2 320.7.45 Truthfulness UNFOUNDED The recorded statement at issue was that the officer was “logged on a call,” which was accurate when made; no recording supports the claim that he said dispatch sent him. FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 POLICY REFERENCE Applicable Policies The following language governs the two allegations in this training case. 320.7.26 Abuse of Position a. Department members shall not use their official position, official identification cards or badges for personal or financial gain, for obtaining privileges not otherwise available to them except in the performance of duty, or for avoiding consequences of illegal acts. b. Members shall not lend to another person, their identification cards or badges or permit them to be photographed or reproduced without the approval of the Chief of Police, or their authorized designee. c. Department members shall not authorize the use of their names, photographs, or official titles that identify them as members of the Charlottesville Police Department, in connection with testimonials or advertisements of any commodity or commercial enterprise, without the approval of the Chief of Police. d. Members shall not expend any money or make any financial obligations in the name of the Department without prior knowledge and permission from the Chief of Police, or their authorized designee. GUIDANCE NOTE This section prohibits a member of the Department from lending or abusing identification cards or badges, as well as commercial exploitation of official position. 320.7.45 Truthfulness a. Department members are to speak the truth at all times and under all circumstances. In cases where it is not allowed by law or by Department regulations to divulge facts and/or opinions within their knowledge, they will not speak on the subject. The only exception to this rule is during undercover investigations or toward lawful objectives during an investigation. Allegation Framing Used by Internal Affairs ALLEGATION QUESTION INVESTIGATED Abuse of Position Whether Officer Mercer used his on-duty police status, uniform, marked vehicle, badge, or official influence to obtain a towing-related privilege for Erin Caldwell that would not otherwise have been available. Truthfulness Whether Officer Mercer falsely told Maya Brooks that dispatch had sent him to the parking lot or that he was present because of a preexisting official call. FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 DOCUMENT 1 OF 7 Citizen Complaint Submitted through the Department’s online complaint portal Complainant Maya Brooks Date Submitted February 14, 2026 Incident Date February 12, 2026 Incident Location Parking lot near West Main Street and 10th Street NW Preferred Contact Telephone and email Employees Identified Uniformed male officer later identified as Officer Daniel Mercer Complaint Narrative On Thursday night, February 12, I parked in the lot near West Main and 10th to pick up food. A tow truck driver had my car lifted and told me I had to pay $95 to get it back. A gray SUV was also about to be towed. A police officer drove into the lot in a marked police car. He went right to the woman with the gray SUV. She called him Dan and hugged him. The officer talked to the tow driver. I heard him say, “Can you work with me on this one?” The tow driver lowered her SUV and did not charge her. I asked why she got her car for free while I had to pay. The officer said he was there on a police call and was keeping the peace. I told him it looked like he used his badge to help someone he knew. He said he did not make the tow driver do anything. I do not think that was honest. The tow driver would not give me a break, but he helped the other woman as soon as the officer spoke to him. I also do not think the officer was sent there. It looked like he came because he knew her. I paid $95. I am not asking the police to pay me back. I want someone to check the videos, call records, and police car records. Officers should not use their job to get special treatment for family or friends. Electronic Certification “I certify that the information above is true to the best of my knowledge.” Electronic Signature /s/ Maya Brooks Submission Timestamp February 14, 2026, 10:42 a.m. FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 DOCUMENT 2 OF 7 Incident Summary and Investigative Actions Prepared by Sergeant Alan Price, Internal Affairs Incident Summary At approximately 7:11 p.m. on February 12, 2026, Officer Daniel Mercer arrived in marked Patrol Unit 214 at a privately operated parking lot near West Main Street and 10th Street NW. Mercer was on duty, in uniform, and available for calls. He was not assigned by dispatch to the lot before his arrival. Mercer went to the location after receiving a personal telephone call from Erin Caldwell, his domestic partner. Caldwell’s gray sport utility vehicle and Maya Brooks’s vehicle were both in the process of being removed for unauthorized parking. Brooks was charged the towing company’s on-scene drop amount of $85 plus a $10 card-processing charge. Caldwell’s vehicle was lowered and released without charge after Mercer spoke with the tow operator. The first recorded body-worn-camera footage begins after Mercer’s initial conversation with the tow operator and while Caldwell’s vehicle is being lowered. The footage later captures Brooks challenging the different treatment. Mercer told Brooks that he had not ordered the operator to release Caldwell’s vehicle and stated, “I’m logged on a call now, and I’m keeping this from turning into a bigger problem.” The CAD event had been self-initiated by Mercer shortly before that statement, after he had already arrived at the lot. Brooks submitted a complaint two days later alleging that Mercer used his police status to obtain special treatment for Caldwell and was untruthful about being present on a police call. The abuse allegation was investigated as a potential use of official status to obtain a personal privilege. The truthfulness allegation was framed as whether Mercer falsely claimed that dispatch sent him or that an official call existed before he came to the scene. Investigative Actions Internal Affairs opened the case on February 14, 2026 following intake of the online complaint, screening the allegations under Policies 320.7.26 and 320.7.45. Department records — body-worn camera, CAD, radio traffic, RMS entries, and vehicle-location data — were preserved on February 16. No contemporaneous request was made to the private lot for its surveillance video. Brooks was interviewed by telephone for 22 minutes on February 17; she was not shown the body-worn camera recording and was not re-interviewed after the evidence review. Lieutenant Kim was interviewed on February 18 regarding Mercer’s assignment, notification practice, and prior counseling. Mercer’s body-worn camera was reviewed and time-correlated with CAD data on February 19, confirming that the recording begins after his initial conversation with the tow operator. The towing company’s manager supplied the lot sheet, charge receipt, and written fee schedule on February 20. Two voicemail messages were left for tow operator Thomas Reed on February 23, followed by a single email on March 5; no response was received, and no in-person or employer-assisted interview attempt is documented. Officer Walsh’s body- FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 worn camera was reviewed on February 24, but Walsh was not separately interviewed. Caldwell submitted an unsworn email statement on February 25 and was not interviewed, the investigator having considered her reason for calling substantially undisputed. Mercer was interviewed on February 27 for 63 minutes with a representative present, after reviewing his body-worn camera footage, the CAD event, and his report. A request to the property manager on March 2 established that the private lot’s surveillance video had been automatically overwritten after 14 days. Training records, performance history, and prior discipline were reviewed on March 10. Draft findings were submitted for command review on March 13. On March 17 the Deputy Chief requested clarification of the fee amount and the precise wording of Mercer’s statement to Brooks. Those clarifications were incorporated, the findings were approved, and the investigation was completed on March 20, 2026 and forwarded for disciplinary action. Evidence Source Abstracts Body-Worn Camera: Officer Mercer Recording begins at 7:14:31 p.m. Caldwell’s SUV is already being lowered from the tow apparatus. Tow operator: “I’ll do you the courtesy this time, but she has to move it now.” Mercer: “I appreciate it. She’ll move it now.” Brooks: “You came for her and made him let her go.” Mercer: “I didn’t order him. I asked if he had discretion.” Mercer, later: “I’m logged on a call now, and I’m keeping this from turning into a bigger problem.” Brooks: “You said dispatch sent you.” Mercer: “I said I logged the call. Nobody dispatched me.” Body-Worn Camera: Officer Walsh Walsh arrives after Brooks asks for another officer. The tow operator tells Walsh, outside Mercer’s immediate hearing, “I dropped it because he asked and he’s police. I didn’t want an issue.” Walsh’s recording does not capture the initial request, and Walsh states on camera that she did not witness the release decision. Tow-Company Records VEHICLE / DRIVER RECORD ENTRY AMOUNT Brooks vehicle Drop completed on scene; standard drop charge plus card fee $95 total Caldwell SUV “N/C — PD courtesy; Officer Mercer asked” $0 FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 RMS Incident Report Excerpt “While in the area of West Main Street, I observed a verbal dispute involving a tow operator and two motorists. I stopped to prevent the dispute from escalating. One motorist was personally known to me. The tow operator voluntarily released one vehicle and collected a drop fee for the other vehicle. No enforcement action was taken.” Officer Mercer, incident report submitted February 12, 2026 The report does not state that Caldwell called Mercer before he arrived, does not identify her as his domestic partner, and does not describe Mercer’s request that the operator exercise discretion. Internal Affairs characterized the wording as incomplete but not demonstrably false and did not open a separate truthfulness allegation regarding the report. FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 DOCUMENT 3 OF 7 Investigation Analysis Assessment of evidence, credibility, and policy application Method and Standard The analysis applies the preponderance-of-the-evidence standard to each allegation as framed at intake. Direct recordings and contemporaneous system records were given greater weight than later recollections. Admissions against interest were given substantial weight. Where evidence was unavailable, the investigator considered whether the remaining record was sufficient to reach a classification. Findings of Fact 1. Officer Mercer was on duty, in uniform, and operating a marked police vehicle when he went to the parking lot. 2. Mercer was not assigned or sent to the lot by dispatch before his arrival. 3. Mercer went to the lot after a personal call from Erin Caldwell, his domestic partner. 4. Mercer changed direction and drove directly to the lot after the call. He did not notify his supervisor before doing so. 5. Both Caldwell’s and Brooks’s vehicles were subject to the tow company’s on-scene fee schedule. 6. Mercer spoke with the tow operator before activating his body-worn camera. The exact words of that first conversation are not recorded. 7. Mercer acknowledged asking whether the operator had discretion to release Caldwell’s vehicle and acknowledged that his status as an officer could carry influence. 8. The tow operator released Caldwell’s vehicle without charge and recorded “PD courtesy; Officer Mercer asked.” 9. Brooks paid $85 plus a $10 card fee to obtain release of her vehicle. 10. No evidence shows that Mercer expressly threatened the tow operator, issued a police command, or claimed legal authority over the private tow. 11. Mercer created a self-initiated CAD event after arriving but before telling Brooks that he was “logged on a call.” 12. The available BWC recording does not show Mercer saying that dispatch sent him. When Brooks accused him of saying that, he expressly responded, “Nobody dispatched me.” 13. Mercer’s RMS report used the phrases “while in the area” and “personally known to me,” but did not disclose that Caldwell had called him or was his domestic partner. 14. The tow operator was not interviewed by Internal Affairs. Caldwell provided an unsworn email but was not interviewed. The private-lot surveillance video was requested after it had been overwritten. 15. Mercer had no prior sustained Internal Affairs findings and had received a 2024 counseling entry concerning personal business during duty hours. Allegation 1: Abuse of Position Policy question. Did Mercer use his official position to obtain a personal privilege not otherwise available in the performance of duty? FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 Mercer’s initial reason for going to the lot was personal. Caldwell called him, he drove directly to her location, and he knew that her vehicle was being towed before he arrived. Although he later performed a legitimate peacekeeping function when the dispute became heated, that later function did not convert the original personal intervention into a duty assignment. Mercer did not need to remove or separately display his badge to invoke official status. He was in full uniform, arrived in a marked police vehicle, identified himself as a police officer, and asked the tow operator to exercise discretion for his domestic partner. The tow operator’s contemporaneous notation and statement on Walsh’s BWC directly connect the no-fee release to Mercer’s police status and request. The absence of an explicit order or threat is mitigating but not dispositive. Policy 320.7.26 prohibits using official position to obtain a privilege, not only commanding or coercing another person. Caldwell received an $85 benefit and avoided the card charge that Brooks paid. The privilege was personal to Mercer because it benefited his domestic partner and arose from his personal intervention. Mercer could have remained outside the financial discussion, requested a neutral officer, advised Caldwell to pay the standard charge, or notified a supervisor before intervening. Instead, he used the credibility and influence of his on-duty position to seek a favorable exception. The evidence therefore establishes a policy violation by a preponderance of the evidence. RECOMMENDED FINDING: SUSTAINED The evidence more likely than not establishes that Mercer used his official position to obtain a no-fee release for a person with whom he had a close personal relationship. Allegation 2: Truthfulness Policy question. Did Mercer falsely tell Brooks that dispatch sent him to the lot or that a preexisting official call caused his presence? Brooks credibly perceived that Mercer came to assist Caldwell and later used the existence of a CAD event to describe himself as being on a police call. Her broader concern about the origin of Mercer’s involvement is supported by the phone and vehicle-location records. The specific statement captured on BWC, however, was: “I’m logged on a call now.” At the time Mercer made that statement, he had self-initiated a CAD event. When Brooks said that he claimed dispatch sent him, Mercer immediately responded, “I said I logged the call. Nobody dispatched me.” The recording therefore contradicts the precise allegation that Mercer falsely said he had been dispatched. The unrecorded period before BWC activation prevents a complete reconstruction of every statement made to the tow operator or Caldwell. Brooks did not identify a separate earlier statement to her before the recording began, and no available witness reported hearing Mercer claim that dispatch sent him. On the allegation as framed, the available evidence establishes that the claimed false statement did not occur. Mercer’s RMS wording and his description of Caldwell as a person “known to me” were imprecise and minimized the personal origin of his involvement. Internal Affairs considered those issues but did not find sufficient evidence of an intentionally false material statement and did not expand the truthfulness allegation FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 beyond the statement identified by Brooks. RECOMMENDED FINDING: UNFOUNDED The recorded exchange establishes that Mercer did not say dispatch sent him and accurately stated that he was logged on a self-initiated call when he made the statement at issue. Scope Decisions The investigator did not open additional allegations concerning BWC activation, report completeness, failure to notify a supervisor, or conduct unbecoming. Those matters were referred to the patrol chain of command for coaching or review. The investigation did not include a written analysis of whether the RMS phrasing constituted a separate truthfulness issue. FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 DOCUMENT 4 OF 7 Interview of Officer Summary Interview conducted February 27, 2026 Interviewee Officer Daniel Mercer, Badge 417 Interviewer Sergeant Alan Price, Internal Affairs Location Professional Standards interview room Duration 63 minutes Representation Officer representative present Pre-Interview Review Mercer reviewed his BWC, CAD event, and RMS report before the interview Advisement Administrative interview advisement acknowledged in writing Summary of Officer’s Account Mercer said he was working the 3:00 to 11:00 p.m. patrol shift, in service and unassigned, when Caldwell called his personal telephone. He identified Caldwell as his domestic partner of approximately two years and confirmed that they share a residence. He described her as upset and reporting that a tow operator was “being aggressive” while preparing to tow her sport utility vehicle. He denied that she asked him to stop the tow or the fee, saying she asked him to come because she felt unsafe, while acknowledging that the call involved an immediate towing problem. He said he responded personally rather than requesting another unit because he was nearby and expected the contact to take only a few minutes, and he acknowledged that a neutral unit would have been the better choice. He did not notify his supervisor beforehand; he did not regard the initial contact as a police matter and intended to notify a supervisor only if enforcement became necessary. Describing the interval before his camera was activated, Mercer said he asked the operator what was happening, identified Caldwell as his partner, and asked whether there was any discretion to let her move the vehicle immediately. He recalled the words, “Is there any discretion to let her move it?” and denied saying “as a police officer,” issuing an order, or threatening enforcement. He said he did not remove or present his badge, but acknowledged that it was visible on his uniform and that he may have touched the badge area while identifying himself. He denied using the words “waive the fee,” said he understood the operator was extending a courtesy, and stated that he did not know the precise amount Caldwell avoided until after the complaint. Asked about the lot-sheet notation “PD courtesy; Officer Mercer asked,” he said it fairly reflected that the operator acted after his request but disagreed that he had used police authority, adding, “I can see why my uniform made the request different from a normal customer asking.” On the timing of his records, Mercer said he created the CAD event once Brooks challenged the operator and voices rose, in order to document his presence and request another unit if needed. He said he activated his camera at the point the contact shifted from a personal welfare check to an official dispute, and he agreed that FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 activating on arrival would have protected everyone present and preserved the key conversation. On the truthfulness allegation, Mercer denied telling Brooks that dispatch sent him: “I told her I had logged the call, and then I told her directly that nobody dispatched me.” He said his reference to being on a police call described his status at that moment, because he had created a CAD event and was keeping the peace, and he denied using the event to conceal the personal reason he came. Regarding his report, Mercer said “while in the area” was routine language and accurate as to his location, but acknowledged that the phrase could suggest a chance encounter and that he should have explained Caldwell’s call. He said he described her only as “personally known to me” to avoid unnecessary personal detail in a public-facing report, and acknowledged that “domestic partner” was both more accurate and more relevant. He confirmed familiarity with Policy 320.7.26 and said he understood that officers cannot use their position for personal gain, but believed at the time that asking for discretion without ordering it was permitted. He characterized the 2024 counseling entry as a brief personal errand during a quiet shift, said he had not connected it to this incident, and acknowledged that both matters involved personal business while in service. Asked what he would do differently, Mercer said he would request a neutral unit through dispatch, notify a supervisor, activate his camera before making contact, stay out of the fee discussion, and advise Caldwell to follow the same process as any other driver. Investigator Follow-Up Assessment Mercer made meaningful admissions concerning his personal purpose, the request for discretion, the influence of his uniform, delayed BWC activation, and incomplete report wording. He continued to distinguish a request from an order and maintained that he did not intentionally obtain a fee waiver. The investigator did not confront Mercer with the tow operator’s statement from Walsh’s BWC word-for-word during the interview, because the recording was treated as corroborative rather than as a separate witness interview. “I did not threaten him or tell him what to do, but I understand now that a request from me in uniform was not the same as a request from anyone else.” Officer Mercer, administrative interview FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 DOCUMENT 5 OF 7 Conclusion Internal Affairs case disposition summary Conclusion The investigation established that Officer Mercer went to a private towing dispute for a personal reason involving his domestic partner while he was on duty, in uniform, and operating a marked police vehicle. He asked the tow operator to exercise discretion, and the operator released Caldwell’s vehicle without the fee charged to another driver. Although Mercer did not issue a direct order or make an explicit threat, his official position supplied the influence that produced the personal privilege. The Abuse of Position allegation is therefore sustained. The investigation did not establish that Mercer falsely told Brooks that dispatch sent him. The recorded exchange shows that he said he was “logged on a call now,” which was accurate after he self-initiated the CAD event, and he expressly stated that nobody dispatched him. The Truthfulness allegation, as specifically framed from the complaint, is therefore unfounded. The investigation also identified delayed BWC activation, incomplete report language, lack of advance supervisory notice, and avoidable involvement in a personal dispute. Those issues were not charged as separate policy allegations and were referred to the patrol chain of command for corrective coaching. The case was completed on March 20, 2026, and forwarded to the Chief of Police for disciplinary action on the sustained finding. DISPOSITION SUMMARY Abuse of Position — Sustained. Truthfulness — Unfounded. Additional BWC, reporting, and supervisory-notification issues referred for non-disciplinary review. Investigator Certification I certify that this report accurately summarizes the evidence reviewed and the conclusions reached in this administrative investigation. The case file contains the listed evidence or documentation of its unavailability. Sergeant Alan Price Assigned Internal Affairs Investigator SIGNED March 20, 2026 Deputy Chief Monica Hale Command Review and Approval SIGNED March 20, 2026 FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 DOCUMENT 6 OF 7 Findings Final allegation classifications Final Findings NO. ALLEGATION CLASSIFICATION BASIS 1 320.7.26 Abuse of Position SUSTAINED Mercer used the influence of his on-duty status, uniform, marked vehicle, and police identity to obtain a no-fee towing release for his domestic partner. A direct order or threat was not required for the policy violation. 2 320.7.45 Truthfulness UNFOUNDED The available recording establishes that Mercer did not tell Brooks that dispatch sent him. His statement that he was logged on a call was accurate at the time it was made. Classification Notes The sustained finding is based on the benefit obtained and the influence of official position, not on proof of an explicit command. The unfounded finding is limited to the specific alleged false statement concerning dispatch or a preexisting official call. No finding was entered regarding the completeness of Mercer’s RMS report or the timing of his BWC activation because those issues were not opened as separate allegations. The investigator determined that the remaining record was sufficient despite the unavailable private video and uncompleted tow-operator interview. Notice to Subject Officer Officer Mercer was notified of the findings on March 23, 2026. He accepted the sustained finding for purposes of the administrative process but submitted a written statement disputing that he intended to use police authority. His statement was included in the disciplinary packet. FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 DOCUMENT 7 OF 7 Disciplinary Action Final action issued by the Chief of Police Memorandum Date March 27, 2026 To Officer Daniel Mercer, Badge 417 From Chief Dana Whitfield Subject Final Administrative Action — IA-26-014 Sustained Violation Policy 320.7.26, Abuse of Position Effective Date April 4, 2026 Decision After reviewing the Internal Affairs report, supporting evidence, Officer Mercer’s written response, and the command recommendation, I affirm the sustained finding for Abuse of Position. The Truthfulness allegation remains unfounded. Mercer’s conduct created unequal treatment in a private financial matter and reasonably caused the complainant to believe that police status determined who received relief from the towing charge. Discipline is assessed under G.O. #1003 and the Department’s Disciplinary Matrix. Disciplinary Matrix Classification The sustained violation was classified under the Department’s Disciplinary Matrix, G.O. #1003, Discipline and Disciplinary Matrix (revised June 16, 2025), § 1003.9. Matrix Offense (1-1) Violations concerning general misconduct — Conduct-General (1-0) Matrix Range Category A through Category D Category Assessed Category C — first occurrence, § 1003.6.3(a)(1) Category C Options Letter of reprimand; two (2) to four (4) day loss of leave; or two (2) to four (4) day suspension without pay. Corrective action: involuntary restitution. Reckoning Period Thirty-six (36) consecutive months. A same or similar sustained violation within that period enhances the next violation to Category D, § 1003.6.3(a)(4). Category C was selected rather than Category B because the misconduct produced an unequal financial outcome for a member of the public and leveraged uniform, marked vehicle, and police identity for the benefit of a family member. Category D was not selected because there was no explicit command or threat, no enforcement action, FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 and no prior sustained finding within the reckoning period. Mitigating factors under § 1003.5(b) place the sanction at the low end of the Category C range rather than supporting a movement across categories, which § 1003.4(l) reserves for exceptional cases. Disciplinary and Corrective Action ACTION TERMS Letter of Reprimand Category C, § 1003.6.3(b)(1) A formal letter of reprimand on Department letterhead will be maintained by the Chief of Police in the Internal Affairs Office and duplicated to the member’s City of Charlottesville Human Resources personnel file, § 1003.8.2. Two-Day Suspension Without Pay Category C, § 1003.6.3(b)(3) Two (2) days without pay, the minimum of the Category C range, to be served on dates set by the Division Commander. The suspension is served rather than held in abeyance; abeyance is not a sanction authorized by the Matrix. Policy and Ethics Training Corrective action, § 1003.6.1(b)(1) Four hours of individualized instruction addressing abuse of position, conflicts of interest, and intervention in matters involving family or close associates, to be completed by May 31, 2026. Supervisory Monitoring Corrective action, § 1003.6.1(b)(2) For six months, Mercer will meet quarterly with his lieutenant to review personal-business boundaries and BWC activation expectations. Corrective Report Supplement Corrective action, § 1003.6.1(b)(5) Mercer must submit a supplemental RMS entry identifying Caldwell as his domestic partner and explaining that her call caused him to go to the lot. Mitigating and Aggravating Factors Assessed under § 1003.5(b) — employee motive, degree of culpability, truthfulness, disciplinary history, severity of infraction, and acknowledgment of error. CATEGORY FACTORS Mitigating No prior formal discipline; cooperation and material admissions; no explicit threat or police command; no arrest, citation, or use of force; no delayed emergency response; acknowledgment that a neutral officer should have handled the matter. Aggravating On-duty intervention for a domestic partner; unequal financial outcome; use of marked vehicle and uniform; delayed BWC activation; incomplete report language; prior counseling concerning personal business during duty hours; harm to public confidence. FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 Proportionality Statement The sanction falls within the range prescribed for a Category C offense and represents the least intrusive measure adequate to correct the behavior, consistent with § 1003.5(a)(1). No movement to a higher or lower category was made; under § 1003.4(h) a Commanding Officer’s recommendation may move no more than one category in either direction, and § 1003.4(l) requires strong and specific justification for any such movement. The disciplinary packet does not include comparator cases from prior Category C dispositions. FINAL ADMINISTRATIVE ACTION Category C. Letter of reprimand; two-day suspension without pay; four hours of individualized policy and ethics training; six months of supervisory monitoring; and a corrective report supplement. Thirty-six-month reckoning period applies. Acknowledgment My signature acknowledges receipt of this memorandum and does not necessarily indicate agreement with the decision. Officer Daniel Mercer Subject Officer SIGNED March 30, 2026 Chief Dana Whitfield Disciplinary Authority SIGNED March 27, 2026 END OF CASE FILE Fictional training material — Case IA-26-014 FICTIONAL TRAINING MATERIAL IA-26-014 INTERNAL AFFAIRS INVESTIGATION Charlottesville Police Department · Professional Standards Case IA-26-014 # Allegation IA Disposition 1 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved 2 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved 3 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved 4 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved # Allegation IA Disposition 5 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved 6 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved 7 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved 8 ☐ Sustained ☐ Unfounded ☐ Exonerated ☐ Not Resolved Sustained Unfounded IA-26-014 Citizen (External) February 14, 2026 February 14, 2026 March 20, 2026 1 Abuse of Position Truthfulness 11 2 Letter of Reprimand, (2) Day Suspension w/o Pay, Training, Supervisor Monitoring, Corrective Report Internal Affairs Investigation File - Citizen Complaint, Incident Summary, Investigative Actions, Investigation Analysis, Officer A (subject of complaint) Interview. Body-Worn Camera Footage - Officer A; Officer B (arrives on scene) ■ ■ Abuse of Position Board Member A IA-26-014 February 14, 2026 Board Member A August 6, 2026 The report mostly sticks to what's on the video and in the paperwork. You can check it against the body camera, the tow company's records, or what the officer admitted. I'll also give them credit for saying up front that the first conversation wasn't recorded, instead of guessing at what was said. Nobody ever actually talked to the tow driver and he's the one who decided to waive the fee. Two voicemails and one email doesn't feel like really trying. And the parking lot's own camera video got erased because nobody asked for it until it was too late. It didn't read like they were protecting their own. They used the officer's admissions against him, took the complainant seriously, and didn't accept “I never gave an order” as the end of it. On the first charge, the reasoning holds up. He went there because his partner called, his uniform did the talking, and she got her car back free. The discipline follows. My hesitation is the honesty charge: “I'm logged on a call now” was only true because he created the call himself. The timing bugged me, he created the call in the computer after arriving, right before telling the complainant he was on a call. He also had a note in his file from 2024 about personal business on duty, so this wasn't brand new. His own words in the interview summed it up: he knew a request from him in uniform wasn't the same as a request from anyone else. ☐ ☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐ ☐ ☐ ☐ 1 - Abuse of Pos. 2 - Truthfulness 1 - Abuse of Pos. 1. Ask businesses for their camera video right away, before it gets erased. The police records were saved within days, the lot's video should have been too. 2. Don't close a case without a real try at the key witness. If calls and email don't work, go in person or through the employer. 3. Go back to the person who complained once the evidence has been reviewed, and let them see the footage if that's allowed. 4. When an officer's statement is technically true but gives the wrong impression, look at that directly instead of stopping at “the exact words were accurate.” ■ ■ ■ Board Member B IA-26-014 February 14, 2026 Board Member B August 8, 2026 Mostly solid. The facts all tie back to a recording or a record, and the file is honest about what wasn't recorded. The least accurate document is the officer's own incident report, “while in the area” and “personally known to me” aren't technically false, but they sure don't tell you what happened. The complainant says she heard him ask the driver to “work with me on this one.” Maybe she heard right, maybe not, but the two things that could have settled it are gone: the lot's own video was erased before anyone asked for it, and the tow driver was never interviewed. They believed the complainant's basic story and used the officer's own admissions to sustain the main charge. I'll say this, though: the officer got a full preview of the footage before his interview and the complainant got nothing. That's less about the investigator picking sides and more about a one-sided process. On the abuse charge the logic is airtight. The discipline runs a little light but it's inside their own matrix, he cooperated, and the training plus check-ins count for something. The honesty analysis is where I get off the bus. They answered the narrow question and called it a day. Apparently a statement can be true and still leave a false impression. Reading the report he filed, you'd never know his partner called him there. That wording was his choice, not the investigator's, and it's the same instinct as the “logged on a call” line: never quite false, never quite straight. ☐ ☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐ ☐ ☐ ☐ 1 - Abuse of Pos. 2 - Truthfulness 1 - Abuse of Pos. 1. Require plain disclosure in reports going forward: if an officer responds to anything involving a family member or partner, the report has to say so in those words, no “personally known to me.” 2. Build a step into every future investigation where the complainant gets an update and a chance to respond to the evidence before the case closes. 3. Private cameras record over themselves fast: make preservation requests to nearby businesses a first-week routine in every case. 4. In future truthfulness cases, don't let “technically true” end the inquiry. If a statement was framed to leave a false impression, the investigation should say so and deal with it. ■ ■ ■ Board Member C IA-26-014 February 14, 2026 Board Member C August 3, 2026 Everything in the report checks out against something. The body camera, the tow company's paperwork, or the officer's own interview. He confirmed most of the important parts himself. I didn't catch the report claiming anything it couldn't back up. They never managed to reach the tow driver, and the parking lot's video was gone by the time they asked for it. But I kept asking myself: would either of those actually change anything? The officer admitted he went because his partner called and admitted asking for the favor. No complaints here. The case against the officer is built mostly out of his own mouth, which tells me nobody was covering for him. They took the complaint seriously from day one and didn't let “I never ordered him to do it” end the conversation. The first charge adds up: he shows up in uniform, asks for a favor, and she saves the money. On the honesty charge: what the complainant said he said isn't what the camera shows. The “logged on a call” line was slippery, but slippery isn't lying. The discipline felt right for a first offense from someone who owned it. What stuck with me is how much he admitted: the personal reason for going, the pull of the uniform, the late camera, the vague report wording. When they asked what he'd do differently, he had the whole list ready: send a different unit, tell a supervisor, camera on from the start, stay out of the money talk. That made the outcome easier to trust. ☐ ☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐☐ ☐ ☐ ☐ ☐ 1 - Abuse of Pos. 2 - Truthfulness 1 - Abuse of Pos. 1. Camera on from the very start of any contact, even one that begins as personal. A case like this is much simpler to judge when the first few minutes are on video. 2. Make it a clear rule: if a call involves an officer's own family or partner, they don't respond, dispatch sends a different unit. 3. Make it standard practice to request private security footage in the first few days of an investigation, before it gets taped over. ■ ■ ■ ☐ ☐ ☐ ☐ ☐ ☐ ☐ ☐ ☐ ☐ ☐ ☐ Training sample — one case (IA-26-014) Three: M1 - August 6; M2 - August 3; M3 - August 8 August 20, 2026 (one week after Aug 13 meeting) September 3, 2026 (two weeks from issuance) IA-26-014 February 14, 2026 March 20, 2026 Abuse of Position (Policy 320.7.26) Truthfulness (Policy 320.7.45) Yes No Yes Yes September 10, 2026 on the Final Case Review Package Yes Yes Yes Yes Yes No Yes Yes Letter of reprimand; two-day suspension without pay; four hours of ethics training; six months of supervisory monitoring; corrective report supplement Yes — unanimous No — 2 of 3 (mixed) Yes — unanimous Yes — unanimous Yes — unanimous All three members found the investigation's factual claims verifiable against the record (the body-worn camera, the tow company's paperwork, and the officer's own admissions) and credited the file for stating plainly that the first minutes of the encounter were not recorded rather than characterizing them. [ALL] No — 2 of 3 All three members identified the same two evidence gaps. The tow operator was never interviewed; the file documents two voicemails and one email, with no in-person or employer-assisted attempt, an effort one member described as “doesn't feel like really trying.” And the private lot's surveillance video, the only independent record of the interval before camera activation, was overwritten before it was requested. [ALL] Two members additionally found that the complainant was never re-contacted or shown the footage. [M1 · M3] Yes — unanimous Members found the analysis evenhanded: the case against the officer rests substantially on his own admissions, the complainant's account was credited, and the absence of an explicit order was not treated as the end of the inquiry. [ALL] Two members recorded the same concern: the officer reviewed the footage, the CAD entry, and his report before his interview. Both concluded this did not alter the outcome; one framed it as a process “built more comfortable for one side." [M1 · M3] Yes — unanimous Members found the reasoning on the Abuse of Position allegation sound. On discipline, all three found the sanction within the Department's matrix and adequately explained for a first sustained finding, identifying the training and six months of supervisory check-ins as likely to change behavior. [ALL] Two members recorded a reservation about the truthfulness analysis: it answered the narrow question (whether the officer said dispatch sent him) without addressing whether a technically accurate statement left a false impression. [M1 · M3] Members separately noted: the timing of the self-initiated CAD entry, created after arrival and immediately before the “logged on a call” statement [M1 · M3] and the extent of the officer's admissions and his own corrective list (supervisor notice, camera on from the start, staying out of the fee discussion) made the outcome "easier to trust” [M2]; and the officer's report wording, characterized as “never quite false, never quite straight” [M3]. The members part ways only on what the gaps mean. Two concluded the missing evidence leaves the truthfulness allegation unresolved, because the unrecorded interval is precisely when the alleged statement could have been made, one noting the complainant reported hearing the officer ask the operator to “work with me on this one” before any camera was on. [M1 · M3] One concluded the gaps would not have changed either outcome, because the officer's admissions and the operator's recorded explanation on the second officer's camera. [M2] All three agree the gaps do not affect the sustained finding. [ALL] The consolidated Findings record the gaps themselves, on which all members agree. The disagreement concerns their weight for Allegation 2 only and is carried into the Proposed Determination below, which follows the majority of reviewing members with the minority position preserved in the record. Members are asked to address this point specifically during the comment period. ☐ ☐ ☐ ☐ ☐ ☐ ☐ ☐ DIRECTOR’S ADVISORY ON FEASIBILITY Abuse of Position (IA finding: Sustained) Truthfulness (IA finding: Unfounded) Abuse of Position (IA finding: Sustained) Make preservation requests for third-party camera footage a standard first-week step in every investigation. [ALL] Before closing an investigation, interview any witness central to an allegation, or document escalated attempts. [M1] Build a step in which the complainant receives an update and opportunity to respond to evidence before a case closes. [M1 · M3] In truthfulness investigations, address directly whether a technically accurate statement was a false impression. [M1 · M3] Require plain disclosure in reports when an incident involves an officer's family member or partner, stated in those terms. [M3] Adopt a clear rule that officers do not respond to calls involving their own family or partner; dispatch sends a different unit. [M2] Director's advisory on feasibility: all six are within the Board's recommending authority. Items 1–3 are investigative-practice changes achievable within Internal Affairs procedure; items 5–6 would require policy or reporting amendments adopted by the Chief; item 4 concerns the analytical practice applied under the truthfulness policy. 3-0 2-1 CITY OF CHARLOTTESVILLE, VIRGINIA Community Survey Eyes, Ears, and Voice of the Community This survey gauges trust levels in the City of Charlottesville Police Department and collects community experiences with the police, to help inform, guide, and prioritize the work of the Police Civilian Oversight Board. Questions 1–5 are required. 6–9 are optional. Anonymous. No identifying information is collected unless you provide it. Print in dark ink. Fill one box per scale, like this: 1 How would you rate your level of trust in the Charlottesville Police Department, its officers, and staff? REQUIRED 0 10 20 30 40 50 60 70 80 90 100 0 — No trust 50 — Mixed 100 — Full trust 2What has been your experience with the City of Charlottesville Police Department? REQUIRED 3 4Using the diagram below, to what extent (1–7) do you believe your values, intentions, and desires align with each of the following? REQUIRED In each pair, the left circle is you and the right circle is the group named on the left. Fill in one box per row. 1 2 3 4 5 6 7 3.The Charlottesville Police 4.The community 1 — Not at all aligned 7 — Completely aligned PLEASE CONTINUE ON THE BACK → Police Civilian Oversight Board · Community Survey City of Charlottesville, Virginia · Please complete both sides 5What location(s) in Charlottesville does your experience and/or response best represent? REQUIRED Name a street, neighborhood, shopping area, place of work, city landmark, or similar. QUESTIONS 6–9 · OPTIONAL Answer only what you are comfortable sharing. 6What is your gender? Woman Man Non-binary Other 7What is your race? Asian / Asian Indian / Pacific Islander Black / African-American Hispanic / Latino Indigenous / American Indian White, non-Hispanic Multiple / Other: 8What is your age? Under 18 18–24 25–34 35–44 45–54 55–64 65 and older 9Do you have any additional comments, questions, or thoughts? THANK YOU — WHERE TO RETURN THIS Police Civilian Oversight Board, City Hall, 605 E. Main Street, Charlottesville, VA 22902 Prefer to answer online, or have questions for the Board? Visit the City of Charlottesville website for the online survey and Board contact details. Police Civilian Oversight Board · Community Survey City of Charlottesville, Virginia · Please complete both sides CHARLOTTESVILLE POLICE CIVILIAN OVERSIGHT BOARD AUGUST 2026 Community Survey Results What residents told us about their trust in, experience with, and alignment to the Charlottesville Police Department 14 community members surveyed on trust and experience with CPD 9 of 14 described their experience with CPD as positive 69/100 average community trust rating of the Charlottesville Police Department Surveys conducted July–August 2026. Small samples; results are directional, not statistically representative. COMMUNITY SURVEY · TRUST Trust is high for most — but not for everyone Asked to rate their trust in the Charlottesville Police Department on a 0–100 scale, respondents averaged 69 with a median of 82. Ten of fourteen rated their trust at 70 or above — while two rated it 0, pulling the average down and producing a wide spread. 0 — No trust 25 50 75 100 — Full trust Each dot is one respondent (n = 14). 82 Median rating 10 of 14 Rated trust 70 or higher 2 of 14 Rated trust at zero 31 Standard deviation — a wide spread Community Survey, July 2026 (n = 14) 02 / 11 MEAN 69 COMMUNITY SURVEY · VALUES ALIGNMENT Residents feel closer to community than to police On a 1–7 scale of how much their values, intentions, and desires align, respondents placed themselves at 5.6 with the community but 4.7 with the Charlottesville Police — and alignment with police varied far more from person to person. ALIGNMENT WITH POLICE 4.7 / 7 average 7 1 6 6 5 1 4 2 3 2 2 2 1 0 n = 14 · 6 of 14 answered 3 or below ALIGNMENT WITH COMMUNITY 5.6 / 7 average 7 1 6 8 5 3 4 0 3 1 2 0 1 0 n = 13 · 12 of 13 answered 5 or above Why it matters: the gap between the two scores — and the much wider spread on the police question (SD 1.6 vs 0.9) — suggests that feelings about CPD divide residents in a way that feelings about community do not. Community Survey, July 2026 03 / 11 COMMUNITY SURVEY · EXPERIENCE Most experiences positive; concerns focus on presence and responsiveness Positive — 9 Neutral — 2 Critical — 3 All 14 respondents described their experience with CPD; coded by overall sentiment. WHAT PEOPLE PRAISED Visible patrols — bike patrols, Downtown Mall presence, neighborhood rounds Quick, respectful responses — help after a theft, respectful conduct even during a citation Protection of gathering places — congregation security, school communities WHAT PEOPLE CRITICIZED Little foot presence in residential neighborhoods Slow response to non-emergency calls; secondhand reports of unresponsiveness on the Mall Perceived hesitancy — a view that officers avoid enforcement for fear of complaints “Overall very positive. They have had quick response times and have been very respectful and responsive.” — Community respondent “Not present on foot in neighborhoods. Slow to respond when non-emergency calls made.” — Community respondent Community Survey, July 2026 (n = 14) 04 / 11 COMMUNITY SURVEY · PLACES & OPEN COMMENTS Downtown dominates the picture Half of respondents tied their experience to Downtown and the Downtown Mall. Residential neighborhoods — where the main criticisms about foot presence arose — appear less often. Downtown / Downtown Mall 7 Residential neighborhoods* 5 Other sites† 3 *Prospect Ave & Westhaven, 14th St, Fifeville / 10th & Page / Rose Hill, Riverview, Locust Ave †UVA Health, Hydraulic Rd, schools. One response named multiple places. IN THEIR OWN WORDS — CLOSING COMMENTS “We MUST have people of color on the police force in much greater numbers for us to make real progress.” “Too many guns & shootings in Charlottesville.” “Glad to see the police working with IMPACT to address issues with public safety.” “I am surprised to learn that a community as small as Cʼville needs a police civilian oversight board.” 5 of 14 left a closing comment; themes ranged from officer diversity to gun violence to the Board’s purpose itself. Community Survey, July 2026 (n = 14) 05 / 11 COMMUNITY SURVEY · WHO RESPONDED Respondents skew older, white, and male Nearly half of respondents were 65 or older, and none were under 18 or Hispanic/Latino. Future outreach should reach younger residents and communities of color, whose experiences may differ. AGE (N = 13) 65+ 6 · 46% 45–54 1 35–44 4 · 31% 25–34 1 18–24 1 Under 180 RACE (N = 13) White 9 · 69% Black 3 · 23% Multiple / Other 1 GENDER (N = 14) Man 9 · 64% Woman 5 · 36% Reading note: demographic questions were optional. With 13–14 respondents, each person represents 7–8 percentage points — treat shares as rough proportions only. Community Survey, July 2026 06 / 11 ACCOUNTABILITY TRUST TRANSPARENCY TAKE OUR3 ‑MINUTE SURVEY Take the survey more than once as your experience and thoughts change over time! Scan with your phone camera Tell us about your experience with policing in Charlottesville. The Police Civilian Oversight Board is volunteer community members appointed by City Council to provide oversight of the Charlottesville Police Department. pcob@charlottesville.gov  ·  (434) 970 ‑ 3794 Front Back Front Back Page 1 of 3 To: Dr. Royal Gurley, Jr., Superintendent – Charlottesville City Schools CC: Kim Powell, Chief Operations Officer – Charlottesville City Schools Michael Kochis, Chief of Police – Charlottesville Police Department CC: Greg Wade, Lieutenant – Charlottesville Police Department From: Dr. Jeffrey Fracher, Chair – On Behalf of the Charlottesville Police Civilian Oversight Board Re: Role, Scope, and Jurisdiction of the PCOB in Oversight of the School Resource Officer Program; Initial Questions and Comments. Date: August 13, 2026 With the kickoff of the 2026–2027 school year, the Memorandum of Understanding (MOU) between the Charlottesville Police Department (CPD) and Charlottesville City Schools ( CCS) regarding the School Resource Officer (SRO) program is now underway. The Police Civilian Oversight Board (PCOB or “the Board”) issues this position statement to: 1. Clarify the Board’s role, scope, and jurisdiction with respect to the SRO program; 2. Transmit an initial set of questions and comments as the program begins. The Board offers this statement in a spirit of partnership. Students, families, school staff, and officers are all best served when the boundaries of oversight are clear, expectations are communicated early, and information flows in a structured and predictable way. The Board's aim is to advance policing that is transparent, accountable, and worthy of community trust. The Board's Role, Scope, and Jurisdiction The Board's oversight jurisdiction extends only to the Charlottesville Police Department, and the Board affirms it does not extend to school discipline, school policy and operations, or the evaluation of CCS personnel. Accordingly, the PCOB will not evaluate school disciplinary decisions or speak to the operation of CCS. The Board's role is to assess whether CPD policies, training, supervision, complaint processes, and officer conduct align with the values and expectations set out in the MOU. Initial Questions and Requests for Clarification As the program begins, the Board respectfully requests responses to the following questions. The Board raises these not as criticisms, but as areas where early clarity will benefit all parties. Area 1 — Boundary Between School Discipline and Law Enforcement 1. Are non-SRO officers who are called onto school property for assistance limited by the same criteria the MOU establishes for SROs? (Not addressed in MOU; p.2, item 2-b-iii) 2. Which personnel can serve as a school administrator's “designee”? (MOU p.11) 3. When student conduct could technically support a criminal charge, how is the decision to defer to school discipline documented? (MOU p.14 and p.16) 4. How is the term “substantial” defined as used in the MOU? (MOU p.16) Page 2 of 3 Area 2 — High-Consequence Police Encounters with Students 5. Are SROs provided with student IEPs, Section 504 plans, behavior intervention plans (BIPs), or other accommodation-related documentation? (MOU p.11 and p.17) 6. If a juvenile is wanted in connection with an outstanding matter, would the SRO make the arrest or call-in other officers? (MOU p.18) Area 3 — SRO Selection, Training, Supervision, and Performance 7. What training is given to non-SRO officers who may respond to a school? 8. Does CPD–CCS joint training include scenarios involving adolescent behavior and development, disabilities, trauma, bias, de-escalation, or restorative practice? Area 4 — Data Integrity, Equity, and Identification of Trends 9. How are informal contacts and verbal resolutions captured, if at all? (MOU p.7) 10. Is the “CCS Law Enforcement Official Contact Report” form available? (MOU p.8) Area 5 — Complaints, Feedback, Transparency, and Community Trust 11. How can parents or guardians request a copy of an official contact report? (MOU p.7) 12. Is the “Stakeholder Feedback & Formal Complaints” form available? (MOU p.8) 13. Are complaints about an SRO submitted to CPD always reported to CCS? (MOU p.9) Recommendations The Board offers two recommendations at the outset of the program: 1. Capture positive interactions. Official contact data reflects only one dimension of the SRO role. Documenting positive interactions alongside enforcement activity would present a more complete picture. The Board is also interested in whether officers are recognized for appropriate restraint, relationship-building, and problem-solving. In the Board's view, quality policing is advanced both through accountability as well as recognition of exemplary and model conduct. 2. Consistency between General Orders and the MOU. The MOU articulates values, goals, and expectations for the SRO program, while CPD General Orders govern officer conduct department wide. A review of relevant General Orders against the MOU would help identify any points where existing departmental polic y and the agreement may be in tension. The Board offers to conduct this analysis as part of its policy review jurisdiction. The Board thanks the staff of both organizations for their engagement as the school year begins, and looks forward to a constructive, transparent working relationship in support of Charlottesville's students. We welcome further dialogue to this end. On behalf of the Police Civilian Oversight Board, Dr. Jeffrey Fracher Chair, Police Civilian Oversight Board Page 3 of 3 James Walker, Director Office of Police Civilian Oversight Email: walkerj@charlottesville.gov Phone: (434) 970-3794 Motion to adopt and transmit this set of initial questions and comments to CPD and CCS representatives for the SRO program made by [Name], seconded by [Name]. Adopted by the Charlottesville Police Civilian Oversight Board on the 13th day of August, 2026. Certified: _______________________ Yes No Fracher ___ ___ Dobson ___ ___ Frye ___ ___ LaFave ___ ___ LeNoir-Kelly ___ ___ Reaves ___ ___ Vaughan ___ ___ Note: The law enforcement seat , currently held by Mr. Dillard, is specifically designated as a non- voting member. The seat is intended to provide the Board with an advisory perspective and expertise from law enforcement experience. Page 1 of 3 To: Charlottesville Police Civilian Oversight Board From: James Walker, Director – Office of Police Civilian Oversight Re: Proposed Revisions to Article XVI – Police Civilian Oversight Board Ordinance: Legal Review Update and Selection of Purpose Statement Date: August 13, 2026 At its May 14, 2026 meeting, the Board adopted the proposed ordinance revisions for submission to City Council, subject to two remaining items: completion of legal review and reconsideration of the purpose statement. This memo reports on the first item and brings the second to the Board. Legal Review The legal review is nearly complete. The City Attorney's Office and the Board's independent legal counsel have reviewed the proposed ordinance revisions, and their review produced only minor definitional and clarifying changes. It resulted in no substantive change to the content, powers, duties, or intent of the revised ordinance as adopted by the Board in May. With legal review concluded, the last step before submission to Council is the creation of a final redline draft showing all proposed revisions, strikes, and additions applied to the current ordinance. Purpose Statement Board members expressed interest in modifying the draft purpose statement presented at the May 2026 meeting. Perspectives and feedback were collected to create two alternate purpose statements. The three options that follow, including the current draft and two alternates, are an effort to synthesize the input members have offered. All three preserve the same operational core. Where they differ is in how directly they name the values raised in the feedback provided (e.g. rights, dignity, fairness, and community voice ) and in how closely that language is tied to the Board's authorized functions. The three options presented are as follows: [Current Draft] Purpose. The purpose of the board is to support community well -being and safety by advancing the quality of policing in the City of Charlottesville through civilian- led transparency and accountability. The board fulfills this purpose by monitoring, auditing, and reviewing department conduct, policies, practices, and procedures, and by issuing public reports with recommendations for corrective action and the adoption of best practices in policing. [Alternate 1] Purpose. The purpose of the board is to support community well -being and safety by advancing, through civilian- led transparency and accountability, policing that is lawful, fair, and respectful of the rights and dignity of all people in the City of Charlottesville. The board fulfills this purpose by monitoring, auditing, and reviewing department conduct, policies, practices, and procedures, and by issuing public reports with recommendations for corrective action and the adoption of best practices in policing. Page 2 of 3 [Alternate 2] Purpose. The purpose of the board is to support community well -being and safety through civilian-led oversight that brings transparency and accountability to policing in the City of Charlottesville. The board promotes policing that respects the rights and dignity of all people and provides the community with a direct voice in public safety . The board fulfills this purpose by monitoring, auditing, and reviewing department conduct, policies, practices, and procedures, and by issuing public reports with recommendations for corrective action and the adoption of best practices in policing. The Board is asked to review the three options and select one as the Board's final purpose statement or reach consensus on another alternative. Minor refinements to the selected option can be handled by motion, but the goal for the meeting is to land on final language. Once the purpose statement is adopted, it will be modified in the final redline ordinance proposal and ready for submission to Council pending the revisions resulting from legal review. Thank you to all members for the care and thought you have brought to this work throughout the process. Whichever option the Board selects, the statement will be stronger for the full range of perspectives that shaped it. Sincerely, James R. Walker Director, Office of Police Civilian Oversight Page 3 of 3 James Walker, Director Office of Police Civilian Oversight Email: walkerj@charlottesville.gov Phone: (434) 970-3794 Motion to adopt [Indicate selection and/or modifications] made by [Name], seconded by [Name]. Adopted by the Charlottesville Police Civilian Oversight Board on the 13th day of August, 2026. Certified: _______________________ Yes No Fracher ___ ___ Dobson ___ ___ Frye ___ ___ LaFave ___ ___ LeNoir-Kelly ___ ___ Reaves ___ ___ Vaughan ___ ___ Note: The law enforcement seat , currently held by Mr. Dillard, is specifically designated as a non- voting member. The seat is intended to provide the Board with an advisory perspective and expertise from law enforcement experience. Page 1 of 3 To: Mayor and Members of City Council From: Dr. Jeffrey Fracher, Chair – On Behalf of the Police Civilian Oversight Board Re: Position Statement – Support for the Adoption of Data Management and Analytics Systems by the Charlottesville Police Department Date: August 13, 2026 The Charlottesville Police Civilian Oversight Board (the Board) provides this position statement in support of the Charlottesville Police Department’s (CPD/the Department) initiative to adopt more robust data management and analytics systems. The Board offers this statement both to express its support and to define clearly what that support does, and does not, encompass. Context At its June 11, 2026 regular meeting, the Board received a presentation from Chief Michael Kochis and CPD staff who use and manage departmental data systems, including command staff, technology and data systems administrators, and the crime analyst. The presentation reviewed CPD’s current technology environment and made one point unmistakably clear: the Department’s central challenge is turning data held across many disconnected systems into actionable information. CPD s taff described systems constrained by screen size and device capacity; a records platform not designed to serve as a comprehensive data repository; limited customization and search functionality; system-required workflows that have increased task -completion times; data treated as static records rather than dynamic information; and analytical tools dependent on participation and data sharing across multiple jurisdictions. Board members have witnessed these challenges directly through participation in the Department’s CompStat meetings, where policing and crime intervention data are presented and reviewed. Preparing the material for a single monthly meeting requires significant manual effort to locate, extract, and consolidate information from separate systems. These inefficiencies are more than an administrative burden; slow and fragmented data access carries real consequences for community safety, for aligning services with need, and for the quality of information available to decision-makers as well as oversight practitioners. Position Statement The Board recognizes that modern data management and analytics tools serve two complementary purposes: they strengthen public safety operations, and they strengthen civilian oversight. Both advance the community’s interest in high- quality, transparent, and accountable policing. Broadly, the Board supports systems that bring together disconnected data into actionable insights, empowering CPD to make informed, evidence-based decisions. The Board’s support extends to platforms that connect records now scattered across policing, dispatch, and the broader justice system; that make the information the Department already holds genuinely searchable and usable rather than static; that can be organized around operational needs instead of forcing work to conform to the software; and that build in strong audit trails, analytics, and reporting. Page 2 of 3 Tangentially, within the Internal Affairs Bureau, the Board supports a digital case management system for administrative investigations, specifically those originating from citizen complaints. Implementation of such a system would bring consistency and efficiency to investigative records, allow the Department’s Early Intervention System to capture internal case data more effectively, and streamline the Board’s access to case files for its review. Scope The Board’s support is deliberately bounded, and the Board asks that its scope be clearly understood by the Department, City Council, and the community: No new collection of personal information. This statement supports data management and analytics systems that improve and enhance CPD’s use of the data it already lawfully collects and maintains. It does not advocate for, and should not be read to endorse, any new system, device, or program for the collection of personal information. Proposals to expand data collection are distinct matters warranting their own public process, policy development, and oversight review. Clear and defined policy before deployment. The adoption and use of any data management or analytics system should be restrained by clear and defined written policy, established before implementation, that articulates the purpose of the system; the outcomes it is intended to achieve; proper usage, including access controls and limitations; and the auditing and assessment of use, so that compliance can be verified and performance evaluated over time. The Board expects such policies to be available for Board review and intends to exercise its oversight role with respect to implementation, auditing, and ongoing assessment. Conclusion For these reasons, the Police Civilian Oversight Board supports the adoption and implementation of more robust data management and analytics systems by the Charlottesville Police Department, within the parameters set out above. Properly governed, these tools will improve operational effectiveness, strengthen internal accountability and early intervention, enhance transparency for the public, and materially support the work of civilian oversight. The Board is ready to work with the Chief, the Department, and City Council to see this initiative implemented responsibly. Sincerely, Dr. Jeffrey Fracher Chair, Police Civilian Oversight Board Page 3 of 3 James Walker, Director Office of Police Civilian Oversight Email: walkerj@charlottesville.gov Phone: (434) 970-3794 Motion to adopt and transmit this position statement supporting data management and analytics systems to be used by the Charlottesville Police Department made by [Name], seconded by [Name]. Adopted by the Charlottesville Police Civilian Oversight Board on the 13th day of August, 2026. Certified: _______________________ Yes No Fracher ___ ___ Dobson ___ ___ Frye ___ ___ LaFave ___ ___ LeNoir-Kelly ___ ___ Reaves ___ ___ Vaughan ___ ___ Note: The law enforcement seat, currently held by Mr. Dillard, is specifically designated as a non- voting member. The seat is intended to provide the Board with an advisory perspective and expertise from law enforcement experience.

Source: City of Charlottesville website. First collected Oct 6, 2026.