The Clearance Questionnaire Run, From eApp Invite to Interim Decision

This guide is for anyone holding a conditional offer for a cleared or public trust role who has an eApp registration code and a start date that depends on an interim decision. It takes you from the invite to a signed questionnaire that the security office has released, with fingerprints logged inside the 14-day hold and every entry checked against your records and the resume you were hired on. It finishes with a dated tracker that runs until the interim notice arrives.

Most of what ranks for this topic explains the SF-86 one section at a time. That helps, but it is not a sequence of actions, and some pages still describe e-QIP, the system eApp replaced. This guide is the sequence.

Which questionnaire and system does your invite open?

Fill in the form your sponsor's invitation opens, in the system it names, and treat any guide that disagrees as out of date. Most new hires still get the SF-86, SF-85P or SF-85 in eApp. The Personnel Vetting Questionnaire (PVQ) is the replacement form being phased in under Trusted Workforce 2.0, the government's program to overhaul personnel vetting.

Three things are changing at the same time, and each one has tripped people up:

• Form edition. DCSA turned on a revised edition of SF-85, 85P, 85P-S and 86 inside NBIS eApp and then made it mandatory. If a checklist's section numbers do not match your screen, check the edition date printed on the form.
• PVQ rollout. The Trusted Workforce 2.0 quarterly progress report on performance.gov tracks how many PVQs have been collected and the target date for using the PVQ in every vetting scenario. One quarter recorded more than 300 PVQs collected. That is a small number, so the PVQ is still the exception. Check the latest report rather than trusting a figure on a blog.
• Initiation system. Case initiation is moving from NBIS to DISS-JVS, and secondary reports describe a cutoff for new NBIS applications and an NBIS sunset. Ignore the reported dates. The system named in your invite is the one that counts.

The form matters for more than formatting, because the questions differ. The SF-86 asks about all drug use, including marijuana, within the last seven years. The PVQ starts by asking whether you used marijuana or a derivative substance in the last 90 days, and only then asks about your earlier history. Answer the version in front of you, not one you prepared for.

What clocks start running once the questionnaire is moving?

Five clocks control this job. Two of them, a 14-day fingerprint hold and a 120-day validity on prints and signatures, decide whether your first submission is accepted. The employer submits the prints, not you, but if they miss the window your case goes back to the start.

The fingerprint rule is precise. If no fingerprint result is on file, DCSA may hold the request for up to 14 days. After that it flags the request as unacceptable and returns it to the submitting office. Industry guidance says the security office must submit electronic prints within 14 days of the "Received" status date, and DCSA recommends doing it the same day the eApp is submitted. Initial requests need electronic prints. Paper SON 346W hard cards are rejected.

Because both validities are 120 days and the hold is 14 days, timing works as a window rather than a single deadline. Prints taken months before you certify can go stale. Prints taken weeks after release miss the hold. DCSA's advice to take prints at the same time as release, or just before, fits inside both limits.

What records does the ledger need, section by section?

The ledger needs a document behind every month of the last 10 years and a named verifier wherever the form asks for one. The records ledger is a single sheet with one row per period (a residence, a job, a school, a stretch of unemployment), and you type from it into eApp. Building it before you log in is what makes a first-pass acceptance likely.

These are the lookbacks and verifier rules that most often produce gaps:

Sources: the OPM SF-86 form and an Army section-by-section checklist. The foreign travel lookback comes from a national lab's eApp tip sheet, so check it against the wording on your screen.

Pull these records over days 0 to 3:

• Leases or mortgage statements for every residence, so you have full street addresses and move dates
• W-2s and offer letters for every employer, so start and end months come from payroll, not memory
• Transcripts for schools in the lookback
• Passport stamps and travel records for the foreign travel section
• Court dispositions for any police record, including matters you think were expunged or dismissed

A record proves a date. A record lies when it shows a signing date rather than a start date: an offer letter dated two weeks before your first day will stretch the employment row unless you check it against the first pay stub. Where two documents disagree, use the one closer to payroll or the lease term.

Type | From (MM/YYYY) | To (MM/YYYY) | Employer / school / landlord | Full street address (no P.O. box) | Verifier name | Verifier relationship | Verifier phone | Verifier address | Proof document | Resume dates | Application dates | Conflict (Y/N) | Note
Residence | MM/YYYY | MM/YYYY | | | | | | | Lease | n/a | n/a | |
Employment | MM/YYYY | MM/YYYY | | | Supervisor name, title | Supervisor | | | W-2 + first pay stub | MM/YYYY-MM/YYYY | MM/YYYY-MM/YYYY | |
Unemployment | MM/YYYY | MM/YYYY | n/a | | | | | | Benefit letter or bank statement | n/a | n/a | |
Education | MM/YYYY | MM/YYYY | | | | | | | Transcript | | | |

