If your contract involves accessing government information classified as Protected B or higher, you'll need to verify that your contractor's personnel hold the appropriate security clearances before you award. This pre-screening requirement catches many vendors off guard—especially those new to federal contracting—because the timeline for obtaining clearances can significantly delay contract start dates.
How It Works
The Supply Manual Chapter 6 makes it clear: contracting officers must ensure security requirements are identified in contract files and that contractors understand what's required. Here's the thing: you're dealing with three levels of personnel screening—Reliability Status, Secret, and Top Secret—and which one you need depends on the sensitivity of information or assets your contractor will access.
Security Requirement Check Lists (SRCLs) determine the clearance level. SRCL #1 applies when contractors need access to Secret or Top Secret information or assets. SRCL #2 covers contracts requiring access up to and including Protected B. Most contracts requiring security screening fall under SRCL #2, where Reliability Status serves as the baseline. The Contract Security Manual specifies that screening must be initiated before granting any access to protected or classified information. Not during onboarding. Before.
Processing times vary wildly depending on the clearance level. Reliability Status typically takes 2-4 weeks, but Secret and Top Secret clearances can stretch months—sometimes six months or longer if background checks hit complications. You'll work with the Contract Security Program within PSPC or the relevant departmental security officer to coordinate the screening. For bidders, this means factoring clearance timelines into their proposals. For you as the contracting officer, it means building these timelines into your procurement schedule and being explicit about requirements in your solicitation documents.
Key Considerations
- Timeline planning is non-negotiable. If you're running a competitive process and the successful bidder doesn't hold the required clearances, you're looking at weeks or months before contract start. Build this into your project schedule from day one.
- Not all personnel need the same level. Your SRCL determines who needs what clearance based on their specific duties. An employee accessing Protected B financial data needs different screening than someone handling Secret intelligence assessments.
- Clearances aren't transferable between departments. A contractor with Secret clearance from DND may still need additional screening for your SSC contract, depending on departmental security protocols and the specific nature of the work.
- Pre-qualification can save you time. Some departments maintain pre-qualified vendor lists where security screening is already complete. Check if this exists for your procurement category before launching a full competitive process.
Related Terms
Security Requirement Checklist (SRCL), Protected Information Classification, Contract Security Program
Sources
- Supply Manual - Chapter 6 - Security and Intelligence
- Standard Acquisition Clauses and Conditions Manual - Security Requirement Checklists
- Treasury Board Policy on Government Security
Bottom line: identify your security requirements early, communicate them clearly in your solicitation, and build realistic timelines that account for screening delays. Your project schedule will thank you.