Every entry on DA Form 1156 exists because a record system needs it in writing. The form's official title is CASUALTY FEEDER CARD, and it is raised whenever an office must casualty feeder card in a way that survives the departure of everyone involved. Memory does not transfer between assignments; a filed document does. The edition dated June 2015, status not stated, is what stands here, spread across 1 page(s) and about 200 fields — a count that reflects how much detail the receiving system requires, not how much the drafter wishes to give.
The form has an author and an occasion, held by different authorities. DCS, G-1 owns the content and reshapes it when what is being recorded changes. (AR 638-8) 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.
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
Formats exist because completion happens under different conditions, not because anyone wanted variety. The published set is PDF, XFDL. A fillable pdf carries live entry objects, so typed text lands in fixed positions and stays legible whoever reads it later. A printable pdf drops those objects and leaves the page as an image, which is what an office needs where a screen is unavailable and a pen is not. The document itself is unchanged between them; what differs is the circumstance each anticipates.
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
- ACH
- APC
- APDATE
- APPROVER
- ARTILL_A
- ARTILL_B
- BLPS
- CIRCUMST
- CVC
- ContentArea1
- DAP
- DATE
- DEATHDAT
- DIED_IN_mutexcl
- DUTY
- ENEMY_mutexcl
- ENG
- ESS
- GRENADE
- GRID
- GROIN
- HELI_A
- HELI_B
- HMMWV
The routing in (AR 638-8) 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.
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.
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 DCS, G-1 or your servicing administrative office.
Questions and answers
- What is DA Form 1156?
- CASUALTY FEEDER CARD
- Which edition is current?
- June 2015
- Who is responsible for this form?
- DCS, G-1
- In which formats can it be downloaded?
- PDF, XFDL