Administrative documents are written for readers who were not present, and DA Form 7338-R is no exception. Titled TOW GUNNERY TABLE 9: SECTION GUNNERY PRACTICE, it is used to tow gunnery table 9: section gunnery practice — a transaction that means little in conversation and a great deal in a file. The published edition here carries the date August 2003 and the status not stated. Its 1 page(s) and roughly 174 fields are sized to what the record must prove years later, which is always more than the moment appears to need.
Two offices stand behind the form, and the distinction between them explains most of what follows. TRADOC is the proponent: it decides what the form asks and revises it when the underlying process changes. FM 3-22.34 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.
Retrieval governs the order of entry. The head of the form takes name, identification number, unit and date, and those values become the handles by which the record is found later — the substantive blocks are never searched on. This is why the spelling must match official records exactly rather than approximately.
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.
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
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.
There is no charge and no sign-up. Published documents are distributed as published, without modification.
What the form asks for
- BATTALIO
- COMPANY
- CREWA
- CREWB
- CREWC
- CREWD
- CREWE
- ContentArea1
- DATE
- DVRA
- DVRB
- GNRA
- GNRB
- LDRA
- LDRB
- PLATOON
- POINTA
- POINTB
- POINTC
- POINTD
- POINTE
- POINTSA
- POINTSB
- POINTSC
Where the signed form goes is settled by FM 3-22.34 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 TRADOC or your servicing administrative office.
Questions and answers
- What is DA Form 7338-R?
- TOW GUNNERY TABLE 9: SECTION GUNNERY PRACTICE
- Which edition is current?
- August 2003
- Who is responsible for this form?
- TRADOC
- In which formats can it be downloaded?
- PDF, XFDL