Open Meeting Law Requires Naming Officers on Closed Citizen Review Board Agendas; No Nontrivial Privacy Interest in Officer Names and Badge Numbers Already Mandatorily Public

1. Introduction

This appeal arose from a dispute over transparency in police-oversight proceedings. The Las Vegas Police Protective Association (LVPPA) and seven named Las Vegas Metropolitan Police Department (LVMPD) officers sought declaratory and injunctive relief to stop the Las Vegas Metropolitan Police Department Citizen Review Board (CRB) from publishing peace officers’ names and badge numbers on CRB meeting notices, agendas, and in CRB findings and recommendations.

The core issues were:

• Open Meeting Law compliance: whether the Nevada Open Meeting Law (OML), NRS Chapter 241, requires listing officers’ names on agendas even when CRB misconduct meetings are closed under NRS 289.387(10).
• Confidentiality sources: whether statutes (including NRS Chapter 289), collective bargaining agreement (CBA) provisions, operating agreements, CRB policies, or local ordinances bar disclosure of names and badge numbers.
• Privacy balancing: whether officers have a “nontrivial” privacy interest in their names and badge numbers under the balancing test articulated in Clark County School District v. Las Vegas Review-Journal (CCSD), 134 Nev. 700, 429 P.3d 313 (2018), sufficient to overcome public disclosure.

The district court granted the CRB’s NRCP 12(c) motion for judgment on the pleadings. The Supreme Court of Nevada affirmed.

2. Summary of the Opinion

The Nevada Supreme Court held:

• The CRB is a “public body” subject to the OML, and NRS 241.020(3)(d)(4) requires the CRB to include on its agenda the name of any officer whose character, alleged misconduct, or professional competence will be considered when any portion of the meeting will be closed for that purpose.
• NRS 289.387(10) (requiring CRB misconduct meetings to be closed to the public) does not create officer-identity confidentiality and does not conflict with the OML agenda-naming requirement; the provisions are “complementary.”
• The OML does not affirmatively require inclusion of badge numbers on agendas, but nothing prohibits inclusion of badge numbers; LVPPA identified no authority barring publication.
• Even assuming the CCSD balancing framework could be invoked by officers (and noting the later case Matter of Public Records Requests to Las Vegas Metropolitan Police Department, 141 Nev., Adv. Op. 26, 569 P.3d 624 (2025)), the officers failed at step one: they do not have a cognizable “nontrivial” privacy interest in names and badge numbers that are already mandatorily public under LVMPD policy and practice and are not protected by statute (in contrast to information expressly protected by NRS 289.025).

3. Analysis

3.1 Precedents Cited

A. Pleading posture and standard of review

• Sadler v. PacifiCare of Nev., 130 Nev. 990, 340 P.3d 1264 (2014)
  Cited for de novo review of a judgment on the pleadings and for the rule that courts accept complaint allegations as true and draw inferences for the nonmoving party at the NRCP 12(c) stage. The court relied on Sadler to frame its review as purely legal given the nature of the dispute (statutory obligations and whether the pleaded facts state a claim).
• Duff v. Lewis, 114 Nev. 564, 958 P.2d 82 (1998) (quoting Bernard v. Rockhill Dev. Co., 103 Nev. 132, 734 P.2d 1238 (1987))
  Cited for the proposition that judgment on the pleadings is improper if the pleadings allege facts that, if proved, would permit recovery. The court’s use of these cases underscores that LVPPA’s dismissal turned on the insufficiency of legal authority and the inability to plead a protectable privacy interest given publicness of the identifiers.

B. Statutory interpretation and public-record/open-meeting questions

• Clark County School District v. Las Vegas Review-Journal (CCSD), 134 Nev. 700, 429 P.3d 313 (2018)
  The centerpiece precedent for Nevada’s privacy balancing in the public-records context: (1) the resisting party must show a “nontrivial” privacy interest; then (2) the requester must show significant public interest advanced by disclosure. The court treated CCSD as potentially applicable by analogy but held the officers failed at prong one because their names and badge numbers are already public by policy and practice.
