The reason DA Form 200 looks the way it does is that a file has to speak for itself. Officially TRANSMITTAL RECORD, it serves to transmittal record, and the record it produces outlasts the people and the circumstances behind it. Edition 05/01/2013, status ACTIVE, is the version published here: 1 page(s), close to 117 fields, each one present because some later reader will need that fact without being able to ask for it.
Two offices stand behind the form, and the distinction between them explains most of what follows. CIO is the proponent: it decides what the form asks and revises it when the underlying process changes. AR 25-50 is the prescribing authority: it decides when the form is raised at all and where the completed document travels. Content and occasion are separated deliberately, so that a change in procedure does not require redesigning the page.
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.
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.
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.
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.
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
- APD
- AsofDate
- Authority
- Button8
- CHECK1
- CHECK10
- CHECK11
- CHECK12
- CHECK13
- CHECK14
- CHECK15
- CHECK16
- CHECK17
- CHECK2
- CHECK3
- CHECK4
- CHECK5
- CHECK6
- CHECK7
- CHECK8
- CHECK9
- Cassettes
- ContentArea1
- Courier
Where the signed form goes is settled by AR 25-50 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. CIO 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 200?
- TRANSMITTAL RECORD
- Which edition is current?
- 05/01/2013
- Who is responsible for this form?
- CIO
- In which formats can it be downloaded?
- PDF, XFDL, PDF