Keeping a Cleared Veteran Between Contract Awards: Bench and Overhead Options

8 min read
There's no single bench rule for cleared staff between awards. Here's who pays the bench time, what security still owes and when to debrief.

Hire veterans who are ready for the job

We turn real military records into clear, civilian resumes so your hiring team can see what each veteran actually did.

Talk to us about hiring veterans

There's no single "bench rule" for keeping a cleared veteran between contract awards. Keep them employed and expect a need, and you can hold them and usually restore access without reinvestigation.

The first part comes from DCSA's January 2025 guidance on managing DISS. It says the contractor "can keep the employee in the SMO without access." The test is a "reasonable expectation" that they'll need access again. The second part is 32 CFR 117.10(i). It lets you give access back "without further investigation" if they stayed in your "continuous employment." They also have to be still eligible, in scope, with no new derogatory information known.

So the clock that matters is payroll, not a fixed number of days. You'll get a copy-ready gap checklist, the limit on each option with its source, and one worked gap.

What goes on our gap checklist?

Copy this into your gap plan. Each row is one step, who owns it, and the rule behind it.

StepWho does itThe ruleSource
1. Decide if you expect they'll need access againProgram manager and FSOThe contractor makes this call, not DCSADCSA DISS guidance, footnote 1
2. Remove access in DISS (not the full debrief in step 9)FSOAccess comes off when the need endsDCSA DISS guidance, break in access, item 1
3. Keep their record in your security office (SMO)FSOAllowed while you expect a future needDCSA DISS guidance, break in access, item 1
4. Keep them enrolled in continuous vettingFSOSF-86 through NBIS eApp every 5 yearsDCSA DISS guidance, break in access, item 1
5. Keep filing SEAD 3 and adverse reportsFSO and the employeeReporting goes on even with access off32 CFR 117.10(i)
6. Give annual refresher trainingFSOStill owed while they sit in your SMODCSA DISS guidance, break in access, item 1
7. Code their hours to the right labor accountProgram manager and financeOnly hours worked bill on a T&M contractFAR 52.232-7
8. Restore access when new work needs itFSONo new investigation if still eligible and in scope32 CFR 117.10(i)
9. Debrief and out-process if the need is goneFSORequired once there's no reasonable expectationDCSA DISS guidance, footnote 3

Can we keep them on payroll when no contract pays for their time?

Yes, but the ended contract won't pay for it. On a time-and-materials contract, FAR 52.232-7 bills rates times "the number of direct labor hours performed." Hours nobody worked on that contract don't bill to it.

So where does the cost go? The FAR doesn't name bench time. But FAR 31.202 bars charging a cost direct if like costs sit in an indirect pool. And FAR 31.203 defines indirect costs as those spread across two or more cost objectives. Read together, unassigned time usually lands in an indirect pool. That's an inference from those two sections, not a FAR rule.

DCAA flags this kind of time for review. Its Contract Audit Manual, chapter 6 (February 2025 edition), calls standby labor a "sensitive labor account." It defines it as idle time, "capability retention, and waiting for special customer security clearance." Auditors test how you code and control that time.

What that means for you: bench time costs real overhead, and an auditor may ask why. Write down the expected need for each person. Which pool it goes in turns on your disclosed practices. So does how long your rates can carry it. Check with your contracts and security team.

Can we move them onto another contract or a proposal?

Often, when another contract or a proposal has work they can do. If another classified contract needs their access, the FSO updates their DISS record. If they're still eligible, DCSA says you "may update" the record "with the appropriate access level."

Unclassified work counts too. A cleared engineer can write a proposal volume or support an unclassified task with access off. Their record stays in your SMO the whole time, as long as you still expect a classified need. Moving them keeps hours on a real charge number. If that work is a SAP, see hiring cleared veterans for special access programs. To staff the other side of a recompete, see how to source cleared veterans during a contract recompete.

What does our security office still owe while they wait?

Taking access off doesn't end your duties. Per the DISS guidance, the FSO keeps doing four things:

  • Continuous vetting: they stay enrolled, with a new SF-86 through NBIS eApp at 5-year intervals.
  • Reports: SEAD 3 and adverse information reports.
  • Training: an annual refresher, the same as anyone with access.
  • The SMO record: you keep the affiliation until a separation action is needed.

The rule itself repeats the reporting duty. 117.10(i) says adverse information "must continue to be reported" even when access "has been administratively terminated." Tell the employee that on the day access comes off. New to FSO duties? Start with facility clearance basics.

Does holding cleared people between awards count as a cache?

Not if they're already eligible and you expect a need. The cache rule is 117.10(a)(5). It says eligibility requests "will not be used to establish a cache of cleared employees."

DCSA scopes that rule in footnote 2 of its DISS guidance. The cache limit is "referring to personnel who do not have current eligibility." Keeping cleared people in the SMO without access "is not considered establishing a cache." That holds "even when an SF 86 is submitted for CV purposes."

