An owner calls the county courthouse asking about a Pennsylvania security guard company license and gets an answer that’s correct but incomplete, because the clerk on the phone is only describing one of two entirely separate approval tracks — and it isn’t the one that determines whether your officers can carry a weapon on post.
Why a Pennsylvania security guard company license means two approvals, not one
Pennsylvania splits security-industry licensing in a way that trips up owners moving in from states where one agency handles the whole thing.
Track one: the business license, through the county court
The underlying business license to operate as a watch, guard, or patrol company in Pennsylvania is issued at the county court level, under the state’s long-standing Private Detective Act from 1953. That means the office you deal with for your company’s basic license to operate isn’t a state public-safety agency at all — it’s the court of common pleas in the county where you’re applying, which is a structure most owners coming from a state-agency licensing model simply don’t expect.
Track two: armed certification, through the State Police
Separately, if any of your officers will carry a firearm on duty, that individual certification — commonly referred to by its “Act 235” designation, formally the lethal weapons training certification — is administered by the Pennsylvania State Police, not the county court. This is a completely different application, a different authority, and a different set of requirements from the business license above.
The two tracks don’t automatically talk to each other. Your company can be properly licensed at the county level and still have an officer working armed without current state certification if nobody separately confirmed that piece — and the reverse is also true, an individually certified armed officer doesn’t substitute for the company itself holding a proper business license in the county where it operates.
Why this specific mistake is so common
Most states put licensing under one recognizable public-safety or licensing board, so an owner who’s operated in several states develops an instinct: find “the” regulator, submit “the” application, get “the” license. Pennsylvania doesn’t reward that instinct, because there genuinely isn’t a single office that owns both pieces. An owner who calls the State Police assuming they issue the general business license gets redirected, correctly, to the county — and an owner who only deals with the county court and never separately checks armed-officer certification can end up with guards on post who are current on the business side and lapsed on the individual side, without anyone flagging the gap until an incident forces the question.
This matters most when you’re expanding into Pennsylvania from another state, or opening a new branch office within Pennsylvania itself, because the county-level structure means the specifics — what a given county court’s clerk’s office actually wants, how they want it submitted — can vary by county in ways that a one-size answer from a national compliance guide won’t capture. A company opening branches in two different Pennsylvania counties in the same year may find the two clerk’s offices handle intake differently enough that a checklist built from the first county’s experience doesn’t transfer cleanly to the second, which is one more reason to confirm locally each time rather than assuming statewide consistency.
The scenario that actually plays out on post
Picture the sequence that creates the gap in practice. A company opens a branch in a new Pennsylvania county, gets the business license squared away with the local court, and starts staffing an armed post for a client who specifically wants armed coverage overnight. The officer originally assigned holds current Act 235 certification. Six months in, that officer transfers to a different post, and a field supervisor fills the armed post with someone else on short notice — someone who is a fully licensed, capable officer, but whose own individual armed certification lapsed months earlier without anyone cross-checking it against the specific post’s requirement before the shift started.
Nothing about the company’s business license changes in that moment. The county-level approval is still current. What’s wrong is invisible at the company level and only visible if someone checks the individual officer’s certification against the specific post they’re being assigned to, which is exactly the check that gets skipped when scheduling is handled as “who’s available” rather than “who’s available and currently certified for this specific post’s requirements.”
Building this into your expansion checklist
If Pennsylvania is a new market for your company, treat the two tracks as two separate project items with two separate owners inside your compliance process, not one task called “get licensed in PA.” Confirm the current county-level business license requirements directly with the court of common pleas in the specific county where you’ll be operating, since requirements and procedures can vary by county and change over time. Separately and independently, confirm current State Police requirements for any officer who will be armed on a Pennsylvania post, and track each individual officer’s certification status the same way you’d track any other credential with a currency that can lapse. Add both tracks to your written evaluation checklist for entering any new state, not just Pennsylvania.
Neither of these steps should be treated as a one-time box to check at company formation. County requirements and state certification rules are both subject to change, and an officer’s individual certification status needs the same ongoing tracking you’d apply to a driver’s license or a first-aid card — something a scheduling system can help flag before it lapses, rather than after an officer shows up to a post without current credentials. Keeping that status visible in the guard app each officer carries makes it a routine check instead of a surprise.
Verify before you commit
Nothing here should be treated as a complete statement of what Pennsylvania requires — fees, specific procedural steps, and timelines are not addressed above on purpose, because they vary and change, and restating them with false confidence would be worse than not stating them at all. Confirm current business licensing requirements with the court of common pleas in your specific county, confirm current armed-certification requirements with the Pennsylvania State Police, and have both reviewed by counsel familiar with Pennsylvania’s private security statute before you open a location or put an armed officer on post. This article is not legal advice.
If you want to see how credential and certification tracking works for officers across multiple posts, explore CGuardPro or get in touch.