Every entry on DA Form 3703-R exists because a record system needs it in writing. The form's official title is PRODUCT QUALITY INSPECTION SUMMARY (LRA), and it is raised whenever an office must product quality inspection summary (lra) in a way that survives the departure of everyone involved. Memory does not transfer between assignments; a filed document does. The edition dated 08/01/1978, status ACTIVE, is what stands here, spread across 2 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.
Behind any Army form sit two separate decisions. What the document asks is settled by AMC, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by TB 55-1500-325-25. That division is the reason a form can outlive several changes in the process it serves.
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.
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.
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
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.
There is no charge and no sign-up. Published documents are distributed as published, without modification.
What the form asks for
- ACCEPTD
- ADEQUATE
- AGENCY
- AUTOVON
- CONTRACT
- ContentArea1
- ContentArea2
- DATE
- DEFECT_A
- DEFECT_A_1
- DEFECT_A_2
- DEFECT_A_3
- DEFECT_A_4
- DEFECT_A_5
- DEFECT_A_6
- DEFECT_A_7
- DEFECT_B
- DEFECT_B_1
- DEFECT_B_2
- DEFECT_B_3
- DEFECT_B_4
- DEFECT_B_5
- DEFECT_B_6
- DEFECT_B_7
Where the signed form goes is settled by TB 55-1500-325-25 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.
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.
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 AMC or your servicing administrative office.
Questions and answers
- What is DA Form 3703-R?
- PRODUCT QUALITY INSPECTION SUMMARY (LRA)
- Which edition is current?
- 08/01/1978
- Who is responsible for this form?
- AMC
- In which formats can it be downloaded?
- PDF, XFDL, PDF
Publisher notes
- 41-ITEM ALSO PRODUCED IN ELECTRONIC MEDIA