Administrative documents are written for readers who were not present, and DA Form 7595-1-1 is no exception. Titled PERFORM A COMBAT CASUALTY ASSESSMENT, it is used to perform a combat casualty assessment — a transaction that means little in conversation and a great deal in a file. The published edition here carries the date May 2014 and the status not stated. Its 1 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.
The form has an author and an occasion, held by different authorities. TRADOC owns the content and reshapes it when what is being recorded changes. TC 8-800 governs the event that calls for the form and the route the finished document takes afterwards. Keeping those two apart is what allows a procedure to be amended without the page being rebuilt each time.
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.
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
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.
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
- ContentArea1
- Date1
- Eval_Comments
- Fail10_a
- Fail10_b
- Fail10_c
- Fail11_a
- Fail11_b
- Fail11_c
- Fail12_a
- Fail12_b
- Fail12_c
- Fail13_a
- Fail13_b
- Fail13_c
- Fail14_a
- Fail14_b
- Fail14_c
- Fail15_a
- Fail15_b
- Fail15_c
- Fail16_a
- Fail16_b
- Fail17_c
Where the signed form goes is settled by TC 8-800 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.
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.
Editions change because the process changes, and the printed edition date is the only marker of which version a page belongs to. A copy saved locally cannot know it has been superseded, so the date on it is compared against the edition in force before reuse. Records already executed under an earlier edition are left alone — a document is read under the terms it was made, and reopening completed files to match a later form would falsify the account.
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 7595-1-1?
- PERFORM A COMBAT CASUALTY ASSESSMENT
- Which edition is current?
- May 2014
- Who is responsible for this form?
- TRADOC
- In which formats can it be downloaded?
- PDF, XFDL