The reason DA Form 370 looks the way it does is that a file has to speak for itself. Officially REQUEST FOR ALTERATION AND REPAIRS, it serves to request for alteration and repairs, and the record it produces outlasts the people and the circumstances behind it. Edition April 1949, status not stated, is the version published here: 1 page(s), close to 58 fields, each one present because some later reader will need that fact without being able to ask for it.
Behind any Army form sit two separate decisions. What the document asks is settled by OAAA, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by AR 1-21. That division is the reason a form can outlive several changes in the process it serves.
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.
The Privacy Act statement is on the page because collecting personal information requires the collector to disclose the terms first — the authority relied on, the purpose, the routine uses, and whether an answer is required or may be withheld. That order is the point: the statement is read before the entries it governs, since consent given afterwards is not consent. Once completed, the copy is a personal record and carries the handling obligations that attach to one.
Download the form
Why several files for one page? Because the form has to be completed in a headquarters and in places without a workstation, and PDF, XFDL covers both. The fillable pdf holds interactive fields that fix each entry in place and remove handwriting from the equation. The printable pdf is the same layout without those fields, meant for a printer and a pen. Neither is a lesser copy of the other; each answers a condition the other cannot.
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.
No charge and no account apply: these are published documents, and access to them is not something a distributor is entitled to price.
What the form asks for
- ACTIV
- APPR
- Button3
- ContentArea1
- DATE
- ESCOST
- JUSTIF
- NONREIM
- Page1
- R44
- R45
- R46
- R47
- R48
- R49
- R50
- R51
- R52
- R53
- R54
- REQNO
- REQOFF
- REQSIG
- RIEMB
Where the signed form goes is settled by AR 1-21 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.
Series and number are how the DA series signals which documents belong together, and the grouping follows real process boundaries: a shared proponent or directive usually means a shared purpose. A form cited on the face of another is part of that same transaction, and continuation sheets, covers and transmittals complete it.
An edition marks the form at a point in a process that keeps moving, and the date printed on the page is what distinguishes one from another. Since a saved file never announces its own obsolescence, compare its date against the current edition before using it again. Prior executions remain valid: the change applies forward, and a record is read against the edition it was written under.
One boundary should be stated clearly. What is distributed here are copies of published Department of the Army forms; the site is independent, issues nothing of its own, and holds no position in the system it describes. Proponency, prescribing directives and retention schedules operate without reference to it. Consequently nothing here is legal advice and no assurance about acceptance is possible. Questions about a particular entry, a requirement or eligibility belong with OAAA or your servicing administrative office.
Questions and answers
- What is DA Form 370?
- REQUEST FOR ALTERATION AND REPAIRS
- Which edition is current?
- April 1949
- Who is responsible for this form?
- OAAA
- In which formats can it be downloaded?
- PDF, XFDL