Administrative documents are written for readers who were not present, and DA Form 543 is no exception. Titled REQUEST FOR RECORDS, it is used to request for records — a transaction that means little in conversation and a great deal in a file. The published edition here carries the date 08/01/2010 and the status ACTIVE. Its 1 page(s) and roughly 100 fields are sized to what the record must prove years later, which is always more than the moment appears to need.
Behind any Army form sit two separate decisions. What the document asks is settled by CIO, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by PAM 25-403. That division is the reason a form can outlive several changes in the process it serves.
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.
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.
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
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.
Downloads are free and unregistered. The material was published for general use, and the files are passed on unaltered.
What the form asks for
- ADD_CUST
- ContentArea1
- DATERET
- DATE_A
- DATE_B
- ESTIMATED
- First
- MUSTRETURN
- NAMEADDTEL
- NAMESIG
- NAME_CUST
- PHONENO_A
- PHONENO_B
- Page1
- R59
- R60
- R61
- R62
- R63
- R64
- R65
- R66
- R67
- R68
Where the signed form goes is settled by PAM 25-403 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.
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 CIO or your servicing administrative office.
Questions and answers
- What is DA Form 543?
- REQUEST FOR RECORDS
- Which edition is current?
- 08/01/2010
- Who is responsible for this form?
- CIO
- In which formats can it be downloaded?
- PDF, XFDL, PDF