Section 22 of BC’s Freedom of Information and Protection of Privacy Act

Public bodies in BC may only withhold information under FIPPA if a specific exception applies:

• Section 13: Policy advice or recommendations—protects advice, proposals, recommendations, analyses or policy options developed for decision-makers before a policy is finalised.
• Section 14: Legal advice—protects solicitor-client communications and legal opinions between the district and its lawyer.
• Section 15: Disclosure harmful to law enforcement—protects information that could compromise law enforcement operations, investigations, or prosecutions.
• Section 16: Disclosure harmful to intergovernmental relations or negotiations—protects confidential communications between governments or sensitive intergovernmental discussions.
• Section 17: Disclosure harmful to financial or economic interests—protects information that could damage the government’s financial position, negotiating power, or economic interests.
• Section 19: Disclosure harmful to individual or public safety—protects information whose release could threaten someone’s safety or public security.
• Section 20: Information that will be published or released within 60 days—allows temporary withholding of information the public body intends to release publicly within 60 days.
• Section 21: Disclosure harmful to business interests of a third party—protects commercial, financial or technical trade secrets belonging to private third parties.
• Section 22: Disclosure harmful to personal privacy—protects recorded information about identifiable individuals that would constitute an unreasonable invasion of personal privacy.

Each redaction must cite the exact statutory section and explain how disclosure would cause the harm the exemption is meant to prevent, as detailed in Section 8 of FIPPA.

This article was prepared for my own edification for advocacy actions I plan to take and does not constitute legal advice. From experience, section 22 is most commonly deployed and often incorrectly, so if you want to jump ahead, that will probably cover most scenarios you experience.

Section 13: policy advice or recommendations

• What it protects: Advice, proposals, recommendations, analyses or policy options developed for a public body. This covers internal deliberations and staff advice to decision-makers, as described in Section 13 of FIPPA.
• Legitimate uses: Draft policy proposals under active consideration, internal strategy memos weighing options, or staff recommendations to trustees on future policy directions.
• Areas requiring scrutiny: Section 13 protects the deliberative process before decisions are made, but loses force once policies are implemented. Watch for attempts to withhold final decisions, published reports, completed policies, finalised analyses, background research on adopted practices, or factual descriptions of how current policy operates—these documents describe outcomes rather than pre-decisional advice.
• How to challenge it: Emphasise that section 13 only protects advice generated before a decision. Once a policy is implemented, it represents the actual decision or outcome rather than advice about what to do. Information documenting what was done (not what was considered) falls outside this exemption’s scope.
• Potential overreach: Evaluative reports or post hoc reviews examining implemented programs or analysing past decisions may be redacted as “policy advice” even though they describe what happened rather than what was being considered. Requesters can argue these reports constitute factual accounts of completed actions, which serve transparency rather than compromise deliberative processes.

Section 14: legal advice

• What it protects: Solicitor-client communications and legal opinions. Correspondence between the board/district and its lawyer offering legal advice is privileged, as specified in Section 14 of FIPPA.
• Legitimate uses: Emails or memos between district staff and lawyers analysing laws, discussing litigation strategy, or advising on legal obligations. Formal legal opinions prepared for the district.
• Areas requiring scrutiny: The exemption protects confidential legal counsel, not general policy documents or factual explanations of legal duties. Merely stating what a law requires (even if a lawyer wrote it) constitutes factual information rather than privileged advice. Administrative matters should not be hidden by citing legal privilege.
• How to challenge it: Distinguish legal advice from information or administrative discussion. Point out that laying out statutory requirements or describing how the district applies a law to school operations differs from a lawyer’s confidential advice. If an email was not truly seeking or giving legal counsel, the exemption may not apply.
• Potential overreach: Watch for situations where lawyers are copied on routine emails, which may then be redacted under section 14, or where documents are redacted simply because they “mention lawyers” even if they just state what the law is. Requesters can insist that basic legal facts (such as a child’s rights under special education law) are not protected advice.

Section 15: harm to law enforcement

• What it protects: Information that could compromise law enforcement or investigations, as outlined in Section 15 of FIPPA. This includes details of police investigations, techniques, identities of confidential informants, criminal intelligence, or things that could prejudice a prosecution.
• Legitimate uses: Ongoing criminal investigation details, police methods or surveillance techniques, identities of confidential informants, or anything whose release could interfere with active policing.
• Areas requiring scrutiny: Section 15 applies to law enforcement operations, not routine school disciplinary processes. General incident reports after any investigation is complete and non-police “investigations” by the school typically fall outside law enforcement matters. Statistical reports on discipline outcomes are also not law enforcement information.
• How to challenge it: Emphasise that typical school discipline or reports of student behaviour are not “law enforcement operations,” even if police were involved. Once an investigation is finished, concealing the outcome under section 15 lacks justification—completed cases can be disclosed. Show that withheld information describes school responses rather than police tactics.
• Potential overreach: Watch for situations where every interaction with police is treated as “law enforcement information,” with emails about bringing officers in for school incidents being redacted. Routine safety-related reports may also be claimed as confidential. Requesters can note that unless it involves an active criminal case, section 15 application may be questionable.

