Reliability Status is the baseline personnel security screening you'll encounter in federal contracting—it's what allows contractor personnel to access Protected A or Protected B information, government assets, or federal worksites. If your team is working on-site at a departmental facility or handling anything beyond public information, you're going to need this. The Supply Manual makes clear that contracting officers must identify and incorporate these security requirements into solicitations and contracts whenever protected information or federal worksites are involved.
How It Works
Reliability Status isn't a quick checkbox exercise. The screening involves a 5-year background check that includes identity verification, mandatory RCMP law-enforcement inquiries via electronic fingerprints, and mandatory credit checks. Additional verifications—out-of-country checks or interviews—may be required depending on what turns up. The whole process can take weeks or even months, which is why experienced contractors start the process early. Don't wait until after contract award.
You can't just apply for this yourself. Only a registered Company Security Officer (CSO) or Alternate Company Security Officer (ACSO) enrolled in PSPC's Contract Security Program can request Reliability Status on behalf of individuals. They submit the TBS/SCT 330-23E Personnel screening, consent and authorization form. Once issued, it's valid for 10 years unless revoked, and PSPC recommends requesting updates at least 6 months before expiry.
The critical distinction: Reliability Status covers Protected A and B information only. It does not authorize access to classified information (Confidential, Secret, or Top Secret). If your contract involves classified material, you'll need to upgrade to a security clearance, which requires an additional form (TBS/SCT 330-60E) and more extensive vetting. Section 3.140 of the Supply Manual requires contracting officers to use the Security Requirements Check List (SRCL) to ensure all necessary security clauses make it into the contract documentation.
Key Considerations
- Timing is everything. Most contracts require Reliability Status to be in place before work commences. Don't assume you can start while screening is "in progress"—you're putting the contract at risk.
- It's individual, not corporate. Each person who needs access requires their own screening. Winning a contract doesn't automatically grant your team access to anything. Plan for this in your staffing and timeline.
- Protected B is everywhere. You might be surprised how many federal contracts involve Protected B information—personnel records, procurement details, draft policy documents. Assume you'll need it unless the solicitation explicitly states otherwise.
- The 10-year validity matters for long-term contracts. If you're on a multi-year standing offer or a contract with options, track expiry dates. Letting someone's status lapse mid-contract creates operational headaches and potential compliance issues.
Related Terms
Security Clearance, Protected Information, Security Requirements Check List (SRCL), Company Security Officer
Sources
- Supply Manual Section 3.135 – Security requirements
- PSPC – Reliability status request process
- Treasury Board Standard on Security Screening
Bottom line: factor security screening into your proposal timelines and resource planning from day one. It's non-negotiable for most federal work, and catching up after contract award rarely goes smoothly.