When a Decision Is Final… What Happens Next?
If an independent agency orders a government agency to produce records, why doesn’t that automatically end the dispute? Understanding administrative compliance, enforcement, and the gap between decision and action.
Before evaluating a system, understand how it was designed. This exhibit does not criticize any agency or speculate about motives. It teaches the architecture.
The Visitor Question
If an independent agency orders a government agency to produce records, why doesn’t that automatically end the dispute?
This exhibit uses Pennsylvania’s Right-to-Know Law and Office of Open Records as a real, public model — not to examine any specific case, but to illuminate a general administrative principle: obtaining a favorable decision and obtaining its practical benefit are frequently two different administrative events.
Visitor Assumptions
What you might already believe — and why that’s understandable
- “If I won, I’m done.”
Understandable — in most everyday disputes, a ruling in your favor concludes the matter. Administrative law frequently doesn’t work this way.
- “Government agencies must immediately obey.”
Reasonable given how binding the word “determination” sounds — but “binding” and “self-executing” are not the same legal property.
- “Someone automatically enforces the decision.”
Most citizens’ experience with authority comes with built-in enforcement. Assuming the same structure applies here is a natural transfer of that experience.
- “An appeal office has enforcement power.”
Arguably the most understandable assumption of all — an office with authority to decide sounds like it should have authority to compel. Whether it does is a specific, answerable administrative fact.
Historical Context
What institutional problem existed, and what pressures produced this separation
Pennsylvania’s current Right-to-Know Law was enacted in February 2008 and took effect in January 2009, replacing a much narrower 1957 law that placed the burden on the requester to prove records were public, rather than presuming openness. The reform was substantial: it flipped the legal presumption so records are presumed public unless an agency can show otherwise, and it created something the old law never had — the Office of Open Records, an independent, quasi-judicial agency whose sole function is to decide appeals when a records request is denied.
That design choice — creating a decision-making body separate from any enforcement body — wasn’t an oversight. It reflects a structural principle common across American administrative law: agencies that adjudicate disputes are frequently not given the power to enforce their own rulings by force. That power is reserved for courts, consistent with a general separation-of-powers instinct that keeps compulsion within the judicial branch, even when the initial decision is made somewhere else entirely.
This is the same architectural pattern this collection has documented in six other institutions, wearing different clothes: a body that decides is not the same body that compels compliance, and the space between those two events is where a citizen’s experience of “winning” and a citizen’s experience of “receiving the remedy” can come apart.
Administrative Structure
Investigation, Decision, Compliance, Enforcement — four distinct events
Investigation
When a request is denied and appealed, the Office of Open Records — or, for certain agency types, a different appeals officer — reviews the dispute: written arguments, sometimes evidence, occasionally a hearing.
Decision
The OOR issues a Final Determination — legally binding on both parties once issued, required by law to include factual findings and legal reasoning.
Compliance
The agency is expected to actually turn over the records — a separate administrative event from the decision itself, and not automatic. As of the date a Final Determination becomes unappealable, if the agency still hasn’t produced the records, the requester — not the OOR — must take the next step.
Enforcement
If compliance doesn’t happen voluntarily, the path depends on which kind of agency is involved. For a Commonwealth agency, the requester must file a petition to enforce under Pennsylvania’s appellate procedure rules. For a local agency, the typical path is an action in mandamus — a distinct court petition asking a judge to compel a public official to perform a legal duty, a mechanism confirmed in Pennsylvania case law addressing exactly this gap.
Fig. 1 — Four administrative events, not one. The break in solid connecting lines after Decision marks where OOR’s authority ends.
The Compliance Gap, named directly: a Final Determination can be fully binding, fully final, and completely unappealable — and the records still not exist in the requester’s hands. No further investigation is needed. No further decision is needed. What’s needed is compliance, and if it doesn’t come voluntarily, enforcement — a step the deciding agency has no power to take itself.
Tradeoffs
Multiple institutional reasons this separation exists
Efficiency of voluntary compliance vs. the cost of relying on it
Most agencies do comply once a determination is issued — enforcement litigation is the exception, and a system built to expect voluntary compliance is generally faster and cheaper than one that routes every dispute through court. The tradeoff: “generally” isn’t “always,” and the citizen who lands in the exception bears the full cost of that design choice.
Limited administrative authority vs. protecting agencies from an unchecked adjudicator
A body with both decision-making and direct enforcement power concentrates significant authority with no built-in check. Keeping enforcement in the judiciary means a second, independent institution reviews the matter before compulsion is used. The tradeoff: that protection for the agency is also a second delay for the citizen.
Judicial oversight protecting due process vs. adding a second full proceeding
Requiring court involvement before compulsion ensures a fair, independent hearing before an agency is formally ordered to act under legal force. The tradeoff: a citizen who already won once may need to essentially start a second legal proceeding to actually receive what they won.
Separation of powers as design vs. an ordinary citizen’s expectation of finality
This reflects a coherent, defensible constitutional instinct shared across many areas of government. The tradeoff is squarely about expectation: a citizen using the system for the first time has no way to know this instinct exists, or that it applies to them, until they’re already standing in the gap it creates.
A Practical Note — Not Legal Advice
Because this gap is a structural feature rather than a malfunction, citizens who understand it in advance are generally better positioned to navigate it. Reasonable, non-legal practices worth knowing about: keeping a clear written timeline of the request, appeal, and determination; maintaining professional, documented correspondence with the agency after a determination is issued; allowing a reasonable window for voluntary compliance before assuming enforcement is necessary; and understanding — ideally before it’s needed — that the enforcement pathway differs depending on whether the agency involved is a Commonwealth agency or a local one. For any specific situation, consulting a licensed attorney is the appropriate next step, not a substitute for it.
Reflection
Better questions, not a conclusion
What does “final” actually mean, administratively? Is a Final Determination the end of a process, or the beginning of a different one — and does the word “final” itself contribute to the assumption this exhibit opened with?
Why might a government intentionally separate the power to decide from the power to compel? Having seen the same shape in six other Systems Hall exhibits — a department investigating its own officers, a prosecutor deciding whether to charge the institution it depends on, an arbitrator’s ruling with no guaranteed path to enforcement — does this recurrence change how you’d read any single instance of it?
Administrative literacy changes expectations — but should the system require that literacy in the first place? Is it reasonable to expect an ordinary requester to know, in advance, that winning and receiving are different events?
This exhibit’s Compliance Gap is a close cousin of this collection’s capstone finding — that no single actor is responsible for the coherence of a citizen’s whole experience. Here, the OOR did its job completely; a court, if needed, would do its job completely. Does knowing that make the space between them feel more or less like something that should be fixed?
You don’t have to answer these to have gotten something real from this exhibit. The goal was never agreement — yours or the museum’s. It was making sure that whatever conclusion you reach, you’re standing on the actual architecture rather than a guess about it.
Visitor Takeaway
Winning an administrative decision and receiving its practical benefit are two different events, decided by two different kinds of authority. Understanding that gap — not distrusting the system, but reading it accurately — is what separates surprise from preparedness the next time a “final” decision turns out to be the start of a second process.
Related Systems Hall Exhibits
Sources & Further Reading
- Pennsylvania Right-to-Know Law, 65 P.S. § 67.101 et seq. (enacted 2008, effective 2009)
- Pennsylvania Office of Open Records, “Citizens’ Guide to the Right-to-Know Law”
- Pennsylvania Office of Open Records, “Post-Final Determination” guidance
- Pa. R.A.P. 3761(b), Enforcement of Final Determinations of the Office of Open Records
- Capinski v. Upper Pottsgrove Township, 164 A.3d 601 (Pa. Commw. Ct. 2017)