Every entry on DA Form 3645 exists because a record system needs it in writing. The form's official title is ORGANIZATIONAL CLOTHING AND INDIVIDUAL EQUIPMENT RECORD, and it is raised whenever an office must organizational clothing and individual equipment record in a way that survives the departure of everyone involved. Memory does not transfer between assignments; a filed document does. The edition dated 12/01/2023, status ACTIVE, is what stands here, spread across 1 page(s) and about 200 fields — a count that reflects how much detail the receiving system requires, not how much the drafter wishes to give. A later edition has since been published, which is why this one remains: records executed against it must still be readable in the terms they were written.
Behind any Army form sit two separate decisions. What the document asks is settled by G-4, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by AR 710-4. That division is the reason a form can outlive several changes in the process it serves.
The heading blocks come first because the record is retrieved by them, not read into. Name as official records spell it, identification number, unit, date of preparation — those four are the index, and everything below them is content that only surfaces once the index has done its work. A form filed under a name written casually is not lost in principle, only in practice, which amounts to the same thing.
Tab order is not a convenience feature; it was fixed when the form was built and generally traces the page, so following it produces the sequence the designer intended and leaves fewer gaps than a mouse. Exclusive option groups clear the previous selection because the record is not permitted to hold two contradictory answers. Single-line fields do not wrap for the same reason the layout is fixed: the printed page has to fall in known positions, so text past the field width is cut at the margin even though the screen still shows it whole. Overflow belongs in remarks or on a continuation, where there is room designed for it. And an inapplicable field is marked rather than skipped, since a blank tells a later reader nothing about whether the question was considered.
Signing is the act that makes the document evidence, and until it happens the entries are only a proposal. Additional signatures — reviewer, approver, witness — each stand for a separate judgement, dated when applied so the record shows who accepted what and in what order. The common faults all damage that record in the same way: a blank mandatory field breaks the chain of required answers, swapped digits in an identification number detach the document from its subject, an inverted day and month misplaces it in time, and stale data from a reused copy states things nobody meant to state.
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
The published formats — PDF, XFDL — reflect the range of places a form gets filled in. Where there is a computer, the fillable pdf supplies live fields that keep entries positioned and readable. Where there is not, the printable pdf gives the identical page as flat artwork for pen entry. The distinction is one of setting rather than of authority; the page is the same document in both.
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.
There is no charge and no sign-up. Published documents are distributed as published, without modification.
What the form asks for
- AUTH_A
- AUTH_A_1
- AUTH_A_10
- AUTH_A_11
- AUTH_A_12
- AUTH_A_13
- AUTH_A_14
- AUTH_A_15
- AUTH_A_16
- AUTH_A_17
- AUTH_A_19
- AUTH_A_2
- AUTH_A_20
- AUTH_A_21
- AUTH_A_22
- AUTH_A_23
- AUTH_A_24
- AUTH_A_25
- AUTH_A_26
- AUTH_A_27
- AUTH_A_28
- AUTH_A_29
- AUTH_A_3
- AUTH_A_30
Where the signed form goes is settled by AR 710-4 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.
Forms cluster by series and number for the same reason files do: shared proponency and a shared prescribing directive usually mean a shared process. So a document in the DA series referenced on the face of another is generally part of the same transaction, and continuation sheets, cover sheets and transmittals belong to the package from the outset rather than arriving after a query.
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.
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 G-4 or your servicing administrative office.
Questions and answers
- What is DA Form 3645?
- ORGANIZATIONAL CLOTHING AND INDIVIDUAL EQUIPMENT RECORD
- Which edition is current?
- 12/01/2023
- Who is responsible for this form?
- G-4
- In which formats can it be downloaded?
- PDF, XFDL, PDF
Publisher notes
- DATA REQUIRED BY THE PRIVACY ACT OF 1974