Lead Opinion
Opinion
Under the Firefighters Procedural Bill of Rights Act (Gov. Code, § 3250 et seq.),
I. Facts
Captain Culp, plaintiff Steve Poole’s supervisor, maintained what he called a “daily log” regarding each of the employees that he supervised. He created the log using both a computer and handwritten notes. He created a separate file for each employee, stored on a flash drive and also in hard copy, which he kept in his desk with the employee’s name on it. He included in the log “[a]ny factual occurrence or occurrences that would aid [him] in writing a thorough and fair annual review.” He kept these logs throughout the time he was supervising each employee. Culp would address with the employee behavior recorded in the log about which he had concerns, and if the behavior nevertheless continued it might be mentioned in the employee’s performance review.
Culp kept the log concerning plaintiff from December of 2008 to July of 2010. He used the log as a reference in preparing annual reviews and assessments of plaintiff’s performance under a performance improvement plan. The daily log prepared by Culp regarding plaintiff included many descriptions of plaintiff’s activities on the job and his interactions with Culp, noting both positive and negative aspects of plaintiff’s behavior. Some of the incidents described in the log were included in plaintiff’s annual performance reviews and his assessments under a performance improvement plan. For example, the log notes several incidents in which plaintiff failed to complete his assigned duties in cleaning up the fire station. As also noted in the log, Culp addressed his concerns with plaintiff before the annual evaluation in an attempt to correct plaintiff’s behavior, and plaintiff’s performance on cleanup duties was addressed in a performance improvement plan. Plaintiff’s annual performance review indicated that this was an area in which he needed to continue to show improvement.
Many incidents recorded in the log were never included in a review. For example, Culp noted in the log that plaintiff left a training class early one day and went outside to talk on his cell phone. Culp later discussed the incident with plaintiff and his log notes indicate that plaintiff explained that he had already taken that class and passed the associated examination. The log also describes a training session conducted in a stressful environment during which plaintiff became very anxious. Culp discussed this incident with
From time to time Culp discussed his concerns about plaintiff’s performance with Culp’s own supervisor, Battalion Chief Phillips, Office Chief Camargo, human resources personnel, and attorneys for the Orange County Fire Authority, relating some of the incidents recorded in his daily log. But he did not share the log itself with them and he did not allow other employees to review the daily log.
Plaintiff had the opportunity to review all of his performance evaluations, which he understood were then placed in his personnel file at headquarters. When he went to the human resources department at headquarters and asked to see his personnel file he was allowed to review it and make copies of his performance evaluations. Plaintiff showed a copy of his performance evaluation to a union representative, Bob James. The level of documentation in the review caused James to wonder whether Culp may have been maintaining a file on plaintiff at the station house. James demanded that Culp provide him with a copy of plaintiff’s “station file,” and Culp gave him a copy of his daily log regarding plaintiff.
Shortly thereafter, plaintiff wrote to the director of human resources of the Orange County Fire Authority, asserting that the inclusion of negative comments in Culp’s daily log without providing plaintiff an opportunity to review those comments violated section 3255. He requested that all negative comments be removed from the log and that all “personnel files” be made available for his inspection. In response, the fire authority denied his request, asserting that section 3255 did not apply to Captain Culp’s “supervisory notes.”
Plaintiff and the Orange County Professional Firefighters Association filed a petition and complaint in the superior court, seeking declaratory and injunctive relief, damages, civil penalties, and a writ of mandate directing defendant to comply with section 3255 before including adverse comments in plaintiff’s personnel files. After a trial based on the papers (including transcripts of depositions of both plaintiff and Culp), the trial court denied relief, concluding that Culp’s daily log was not subject to section 3255. The trial court observed, “If Culp made a negative note about [plaintiff] in his notes, but did not address it in the yearly evaluation, it does not exist, at least for personnel purposes.”
The Court of Appeal reversed. It reasoned that the daily log constituted a “file used for . . . personnel purposes” (§ 3255) because a substandard performance evaluation was based on adverse comments contained in the
II. Analysis
Because this appeal involves the application of a statute to undisputed facts, our review is de novo. (See Southern California Edison Co. v. State Board of Equalization (1972)
The Firefighters Procedural Bill of Rights Act (the Act) provides firefighters with certain rights concerning their employment. (§ 3250 et seq.) At issue here is section 3255, which provides that “[a] firefighter shall not have any comment adverse to his or her interest entered in his or her personnel file, or any other file used for any personnel purposes by his or her employer, without the firefighter having first read and signed the instrument containing the adverse comment indicating he or she is aware of the comment.” The firefighter has 30 days to respond, in writing, to an adverse comment, and “[t]he written response shall be attached to, and shall accompany, the adverse comment.” (§ 3256.)
Captain Culp, the author of the daily log, was the only person who had access to it. He discussed some of the incidents described within it with his superiors and with human resources personnel, but it is undisputed that he did not permit them to review the log itself. To the extent Culp used any of the adverse comments contained in the log in any review or assessment of plaintiff’s performance, those comments were shared with plaintiff in accordance with section 3255. The question presented under these undisputed facts is whether negative comments contained in a document memorializing a supervisor’s own thoughts and observations that is not itself made available to or shared with anyone else comes within section 3255. As explained below, we conclude that any negative comments contained in the log that were not included in a performance review or performance improvement plan concerning plaintiff were not entered in a file “used for any personnel purposes by his or her employer.” (§ 3255.)
The Act does not define the phrase “used for any personnel purposes by his or her employer.” In discerning the scope and meaning of section 3255, “ ‘[w]e begin with the plain language of the statute, affording the words of the provision their ordinary and usual meaning and viewing them in their statutory context, because the language employed in the Legislature’s enactment generally is the most reliable indicator of legislative intent.’ [Citations.]
The statutory language referring to a file “used for any personnel purposes by his or her employer” might, in isolation, be read broadly enough to include Culp’s log, which he used in the performance of his duties as a supervisor. But critical to an understanding of section 3255 is its statutory context. (See Horwich v. Superior Court (1999)
Section 3255 is one of three neighboring provisions of the Act that concern the rights of firefighters with respect to their personnel files. Section 3255 requires the employer to inform the firefighter of any comment adverse to his or her interest in a personnel file or any other file used by the employer for personnel purposes. Section 3256 entitles a firefighter to respond in writing to any adverse comment “entered in his or her personnel file” and the response “shall be attached to, and shall accompany, the adverse comment.” Section 3256.5 entitles a firefighter to inspect “personnel files that are used or have been used to determine that firefighter’s qualifications for employment, promotion, additional compensation, or termination or other disciplinary action.” (§ 3256.5, subd. (a).) If, after reviewing the file, “the firefighter believes that any portion of the material is mistakenly or unlawfully placed in the file, the firefighter may request, in writing, that the mistaken or unlawful portion be corrected or deleted.” (§ 3256.5, subd. (c).) The employer must respond to the request in writing, and both the request and the response become part of the personnel file. (§ 3256.5, subds. (c), (d).)
As subdivision (a) of section 3256.5 makes clear, the Legislature was not concerned with any and all files that might in some sense be connected with personnel matters; the Legislature was, rather, specifically concerned with
As we have observed, an employee’s “personnel file serves as a permanent record of his employment; derogatory information placed in that record may be used against the employee long after the informant becomes unavailable. Thus the statute provides the employee with the concurrent right to place on the record material in rebuttal.” (Miller v. Chico Unified School Dist. (1979)
A supervisor’s log that is used solely to help its creator remember past events does not fall within the scope of that definition. Even if a supervisor uses his or her notes to help draft performance evaluations and other documents that ultimately are placed in a personnel file, the notes
Cases applying similar statutes are consistent with this conclusion. They have held that a document containing adverse comments may come within the disclosure requirement even if not formally entered into the official personnel file, if the document was either (1) maintained in such a manner that it would be available to those making personnel decisions in the future, or (2) was actually used by the employer in making a personnel decision, or both. For example, in Miller, supra,
In County of Riverside v. Superior Court (2002)
Similarly, cases from the Courts of Appeal have concluded that disclosure requirements apply to adverse comments about a police officer even though they were not entered into the officer’s official personnel file, and even though they had not been used in making any personnel decision, when those files might be available to persons making personnel decisions in the future. In Sacramento Police Officers Assn. v. Venegas (2002)
Likewise, in Aguilar v. Johnson (1988)
In the present case, there is no evidence that Culp’s log would be available to anyone making personnel decisions in the future. The log was available to no one other than Culp himself. Many of the potentially negative comments contained in the log were never included in any document made available to plaintiff’s employer, because Culp either deemed the incidents inconsequential or resolved them in plaintiff’s favor. And it is undisputed that the documents Culp prepared with the assistance of the log — plaintiff’s performance evaluations and improvement plan — were disclosed to plaintiff before they were entered into his personnel file.
In concluding that section 3255 applied to Culp’s log, the Court of Appeal found this case to be analogous to Miller, supra,
We are not persuaded to the contrary by the Court of Appeal’s reasoning. The Court of Appeal asserted that “[l]ike the situation in Miller, information not contained in [plaintiff’s] main personnel file was presented to his employer prior to an adverse employment action by the employer. As in Miller, revealing the contents of the daily logs to Battalion Chief Phillips denied Poole the opportunity to respond to the adverse comments made known to the employer, contrary to the intent of the protective statutory enactment.” This case is distinguishable from Miller. It is undisputed that Culp did not share his log with anyone; he merely discussed with others some of the incidents that he had observed and also recorded in his log, preliminary to completing plaintiff’s evaluations and performance improvement plan. Nothing in the Act attempts to regulate a supervisor’s preliminary verbal consultations with his superiors or human resources personnel prior to completing an evaluation. The statute plainly gives firefighters the right to review and file a written response to certain documents. Its language cannot be stretched to include a right to file a written response to verbal communications.
The problem identified by the Court of Appeal would exist to some degree regardless of whether a supervisor kept notes or simply relied on an excellent memory. If performance reviews occur only annually, an employee may have a different recollection from his or her supervisor of events occurring many months earlier, or may not recall those events at all. Unreasonable delay in informing an employee about incidents that could affect his or her employment status might sometimes be prejudicial to the employee’s ability to rebut an employer’s characterization of the employee’s conduct, but prejudice resulting from such delay is not the issue that is addressed in section 3255. The only timing requirement in section 3255 is the requirement that the employee have the opportunity to review the adverse comment before it is actually entered into the file. There is a provision in the Act that addresses delay, in the context of allegations of misconduct. (§ 3254.) Generally, no punitive action may be taken on an allegation of misconduct unless the investigation of the allegation is completed and the employee is notified of the proposed disciplinary action within one year. (§ 3254, subd. (d).) Plaintiff, however, does not allege that section 3254 was violated or that there was any unreasonable delay in informing him of incidents that might cause him to receive a negative evaluation.
III. Conclusion
The decision of the Court of Appeal is reversed.
Notes
References to statutes are to the Government Code unless otherwise indicated.
Section 3255 is virtually identical to a statute applicable to public safety officers (§ 3305), and it establishes rights regarding adverse comments that are very similar to those that have been granted to teachers. (Ed. Code, § 44031, subd. (b)(1).) Consequently, cases interpreting those statutes are relevant to our interpretation of section 3255.
Concurrence Opinion
Concurring. — Today the court strikes a careful balance between firefighters’ procedural protections and the realities that supervisors confront when managing public organizations. The foundation for the court’s opinion is its interpretation of the Firefighters Procedural Bill of Rights Act (Gov. Code, § 3250 et seq.), and the logic of that interpretation is unassailable. I nonetheless write separately to underscore an important principle
Suppose a statute is enacted with provisions similar to the ones at issue in this case. “Any public employee,” the statute provides, “has a right to review personnel files that are used or have been used to determine the employee’s qualifications for employment, promotion, or discipline.” The question later arises whether a supervisor’s hastily scrawled note on a napkin about a subordinate’s performance — subsequently placed in a file folder, and then digitally copied onto a smartphone — constitutes a “personnel file,” and whether the supervisor’s occasional glance at the napkin or the digital file before writing a more formal evaluation constitutes “use[] to determine the employee’s qualifications for employment, promotion, or discipline.” That the ordinary usage and dictionary definitions of terms like “file,” “use,” and “determine” would matter in answering these questions is beyond question. (E.g., Ceja v. Rudolph & Sletten, Inc. (2013)
What would be difficult to defend, however, is the proposition that the inquiry should end without considering what the rest of the statute tells us about the meaning of the phrase at issue. Does a separate statutory provision imply that “personnel file” is to be construed broadly or narrowly? Are electronic records addressed elsewhere in the statute? If a phrase like “used to determine the employee’s qualifications” is not explicitly defined in the statute, do other provisions illuminate anything relevant about how the statutory scheme understands the limits of the procedural protections it affords?
The devil, in short, is in the details. And the details are elucidated by context — the statutory structure and the words of surrounding or related provisions. The statute’s structure and its surrounding provisions can reveal the semantic relationships that give more precise meaning to the specific text being interpreted, even if the text may have initially appeared to be unambiguous.
The majority’s framework for interpreting Government Code section 3255 appears very much in accord with these concerns. (See maj. opn., ante, at pp. 1384-1385.) That is, this court’s approach to interpreting statutes emphasizes the primacy of the Legislature’s intended purpose. (Goodman v. Lozano (2010)
There is a certain simplicity in the idea that our interpretive task ends if the meaning of a pivotal statutory phrase is “plain.” (E.g., People v. Cornett (2012)
In Apple Inc. v. Superior Court (2013)