• Chanos v. Nev. Tax Comm'n, 124 Nev. 232, 181 P.3d 675 (2008)
  Cited for de novo review of legal conclusions, including interpretation of the OML and NPRA. This reinforced that the court’s task was statutory construction, not factfinding.
• Matter of Public Records Requests to Las Vegas Metropolitan Police Department, 141 Nev., Adv. Op. 26, 569 P.3d 624 (2025)
  Used to correct/clarify the district court’s narrower view of CCSD litigation posture. The 2025 case recognized that a subject of records may seek declaratory relief to prevent disclosure. The court nevertheless found that even if the officers could invoke the privacy balancing framework, they lacked a nontrivial privacy interest in the information at issue.

C. Defining “nontrivial” privacy interests

• Cameranesi v. U.S. Dep't of Def., 856 F.3d 626 (9th Cir. 2017)
  Quoted (via CCSD) for the “nontrivial or more than de minimis” privacy threshold and the corresponding burden on the requester to show the disclosure would significantly advance a public interest. The Nevada Supreme Court continued aligning Nevada’s privacy analysis with familiar federal FOIA-style balancing principles.
• L.V. Metro. Police Dep't v. L.V. Rev.-J., 136 Nev. 733, 478 P.3d 383 (2020)
  Cited to illustrate where nontrivial privacy can exist “where disclosure poses a risk of harassment, endangerment, or similar harm,” and to contrast the present dispute: in that case, the court recognized a privacy interest in unit assignments after names and badge numbers had already been disclosed. The 2026 opinion uses this contrast to emphasize that once identifiers are already public as a matter of law/policy, the incremental privacy interest is difficult to establish.

D. Standing

• Nat'l Ass'n of Mut. Ins. Cos. v. State, Dep't of Bus. & Indus., 139 Nev. 18, 524 P.3d 470 (2023)
  Cited for the general standing requirements (injury-in-fact, causation, redressability). The court did not rest its decision on standing, but noted the individual officers plausibly satisfied these elements to bring a privacy-right claim, even if associational standing for LVPPA could be debated.

3.2 Legal Reasoning

A. Harmonizing the OML with CRB-closure statutes

The opinion’s central statutory move is harmonization. LVPPA argued that because NRS 289.387(10) requires CRB misconduct meetings to be closed, officer identities should not appear on agendas. The court rejected that reading by focusing on the text of NRS 241.020(3)(d)(4):

Rather than creating a conflict, the closure requirement is what triggers the agenda-identification requirement. The court’s interpretive approach is pragmatic and transparency-forward: closing the meeting protects sensitive discussion, while naming the subject on the agenda preserves minimal public accountability about what is being discussed and who is affected.

B. Rejecting confidentiality-by-proxy arguments (CBA, operating agreements, internal policies)

LVPPA invoked multiple sources—CBA purge provisions, statutory rules about what may remain in an officer’s administrative file, and CRB/LVMPD operating agreements—to argue for anonymity. The court’s reasoning separates:

• Employment/personnel record confidentiality (e.g., what the employing agency can retain in administrative files) from
• Public-body meeting-notice obligations (what the CRB must disclose in agendas and what it may publish in findings).

Key points:

• CBA limits do not bind a separate public body’s statutory duties: even if the CBA governs LVMPD’s internal files, it does not override the CRB’s independent OML duties.
• Statutes limiting personnel file content are not confidentiality grants: provisions such as NRS 289.040(3) regulate retention in an officer’s personnel file; they do not create a general prohibition on public identification in oversight proceedings.
• Subordinate instruments cannot defeat statutes: internal manuals or operating agreements cannot nullify OML requirements.

C. Badge numbers: not required, not prohibited

The court drew a careful line: OML requires names (NRS 241.020(3)(d)(4)), but does not require “additional identifying information.” However, because LVPPA identified no law prohibiting badge number publication, the CRB may include them. This portion functions as a restraint on overreading OML while still rejecting the requested gag order.

D. Privacy balancing fails at the threshold

Even assuming officers can sue to block disclosure (as recognized in Matter of Public Records Requests to Las Vegas Metropolitan Police Department), the court held the officers failed to plead a “nontrivial” privacy interest under CCSD.

The opinion’s rationale is essentially “no reasonable expectation of privacy” given:

