Every entry in the Defense records system exists because some decision needed a documented basis, and DD Form 67 is one of those instruments: Form Processing Action Request, created to Form Processing Action Request. 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.
This is why the arrangement matters to you rather than only to the archivists. not stated governs the form throughout the Department, with not stated as the responsible office, so the record you create is legible outside your own component. Joint assignments, agency details and cross-service transactions all depend on that: the paperwork does not have to be reconstructed each time it crosses a boundary.
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.
Work down the page in the printed order, and understand why the order exists. The identifying block establishes whose record this is and under what circumstances it arises. The body of the form then answers questions that are only meaningful once that context is fixed. The signature block comes last because a certification signed before the entries are complete certifies nothing.
Verify the printed edition against not stated first. Field structure shifts between editions, and the office that receives your record is reading the current one. That office may sit outside your service, which removes even the informal accommodation you might expect from a colleague who used the old version last month.
For an ambiguous field, read the form's own instruction, then not stated, which controls.
Download the form
The set published here is PDF, covering unknown pages with roughly unknown fields. More than one format survives because the Department serves users under very different conditions, from a desk with current software to a location where a printer is the only reliable output.
The difference between a fillable and a printable pdf is a difference in what the file contains. A fillable release carries an interactive layer: each box is a defined field with a name and a data type, and what you type is stored as data inside the document. A printable release has no such layer — it is an image of the page, and the only place your answers can go is onto paper. The distinction matters downstream, because a Department record often gets scanned and forwarded several times before it reaches its final file, and typed characters survive that chain in a way pen strokes do not.
The xfdl file is a survival from an earlier phase of Defense form automation. Xfdl is the IBM Lotus Forms format, and for a long period it was the Department's standard for electronic forms — fielded broadly enough that it still appears in distribution sets today. It opens in IBM Lotus Forms Viewer or a compatible client and nowhere else; a pdf reader will report it as damaged, which is not a fault in the file.
Nothing here is charged for. Published Defense forms are public documents and distribution carries no fee, in any format. One caution about software: fill the form in a desktop pdf application rather than a browser tab. Browser-embedded viewers implement field behaviour inconsistently, and the failure mode is silent loss of everything you entered.
Submission follows not stated and whatever local instruction supplements it. Make a copy before the original leaves. Department forms travel across organizational lines by design, and the administrative distance that makes them useful is the same distance that makes tracing a lost one difficult.
Forms referenced inside this one are located by number alone, and that simplicity is a direct product of Department-level numbering. Because the DD sequence is maintained centrally and not duplicated by service, a number is a complete address: one number, one document, throughout the Defense establishment.
Where a service form is cited in the same instruction, the two numbering systems should not be read across. DA numbering belongs to the Army and is administered by an Army proponent; DD numbering belongs to the Department and is administered by not stated or an equivalent Department office. The systems developed separately and were never harmonized, so identical digits in each identify two documents with nothing in common. The prefix, not the number, tells you which system you are in.
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.
A word on what this page is. It distributes a published Department of Defense document and describes what the document contains and how it is completed. It is not the issuing authority, does not speak for one, and offers no legal advice; nothing written here determines whether a particular submission will be accepted, because that determination belongs entirely to the office receiving it. Questions of applicability, eligibility or procedure go to not stated, to your servicing personnel office, or to the office identified in not stated.
Questions and answers
- What is DD Form 67?
- Form Processing Action Request
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?