Every entry on DA Form 5480 exists because a record system needs it in writing. The form's official title is MAINTENANCE REQUEST AND ASSIGNMENT REGISTER, and it is raised whenever an office must maintenance request and assignment register in a way that survives the departure of everyone involved. Memory does not transfer between assignments; a filed document does. The edition dated June 2003, status not stated, 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.
Behind any Army form sit two separate decisions. What the document asks is settled by DCS, G-4, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by AR 750-1. 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.
A signature is what converts entries into a record, which is why it comes last and why an unsigned form remains a draft however complete it looks. Where a reviewing official, an approving authority or a witness also signs, each adds a distinct attestation, and each dates the day of signing rather than the day of preparation — the dates trace the sequence of responsibility. The recurring defects are worth knowing precisely because they defeat that purpose: an empty mandatory field leaves an obligation unmet, transposed identification digits attach the record to nobody, a date with day and month reversed puts events in the wrong order, and entries left in a reused working copy assert facts nobody intended.
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
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.
Where a file opens matters more than it appears to. A browser will display a pdf, but browser viewers were built to read documents, and some accept keystrokes into fields they never intended to store — the entries are gone at tab close, without warning, because saving was never part of what that viewer does. A dedicated reader is built around the file's own structure and keeps what you enter. The xfdl file belongs to a different lineage entirely: IBM Lotus Forms, adopted across Army systems for the routing and signature handling built into it. That is why only the Lotus Forms Viewer reads it.
Downloads are free and unregistered. The material was published for general use, and the files are passed on unaltered.
What the form asks for
- ASS_REQ
- ASS_REQ_1
- ASS_REQ_10
- ASS_REQ_11
- ASS_REQ_12
- ASS_REQ_13
- ASS_REQ_14
- ASS_REQ_15
- ASS_REQ_16
- ASS_REQ_17
- ASS_REQ_18
- ASS_REQ_19
- ASS_REQ_2
- ASS_REQ_20
- ASS_REQ_21
- ASS_REQ_22
- ASS_REQ_23
- ASS_REQ_24
- ASS_REQ_25
- ASS_REQ_3
- ASS_REQ_4
- ASS_REQ_5
- ASS_REQ_6
- ASS_REQ_7
Where the signed form goes is settled by AR 750-1 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.
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.
It is worth being plain about what this page is within all of the above. The files are reproductions of published Department of the Army documents, offered for download by a site with no official standing and no part in issuing anything. That matters because the machinery described here — proponency, prescribing directives, records schedules — runs entirely elsewhere. Nothing written here is legal advice, and no statement can be made about whether an office will accept a given document. DCS, G-4 and the administrative office servicing your unit answer questions of entry, requirement and eligibility, and they are the ones positioned to.
Questions and answers
- What is DA Form 5480?
- MAINTENANCE REQUEST AND ASSIGNMENT REGISTER
- Which edition is current?
- June 2003
- Who is responsible for this form?
- DCS, G-4
- In which formats can it be downloaded?
- PDF, XFDL