Every entry in the Defense records system exists because some decision needed a documented basis, and DD Form 2536 is one of those instruments: DD Form 2536, Request for Armed Forces Participation in Public Events (Non-Aviation), 20160211 draft, created to Request for Armed Forces Participation in Public Events (Non- Aviation). 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.
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.
Every field takes an entry, N/A included. The reason is evidentiary rather than clerical: a completed record is supposed to show what was asked and what was answered, and blank space records neither. On dates, follow the format printed beside the field. Conventions vary between components, and a joint document is read by people who do not share your habits.
Where the form collects personal identifiers, a Privacy Act Statement accompanies it, and its placement is meaningful. The statute requires disclosure at the point of collection — authority, purpose, routine uses, and the consequence of declining — so that the person supplying the information does so knowing what becomes of it. Reading it after you have filled the fields inverts the arrangement entirely.
Signature is the point at which a completed form becomes a certification, and the requirement follows from that. On paper it means ink in the designated block; electronically it means a credentialed digital signature, ordinarily applied with a Common Access Card in software that supports it. A name typed into the signature field is data, not an act — it demonstrates nothing about who entered it. The date beside the signature fixes when the certification was made, which is why a signed but undated block is treated as incomplete.
Recurring defects have a pattern to them, and it is mostly the pattern of a record that cannot be relied on: an edition that does not match, gaps that cannot be interpreted, entries that cannot be read after scanning, dates that could mean two things, and a certification nobody executed. For an ambiguous field, read the form's own instruction, then not stated, which controls.
Download the form
What you can download: PDF. The form runs 2 pages and asks for approximately 40 entries. The plurality of formats is deliberate: Defense distribution has never been able to assume one operating environment across the whole force.
Two states of the same page circulate, and the reason is worth knowing. In the fillable pdf, the boxes are real fields holding real data; in the printable pdf, the boxes are drawings. Where a record will cross components — as Department records regularly do — the typed version is the safer artifact. Each scan, each forwarding, each reproduction costs handwriting a little legibility, and the office that finally files the record is rarely the office that received it first.
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.
What the form asks for
- Section I - Event Data. 1. Specific requirement (i.e., band, marching unit, color guard, tank, etc.).
- 2. Date of event: 4 digit year, 2 digit month, 2 digit day.
- 3. Time of event: from.
- To.
- 4. Title of event (website, if applicable).
- 5. Expected attendance.
- 6. Site of event (park, auditorium, etc.).
- 7. Address of event (street, city, state, zip code).
- 8. Program (describe theme and objective, audience size and civic makeup, and purpose of Armed Forces participation).
- 10. Is there any charge (admission, parking, etc.)? If so, specify.
- 11. Is this event being used to raise funds for any purpose? If yes, specify how funds will be distributed.
- 12. Will all aspects of this event be available to all persons without regard to race, creed, color, gender or national origin? X first box if yes, second box if no.
- Section II - Sponsoring organization data. 13. Name and website of sponsoring organization.
- 14. Is the sponsoring organization a civic organization? X first box if yes, second if no.
- 15. Does the event have the official backing of the local government? X first box if yes, second if no.
- 16.a. Does the sponsoring organization exclude or discriminate against any person based on race, creed, color, gender or national origin? X first box if yes, second box if no.
- 17. Sponsor's representative. a. Name.
- b. Address (street, city, state, zip code).
- d. Alternate telephone number.
- c. Primary telephone number (include area code).
- e. Fax number (include area code).
- f. E-mail address.
- Section VI - Certification. 19.a. Signature of sponsor's representative.
- b. Date signed (4 digit year, 2 digit month, 2 digit day).
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.
When DD Form 2536 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.
Procedures that touch both Department and service processes will cite forms from both sequences, and the coincidence of numbers between them is exactly that — coincidence. An Army proponent maintains the DA series for the Army; not stated or another Department office maintains the DD series for the whole Department. Two independent registries, two independent numbering runs, no correspondence at any value.
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 2536?
- DD Form 2536, Request for Armed Forces Participation in Public Events (Non-Aviation), 20160211 draft
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?