The reason DA Form 5484 looks the way it does is that a file has to speak for itself. Officially MISSION SCHEDULE/BRIEF, it serves to mission schedule/brief, and the record it produces outlasts the people and the circumstances behind it. Edition 01/01/2006, status ACTIVE, is the version published here: 1 page(s), close to 200 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 G-3/5/7, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by AR 95-1. That division is the reason a form can outlive several changes in the process it serves.
Identification precedes substance for a structural reason. Name, identification number, organisation and date of preparation are how the finished document is located in a file or a database; the body of the form is what someone reads after the search has succeeded. Spell the name as official records spell it, since the search runs against those records and not against habit.
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.
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.
Personal information may not be gathered silently, and the Privacy Act statement is how that obligation is met on paper: it names the collection authority, the purpose, the routine uses and whether disclosure is mandatory. Because it exists to inform a decision, it belongs before the fields it covers rather than after them. A filled copy then holds personal data and is stored and transmitted under the corresponding safeguards.
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.
Downloads are free and unregistered. The material was published for general use, and the files are passed on unaltered.
What the form asks for
- ACR
- ACR_1
- ACR_10
- ACR_11
- ACR_12
- ACR_13
- ACR_14
- ACR_15
- ACR_16
- ACR_17
- ACR_18
- ACR_19
- ACR_2
- ACR_20
- ACR_3
- ACR_4
- ACR_5
- ACR_6
- ACR_7
- ACR_8
- ACR_9
- CREWMEM
- CREWMEM_1
- CREWMEM_10
The routing in AR 95-1 decides where the document goes — a named office, the administrative channel, or the individual's file — and the records schedule for the series decides how long it stays. Neither is a local judgement, because a record system loses its meaning if each office keeps things for its own preferred interval. Copy the form before submitting it.
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.
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.
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-3/5/7 or to the administrative office servicing your unit.
Questions and answers
- What is DA Form 5484?
- MISSION SCHEDULE/BRIEF
- Which edition is current?
- 01/01/2006
- Who is responsible for this form?
- G-3/5/7
- In which formats can it be downloaded?
- PDF, XFDL, PDF
Publisher notes
- 42-ITEM ONLY PRODUCED IN ELECTRONIC MEDIA