Military Forms Guide

DA Form 7452-6-R — LIGHTNING PROTECTION GROUNDING SUBSYSTEM CHECKLIST FOR EXISTING FACILITIES (LRA)

lightning protection grounding subsystem checklist for existing facilities (lra)

The reason DA Form 7452-6-R looks the way it does is that a file has to speak for itself. Officially LIGHTNING PROTECTION GROUNDING SUBSYSTEM CHECKLIST FOR EXISTING FACILITIES (LRA), it serves to lightning protection grounding 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 200 fields, each one present because some later reader will need that fact without being able to ask for it.

The form has an author and an occasion, held by different authorities. USACE owns the content and reshapes it when what is being recorded changes. TM 5-690 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.

The heading blocks come first because the record is retrieved by them, not read into. Name as official records spell it, identification number, unit, date of preparation — those four are the index, and everything below them is content that only surfaces once the index has done its work. A form filed under a name written casually is not lost in principle, only in practice, which amounts to the same thing.

Tab order is not a convenience feature; it was fixed when the form was built and generally traces the page, so following it produces the sequence the designer intended and leaves fewer gaps than a mouse. Exclusive option groups clear the previous selection because the record is not permitted to hold two contradictory answers. Single-line fields do not wrap for the same reason the layout is fixed: the printed page has to fall in known positions, so text past the field width is cut at the margin even though the screen still shows it whole. Overflow belongs in remarks or on a continuation, where there is room designed for it. And an inapplicable field is marked rather than skipped, since a blank tells a later reader nothing about whether the question was considered.

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.

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.

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

  • AttachNo
  • AttachYes
  • BelowGrade
  • BendRad_N
  • BendRad_Y
  • BondedNo
  • BondedYes
  • Bonded_No
  • Bonded_Yes
  • ConctdN_A
  • ConctdN_B
  • ConctdY_A
  • ConctdY_B
  • Condtion
  • Condtn_A
  • Condtn_B
  • Condtn_C
  • ContentArea1
  • Date
  • Facility
  • Height
  • Inspector
  • InstalN_A
  • InstalN_B

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.

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.

A word on where this page sits. These are reproductions of published Department of the Army documents, made available by an independent site with no official role and no authority to issue forms. The structure described above — proponent, prescribing directive, records schedule — exists apart from this site entirely, which is why nothing written here is legal advice and why acceptance by any office is not something that can be promised. Put questions of entry, requirement or eligibility to USACE or to the administrative office servicing your unit.

Questions and answers

What is DA Form 7452-6-R?
LIGHTNING PROTECTION GROUNDING 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

  1. 41-ITEM ALSO PRODUCED IN ELECTRONIC MEDIA,

Other forms in the series