Background-investigation packetautomation for federalcontract staffing.

A background packet does not come back with a note saying “close — fix line 14.” It comes back. The candidate re-opens the questionnaire, the submission goes to the back of a queue, and the start date moves. For a staffing firm that has already won the seat, that is billable weeks lost to a formatting error.

The frustrating part is what causes it. These are rarely judgment calls about the person. They are mechanical: a two-month residence gap nobody explained, a verifier with no phone number, a signature dated before the release it covers, a name that reads one way on the questionnaire and another way on the declaration, a scan too dark to read.

Every one of those is a check a computer can run before anything is submitted. Almost nobody runs it. That is the whole premise of this system.

The questionnaires are long by design. The SF-85P, the Questionnaire for Public Trust Positions, asks for roughly seven years of history — where the candidate lived, worked and traveled, plus financial, criminal and substance-use background. The SF-86, the Questionnaire for National Security Positions, goes further back still, and the look-back period changes from section to section. Around them sit the employment declarations and supplemental questionnaires that travel with the packet.

We mapped 219 fields across five of those forms. Every field is named, typed, and given a source: read from the candidate’s government ID, carried from their profile, or flagged as something only the candidate can answer. Nothing is guessed. A field the system cannot source honestly is a field it asks about.

The forms overlap heavily — name, date of birth, place of birth, Social Security number, current address all recur. Typed five times, they disagree five ways, and a disagreement between forms is one of the cleanest reasons to bounce a packet. Mapped once, they cannot drift. That is the least glamorous benefit of the field map and probably the most valuable.

The Defense Counterintelligence and Security Agency retired e-QIP on 1 October 2023. Agencies and cleared contractors completed the move to NBIS eApp — the National Background Investigation Services application — and e-QIP is no longer accessible. The SF-85, SF-85P, SF-85P-S and SF-86 are all completed in eApp now.

eApp is a genuine improvement on what it replaced. It validates as you type, checks addresses, and saves as it goes, so the format errors that used to survive to submission mostly get caught at the keyboard.

What it does not do is anything upstream of the keyboard. Somebody still has to assemble accurate, complete, internally consistent information for the candidate to enter, handle the declarations that sit outside the portal, and run the onboarding around it. That work belongs to the sponsoring company, and it is where packets are actually won or lost.

One practical note: if your SOPs, intake emails or candidate instructions still say “e-QIP,” they are pointing people at a login that was switched off years ago. It is a small thing that costs a real day every time a candidate goes looking for the wrong portal.

Filling a form is the easy half. The half that changes outcomes is the re-scan: the system opens the returned PDFs and reads what is actually on the page — not what the application believes it sent — then reports what would get the packet kicked back.

The defects it looks for are mechanical, and every one is fixable:

• Required fields left empty — and fields that were answered but never landed in the returned PDF.
• Gaps in the residence and employment timelines that nobody accounted for.
• References and verifiers with no reachable contact details.
• Dates that contradict each other: an end date before its start date, a signature dated before the release it authorizes.
• Identity fields that disagree between forms — a middle name on one, an initial on another.
• Pages that came back unsigned, undated, or too dark to read.

The output is a work list, not a score. Each item names the form, the field, and what is wrong with it, so a coordinator can clear it in minutes instead of guessing which of 219 fields is the problem.

To be plain about the limit: this predicts mechanical rejection, not adjudication. Whether a candidate is favorably adjudicated is the government’s call, on the merits, and no software controls it. Anyone selling you an approval rate is selling you something they do not own.

Submission is not the finish line, and treating it as one is how firms end up with cleared people who still cannot badge in. A second board tracks every hire from offer through fingerprinting, training and badge pickup — the whole path, on one screen.

• Offer accepted, packet opened.
• Forms filled, reviewed by the candidate, submitted.
• Fingerprinting scheduled and completed.
• Required training assigned and cleared.
• Badge issued and picked up — the point the person can actually start.

Each stage carries a date, an owner and a blocker. The question a staffing lead actually asks every morning — who is stuck, and on what — is answerable in one look instead of five phone calls.

A background packet contains a Social Security number, a date and place of birth, an image of a government ID, and a complete history of where somebody has lived and worked. We treat that as the constraint the system is designed around, not a footnote.

Where the data lives, who can see it, and how long it is kept are deployment decisions. We make them with you, in writing, before the first record exists — and we would rather walk you through the data flow on a call than post a blanket assurance here.

What we will not tell you: that we hold a FedRAMP authorization, an ATO, or any certification beyond the SBA certification we actually hold. We do not, and a vendor claiming a form-filler is “FedRAMP compliant” is usually describing somebody else’s hosting, not the product you are buying.

What we do bring is the practice behind it. Encryption, access controls, credential management, sandboxed execution — built for our own sensitive operations before any client’s.

• Cleared and federal contract staffing firms placing people into public-trust and national-security positions.
• Primes onboarding subcontractor staff, who inherit the packet quality of somebody else’s process.
• Any firm where the start date — not the signed offer — is the revenue event.

It is a poor fit for a firm processing one or two packets a year — a good checklist is cheaper than software — and for anyone who wants a guarantee of acceptance, which nobody can give.

We built this system, we operate it, and we will show it to you running rather than in slides. An SBA-certified Service-Disabled Veteran-Owned Small Business — eligible for federal set-aside and sole-source awards, fluent in government and commercial requirements.