Section 16: harm to intergovernmental relations

• What it protects: Confidential communications or negotiations between governments or in sensitive intergovernmental discussions, as specified in Section 16 of FIPPA. Information received from another government “in confidence” or records that could harm BC’s relations with other governments is covered.
• Legitimate uses: Cabinet discussions with the federal government, treaty negotiations with Indigenous governments, or confidential funding negotiations with other jurisdictions. Sensitive minister-to-minister communications.
• Areas requiring scrutiny: Section 16 targets sensitive negotiations, not routine interactions with the Ministry of Education or other provincial agencies. Normal data reports submitted to the Ministry, general policy guidance from other departments, or already-public guidance fall outside the scope of intergovernmental secrets.
• How to challenge it: Demonstrate that ordinary correspondence with the Ministry (such as sharing budget numbers or routine inquiries) differs from the kind of confidential negotiation this section targets. If the Ministry itself has publicly released similar information, then disclosure could not harm relations. Emphasise that transparency constitutes the norm unless genuine risk to government relations exists.
• Potential overreach: Watch for attempts to withhold ministry directive letters, funding formulas, or internal accountability communications by treating them as if they were international negotiations. Requesters can argue these constitute normal accountability records rather than protected intergovernmental dealings.

Section 17: harm to financial or economic interests

• What it protects: Information that could damage the government’s financial position or negotiating power, as detailed in Section 17 of FIPPA. This includes financial strategies, budgets not yet public, or trade secrets belonging to the public body.
• Legitimate uses: Ongoing procurement strategies, sealed bid details, or internal discussions of future budget proposals. Proprietary information that could disadvantage the government or impede economic management if released prematurely.
• Areas requiring scrutiny: Already-approved budgets or historical spending information fall outside this exemption’s scope. Once budget allocations are set, revealing how public funds were spent generally serves transparency. General financial data about past projects (if not harming a third party) is not covered.
• How to challenge it: Point out that after a budget or spending decision is implemented, there’s no longer a “negotiating position” at risk. Transparency about expenditures (especially of public funds) is essential for accountability. Argue that basic expenditure reports or breakdowns are past facts rather than future proposals.
• Potential overreach: Watch for situations where details of special education spending or resource allocations are redacted under section 17 with claims that public scrutiny could hurt “financial interests.” Requesters can emphasise that disclosure of how funds were actually used helps assess whether resources are fairly allocated to student needs.

Section 19: harm to individual or public safety

• What it protects: Information whose release could threaten someone’s safety or public security, as specified in Section 19 of FIPPA. This covers details that might enable violence or jeopardise physical safety.
• Legitimate uses: Security procedures (such as alarm codes or detailed emergency response plans), the identity of a person at risk from release of information, or specific safety measures that, if disclosed, could be exploited.
• Areas requiring scrutiny: General safety policies or de-identified incident data fall outside this exemption’s scope. Routine emergency protocols, room-clearing procedures, or general statistics on restraints do not in themselves endanger anyone. After the fact, old incident reports usually pose no new threat.
• How to challenge it: Show that the redacted information is broad policy or practice rather than sensitive details. Emphasise that knowledge of general procedures (how schools handle emergencies or discipline) usually improves safety. If no concrete safety threat is apparent, argue the exception doesn’t apply.
• Potential overreach: Watch for situations where data on restraint or seclusion practices is hidden with claims that any transparency about how disabled children are physically controlled constitutes a safety risk. Requesters can argue the real risk may lie in unchecked use of force. General policies on supervision or restraint (especially after incidents are over) do not inherently endanger others.

Section 20: information that will be published or released within 60 days

• What it protects: Information that the public body intends to release publicly within 60 days of the request, as described in Section 20 of FIPPA. A request can be temporarily withheld if publication is genuinely imminent.
• Legitimate uses: Draft reports or data with a credible, scheduled release plan (for example, a review set to be published next month), or information required by law to be released (budget forecasts, legislated reports).
• Areas requiring scrutiny: Claims of imminent publication require concrete timelines and accountability mechanisms. Watch for use of section 20 as a stalling tactic when no actual publication plan exists, or when the “60 days” repeatedly slides forward without consequence.
• How to challenge it: Ask for the expected publication date and format. The Act requires the body to actually publish within 60 days or else release the information directly to the requester. If the 60-day deadline passes without release, the district must hand over the information. Requesters should hold the public body to that timeline and document any missed deadlines.
• Potential overreach: Watch for situations where section 20 is invoked for reports that remain perpetually “under review” or “awaiting final approval,” with publication dates that keep shifting. Requesters can insist on documentation showing concrete publication plans and can file complaints when deadlines pass without either publication or direct disclosure, exposing the exemption as a delay mechanism rather than a legitimate temporary withhold.

