OOR: School District Must Review and Release PTO Emails on Its Domain That Document District Activity; Specificity Defense Fails (DelVecchio v. Valley Grove SD)
Legal Insights with Attorney Schnee
School districts often host email accounts for booster clubs, parent groups, and other organizations that support their students, and those accounts can become the subject of a Right-to-Know request. A new Final Determination addresses whether emails in a parent teacher organization (PTO) account on a district email domain are records of the district. In Nicholas DelVecchio v. Valley Grove School District, OOR Dkt. AP 2026-3592 (Final Determination issued and mailed Nov. 2, 2026), Appeals Officer Damian J. DeStefano held that emails in the PTO account that document a transaction or activity of the District are public records and must be provided on a rolling schedule, while purely personal emails do not have to be disclosed. The Office of Open Records (OOR) also rejected the District’s specificity defense because the District had already located the responsive emails. The appeal was granted in part and denied in part.
The request
On August 10, 2026, Nicholas DelVecchio asked the Valley Grove School District (District) for all emails sent, received, and stored in relation to the Valley Grove Elementary PTO, identifying the associated address as PTO@staff.VGSD.org. The request covered June 1, 2025 through August 10, 2026 and asked for sent, received, deleted, and quarantined emails.
The District’s response
After a thirty-day extension, the District denied the request as overbroad and insufficiently specific under Section 703 of the Right-to-Know Law (RTKL). The District stated that its search had identified more than 1,800 potentially responsive emails and that, without identification of a particular District business, activity, or transaction, it could not determine which records were being requested.
On appeal, the District, through its Solicitor and with attestations from its Superintendent, who also serves as its Agency Open Records Officer, argued that the PTO is a fully separate entity. The District explained that, apart from the reporting obligation in Section 511(d) of the Public School Code, neither the District nor the School Board can regulate, bind, make decisions for, or terminate the PTO, that the District has no fiscal or operational authority over it, and that the two maintain separate federal employer identification numbers. The Requester responded that the District ran the email domain and had shut down the PTO account, which he argued showed that the emails were within the District’s control.
The issue
Because the District had identified the responsive emails, the OOR framed the sole question as whether the emails in the PTO account are records of the District under Section 102 of the RTKL, which defines a record as information that documents a transaction or activity of an agency and is created, received, or retained in connection with the agency’s business or activity.
The ruling
Locating the records undercut the specificity argument. In a footnote, the OOR explained that an agency’s ability to identify responsive records can show that a request is sufficiently specific, citing Easton Area School District v. Baxter, 35 A.3d 1259 (Pa. Cmwlth. 2012). The District’s search of a single identified account over a defined period was a strong indicator that the request was specific enough, so the OOR did not further address the Section 703 claim.
PTO-related emails can document District activity. The OOR found the District’s arguments about its legal separation from the PTO misplaced. It relied on prior OOR decisions holding that records involving PTOs and similar groups are received or retained in connection with district activities, including Haring v. Pennridge School District (emails about a marching band program), Rittenhouse v. Hempfield School District (PTO budgets), and Tignall v. Dallastown Area School District (records of a district’s interaction with a parent advisory group).
The email address alone does not decide the question. The District cited Meguerian v. Office of the Attorney General, 86 A.3d 924 (Pa. Cmwlth. 2014), for the rule that an email is not an agency record merely because it was sent or received on an agency account or stored on an agency computer. The OOR agreed that emails that are purely personal, or that do not relate to or document a transaction or activity of the District, are not accessible under the RTKL, citing Schnee v. Parkland Sch. Dist., OOR Dkt. AP 2022-0763. But it held that emails created and received in connection with a District transaction or activity are District records, presumed public under Section 305.
The District must review each email. Because the request sought every email in a District-issued account, the OOR directed the District to review the emails and decide whether each one relates to a District transaction or activity or is purely personal. The District had not raised any exemption or offered evidence to withhold the emails, so those that document District activity must be provided. The District may redact personal identification information, such as personal email addresses, under Section 708(b)(6).
Rolling production over ninety days. Given the volume, the OOR ordered the District to produce the responsive emails on a rolling basis every thirty days over a total period of ninety days, citing prior OOR decisions that found a ninety-day rolling schedule reasonable. Any party may appeal to the Venango County Court of Common Pleas within thirty days of the mailing date.
Takeaway
For agencies, DelVecchio is a reminder that hosting an outside group’s email account on an agency domain can bring that account within the RTKL’s reach, at least for emails that touch agency business. Formal separation, separate tax identification numbers, and limited statutory oversight did not end the inquiry. An agency that receives a request for a hosted account should be prepared to review the messages individually, separate personal emails from those documenting agency activity, and support any exemption with evidence. Telling the requester that the search found more than a thousand emails, while also asserting that the request is insufficiently specific, may undercut the specificity defense. If the volume is large, the decision shows that the OOR may set a rolling production schedule.
For requesters, the decision shows the value of tying a request to an identified account and a defined period. That is the kind of detail that let the OOR treat the request as specific. It is also a reminder that personal emails stored on an agency system remain outside the RTKL, so a production may be smaller than the number of emails the search returned. For another recent ruling on how the OOR evaluates requests for communications, see our post on Belkin v. Department of Corrections, and for a Commonwealth Court decision on specificity and large requests, see Commonwealth Charter Academy v. Epstein and Rock the Capital. For response and appeal timelines, see our guide to Pennsylvania RTKL deadlines.
Schnee Legal Services, LLC is based in Lititz, Pennsylvania, and represents individuals, municipalities, and businesses throughout the Commonwealth of Pennsylvania in Sunshine Act and Right-to-Know matters. Learn more about Pennsylvania RTKL representation or visit schneelegal.com (book a consultation at schneelegal.cliogrow.com/book). Phone 717.400.5955, chadwick@schneelegal.com.
This post is for informational purposes only and is not legal advice. Using this website does not create an attorney-client relationship. Email may not be private; do not email confidential information.
Have a request or an appeal of your own?
Business-day clock and appeal package, all in one docket.