Every entry in the Defense records system exists because some decision needed a documented basis, and DD Form 2490-26 is one of those instruments: DD2490-26 NETWORK PLANNING AND CONFIGURATION DATA - NET REKEYING WORKSHEET. This form has not been set up to work with a text-to-speech reader. Contact the Department of Defense Forms Manager for further details if this access is required., created to Network Planning and Configuration Data - Net Rekeying Worksheet. The reason it carries a DD number rather than a service designation is structural — the Department maintains a single body of forms for matters that arise identically in every service, so that a record created in one component remains intelligible in another.
That decision has consequences you will notice. Because not stated prescribes the form for the Department as a whole, and not stated maintains it on the Department's behalf, the same blank passes between the Army, the Navy, the Air Force, the Marine Corps, the Space Force, the Coast Guard when operating under Defense jurisdiction, the defense agencies and the combatant commands without translation. A clerk in one component reads a record created in another and finds the fields where they expect them.
You are looking for edition not stated, listed as not stated. Department-wide supersession is a single event rather than a rollout, which is what distinguishes edition currency on a DD form from the same question on a service publication: nobody anywhere is still accepting the previous version out of habit.
The sequence printed on the form is the sequence in which a reviewer will read it, and the two should agree. Header data frames every entry below it; the substantive fields depend on that frame; the certification stands at the end because its whole function is to vouch for what came before. Entries made out of sequence commonly contradict entries made earlier.
Check the edition date before you type anything, against not stated. Old blanks accumulate in shared drives for years, and the cost of one is not obvious until a reviewer cannot find a field. Because DD forms are revised centrally and replaced across the Department in a single action, there is no component still tolerating the old layout as a local practice.
Unclear entries are resolved from the printed instructions first and from not stated where the two texts diverge.
Download the form
The set published here is PDF, covering 1 pages with roughly unknown fields.
Xfdl appears in the set for reasons of institutional inertia rather than preference. It is the IBM Lotus Forms format, once the Department's electronic forms standard and deployed widely enough that it outlived the decision to move on. IBM Lotus Forms Viewer or an equivalent client opens it; a pdf application will not.
All of it downloads without charge. Where care is needed is in the reader you choose. A fillable pdf depends on field properties that desktop applications honour and browser previews frequently ignore, so work locally rather than inside a browser window.
The completed form goes to the office named in not stated or in local implementing procedure, and it is worth keeping a copy before it goes. On a Department form the destination is frequently outside your own chain — another service, a defense agency, a joint staff — and recovering a document that has crossed an organizational boundary is a slower business than retrieving one from a file down the hall.
When DD Form 2490-26 cites another form, the citation is self-sufficient. The DD series is a single sequence administered at Department level, so the number resolves to exactly one document without any need to establish which component issued it — a convenience that exists only because the sequence was never allowed to fork.
It helps to see the DA and DD sequences as what they are: separate registries with separate custodians. One serves a single service under a service proponent, the other serves the Department under not stated or an equivalent office, and neither was ever indexed against the other. A number that appears in both systems points to two unrelated documents, which is why reading the prefix comes before reading the digits.
Understanding why editions change explains why checking them is not optional. Revision follows directive reissue, changes in what data is required, and amendments to mandatory notice text — decisions made at Department level and communicated through publication rather than notification. The file you saved does not update itself, so the edition date at download is what you rely on.
The role of this page is narrow and worth stating plainly. It makes a published Defense form available and explains its structure. It does not advise, does not interpret policy for your circumstances, and cannot indicate how any office will treat a completed copy — those judgments rest with the authorities that own the process. Direct such questions to not stated, to the administrative office that services you, or to the authority named in not stated.
Questions and answers
- What is DD Form 2490-26?
- DD2490-26 NETWORK PLANNING AND CONFIGURATION DATA - NET REKEYING WORKSHEET. This form has not been set up to work with a text-to-speech reader. Contact the Department of Defense Forms Manager for further details if this access is required.
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?