Section 21: harm to business interests of a third party

• What it protects: Commercial, financial or technical trade secrets belonging to private third parties, as outlined in Section 21 of FIPPA. This includes confidential vendor information or corporate data provided to the school board under promise of secrecy.
• Legitimate uses: Proprietary curriculum material from a private provider, individual consultant proposals or cost breakdowns that are business confidential, or details of a contractor’s methods that could harm their competitive position.
• Areas requiring scrutiny: General contract terms or performance results fall outside this exemption’s scope. Basic information on the services a vendor provides (such as whether consultants met agreed standards) is not a trade secret. Information about how public funds are spent on third-party contracted services should not be redacted.
• How to challenge it: Emphasise that transparency about public contracts (price, scope, performance outcomes) ensures accountability for public spending without harming vendor interests. If a district simply states that a provider met the requirements of a contract, that factual information is not confidential. Argue that information about service effectiveness and usage is in the public interest.
• Potential overreach: Watch for situations where details of contracts with private assessment or therapy agencies are redacted under section 21 as “confidential business information.” Requesters can point out that these agencies operate under public contracts, so disclosing how well they fulfil their commitments serves the public interest without violating legitimate secrecy.

Section 22: personal privacy

• What it protects: Recorded information about an identifiable individual (personal information)—such as details that can identify a student or staff member, as outlined in Section 22 of FIPPA.
• Legitimate uses: Contact and identifying details (names, addresses, phone numbers), medical or disability diagnoses, individual test scores, and personnel records.
• Areas requiring scrutiny: Aggregate data (such as total suspensions by grade, district-wide exclusion rates) or de-identified demographic patterns fall outside privacy protection. Such large-scale figures cannot identify any one person and describe institutional practices rather than individual identifiers.
• How to challenge it: Show the redacted material is systemic or aggregate (not tied to a named individual). Argue that re-identification risks must be plausible rather than speculative. Large-cohort statistics (such as thousands of students) generally do not meet the privacy threshold.
• Potential overreach: Watch for situations where statistics on exclusions, accommodation denials or other broad measures are claimed as “personal” simply because they affect people. Requesters can argue these numbers describe institutional practices rather than personal identifiers and constitute evidence of system-wide decisions.

Procedural obligations

FOI law mandates that districts:

• Cite specific exemptions: Every redaction must reference the exact FIPPA section authorising it, as required by Section 8 of FIPPA. Simply blacking out text without explanation is not allowed.
• Explain the harm: They must explain how disclosure would realistically cause the harm the exemption guards against, not just state the category. For example, if claiming a privacy or safety risk, they should articulate why revealing the information would actually create that risk.
• Sever, don’t refuse wholesale: If only part of a document needs protecting, they must release the rest. Entire-page or whole-document withholds are improper if only fragments should be exempt.
• No blanket categories: Each piece of withheld information must be independently justified. They cannot simply refuse broad categories of records without individualised assessment.
• Bear the burden of proof: The district must supply evidence or rationale showing the redaction is necessary. Requesters shouldn’t have to prove the district is wrong—the district must justify its decision.

In practice, courts and the Privacy Commissioner insist that a public body must state and justify each exception. For example, Section 8 of FIPPA requires the response letter to specify the exception and explain why it applies, rather than merely citing it. Public bodies cannot refuse on “out of scope” grounds without a statutory basis.

When redactions may signal accountability concerns

In some cases, the information withheld appears to be precisely the information that, if released, would reveal how institutional practices affect students. For example, aggregate exclusion rates, accommodations-denied data, or internal reviews may be redacted even though they describe system-wide actions rather than individual circumstances. When privacy or other exceptions are applied to hide these patterns, the nature of the redaction itself can be revealing. Excessive redaction may function as a symptom of accountability concerns rather than legitimate privacy protection, suggesting the withheld data would raise questions about institutional practices.

Challenging redactions through OIPC review

Parents who receive a FOI response can appeal within 30 business days to the Office of the Information and Privacy Commissioner. OIPC review is free. To challenge redactions, the parent submits the original request, the district’s decision letter, and arguments for why each redacted item should be disclosed. OIPC adjudicators (or the commissioner) will review the material and can order release of improperly withheld information. The process can be lengthy and requires research and argument, but decisions are binding. Successful cases set precedents that help clarify proper application of exemptions.

The transparency FIPPA promises

FIPPA is meant to ensure open government and allow public scrutiny of how authorities use power. Section 25 of FIPPA reinforces this by requiring that information clearly in the public interest must be disclosed, even if it would normally be exempt. Broad redaction of data on student exclusions, resource use, or institutional patterns can undermine this transparency purpose. Parents seeking information about exclusion practices or resource allocation function as accountability actors rather than privacy invaders. When districts apply exemptions in ways that prevent meaningful scrutiny, such applications may conflict with FIPPA’s foundational goal of governmental openness and can signal that withheld data would raise legitimate questions about institutional practices.