Holding a cleared employee you expect to use again is fine. Putting uncleared people in for clearances with no contract need is the cache the rule bars.

When do we have to debrief?

You debrief when you no longer expect them to need access at your facility. DCSA's footnote 3 says you "must debrief" once there's "no longer a reasonable expectation." That's a business call, and nobody hands you a date. A lost recompete with no other classified work in the pipeline is the plain case. When you make it, the DISS guidance lists the steps:

  1. Remove their access in DISS.
  2. Add a separation date to their DISS profile.
  3. Out-process their eligibility record from your SMO.
  4. Give them a security debriefing.

They can stay on your payroll after this. They just leave your security program.

What happens to their clearance if they leave during the gap?

Leaving is a "break in employment," whoever starts it. DCSA says that holds whether the company, the employee or both of you start it. You debrief, add the separation date and out-process them from your SMO.

Their eligibility doesn't end that day. Under 117.10(j)(1), a later employer may give access. The person has to remain eligible, with an investigation still in scope. But some breaks cost the person their eligibility. Then 117.10(j)(2) bars access without "a new eligibility determination by the CSA."

How long a break can run before eligibility is lost is set by DCSA, not by part 117. Check DCSA's current guidance before you promise a returning hire a date. For hiring someone whose break already ran long, see hiring a veteran whose clearance lapsed.

Whoever hires them next follows DCSA's new-hire steps. If that employer expects a need for access, it "may establish an affiliation" with their DISS record. To check a returning hire's status, see how to verify a veteran's security clearance.

What does one gap look like, start to finish?

Here's one gap told by events, not dates. Your own calendar fills in the timing.

  • The day the contract ends: A cleared engineer has no billable classified work. The PM and FSO agree there's a reasonable expectation of access. The FSO removes access in DISS and keeps the SMO record. The engineer hears that reporting still applies.
  • While the bid is out: The engineer writes the technical volume for the bid. Hours go to the charge number your accounting system uses for that work. Idle hours, if any, are coded to the account finance picks. The FSO keeps up vetting, reports and the annual refresher.
  • Award day: If you win, the PM confirms the new contract needs the engineer's access. If you lose and no work fits, the PM and FSO decide the expectation is gone. The FSO debriefs, adds the separation date and out-processes the record.
  • Start on the new contract: The FSO restores access in DISS under 117.10(i). No new investigation is needed, because the engineer stayed employed, eligible and in scope.

The two decisions that cost money are the expectation call and the labor coding. Write both down the day the contract ends.

What to Do Next

Keeping one cleared person through a gap buys you time. The next award may need more people with the same clearance. BMR's veteran talent pool is a good place to look before the start date.

Over 1,000 new profiles are added to BMR every month, and 79,061 resumes have been built on BMR. Reach out to access BMR's veteran talent pool. Line up the next cleared hire before the award lands.

Rules from 32 CFR 117, DCSA's DISS guidance and the FAR, checked November 2026.

Frequently Asked Questions

Can we start a clearance for a new hire before the next contract is awarded?

Only in a narrow case. 32 CFR 117.10(f) allows a request before the start date when the job needs access right away. The need must tie to a classified contract, and 32 CFR 117.3 extends those rules to solicitations. You need a written job commitment, and the candidate must accept the offer in writing. The commitment must say work starts within 45 days of the person getting eligibility. The cache limit in 117.10(a)(5) still applies.

Is a signed debriefing form required when we debrief someone?

No. DCSA's DISS guidance says there is no policy requirement to get a signed debriefing. It also says there are no set elements a debriefing must cover. As a best practice, DCSA encourages sharing the debriefing section of the SF 312.

The employee says they no longer want their clearance. What do we do?

Report it. Under 32 CFR 117.8(c)(5), you report that they no longer want processing or access, and why.

Our new hire was cleared by another agency. Do we request a new investigation?

Usually not. Under 32 CFR 117.10(a)(6), skip a new request if another agency cleared or is processing them. Reciprocity under SEAD 7 is used instead, and you give the new agency the details the rule lists.

Can we keep an employee in DISS who only needs base access or an IT-level check?

Yes. DCSA's DISS guidance says contractors are authorized to keep an SMO affiliation for those employees. But those investigations sit outside the NISP. The government contracting activity funds, submits and manages them, not DCSA.

About the author

Brad Tachi is the CEO and founder of Best Military Resume and a 2025 Military Friendly Vetrepreneur of the Year award recipient for overseas excellence. A former U.S. Navy Diver with over 20 years of combined military, private sector, and federal government experience, Brad brings unparalleled expertise to help veterans and military service members successfully transition to rewarding civilian careers. Having personally navigated the military-to-civilian transition, Brad deeply understands the challenges veterans face and specializes in translating military experience into compelling resumes that capture the attention of civilian employers. Through Best Military Resume, Brad has helped thousands of service members land their dream jobs by providing expert resume writing, career coaching, and job search strategies tailored specifically for the veteran community.

Found this helpful?

Share it.

More in Hiring Veterans