DD Form 1532 occupies a particular place in Defense recordkeeping. Its title is Pest Management Report, and it exists to Pest Management Report. What the DD prefix records is an administrative judgment made long before your copy was printed: this transaction was determined to be common to the whole Department rather than peculiar to one service, and so the documentation of it was standardized at Department level.
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.
The edition in force is not stated, carried by the publisher as not stated, and edition discipline is stricter on a Department form than most people expect, precisely because supersession happens everywhere at once. There is no interval during which one service still works from the previous layout while another has moved on.
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.
Before the first entry, compare the date printed on the form face with not stated. This is not bureaucratic fussiness. Editions change field numbering, and a receiving office working from the current layout may look for information where your copy does not put it. On a Department form the exposure is wider than usual: your record may be reviewed by an office in another service entirely, one with no reason to remember what the previous edition looked like.
Fill all of it, marking inapplicable items N/A. A record with gaps cannot later demonstrate whether the gap was a decision or an oversight, which is exactly the ambiguity documentation exists to remove. Dates go in the form's own format — on a document that crosses service lines, an ambiguous date is a real hazard rather than a pedantic one.
Understand what the Privacy Act Statement is doing on the page. It exists because collecting personal data from an individual triggers a duty to explain the collection: under what authority, for what purpose, to whom the information may routinely go, and whether you are obliged to answer. That explanation precedes the fields for the obvious reason — afterwards it is merely a notice, beforehand it is a basis for deciding.
What the signature block asks for is an act, not a text. Ink on a printed copy performs that act; a digital signature bound to your credential performs it electronically, CAC-based in most Defense systems. Typing your name performs nothing, since anyone with the file could type the same characters. Enter the date at the same moment: the certification is a statement about a point in time and needs one recorded.
The defects that return forms are the same ones year after year: a superseded edition, required fields left blank, handwriting that fails on reproduction, dates in a convention the form did not ask for, and certification without a signature or without a date. Where a specific field is genuinely unclear, the instructions printed on the form come first and not stated governs where the two do not agree.
Download the form
What you can download: PDF. The form runs 1 pages and asks for approximately 73 entries. The plurality of formats is deliberate: Defense distribution has never been able to assume one operating environment across the whole force.
Fillable and printable are not two presentations of one file but two different objects. One holds your entries as structured data within the document; the other is a static picture meant to meet a pen. Since a DD form frequently moves outside the organization that created it, the durability of the entry matters more here than on a record that stays in one drawer. Typed text reproduces indefinitely; handwriting degrades at every copy.
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.
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.
What the form asks for
- ADN
- BlBlock4title
- Block1A
- Block1B
- Block1C
- Block1D
- Block1E
- Block1F
- Block1G
- Block1H
- Block1I
- Block1J
- Block1K
- Block1L
- Block1M
- Block1Section
- Block1title
- Block2A
- Block2B
- Block2C
- Block2D
- Block2E
- Block2FSUB
- Block2G
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.
Cross-referenced documents are found by series and number, with nothing further required. That the DD sequence is unified across the Department means a cited number identifies one form and no other, which is the practical payoff of centralizing the numbering in the first place.
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.
A form is downstream of the policy that requires it, and revision usually starts there: a directive is reissued, a collection requirement is altered, notice language is updated by statute. The form is republished as a consequence. Since none of that reaches individual users, an archived copy quietly becomes wrong, and verifying not stated each time you download is the whole remedy.
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 1532?
- Pest Management Report
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?