The reason DA Form 7452-9-R looks the way it does is that a file has to speak for itself. Officially SHIELDING SUBSYSTEM CHECKLIST FOR EXISTING FACILITIES (LRA), it serves to shielding subsystem checklist for existing facilities (lra), and the record it produces outlasts the people and the circumstances behind it. Edition 02/01/2002, status ACTIVE, is the version published here: 1 page(s), close to 139 fields, each one present because some later reader will need that fact without being able to ask for it.
Behind any Army form sit two separate decisions. What the document asks is settled by USACE, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by TM 5-690. 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.
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.
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.
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.
There is no charge and no sign-up. Published documents are distributed as published, without modification.
What the form asks for
- BondCir
- BondCir_1
- BondCir_2
- BondCir_3
- BondCir_4
- ContentArea1
- CurrMeas
- CurrMeas_1
- CurrMeas_2
- Date
- DeficetA
- DeficetA_1
- DeficetA_2
- DeficetB
- DeficetB_1
- DeficetB_2
- Facility
- GrndCirc
- GrndCirc_1
- GrndCirc_2
- Inspector
- LocatA
- LocatA_1
- LocatA_2
Where the signed form goes is settled by TM 5-690 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.
Revision follows the process, which is why editions appear without a fixed interval, and the printed date rather than any version number identifies them. Nothing on a stored copy signals that it has aged; the check is manual. Work already completed under a superseded edition stands as filed, because the record was made under those terms and is properly interpreted under them.
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 USACE or your servicing administrative office.
Questions and answers
- What is DA Form 7452-9-R?
- SHIELDING SUBSYSTEM CHECKLIST FOR EXISTING FACILITIES (LRA)
- Which edition is current?
- 02/01/2002
- Who is responsible for this form?
- USACE
- In which formats can it be downloaded?
- PDF, XFDL, PDF
Publisher notes
- 41-ITEM ALSO PRODUCED IN ELECTRONIC MEDIA,