In government, transparency isn’t tested when things are easy.
It’s tested when the public starts asking questions—and the answers don’t come quickly.
In Columbia Borough, that moment has arrived.
And now, there’s a paper trail.
The First Document: A Delay, Not an Answer
On June 2, 2026, Columbia Borough Manager Jack Brommer responded to a Right‑to‑Know request submitted by ColumbiaPA.online.
The request was simple:
- The complete employment contract for the borough manager
- Any draft versions of that contract
- And an additional employee contract
What came back was not the contract.
It was a 30-day extension notice.
In the letter, Brommer cited multiple reasons for the delay, including:
- The need for redactions
- Staffing limitations
- The need for legal review
- The overall scope of the request
A new deadline was set:
July 14, 2026
What That Letter Really Means
Under Pennsylvania law, agencies are allowed to request a 30-day extension in certain cases.
But extensions are not answers.
They are delays.
And while delays can be appropriate in complex cases, this situation raises a critical question:
What is so complicated about releasing a standard employment contract?
Because that’s what this is.
Not an investigative file.
Not years of records.
Not a broad data request.
A contract.
The Clock Is Now Running
Here’s what matters most:
- The borough has already acknowledged the records exist
- They have not denied access
- They have committed to responding by mid-July
That creates a clear line in the sand.
By law, they must now either:
- Release the contract (with redactions if necessary)
- Or formally deny it—with specific legal justification
There is no third option.
Why the Delay Raises More Questions Than Answers
The reasons listed in the extension are broad—and in some cases, questionable.
- “Staffing limitations”?
- “Extent or nature of the request”?
For a single employment contract, these explanations feel out of proportion.
Which leads to the question:
Is this really about logistics—or about control over information?
And Then There’s the Police Chief Contract
At the same time, attention has turned to another issue:
The handling of a contract involving the borough’s new police chief.
Legally, Borough Council—not the borough manager—holds the authority to:
- Hire the police chief
- Approve compensation
- Execute employment agreements
A borough manager may assist in drafting or negotiating—but cannot unilaterally decide or approve terms.
So when questions arise about the borough manager’s direct involvement in shaping that contract, a deeper issue emerges:
Where does administrative support end—and decision-making begin?
A Pattern in the Paper Trail
Individually, each of these developments can be explained.
But together, they form something else:
A pattern centered around control of information.
- A leadership position filled without open competition
- A public contract that has not been released
- A formal delay backed by broad justifications
- And growing questions about who controls key agreements
And at every stage, one consistent theme:
The public is being asked to wait.
Why Transparency Has a Deadline
Right‑to‑Know laws don’t just guarantee access.
They guarantee timely access.
Because information delayed is information diminished.
And when the subject of that delay is public leadership, public compensation, and public authority—
It matters even more.
What Happens Next
All eyes now turn to July 14.
That’s the deadline set by the borough itself.
And when that date arrives, one of two things will happen:
- The records will be released—and the public will finally see what’s inside
- Or access will be denied—and the issue will move to appeal, legal review, and deeper scrutiny
Either way, the next step won’t be quiet.
Final Word
Right now, the public isn’t asking for something extraordinary.
They’re asking for a contract.
A basic document.
A routine request.
A fundamental piece of transparency.
And if something this simple takes this long—
What else hasn’t been shown yet?