• Undisputed LVMPD policy requiring officers to identify themselves by name and badge number in public interactions.
• Past LVMPD practice of disclosing names and badge numbers in response to public records requests.
• Legislative selectivity: when the Legislature intends to protect officer-identifying information, it does so expressly (e.g., NRS 289.025 protecting home addresses and photographs), but it has not protected names/badge numbers.

The court also treated LVPPA’s alleged harms—threats, harassment, reputational damage, “internet perpetuity”—as inadequately connected to CRB disclosure of information that is already public and commonly known to complainants. In effect, the causal story was too attenuated to establish the kind of “risk of harassment, endangerment, or similar harm” recognized in L.V. Metro. Police Dep't v. L.V. Rev.-J., especially where the identifiers are baseline public facts.

3.3 Impact

A. Operational transparency for oversight bodies

This decision substantially strengthens minimum transparency around closed-door police oversight by requiring that the public can see—via agendas—which officer is the subject of CRB review. It rejects the notion that “closed meeting” equals “anonymous proceeding.”

B. Clear boundary: confidentiality of underlying investigative materials vs. public findings

By emphasizing local code provisions distinguishing confidential submitted/generated records from “public notices and the panel’s findings and recommendations,” the court reinforces a two-tier structure:

• Confidential: investigative materials and certain records of proceedings (as declared confidential by law).
• Public: notices, agendas (including the officer’s name), and findings/recommendations (absent a state/federal law declaring them confidential).

C. Future privacy claims: “already public” is a major barrier

For Nevada public records and open-meeting disputes, the opinion signals that privacy balancing will often fail at prong one where the contested identifier is:

• mandatorily disclosed by agency policy in daily operations,
• routinely released under NPRA practice, and
• not singled out for statutory protection.

This may channel future officer-safety arguments away from categorical anonymity and toward (i) targeted protections for genuinely sensitive data (e.g., addresses, photographs, assignments), or (ii) fact-specific showings tied to particular threats rather than generalized concerns.

D. Agenda drafting practices statewide

Because the holding is anchored in OML’s agenda requirements for closed portions of meetings, it may affect other Nevada public bodies (not only CRBs) that close meetings to discuss an individual’s alleged misconduct or professional competence. The case is a reminder that closure often increases—rather than decreases—the obligation to provide meaningful agenda notice.

4. Complex Concepts Simplified

• Judgment on the pleadings (NRCP 12(c)): A procedural device allowing a court to decide a case based only on the pleadings when, even assuming the nonmoving party’s facts are true, the law provides no relief.
• Open Meeting Law (OML): Nevada’s transparency statute requiring public bodies to provide notice (agendas) of meetings and, in certain situations, to disclose specific information even if part of the meeting is closed.
• “Closed meeting” vs. “confidential identity”: A meeting can be closed to protect sensitive discussion while still requiring public notice identifying who the discussion concerns.
• Nontrivial privacy interest: A privacy interest that is more than minimal—often tied to credible risks like harassment or endangerment. If the information is already public by law or policy, courts are less likely to find a nontrivial privacy interest.
• Balancing test (from CCSD): Step 1 asks whether there is a nontrivial privacy interest; step 2 weighs that against a significant public interest advanced by disclosure. If step 1 fails, the analysis ends.
• Standing: The requirement that a plaintiff show a concrete injury caused by the challenged conduct that a court can remedy.

5. Conclusion

Advance Opinion 55 establishes and clarifies three key points in Nevada law:

• OML agenda identification is mandatory even for closed CRB misconduct meetings: NRS 241.020(3)(d)(4) requires naming the officer whose alleged misconduct or competence is under review.
• No categorical legal bar to publishing badge numbers: while not required by the OML, badge numbers may be included absent an identified prohibition.
• No nontrivial privacy interest in already-public identifiers: where officer names and badge numbers are mandatorily public by policy and not protected by statute, officers cannot satisfy the threshold privacy showing under CCSD to block disclosure.

In broader context, the decision reinforces Nevada’s transparency framework: closure protects deliberation, not anonymity; and privacy protections must be grounded in concrete legal authority or a genuinely nontrivial interest, not generalized concerns untethered from the public status of the information.