Can discrepancies in SF-86 submission dates be used as grounds for revocation of a clearance?

The Standard Form 86, the Questionnaire for National Security Positions, asks for extensive personal history, often including dates of events such as employment, residence, foreign travel, and prior offenses. When the dates a person reports do not line up with records, an adjudicator may ask whether the discrepancy is a basis to revoke a security clearance. The short answer is that a date discrepancy can support revocation, but only if it reflects a deliberate falsification or a broader pattern of unreliability. An innocent error in a date, standing alone, is generally not a ground to revoke a clearance.

Why intent is the central question

Security clearance decisions are governed by the Adjudicative Guidelines for Determining Eligibility for Access to Classified Information. The guideline most relevant to false or omitted information on an SF-86 is Guideline E, Personal Conduct. Guideline E is concerned with conduct involving questionable judgment, lack of candor, dishonesty, or unwillingness to comply with rules, and it specifically reaches the deliberate omission, concealment, or falsification of relevant facts from a personnel security questionnaire.

The operative word is deliberate. A discrepancy in a submission date raises a Guideline E concern only if the government can show the applicant knowingly provided a false date. An honest mistake, a lapse of memory about when an event occurred, a typographical error, or a good faith misunderstanding of what the form asked is not falsification. Adjudicators are instructed to consider the possibility of error, and a single wrong date that the person could not plausibly have intended to mislead about will usually not satisfy the deliberate element.

When a date discrepancy becomes serious

A date discrepancy becomes a real basis for revocation in a few recurring situations. The first is when the inaccurate date appears designed to hide something. If shifting a date conceals a disqualifying event, makes a problem look more remote in time, or moves an offense outside a reporting window, the discrepancy looks deliberate and material. The second is when the pattern of errors suggests the applicant was not candid. Multiple inaccurate dates that all happen to favor the applicant can support an inference of intentional misrepresentation, even if any single date in isolation might be explained away. The third is when the applicant’s later conduct shows a lack of candor, such as continuing to insist on a false date after being shown contrary records.

By contrast, a date that is simply off by a small amount, that does not conceal anything disqualifying, and that the applicant promptly acknowledges and corrects is the kind of discrepancy that typically does not rise to a security concern.

Materiality matters

Even a deliberate misstatement is more serious when it is material, meaning it could affect the outcome of the background investigation or the adjudication. A false date that hides a relevant event is material. A trivial date error about something that would not influence the clearance decision is far less likely to matter. Adjudicators weigh whether the discrepancy actually bore on the integrity of the security process or was a meaningless slip.

The whole-person review and mitigation

Security adjudication is not mechanical. Even where a Guideline E concern is raised, the adjudicator applies a whole-person analysis, weighing the seriousness of the conduct, the circumstances, how recent it was, the applicant’s age and maturity, the likelihood of recurrence, and any evidence of rehabilitation. Several mitigating conditions are directly relevant to date discrepancies. The concern can be mitigated when the offense was minor and does not cast doubt on current reliability. It can be mitigated when the individual made a prompt, good faith effort to correct the error before being confronted with the facts. And it can be mitigated when the omission or error resulted from a reasonable misunderstanding or from reliance on bad advice rather than intent to deceive.

The practical lesson is that responding to an alleged date discrepancy with documentation showing the correct date, an explanation of how the error occurred, and evidence of a prompt correction is far more effective than minimizing or disputing the discrepancy without support.

Process protections before revocation

A clearance is not revoked based on a discrepancy without process. The individual is ordinarily given a statement of reasons identifying the concern, an opportunity to respond in writing, and, in many systems, a hearing before an administrative judge with the right to present evidence and explanation. This process is the appropriate place to show that a date discrepancy was an innocent error rather than a deliberate falsehood. The government bears the burden of establishing the disqualifying conduct, and the applicant then bears the burden of presenting mitigation, with any doubt resolved in favor of national security.

The bottom line

Discrepancies in SF-86 submission dates can be used as grounds to revoke a clearance, but only when they reflect a deliberate falsification or a pattern that shows a lack of candor under Guideline E, and the discrepancy is material to the security determination. An innocent, isolated, and promptly corrected date error generally is not a basis for revocation. The decisive factors are intent, materiality, and the whole-person mitigation an individual can present through the statement of reasons and hearing process.

Disclaimer

This article is provided strictly for general educational and informational purposes. It is intended to explain how the Uniform Code of Military Justice (UCMJ), the Rules for Courts-Martial, the Military Rules of Evidence, and related military administrative processes work as a matter of public legal education. It does not constitute legal advice, a legal opinion, or a recommendation about any particular case, and it is not a substitute for advice from a qualified military defense attorney who can evaluate the specific facts and command, service, and jurisdictional circumstances involved.

Reading this article, or contacting any website on which it appears, does not create an attorney-client relationship between the reader and any law firm, attorney, or author. Every court-martial, nonjudicial punishment action, administrative separation, and security-clearance matter turns on its own facts, the charged articles, the convening authority, the service branch, and the evidence, and outcomes vary widely from one case to another.

Military law also changes over time. The Military Justice Act of 2016 (effective January 1, 2019) and subsequent National Defense Authorization Acts renumbered and rewrote many punitive articles, revised the Article 32 preliminary hearing, and altered sentencing, clemency, and appellate procedures. Statutes, regulations, executive orders, the Manual for Courts-Martial, and decisions of the service Courts of Criminal Appeals and the Court of Appeals for the Armed Forces may have been amended, superseded, or reinterpreted after this article was written, and article numbers or procedures cited here may have changed.

For these reasons, no reader should act or decline to act based on this content without first consulting a licensed attorney experienced in military justice about their own situation. The author and publisher make no warranty, express or implied, as to the accuracy, completeness, timeliness, or current applicability of the information provided, and disclaim any liability for any action taken or not taken in reliance on it. If you are facing investigation, charges, or an adverse administrative action, time limits may apply, and you should seek qualified counsel promptly.

Leave a Reply

Your email address will not be published. Required fields are marked *