Administrative documents are written for readers who were not present, and DA Form 5662 is no exception. Titled DATA INTERCHANGE SUMMARY, it is used to data interchange summary — a transaction that means little in conversation and a great deal in a file. The published edition here carries the date 09/01/2009 and the status ACTIVE. Its 2 page(s) and roughly 200 fields are sized to what the record must prove years later, which is always more than the moment appears to need.
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-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.
The rules of entry all trace back to the page being fixed in advance. Tabbing follows the order built into the form, which usually matches how the page reads and misses less than clicking. An exclusive group discards the earlier selection because contradictory entries would make the record unusable. One-line fields have no wrap because print positions are predetermined, so an overlong entry displays fully and prints truncated. Longer text goes to the remarks area or a continuation, both provided for exactly that. Where nothing applies, the nil mark is entered — a blank leaves the reader unable to tell a considered answer from a skipped one.
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.
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.
Downloads are free and unregistered. The material was published for general use, and the files are passed on unaltered.
What the form asks for
- APPROP
- ASSETPOS
- COL2A
- COL2B
- COL2C
- COL2D
- COL2E
- COL2F
- COL2G
- COL2H
- COL2I
- COL2J
- COL2K
- COL2L
- COL2M
- COL2N
- COL3A
- COL3B
- COL3C
- COL3D
- COL3E
- COL3F
- COL3G
- COL3H
Where the signed form goes is settled by AR 710-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.
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 G-4 or your servicing administrative office.
Questions and answers
- What is DA Form 5662?
- DATA INTERCHANGE SUMMARY
- Which edition is current?
- 09/01/2009
- Who is responsible for this form?
- G-4
- In which formats can it be downloaded?
- PDF, XFDL, PDF
Publisher notes
- 42-ITEM ONLY PRODUCED IN ELECTRONIC MEDIA