DD Form 2835 occupies a particular place in Defense recordkeeping. Its title is Program Access Request, and it exists to Program Access Request. 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.
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.
Current edition: not stated, status not stated. Understand why that date is worth attention here. When the Department reissues a form, the replacement takes effect across every component simultaneously, so an older copy is not merely locally out of date — it is out of date in every office that might receive it.
The form is laid out top to bottom in a sequence that reflects how the record will be read, not merely how it was drawn. Identification comes first because everything below it is understood in relation to a named person, unit or transaction; substantive entries follow; certification closes the document because certification attests to what precedes it. Filling out of order tends to produce internal inconsistencies — an entry that made sense before the header was settled and does not afterward.
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.
For an ambiguous field, read the form's own instruction, then not stated, which controls.
Download the form
Formats available: PDF, across unknown pages and about unknown fields. That several formats coexist is a consequence of scale — the Department cannot standardize the software on every desk that needs this form, so it standardizes the document instead.
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.
If you find an xfdl file here, its presence is historical. The format belongs to IBM Lotus Forms, which the Department adopted Department-wide for electronic forms and fielded on a scale that makes wholesale removal slow. You need the matching viewer to open it; ordinary pdf software cannot read the format and will say so unhelpfully.
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.
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.
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.
What you have here is the document and a description of it, which is a different thing from guidance. This page is not an organ of the Department, gives no legal or procedural advice, and makes no representation about the outcome of any filing; the offices that administer the requirement are the only ones positioned to answer that. Applicability, eligibility and procedural questions belong to not stated, to your servicing personnel office, or to the office designated in not stated.
Questions and answers
- What is DD Form 2835?
- Program Access 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?