The reason DA Form 335-R looks the way it does is that a file has to speak for itself. Officially APPLICATION FOR APPROVAL OF MANAGEMENT INFORMATION REQUIREMENT (LRA), it serves to application for approval of management information requirement (lra), and the record it produces outlasts the people and the circumstances behind it. Edition 12/01/1982, status ACTIVE, is the version published here: 2 page(s), close to 200 fields, each one present because some later reader will need that fact without being able to ask for it.
The form has an author and an occasion, held by different authorities. G-9 owns the content and reshapes it when what is being recorded changes. AR 335-15 governs the event that calls for the form and the route the finished document takes afterwards. Keeping those two apart is what allows a procedure to be amended without the page being rebuilt each time.
Retrieval governs the order of entry. The head of the form takes name, identification number, unit and date, and those values become the handles by which the record is found later — the substantive blocks are never searched on. This is why the spelling must match official records exactly rather than approximately.
Much of the form's behaviour follows from its being a fixed page. Tab order was set at build time along the reading sequence, which is why tabbing catches boxes a pointer passes over. Exclusive groups release one choice when another is made because a record cannot carry two answers to a single question. Single-line fields refuse to wrap because every entry must print where the layout expects it — text beyond the width is lost at the margin, visible on screen to the end. That is what remarks areas and continuation sheets are for. Marking a field that does not apply matters for a related reason: emptiness is ambiguous, and a reviewer reading the file later cannot distinguish an omission from a decision.
The signature is the point at which entries become an assertion someone stands behind, so it follows everything else and its absence leaves a draft. Countersignatures by reviewing, approving or witnessing officials each carry their own weight and are dated at signing, which is how the file preserves the order of responsibility. Seen that way, the familiar errors are not clerical trivia: an unanswered mandatory field, digits transposed in an identification number, day and month reversed, and residue from a reused file each put something false or unresolved into a document that will be relied upon.
Behind the Privacy Act statement is a requirement that anyone asked for personal data be told, in advance, under what authority it is sought, for what purpose, who else routinely sees it, and whether refusal is possible. Reading it after completing the fields defeats its function. And the completed form is itself a personal record from that point on, subject to the handling rules such records carry.
Download the form
Formats exist because completion happens under different conditions, not because anyone wanted variety. The published set is PDF, XFDL. A fillable pdf carries live entry objects, so typed text lands in fixed positions and stays legible whoever reads it later. A printable pdf drops those objects and leaves the page as an image, which is what an office needs where a screen is unavailable and a pen is not. The document itself is unchanged between them; what differs is the circumstance each anticipates.
Software determines whether an entry lasts. A browser viewer is designed for reading, and several will take typed input into fields without any means of writing it back — the text is simply absent when you reopen. A standalone reader handles the form structure properly. The xfdl file is IBM Lotus Forms, carried in Army systems for the routing and signature support it provides, which is why the Lotus Forms Viewer is its only reader.
Downloads are free and unregistered. The material was published for general use, and the files are passed on unaltered.
What the form asks for
- ACT_TAKEN
- ADP
- ADP_1
- AGENCY
- AGENCY_1
- AGENCY_10
- AGENCY_11
- AGENCY_12
- AGENCY_2
- AGENCY_3
- AGENCY_4
- AGENCY_5
- AGENCY_6
- AGENCY_7
- AGENCY_8
- AGENCY_9
- APPROV_BY
- CONFORM
- CONT_SYM
- ContentArea1
- ContentArea2
- DATE_A
- DATE_B
- DIRECTIVE
Where the signed form goes is settled by AR 335-15 rather than by the office holding it — a named recipient, the unit administrative channel, or the individual's own file, depending on why it was raised. Retention likewise belongs to the records schedule for the series, which exists so documents are kept for as long as anyone might need them and no longer. Keep a copy before release; the original serves the file from then on, not you.
Related documents are located by series and number, and the relation is rarely accidental — forms under one proponent or one directive tend to serve steps of a single procedure. Anything the DA series form names on its face normally travels with it, as do the continuations, covers and transmittals the process generates. Assembling them together is what makes the submission a complete account.
Editions change because the process changes, and the printed edition date is the only marker of which version a page belongs to. A copy saved locally cannot know it has been superseded, so the date on it is compared against the edition in force before reuse. Records already executed under an earlier edition are left alone — a document is read under the terms it was made, and reopening completed files to match a later form would falsify the account.
A word on where this page sits. These are reproductions of published Department of the Army documents, made available by an independent site with no official role and no authority to issue forms. The structure described above — proponent, prescribing directive, records schedule — exists apart from this site entirely, which is why nothing written here is legal advice and why acceptance by any office is not something that can be promised. Put questions of entry, requirement or eligibility to G-9 or to the administrative office servicing your unit.
Questions and answers
- What is DA Form 335-R?
- APPLICATION FOR APPROVAL OF MANAGEMENT INFORMATION REQUIREMENT (LRA)
- Which edition is current?
- 12/01/1982
- Who is responsible for this form?
- G-9
- In which formats can it be downloaded?
- PDF, XFDL, PDF
Publisher notes
- 41-ITEM ALSO PRODUCED IN ELECTRONIC MEDIA