Why must the SF-86 employment history match the resume you were hired on?

Your SF-86 employment history should match your payroll records to the month, and the resume and application the employer already has should agree with both. The security office, the investigator and the hiring team all hold copies of what you said, and a three-month difference between documents raises a question nobody would otherwise ask.

Resume drift is common and usually innocent. You rounded a start date, ended a contract role on the month the project finished rather than the last paycheck, or merged two short jobs at one client into a single line. Those choices are fine in a marketing document. They become a problem when the questionnaire, which follows the W-2s, disagrees with the version the employer screened you on.

Fill the last two ledger columns from the exact documents this employer received:

• The resume version you submitted for this posting, not your base resume or the newest edit
• The employer's application form, which often asks for dates in a different format and may have autofilled them

If you applied through Refolk, the tailored resume for this posting is the version to compare against, because that is the one the hiring team read. Mark every row where the dates differ by a month or more.

When the ledger shows a conflict, the SF-86 follows the records, always. Then decide whether to say anything before you certify:

• Rounding to the year, or a single month either side: usually no note needed, but enter exact months on the form.
• A gap the resume hid, or dates stretched across one: tell your recruiter or security office in one plain sentence before you certify. Investigators will see the gap either way, and it is better that they hear about it from you first.

The run, step by step

The run takes about five candidate days of work, followed by an employer-led release and a tracking period you do not control. Keep this section open while you work.

Notes on the steps where people improvise:

• Step 4. The 8 to 15 hour range is an unverified estimate. Split it across two or three sittings and save often. Do not let a deadline push you to guess a date you could look up.
• Step 5. Signing ends your ability to edit. DCSA's own wording: once you certify your eApp submission, you can no longer change what you entered. Download the archival copy, because you will need it if the form comes back and when the five-year re-submission comes around.
• Steps 6 and 7. Sources disagree on whether the security office releases first or fingerprints first. DCSA advises prints at the same time as release or just before it. Do not argue the order. Ask for the date of each.
• Step 7. The SAC (special agreement check) is the fingerprint check record in DISS, the system the security office uses to manage your case. "SAC closed" means the fingerprint result is back.

How does a first-pass submission go wrong?

Most rejections come from seven predictable errors, and nearly all of them look complete on screen. DCSA's common SF-86 errors guide, written for NBIS eApp entry, says that incomplete or inaccurate information gets the form rejected for corrections, which delays vetting and the hiring timeline. I have read only part of its field-by-field list, so read the full PDF before you certify.

1. Carried-forward data

If you filled out a questionnaire before, eApp pre-fills it. The rows look finished, and that is the danger. DCSA tells repeat applicants to:

• Delete old or irrelevant entries, including residences and employment more than 10 years old
• Fix mistakes from previous investigations
• Update addresses and phone numbers for relatives and "people who know you well"

Check: compare every pre-filled row against the ledger. A pre-filled row proves you once wrote it down. It does not prove it is still correct.

2. Wrong lookback on a police question

Some police record questions cover the last seven years and others ask whether something ever happened. If you apply seven years to an "ever" question and leave out an old or expunged matter, you have made a false negative: an answer that is technically "No" and factually wrong. Check: read the time qualifier in every question and highlight it before you answer.

3. A relative as a residence verifier

OPM's form text bars relatives as residence verifiers. One contractor's customer-specific instruction sheet says a verifier can be a relative or spouse/cohabitant, which conflicts with OPM. Check: follow the OPM wording unless your security office tells you otherwise in writing.

4. Fingerprints taken at the wrong time

Prints taken too early can pass the 120-day validity before the case uses them. Prints taken too late miss the 14-day hold. Check: ask the security office for the SAC date and compare it with the release date.

5. Resume drift

Employment dates stretched on the resume end up conflicting with W-2s. The questionnaire follows payroll, and the employer can see both. Check: compare month and year against payroll documents, not against the resume.

6. Incomplete addresses

DCSA requires a complete street number and address or the entry will be rejected. P.O. boxes are not allowed. APO addresses are only for overseas military or diplomatic facilities. Check: every address row in the ledger has a street number and a street designator.

7. Stale guides

Some pages still describe e-QIP and older form editions, so section numbers and question wording will not match. Check: the system name on your invite and the edition date on the form.

What do you do when the SF-86 is rejected for corrections?

A rejected form comes back to you through the security office, and you fix it in eApp, answer the Yes/No questions again, re-sign and re-release. NIH publishes the sequence, and it applies to anyone using eApp:

1. Log into eApp and read the details of the return
2. Make the corrections in eApp
3. Answer all Yes/No questions again
4. Re-certify and digitally sign the questionnaire
5. Re-release the eApp to the agency

Two cautions about timing. One secondary source reports that each rejection took an average of 12.5 days to resolve. The data behind that figure has not been verified, but the direction is right: corrections take time. I found no official rule on whether the 14-day fingerprint clock restarts when you resubmit. Ask the security office what your SAC date is now, and check that the prints will still be under 120 days old when the corrected form is released.

Not every problem you spot needs the same response. Sort it by how serious it is and whether you have already certified:

How long until the interim decision, and how do you track it?

There is no official answer: DCSA has not published an interim duration measured from eApp release. The interim depends on checks coming back after the case is scheduled, so the most useful thing you can do is make sure nothing sends the case back.

DCSA's FSO guidance says an interim determination is made once the investigation is scheduled and the investigation service provider returns the advanced products to the adjudicators. The criteria listed are:

• Favorable review of the SF-86
• Favorable fingerprint check
• Proof of U.S. citizenship
• Favorable review of local records, if applicable

What the published numbers do and do not tell you

• Preliminary determinations. One secondary site says contractor preliminary determinations averaged under two weeks across a multi-year span. Treat it as a guide, not a promise.
• Investigation phase. One quarter's reported average was 44 days for Secret and 57 for Top Secret. That covers the investigation, not the interim, and it was measured on the fastest 90% of cases. Reporting is moving to all cases, so expect published figures to rise.
• Data quality. A GAO review, reported secondhand, found 86% of agency personnel-vetting timeliness data inaccurate.
• Round-number claims. Ranges like "5 to 14 days Secret, 30 to 60 days TS" are industry estimates with no stated method.

If your start date is set as a fixed number of days after submission, push back. Ask for it to depend on the interim notice instead, and give the hiring team this section as the reason.

The tracker

Log each status with the date you learned it and the source. Most of these you will hear from the security office, not see yourself.

Who is reviewing your release

The person releasing your form shapes how fast problems surface. In Refolk's index of professional profiles, the two security-office roles look very different:

Personnel Security Specialists are concentrated: the top employers in the sample were Deloitte (7), the US Air Force (7) and DCSA (4). Facility Security Officers, the contractor-side role, are spread thin. In a 25-person sample, 6 (24%) had current titles other than FSO, such as CEO or founder, which suggests that at small contractors the person reviewing your form often has another job too.

A missing skill on a profile does not prove the person lacks it. People leave skills off all the time. What the figure does support is a habit: ask for dates in writing rather than assuming someone else is tracking them.

Subject: eApp certified - [Your name] - release and fingerprint timing

Hi [Name],

I certified and signed my [SF-86 / SF-85P / PVQ] in [eApp / DISS-JVS] today, [date], and saved an archival copy.

Could you confirm four things when you have a moment:
1. The date you release it to DCSA.
2. Where and when my electronic fingerprints will be taken, so they land at or just before release.
3. The date the SAC shows closed in DISS.
4. The best way to reach you if anything comes back for corrections.

If a follow-up request arrives, I will answer it the same day.

Thanks,
[Your name]
[Phone]

Before you click to sign, and how to keep it current

Run this checklist before you certify, because certifying is the point after which you can no longer edit. Each item can be checked against the ledger or the screen.

After the interim arrives, keep the ledger and the archival copy together. DCSA's industry continuous vetting program requires an updated PVQ or SF-86 eApp, with releases, every five years. A ledger you keep updated turns that re-submission into an afternoon instead of another week of record pulling, and it avoids carried-forward data problems because you will be checking pre-filled rows against something current. When you move house or change jobs, add the row on the day it happens.

The same ledger is also the honest base for every resume you send after this one. If Refolk builds your resume from your own history, give it the ledger dates so the next tailored version cannot drift from what you certified. Both the next employer's security office and this one may end up holding copies.